PNPM install does not differentiate between optional and required peer dependencies in installed packages

[anantoghosh]

I see that when installing a package which defines optional peer with peerDependenciesMeta, pnpm does not treat it as optional.

For example, in the package @emotion/react, https://github.com/emotion-js/emotion/blob/2d3d7dd1d8b0de9dbfd50e42ee716ac00fb70ecd/packages/react/package.json#L41 @babel/core is optional,

But pnpm shows

It even throws an error if strict-peer-dependencies is enabled.

Using pnpm 6.32.3 on windows. I do not know if this behaviour has been changed in v7.

I think two changes are needed here:

• If a dependency is marked as optional, I believe the cli should display it differently.
• Second, strict-peer-dependencies should not throw an error in such cases.

Note both yarn 2+ and npm does not show any information at all about the missing optional dependencies.

[anantoghosh]

I realize now that for the @emotion/babel-plugin, @babel/core is not optional. Then should @emotion/react declare @emotion/babel-plugin in optionalDependencies? would that be reported by pnpm correctly then?