Release/v7.7.0#2922
Merged
Release/v7.7.0 #2922
Uh oh!
There was an error while loading. Please reload this page.
Conversation
This file contains hidden or 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
Iterative change moving us towards a more unified config. No longer pulling config from flatOptions where we don't have to. PR-URL: #2892 Credit: @wraithgarClose: #2892 Reviewed-by: @ruyadorno
When not handled, when there are multiple entries in this.npm.config.list, it causes crash as described in #2834 The change here merge everything in this.npm.config.list, because as I observed, the default config is present only at the last entry. Fix: #2834 Co-authored-by: @wraithgar PR-URL: #2865 Credit: @kenrick95Close: #2865 Reviewed-by: @isaacs, @wraithgar
This replaces the multiple separate sets of objects and documentation, some of which had defaults and/or types, some of which didn't, and cleans up a lot of configs that are no longer used. Deprecated configs are now marked, and the approach used to create these config definitions ensures that it is impossible to create a new config option that lacks the appropriate data for it.
Eventually @npmcli/config will move back to the CLI under lib/utils/config/, so this v2 will be a short-lived release family.
Lots of dead code removed thanks to streamlining of logic. `npm help` `npm <command>` and `npm help-search` are all now separated concerns, handling their own use cases. `help` calls `help-search` as a last resort, but `npm <command>` no longer tries to wind its way through to `help-search` just to get the basic npm usage displayed. The `did you mean` output has been expanded. It now always suggests top level commands, scripts, and bins, and suggests them in the way they should be called. PR-URL: #2859 Credit: @wraithgarClose: #2859 Reviewed-by: @ruyadorno
PR-URL: #2860 Credit: @varmakarthik12Close: #2860 Reviewed-by: @wraithgar
PR-URL: #2869 Credit: @jansepkeClose: #2869 Reviewed-by: @wraithgar
PR-URL: #2872 Credit: @augustobmouraClose: #2872 Reviewed-by: @darcyclarke
This was erroneously removed during a merge conflict
PR-URL: #2876 Credit: @chowkapowClose: #2876 Reviewed-by: @wraithgar
PR-URL: #2881 Credit: @klausbayrhammerClose: #2881 Reviewed-by: @wraithgar
- Add workspaces-related configs: - workspace: list of workspaces names/dir to filter for - workspaces: boolean value to enable/disable workspaces awareness - adds the proposed note in the docs of each of the commands that are not affected by these configs. - Add workspaces support to `npm run-script` - add ability to serially run lifecycle scripts in workspaces - add ability to list scripts for all workspaces - add colors to `npm run` (no args) output Relates to: npm/rfcs#117Fixes: npm/statusboard#276Fixes: npm/statusboard#283Fixes: npm/statusboard#284Fixes: npm/statusboard#285Fixes: npm/statusboard#286 PR-URL: #2864 Credit: @ruyadornoClose: #2864 Reviewed-by: @wraithgar
This is used by npm-registry-fetch to set the 'npm-command' HTTP header. Will be cleaned up in a less ugly way in config refactor part 2. PR-URL: #2903 Credit: @isaacsClose: #2903 Reviewed-by: @wraithgar
Base commands and `npm run` need different outputs PR-URL: #2906 Credit: @wraithgarClose: #2906 Reviewed-by: @ruyadorno
This starts us down the path of tying the params our commands accept to their config items. For now it is optional, and not every current config item would cleanly render if we added them today. The ones that are added here DO render nicely, and we can iterate from here. We can also at a later date do the same kind of appraoch with our positional args. PR-URL: #2908 Credit: @wraithgarClose: #2908 Reviewed-by: @nlf, @isaacs
Add workspaces support to `npm exec` - Refactored logic to read and filter workspaces into `lib/workspaces/get-workspaces.js` - Added location context message when entering interactive shell using `npm exec` (with no args) - Add ability to execute a package in the context of each configured workspace Fixes: npm/statusboard#288 PR-URL: #2886 Credit: @ruyadornoClose: #2886 Reviewed-by: @wraithgar
PR-URL: #2917 Credit: @wraithgarClose: #2917 Reviewed-by: @ruyadorno
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment
8 participants
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.7.0 (2021-03-23)
FEATURES
33c4189f9#2864 addnpm run-scriptworkspaces support (@ruyadorno)e1b3b318f#2886 addnpm execworkspaces support (@ruyadorno)41facf643#2859 expanded "Did you mean?" suggestions for missing cmds and scripts (@wraithgar)BUG FIXES
8cce4282f#2865npm publish: handle case where multiple config list is present (@kenrick95)6598bfe86mark deprecated configs (@isaacs)8a38afe77#2881 docs(package-json): document default main behavior (@klausbayrhammer)93a061d73#2917 add action items tonpm runerror output (@wraithgar)DOCUMENTATION
ad65bd910#2860 fix link in configuring-npm (@varmakarthik12)b419bfb02#2876 fix test-coverage command in contributing guide (@chowkapow)DEPENDENCIES
7b5606b93@npmcli/[email protected]bundleDependencieswhen saving apeerorpeerOptionaldependency. (@isaacs)f76e7c21f[email protected]4928512bc[email protected]1924eb457[email protected]npm version916623056@npmcli/[email protected]a8d0751e4[email protected]npm execaf7eaac50[email protected]f52c51db1@npmcli/[email protected]