-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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.0.12 #2189
Merged
Merged
Release v7.0.12 #2189
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
fix: npm/statusboard#155 PR-URL: #2185 Credit: @ruyadorno Close: #2185 Reviewed-by: @nlf
PR-URL: #2174 Credit: @nlf Close: #2174 Reviewed-by: @ruyadorno
--parseable is left from v6 and is not supported in v7. It was removed from the docs further down and thus should also not be used further up in the Synopsis. Compare: https://docs.npmjs.com/cli/v6/commands/npm-audit PR-URL: #2179 Credit: @Primajin Close: #2179 Reviewed-by: @ruyadorno
When a file named 'npmrc' is in the root of the npm module that is currently running, it adds config values that override the defaults (but not the global or user configs). This is a way for a system package installer to tell the npm that it installs to put its globals somewhere other than the default. In order to keep these configs around when users self-update npm with `npm i -g npm`, these config values must be "sticky", and ride along into the newly globally installed npm. This commit restores this behavior, fixing self-updating npm for Windows users, and any other systems that may make use of this functionality. Fixes: #2002 PR-URL: #2184 Credit: @isaacs Close: #2184 Reviewed-by: @ruyadorno
We have a lot of tests that were not handling errors in callbacks, not defining variables, defining variables that weren't used, and just generally not formatted like the rest of npm. Hazard of moving fast. Thankfully, machines can help.
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.
7.0.12 (2020-11-17)
BUG FIXES
7b89576bd
#2174 fix running empty scripts withnpm run-script
(@nlf)bc9afb195
#2002 #2184 Preserve builtin conf when installing npm globally (@isaacs)DEPENDENCIES
b74c05d88
@npmcli/[email protected]
DOCUMENTATION
4e522fdc9
#2179 remove mention to --parseable option fromnpm audit
docs (@Primajin)