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
{{ message }}
This repository has been archived by the owner on Jul 23, 2024. It is now read-only.
By default NPM 8 workspaces symlinks every packages linked in the root package.json. Nuanced functionality is discussed as RFCs (however, the unanswered questions section of this RFC is only just opening the question we're looking to implement here "Is it reasonable that a workspace with a dependency on a sibling workspace should always resolve to its sibling?")
Options
Alternative package manager e.g. pnpm to specify when to link locally or not as config
Limiting use of OOTB npm workspaces and using lerna link and scripts to manage nuanced requirements
Considerations
NPM 8 functionality is OOTB
Lerna doesn't require changing much npm 8 functionality
pnpm will totally replace npm 8 workspaces and lerna, but requires extra setup
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Problem
By default NPM 8 workspaces symlinks every packages linked in the root
package.json
. Nuanced functionality is discussed as RFCs (however, the unanswered questions section of this RFC is only just opening the question we're looking to implement here "Is it reasonable that a workspace with a dependency on a sibling workspace should always resolve to its sibling?")Options
lerna link
and scripts to manage nuanced requirementsConsiderations
The text was updated successfully, but these errors were encountered: