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
Peer dependencies not getting installed in PNP mode with workspaces #7014
Comments
It shouldn't, hence why it doesn't 😛 Add P as a devDependencies entry to install it locally. |
@arcanis Silly me, I updated the question. I have added Error:
|
Hm that's weird - would you have a repro repo, by any chance? |
Or if you can open a PR to add a failing test to |
@arcanis Its specific to yarn workspaces I think. Here is the repro — |
Getting the same (or similar) error. We're trying to use an external dependency that doesn't specify "react" as a peer dependency (but tries to import it), but it fails even if our top level package has "react" in its dependency list.
|
Still seeing this! And I'm trying to use install-peers-cli which is not found! |
Do you want to request a feature or report a bug?
bug
What is the current behavior?
Peer dependencies don't get installed in workspaces.
Refer: https://github.com/tusharmath/pnp-peer-dep-repro
If the current behavior is a bug, please provide the steps to reproduce.
M
inside the workspace, that depends onD
.D
has apeerDependency
onP
.P
as adependency
to my my moduleM
yarn --pnp
Doesn't installP
What is the expected behavior?
yarn --pnp
should installP
Please mention your node.js, yarn and operating system version.
node :
10.7.0
OS: Mac OS
10.13.6
The text was updated successfully, but these errors were encountered: