-
Notifications
You must be signed in to change notification settings - Fork 3.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Local path peerDependencies
behave like dependencies
#7171
Comments
This is an issue in
|
This issue can be resolved by using --install-links during npm install. Eg: npm i --install -links. --install-links option helps in installing the local dependenciesas packages instead of creating a symlink in the node_modules of app-package. Ref: https://docs.npmjs.com/cli/v8/commands/npm-install |
That worked for me! There's no documentation about using That said, why should |
No argument in this case is equivalent to true. |
Is there an existing issue for this?
This issue exists in the latest npm version
Current Behavior
App depends on Lib. Lib has a peerDependency on
jsdom
.I believe App's
jsdom
stack traces should come fromapp-package
becausejsdom
is a peerDependency oflib-package
. That is not the case:Explicitly adding
jsdom
as a dependency toapp-package
makes no difference.Expected Behavior
Steps To Reproduce
cd local-path-peer-dependencies-reproducible
./setup.sh
./npma.sh run exec
This is related to #5108
Environment
The text was updated successfully, but these errors were encountered: