autoInstallPeers different behavior for developed vs consumed packages

[8ctavio]

Hi,

During development, I'd like for package.json's peerDependencies to be always automatically installed without adding peerDependencies to devDependencies. This way, peerDependencies is basically equivalent to devDependencies during development; peers could also be saved as devDependencies in the lock file.

However, for installed/consumed packages, I'd like to manually install their peers.

With autoInstallPeers I think only one or the other is possible, but it seems that the behavior of peer dependencies could be handled differently for developed/local and external packages.

This would likely require a new configuration option (like autoInstallPeersDuringDevelopment, but shorter) to also support adding peers with pnpm add --save-peer without saving to devDependencies. In addition, pnpm outdated could also show peers if the option is enabled.

Another alternative is to split the options into: autoinstallDirectPeers and autoinstallTransitivePeers, although I'm not sure if that's accurate.