You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When automatically addiing peerDependencies to the built package.json files for publishable libs, some top-level dependencies can be missing if they are also dependencies of other dependencies.
Expected Behavior
All top-level dependencies are included in the peerDependencies section of the built package.json, even if they are also dependencies of other dependencies.
GitHub Repo
No response
Steps to Reproduce
With publishable Angular libs where:
`lib-a` imports from `lib-b` and also from npm package `@external/package`
`lib-b` imports from npm package `@external/package`
After running nx run lib-a:build, the dist package.json file for the lib does not contain @external/package in the peerDependencies, even though lib-a imports from it.
This issue has been automatically marked as stale because it hasn't had any recent activity. It will be closed in 14 days if no further activity occurs.
If we missed this issue please reply to keep it active.
Thanks for being a part of the Nx community! 🙏
Current Behavior
When automatically addiing peerDependencies to the built package.json files for publishable libs, some top-level dependencies can be missing if they are also dependencies of other dependencies.
Expected Behavior
All top-level dependencies are included in the peerDependencies section of the built package.json, even if they are also dependencies of other dependencies.
GitHub Repo
No response
Steps to Reproduce
With publishable Angular libs where:
After running
nx run lib-a:build
, the dist package.json file for the lib does not contain@external/package
in the peerDependencies, even thoughlib-a
imports from it.Nx Report
Failure Logs
No response
Operating System
Additional Information
Same as #14513 which fixed the issue in
@nx/workspace
(which is what the Angular package builder used back in nx 14) - however, it seems out the affected buggy code is duplicated in the@nx/js
pacakge as well, and the Angular builder delegates to that package now.The text was updated successfully, but these errors were encountered: