-
Notifications
You must be signed in to change notification settings - Fork 604
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
[rush] strictPeerDependencies is not enforced for monorepo packages #1865
Comments
Here's an example: https://github.com/dfee/rush-issues/tree/peer-deps You'll notice that |
Thanks for reporting this. Looks like this is an issue. @D4N14L - this will probably be fixed by the workspaces work that you're doing. Can you explicitly test this? |
Closing out, this is resolved when using PNPM workspaces (see #1938) |
This is closed, though it still doesn't seem to work. The docs also doesn't tell more about how to actually get it working. My config:
|
This is intentional. The feature is still experimental. However, if you would like to try it out, it can be enabled by setting: "pnpmOptions": {
"useWorkspaces": true
} |
Please prefix the issue title with the project name i.e. [rush], [api-extractor] etc.
Is this a feature or a bug?
Please describe the actual behavior.
If you've got @mono/package-a that has a peerDependency on
foo
, you can install it into another project @mono/package-b (whilestrictPeerDependencies=true
and you won't get an error.If the issue is a bug, how can we reproduce it? Please provide detailed steps and include a GitHub branch if applicable. Your issue will get resolved faster if you can make it easy to investigate.
What is the expected behavior?
If this is a bug, please provide the tool version, Node.js version, and OS.
The text was updated successfully, but these errors were encountered: