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
Given that tree, all dependencies get hoisted to the root when installed in both cases, but c and d end up resolving to different versions in each case.
Fix: npm/cli#3933
Previously, installing a tree that causes peerSets to be pruned would
cause an infinite loop when done inside a workspace. This patch stops
that check if the entryEdge is a workspace, the same as being done if it
were the project root.
This patch also adds some incorrect tests that were discovered when
debugging this, and will be fixed in the future (#347 #348).
Fix: npm/cli#3933
Previously, installing a tree that causes peerSets to be pruned would
cause an infinite loop when done inside a workspace. This patch stops
that check if the entryEdge is a workspace, the same as being done if it
were the project root.
This patch also adds some incorrect tests that were discovered when
debugging this, and will be fixed in the future (#347 #348).
PR-URL: #343
Credit: @lukekarrysClose: #343
Reviewed-by: @isaacs
fritzy
changed the title
[BUG] different peerSets installed in root vs workspace
[BUG](arborist) different peerSets installed in root vs workspace
Jan 20, 2022
What / Why
A tree with a conflicting peerDependencies ends up with different versions when installed in the root vs a workspace.
How
Current Behavior
Given that tree, all dependencies get hoisted to the root when installed in both cases, but
c
andd
end up resolving to different versions in each case.Steps to Reproduce
Installed in the root
arborist reify --add="@lukekarrys/workspace-peer-dep-infinite-loop-a@2"
npm ls --all
package-lock.json
Installed in a workspace
npm ls --all
package-lock.json
Expected Behavior
I think in the second example when installing in a workspace,
c@2
andd@2
should be installed.References
npm/arborist#343
The text was updated successfully, but these errors were encountered: