why dev dependecies in local package node modules installed ??

[syi0808]

I want to share an instance of next-i18next.
For example, There are 'package a' and 'package b'.
'package b' is just build react component and component in 'package b' use next-i18next but it hasn't next-18next provider (react conext api).
'package a' has next-i18next provider and it should use component in 'package b' with monorepo.
So i add 'package b' in package.json.

package.json for 'package.a'

  ~
  "dependencies": {
    "packageB": "*" ,
    "next-i18next": "~"   
  },
  ~

package.json for 'package b'

  ~
  "dependencies": {
    "lodash": "~"
  },
  "devDependencies": {
    "next-i18next": "~"  
  },
  "peerDependencies": {
    "next-i18next": "~"  
  }
  ~

.yarnrc.yml

nodeLinker: pnp

yarnPath: .yarn/releases/yarn-3.3.0.cjs
nmHoistingLimits: workspaces

I think install only lodash in package/packageA/node_modules/packageB/node_modules. because lodash is dependency and next-i18next is dev dependency.
But, reality is installed lodash and next-i18next.
So, import 'next-i18next' in 'package b' is not find module in package/packageA/node_modules but it find module in package/packageA/node_modules/packageB/node_modules.

How can i do ??