dependencies are ignored in pnpm8 if they are declared as optional dependencies at same time.

[Mister-Hope]

Here is an example package:

{
   "name": "packageB",
  "dependencies": {
    "packageA": "1.0.0-beta.1",
  },
  "peerDependencies": {
    "packageA": "1.0.0-beta.1"
  },
  "peerDependenciesMeta": {
    "packageA": {
      "optional": true
    }
}

Package A is kind of plugin, but it's in beta stage, so if users manually adds pluginA and set something himself, he should install the same version packageB is using when installing packageB

In pnpm7, this feature is working as expected, as pnpm will give warning if the version mismatches.

However, in pnpm8, the packageA is just not installed, I am not sure but I believed this behavior is related to https://github.com/orgs/pnpm/discussions/6329, where pnpm8 disallows a package to have same package as deps and optional peer, which differs with npm and yarn behavior.

I hope someone in official team can explain some details why pnpm choose this behvaior.