Tweak documentation/comments/organization to mention npm workspaces #530
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
bmish
force-pushed
the
npm-workspaces
branch
from
e533ed6
to
56b39b0
Compare
|
you should update this to explain that npms nohoist === npm i --install-strategy=nested |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
nohoistis supported by Yarn, but not supported by npm.workspacestype fromYarnConfigurationtoPackageJsonStandardsince it's supported by both npm and yarn now. There should be no behavior change from the resultingPackageJsontype. TheYarnConfigurationtype has a potentially breaking change but I'm not sure that's considered a public type?Fixes #510 (although nothing was actually broken to my knowledge, the resulting
PackageJsontype is the same).Follow-up to the original change to add
workspacesin #77.