PeerDependencies are not passed through to remote if shell is not using it

[Kawachen97]

With what library do you have an issue?

native-federation

Reproduction of the bug/regression with instructions

Hey,
we are using a package that needs some peerDependencies to work properly. Our shell is not using the components that need the peerDependency. We don't know which of those peerDepenencies will be needed by the remote and therefor also don't know which of them to install. We also want to prevent installing and sharing all of them. On startup, native-federation fails, while resolving the dependencies, which are declared as peer:

As a workaround we are now skipping those subpackages in the federation.config:

Expected behavior

My expectation would be, that those peerDependency constraints are passed through to the remote.
If the remote needs them, it can install them and if not, then not.

Versions of Native/Module Federation, Angular, Node, Browser, and operating system

NativeFederation: 18
Angular: 18

Other information

No response

I would be willing to submit a PR to fix this issue

• Yes
• No