-
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.20.0 #3550
Merged
Merged
Release v7.20.0 #3550
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
"on install" was ambiguous because it wasn't clear if it meant "when npm install is ran on this project" or "when this project is installed somewhere else" PR-URL: #3491 Credit: @wraithgar Close: #3491 Reviewed-by: @ljharb
PR-URL: #3498 Credit: @nlf Close: #3498 Reviewed-by: @wraithgar
Adds an example of when `npm update` would not install the latest version of a package because other subdependencies in your tree have tighter restrictions. PR-URL: #3494 Credit: @wraithgar Close: #3494 Reviewed-by: @lukekarrys
Implements `npm pkg get|set|delete` support. It enables retrieving and modifying values in a `package.json` file of any given project. Included are the implementation based on npm/rfcs#402 along with extensive tests and user documentation. Relates to: npm/rfcs#402 Fixes: npm/statusboard#368 PR-URL: #3487 Credit: @ruyadorno Close: #3487 Reviewed-by: @wraithgar
The flattener worked for everything except for when you are using `npm config set` itself. Now it works for both. PR-URL: #3508 Credit: @wraithgar Close: #3508 Reviewed-by: @nlf
This looks very wrong on white terminals. npmlog still makes its `notice` logs do this but that will have to be fixed in the npmlog repo. PR-URL: #3499 Credit: @wraithgar Close: #3499 Reviewed-by: @nlf
This adds the `audit` config item to the usage output of `npm ci`, and also tweaks how usage flags are shown for boolean options that do not default to false. Their usage is shown as the `--no-x` form of the flag to better communicate that the flag is needed to turn that normally true option OFF. The description of `audit` was also updated to reflect that it runs on many different npm commands, not just install. Because this flag is included in the usage of those commands it's best to let the assocation happen there instead of trying to be comprehensive in the description itself. A small fix to make `install-ci-test` not try to redefine its own usage, but to inherit from `ci` was also included. PR-URL: #3497 Credit: @wraithgar Close: #3497 Reviewed-by: @nlf
PR-URL: #3495 Credit: @wraithgar Close: #3495 Reviewed-by: @nlf
It will be helpful to us when debugging the "exit handler never called" bugs to know which timings were started but not ended. Tests moved to use real npm. PR-URL: #3479 Credit: @wraithgar Close: #3479 Reviewed-by: @ruyadorno
* npm mock logger writes to npm.log.record too now * No more extra process.exit from within the process `exit` event handle. * No more `exit()` function. Logic is rolled up into the exit handler. * Now there is only an exit handler and an exit event listener. `lib/utils/perf.js` was rolled up into npm.js itself. Unfortunately the tests were written in such a way that any further refactoring of the exit handler was going to require also rewriting the tests. Fortunately NOW the tests are interacting with the exit handler in a way that shouldn't require them to be rewritten AGAIN if we change the internals of the exit handler. PR-URL: #3482 Credit: @wraithgar Close: #3482 Reviewed-by: @nlf
Two files got into node_modules in a way that changes if you are on a system that is case sensitive. One was a readme that is now properly being ignored, the other is a typescript file that is upper case in some instances PR-URL: #3540 Credit: @wraithgar Close: #3540 Reviewed-by: @ruyadorno
* nodejs -> Node.js * javascript -> JavaScript PR-URL: #3542 Credit: @relrelb Close: #3542 Reviewed-by: @wraithgar
PR-URL: #3471 Credit: @nlf Close: #3471 Reviewed-by: @wraithgar
Adds ability to using empty bracket syntax as a shortcut to appending items to the end of an array when using `npm pkg set`, e.g: npm pkg set keywords[]=foo Relates to: npm/rfcs#402 PR-URL: #3539 Credit: @ruyadorno Close: #3539 Reviewed-by: @darcyclarke, @ljharb
Currently, the name: `npm-robot` is being used in nodejs changelogs as the atttribution author name for npm-update commits. This makes it so that entries in the changelog referring to our updates reads like: ``` upgrade npm to 7.18.1 (npm-robot) #39065 ``` This change makes it so that the name used in commits is `npm team`, this way the changelogs entry should read instead as: ``` upgrade npm to 7.18.1 (npm team) #39065 ``` Ref: https://nodejs.org/en/blog/release/v16.4.0/ PR-URL: #3541 Credit: @ruyadorno Close: #3541 Reviewed-by: @wraithgar, @targos, @BethGriggs
PR-URL: #3546 Credit: @cinderblock Close: #3546 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.20.0 (2021-07-15)
FEATURES
f17aca5cd
#3487 feat: addnpm pkg
command (@ruyadorno)98905ae37
#3471 feat(config): introducelocation
parameter (@nlf)BUG FIXES
4755b0728
#3498 friendlier errors forERR_SOCKET_TIMEOUT
(@nlf)3ecf19cdc
#3508 fix(config): fix noproxy (@wraithgar)c3bd10e46
#3499 fix(update-notifier): don't force black background (@wraithgar)89483e888
#3497 fix(usage): better audit/boolean flag usage output (@wraithgar)feeb8e42a
#3495 fix(publish): obey --ignore-scripts flag (@wraithgar)103c8c3ef
#3479 chore(exit): log any un-ended timings (@wraithgar)efc4313c2
#3482 chore(refactor): refactor exit handler and tests (@wraithgar)d8eb49b70
#3540 fix(bundle-and-ignore): case sensitivity cleanup (@wraithgar)DOCUMENTATION
339145f64
#3491 fix(docs): clarify what install type gets.bin
(@wraithgar)74c99755e
#3494 fix(docs): add npm update example (@wraithgar)801a52330
#3542 fix(docs): correct Node.js JavaScript stylings (@relrelb)791416713
#3546 fix(docs): how to see background script output (@cinderblock)DEPENDENCIES
691816f3d
@npmcli/arborist@2.7.1
b9597e944
make-fetch-happen@9.0.4
f573e7c56
minipass-fetch@1.3.4
2d5797ea0
pacote@11.3.5