-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
release/v7.8.0 #3017
Merged
Merged
release/v7.8.0 #3017
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
This adds workspaces support to `npm repo` and `npm docs`. It also updates the usage output to support the -w and -ws parameters output, and cleans up some unneccessary functions in `run-script` and `exec`. PR-URL: #2972 Credit: @wraithgar Close: #2972 Reviewed-by: @nlf
Implements workspaces for set-script, also refactors tests to mock as little as possible. PR-URL: #2998 Credit: @nlf Close: #2998 Reviewed-by: @wraithgar
PR-URL: #3001 Credit: @wraithgar Close: #3001 Reviewed-by: @nlf
This got left out of the npm view workspaces PR
* [#2896](#2896) Provide currentEdge in ERESOLVE if known, and address self-linking edge case. * Add/remove dependencies to/from workspaces when set, not root project * Only reify the portions of the dependency graph identified by the `workspace` configuration value. * Do not recursively `chown` the project root path.
If a user runs 'npm install -w foo bar baz', that won't set 'bar' and 'baz' as workspace names. The correct incantation is 'npm install -w foo -w bar -w baz'. PR-URL: #3016 Credit: @isaacs Close: #3016 Reviewed-by: @wraithgar
Adds workspaces configuration to `docs`, `repo`, and `set-script`. PR-URL: #3013 Credit: @wraithgar Close: #3013 Reviewed-by: @darcyclarke
While it is somewhat helpful to get reports on this, since it indicates an underlying problem in Arborist, it's also very disruptive and unhelpful for users. As of 2.3.0, Arborist gives us the currentEdge if available, so we _can_ report on that at least. If there is no node _or_ edge, then we just don't say what the current state is, which isn't useful, but at least is less annoying than a 'property of null' exception. PR-URL: #3015 Credit: @isaacs Close: #3015 Reviewed-by: @wraithgar
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.
v7.8.0 (2021-04-01)
FEATURES
8bcc5d73f
#2972 feat(workspaces): add repo and docs (@wraithgar)ec520ce32
#2998 feat(set-script): implement workspaces32717a60e
#3001 feat(view): add workspace support (@wraithgar)7b177e43f
#3014 feat(config): add 'envExport' flag (@isaacs)BUG FIXES
4c4252348
#3016 fix(usage): specify the key each time for multiples (@isaacs)9237d375b
#3013 fix(docs): add workspaces configuration (@wraithgar)cb6eb0d20
#3015 fix(ERESOLVE): better errors when current is missing (@isaacs)DEPENDENCIES
61da39beb
@npmcli/config@2.1.0
fb095a708
@npmcli/arborist@2.3.0
:workspace
configuration value.chown
the project root path.