Release/v7.7.0 by ruyadorno · Pull Request #2922 · npm/cli

ruyadorno · 2021-03-23T15:54:33Z

v7.7.0 (2021-03-23)

FEATURES

33c4189f9#2864 add npm run-script workspaces support (@ruyadorno)
e1b3b318f#2886 add npm exec workspaces 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)
6598bfe86 mark deprecated configs (@isaacs)
8a38afe77#2881 docs(package-json): document default main behavior (@klausbayrhammer)
93a061d73#2917 add action items to npm run error output (@wraithgar)

DOCUMENTATION

ad65bd910#2860 fix link in configuring-npm (@varmakarthik12)
b419bfb02#2876 fix test-coverage command in contributing guide (@chowkapow)

DEPENDENCIES

7b5606b93@npmcli/arborist@2.2.9
- #254 Honor explicit prefix when saving dependencies (@jameschensmith)
- #255 Never save to bundleDependencies when saving a peer or peerOptional dependency. (@isaacs)
f76e7c21fpacote@11.3.1
- increases tarball compression level
4928512bcsemver@7.3.5
- fix handling prereleases/ANY ranges in subset
1924eb457libnpmversion@1.0.12
- fix removing undescored-prefixed package.json properties in npm version
916623056@npmcli/run-script@1.8.4
- fix expanding windows-style environment variables
a8d0751e4npm-pick-manifest@6.1.1
- fix running packages with a single executable binary with npm exec
af7eaac50hosted-git-info@4.0.1
f52c51db1@npmcli/config@2.0.0

@wraithgar

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

@wraithgar

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.

@isaacs

PR-URL: #2878 Credit: @isaacsClose: #2878 Reviewed-by: @isaacs

@wraithgar

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

@varmakarthik12

PR-URL: #2860 Credit: @varmakarthik12Close: #2860 Reviewed-by: @wraithgar

@jansepke

PR-URL: #2869 Credit: @jansepkeClose: #2869 Reviewed-by: @wraithgar

@augustobmoura

PR-URL: #2872 Credit: @augustobmouraClose: #2872 Reviewed-by: @darcyclarke

This was erroneously removed during a merge conflict

@chowkapow

PR-URL: #2876 Credit: @chowkapowClose: #2876 Reviewed-by: @wraithgar

@klausbayrhammer

PR-URL: #2881 Credit: @klausbayrhammerClose: #2881 Reviewed-by: @wraithgar

@ruyadorno

- 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

@isaacs

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

@wraithgar

Base commands and `npm run` need different outputs PR-URL: #2906 Credit: @wraithgarClose: #2906 Reviewed-by: @ruyadorno

@wraithgar

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

@ruyadorno

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

@wraithgar

PR-URL: #2917 Credit: @wraithgarClose: #2917 Reviewed-by: @ruyadorno

ruyadorno · 2021-03-23T15:54:33Z

v7.7.0 (2021-03-23)

FEATURES

33c4189f9#2864 add npm run-script workspaces support (@ruyadorno)
e1b3b318f#2886 add npm exec workspaces 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)
6598bfe86 mark deprecated configs (@isaacs)
8a38afe77#2881 docs(package-json): document default main behavior (@klausbayrhammer)
93a061d73#2917 add action items to npm run error output (@wraithgar)

DOCUMENTATION

ad65bd910#2860 fix link in configuring-npm (@varmakarthik12)
b419bfb02#2876 fix test-coverage command in contributing guide (@chowkapow)

DEPENDENCIES

7b5606b93@npmcli/arborist@2.2.9
- #254 Honor explicit prefix when saving dependencies (@jameschensmith)
- #255 Never save to bundleDependencies when saving a peer or peerOptional dependency. (@isaacs)
f76e7c21fpacote@11.3.1
- increases tarball compression level
4928512bcsemver@7.3.5
- fix handling prereleases/ANY ranges in subset
1924eb457libnpmversion@1.0.12
- fix removing undescored-prefixed package.json properties in npm version
916623056@npmcli/run-script@1.8.4
- fix expanding windows-style environment variables
a8d0751e4npm-pick-manifest@6.1.1
- fix running packages with a single executable binary with npm exec
af7eaac50hosted-git-info@4.0.1
f52c51db1@npmcli/config@2.0.0

@wraithgar

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

@wraithgar

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.

@isaacs

PR-URL: #2878 Credit: @isaacsClose: #2878 Reviewed-by: @isaacs

@wraithgar

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

@varmakarthik12

PR-URL: #2860 Credit: @varmakarthik12Close: #2860 Reviewed-by: @wraithgar

@jansepke

PR-URL: #2869 Credit: @jansepkeClose: #2869 Reviewed-by: @wraithgar

@augustobmoura

PR-URL: #2872 Credit: @augustobmouraClose: #2872 Reviewed-by: @darcyclarke

This was erroneously removed during a merge conflict

@chowkapow

PR-URL: #2876 Credit: @chowkapowClose: #2876 Reviewed-by: @wraithgar

@klausbayrhammer

PR-URL: #2881 Credit: @klausbayrhammerClose: #2881 Reviewed-by: @wraithgar

@ruyadorno

- 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

@isaacs

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

@wraithgar

Base commands and `npm run` need different outputs PR-URL: #2906 Credit: @wraithgarClose: #2906 Reviewed-by: @ruyadorno

@wraithgar

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

@ruyadorno

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

@wraithgar

PR-URL: #2917 Credit: @wraithgarClose: #2917 Reviewed-by: @ruyadorno

ruyadorno · 2021-03-23T15:54:33Z

v7.7.0 (2021-03-23)

FEATURES

33c4189f9#2864 add npm run-script workspaces support (@ruyadorno)
e1b3b318f#2886 add npm exec workspaces 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)
6598bfe86 mark deprecated configs (@isaacs)
8a38afe77#2881 docs(package-json): document default main behavior (@klausbayrhammer)
93a061d73#2917 add action items to npm run error output (@wraithgar)

DOCUMENTATION

ad65bd910#2860 fix link in configuring-npm (@varmakarthik12)
b419bfb02#2876 fix test-coverage command in contributing guide (@chowkapow)

DEPENDENCIES

7b5606b93@npmcli/arborist@2.2.9
- #254 Honor explicit prefix when saving dependencies (@jameschensmith)
- #255 Never save to bundleDependencies when saving a peer or peerOptional dependency. (@isaacs)
f76e7c21fpacote@11.3.1
- increases tarball compression level
4928512bcsemver@7.3.5
- fix handling prereleases/ANY ranges in subset
1924eb457libnpmversion@1.0.12
- fix removing undescored-prefixed package.json properties in npm version
916623056@npmcli/run-script@1.8.4
- fix expanding windows-style environment variables
a8d0751e4npm-pick-manifest@6.1.1
- fix running packages with a single executable binary with npm exec
af7eaac50hosted-git-info@4.0.1
f52c51db1@npmcli/config@2.0.0

@wraithgar

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

@wraithgar

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.

@isaacs

PR-URL: #2878 Credit: @isaacsClose: #2878 Reviewed-by: @isaacs

@wraithgar

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

@varmakarthik12

PR-URL: #2860 Credit: @varmakarthik12Close: #2860 Reviewed-by: @wraithgar

@jansepke

PR-URL: #2869 Credit: @jansepkeClose: #2869 Reviewed-by: @wraithgar

@augustobmoura

PR-URL: #2872 Credit: @augustobmouraClose: #2872 Reviewed-by: @darcyclarke

This was erroneously removed during a merge conflict

@chowkapow

PR-URL: #2876 Credit: @chowkapowClose: #2876 Reviewed-by: @wraithgar

@klausbayrhammer

PR-URL: #2881 Credit: @klausbayrhammerClose: #2881 Reviewed-by: @wraithgar

@ruyadorno

- 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

@isaacs

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

@wraithgar

Base commands and `npm run` need different outputs PR-URL: #2906 Credit: @wraithgarClose: #2906 Reviewed-by: @ruyadorno

@wraithgar

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

@ruyadorno

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

@wraithgar

PR-URL: #2917 Credit: @wraithgarClose: #2917 Reviewed-by: @ruyadorno

ruyadorno · 2021-03-23T15:54:33Z

v7.7.0 (2021-03-23)

FEATURES

33c4189f9#2864 add npm run-script workspaces support (@ruyadorno)
e1b3b318f#2886 add npm exec workspaces 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)
6598bfe86 mark deprecated configs (@isaacs)
8a38afe77#2881 docs(package-json): document default main behavior (@klausbayrhammer)
93a061d73#2917 add action items to npm run error output (@wraithgar)

DOCUMENTATION

ad65bd910#2860 fix link in configuring-npm (@varmakarthik12)
b419bfb02#2876 fix test-coverage command in contributing guide (@chowkapow)

DEPENDENCIES

7b5606b93@npmcli/arborist@2.2.9
- #254 Honor explicit prefix when saving dependencies (@jameschensmith)
- #255 Never save to bundleDependencies when saving a peer or peerOptional dependency. (@isaacs)
f76e7c21fpacote@11.3.1
- increases tarball compression level
4928512bcsemver@7.3.5
- fix handling prereleases/ANY ranges in subset
1924eb457libnpmversion@1.0.12
- fix removing undescored-prefixed package.json properties in npm version
916623056@npmcli/run-script@1.8.4
- fix expanding windows-style environment variables
a8d0751e4npm-pick-manifest@6.1.1
- fix running packages with a single executable binary with npm exec
af7eaac50hosted-git-info@4.0.1
f52c51db1@npmcli/config@2.0.0

@wraithgar

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

@wraithgar

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.

@isaacs

PR-URL: #2878 Credit: @isaacsClose: #2878 Reviewed-by: @isaacs

@wraithgar

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

@varmakarthik12

PR-URL: #2860 Credit: @varmakarthik12Close: #2860 Reviewed-by: @wraithgar

@jansepke

PR-URL: #2869 Credit: @jansepkeClose: #2869 Reviewed-by: @wraithgar

@augustobmoura

PR-URL: #2872 Credit: @augustobmouraClose: #2872 Reviewed-by: @darcyclarke

This was erroneously removed during a merge conflict

@chowkapow

PR-URL: #2876 Credit: @chowkapowClose: #2876 Reviewed-by: @wraithgar

@klausbayrhammer

PR-URL: #2881 Credit: @klausbayrhammerClose: #2881 Reviewed-by: @wraithgar

@ruyadorno

- 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

@isaacs

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

@wraithgar

Base commands and `npm run` need different outputs PR-URL: #2906 Credit: @wraithgarClose: #2906 Reviewed-by: @ruyadorno

@wraithgar

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

@ruyadorno

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

@wraithgar

PR-URL: #2917 Credit: @wraithgarClose: #2917 Reviewed-by: @ruyadorno

ruyadorno · 2021-03-23T15:54:33Z

v7.7.0 (2021-03-23)

FEATURES

33c4189f9#2864 add npm run-script workspaces support (@ruyadorno)
e1b3b318f#2886 add npm exec workspaces 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)
6598bfe86 mark deprecated configs (@isaacs)
8a38afe77#2881 docs(package-json): document default main behavior (@klausbayrhammer)
93a061d73#2917 add action items to npm run error output (@wraithgar)

DOCUMENTATION

ad65bd910#2860 fix link in configuring-npm (@varmakarthik12)
b419bfb02#2876 fix test-coverage command in contributing guide (@chowkapow)

DEPENDENCIES

7b5606b93@npmcli/arborist@2.2.9
- #254 Honor explicit prefix when saving dependencies (@jameschensmith)
- #255 Never save to bundleDependencies when saving a peer or peerOptional dependency. (@isaacs)
f76e7c21fpacote@11.3.1
- increases tarball compression level
4928512bcsemver@7.3.5
- fix handling prereleases/ANY ranges in subset
1924eb457libnpmversion@1.0.12
- fix removing undescored-prefixed package.json properties in npm version
916623056@npmcli/run-script@1.8.4
- fix expanding windows-style environment variables
a8d0751e4npm-pick-manifest@6.1.1
- fix running packages with a single executable binary with npm exec
af7eaac50hosted-git-info@4.0.1
f52c51db1@npmcli/config@2.0.0

@wraithgar

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

@wraithgar

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.

@isaacs

PR-URL: #2878 Credit: @isaacsClose: #2878 Reviewed-by: @isaacs

@wraithgar

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

@varmakarthik12

PR-URL: #2860 Credit: @varmakarthik12Close: #2860 Reviewed-by: @wraithgar

@jansepke

PR-URL: #2869 Credit: @jansepkeClose: #2869 Reviewed-by: @wraithgar

@augustobmoura

PR-URL: #2872 Credit: @augustobmouraClose: #2872 Reviewed-by: @darcyclarke

This was erroneously removed during a merge conflict

@chowkapow

PR-URL: #2876 Credit: @chowkapowClose: #2876 Reviewed-by: @wraithgar

@klausbayrhammer

PR-URL: #2881 Credit: @klausbayrhammerClose: #2881 Reviewed-by: @wraithgar

@ruyadorno

- 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

@isaacs

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

@wraithgar

Base commands and `npm run` need different outputs PR-URL: #2906 Credit: @wraithgarClose: #2906 Reviewed-by: @ruyadorno

@wraithgar

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

@ruyadorno

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

@wraithgar

PR-URL: #2917 Credit: @wraithgarClose: #2917 Reviewed-by: @ruyadorno

ruyadorno · 2021-03-23T15:54:33Z

v7.7.0 (2021-03-23)

FEATURES

33c4189f9#2864 add npm run-script workspaces support (@ruyadorno)
e1b3b318f#2886 add npm exec workspaces 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)
6598bfe86 mark deprecated configs (@isaacs)
8a38afe77#2881 docs(package-json): document default main behavior (@klausbayrhammer)
93a061d73#2917 add action items to npm run error output (@wraithgar)

DOCUMENTATION

ad65bd910#2860 fix link in configuring-npm (@varmakarthik12)
b419bfb02#2876 fix test-coverage command in contributing guide (@chowkapow)

DEPENDENCIES

7b5606b93@npmcli/arborist@2.2.9
- #254 Honor explicit prefix when saving dependencies (@jameschensmith)
- #255 Never save to bundleDependencies when saving a peer or peerOptional dependency. (@isaacs)
f76e7c21fpacote@11.3.1
- increases tarball compression level
4928512bcsemver@7.3.5
- fix handling prereleases/ANY ranges in subset
1924eb457libnpmversion@1.0.12
- fix removing undescored-prefixed package.json properties in npm version
916623056@npmcli/run-script@1.8.4
- fix expanding windows-style environment variables
a8d0751e4npm-pick-manifest@6.1.1
- fix running packages with a single executable binary with npm exec
af7eaac50hosted-git-info@4.0.1
f52c51db1@npmcli/config@2.0.0

@wraithgar

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

@wraithgar

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.

@isaacs

PR-URL: #2878 Credit: @isaacsClose: #2878 Reviewed-by: @isaacs

@wraithgar

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

@varmakarthik12

PR-URL: #2860 Credit: @varmakarthik12Close: #2860 Reviewed-by: @wraithgar

@jansepke

PR-URL: #2869 Credit: @jansepkeClose: #2869 Reviewed-by: @wraithgar

@augustobmoura

PR-URL: #2872 Credit: @augustobmouraClose: #2872 Reviewed-by: @darcyclarke

This was erroneously removed during a merge conflict

@chowkapow

PR-URL: #2876 Credit: @chowkapowClose: #2876 Reviewed-by: @wraithgar

@klausbayrhammer

PR-URL: #2881 Credit: @klausbayrhammerClose: #2881 Reviewed-by: @wraithgar

@ruyadorno

- 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

@isaacs

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

@wraithgar

Base commands and `npm run` need different outputs PR-URL: #2906 Credit: @wraithgarClose: #2906 Reviewed-by: @ruyadorno

@wraithgar

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

@ruyadorno

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

@wraithgar

PR-URL: #2917 Credit: @wraithgarClose: #2917 Reviewed-by: @ruyadorno

ruyadorno · 2021-03-23T15:54:33Z

v7.7.0 (2021-03-23)

FEATURES

33c4189f9#2864 add npm run-script workspaces support (@ruyadorno)
e1b3b318f#2886 add npm exec workspaces 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)
6598bfe86 mark deprecated configs (@isaacs)
8a38afe77#2881 docs(package-json): document default main behavior (@klausbayrhammer)
93a061d73#2917 add action items to npm run error output (@wraithgar)

DOCUMENTATION

ad65bd910#2860 fix link in configuring-npm (@varmakarthik12)
b419bfb02#2876 fix test-coverage command in contributing guide (@chowkapow)

DEPENDENCIES

7b5606b93@npmcli/arborist@2.2.9
- #254 Honor explicit prefix when saving dependencies (@jameschensmith)
- #255 Never save to bundleDependencies when saving a peer or peerOptional dependency. (@isaacs)
f76e7c21fpacote@11.3.1
- increases tarball compression level
4928512bcsemver@7.3.5
- fix handling prereleases/ANY ranges in subset
1924eb457libnpmversion@1.0.12
- fix removing undescored-prefixed package.json properties in npm version
916623056@npmcli/run-script@1.8.4
- fix expanding windows-style environment variables
a8d0751e4npm-pick-manifest@6.1.1
- fix running packages with a single executable binary with npm exec
af7eaac50hosted-git-info@4.0.1
f52c51db1@npmcli/config@2.0.0

@wraithgar

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

@wraithgar

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.

@isaacs

PR-URL: #2878 Credit: @isaacsClose: #2878 Reviewed-by: @isaacs

@wraithgar

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

@varmakarthik12

PR-URL: #2860 Credit: @varmakarthik12Close: #2860 Reviewed-by: @wraithgar

@jansepke

PR-URL: #2869 Credit: @jansepkeClose: #2869 Reviewed-by: @wraithgar

@augustobmoura

PR-URL: #2872 Credit: @augustobmouraClose: #2872 Reviewed-by: @darcyclarke

This was erroneously removed during a merge conflict

@chowkapow

PR-URL: #2876 Credit: @chowkapowClose: #2876 Reviewed-by: @wraithgar

@klausbayrhammer

PR-URL: #2881 Credit: @klausbayrhammerClose: #2881 Reviewed-by: @wraithgar

@ruyadorno

- 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

@isaacs

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

@wraithgar

Base commands and `npm run` need different outputs PR-URL: #2906 Credit: @wraithgarClose: #2906 Reviewed-by: @ruyadorno

@wraithgar

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

@ruyadorno

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

@wraithgar

PR-URL: #2917 Credit: @wraithgarClose: #2917 Reviewed-by: @ruyadorno

ruyadorno · 2021-03-23T15:54:33Z

v7.7.0 (2021-03-23)

FEATURES

33c4189f9#2864 add npm run-script workspaces support (@ruyadorno)
e1b3b318f#2886 add npm exec workspaces 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)
6598bfe86 mark deprecated configs (@isaacs)
8a38afe77#2881 docs(package-json): document default main behavior (@klausbayrhammer)
93a061d73#2917 add action items to npm run error output (@wraithgar)

DOCUMENTATION

ad65bd910#2860 fix link in configuring-npm (@varmakarthik12)
b419bfb02#2876 fix test-coverage command in contributing guide (@chowkapow)

DEPENDENCIES

7b5606b93@npmcli/arborist@2.2.9
- #254 Honor explicit prefix when saving dependencies (@jameschensmith)
- #255 Never save to bundleDependencies when saving a peer or peerOptional dependency. (@isaacs)
f76e7c21fpacote@11.3.1
- increases tarball compression level
4928512bcsemver@7.3.5
- fix handling prereleases/ANY ranges in subset
1924eb457libnpmversion@1.0.12
- fix removing undescored-prefixed package.json properties in npm version
916623056@npmcli/run-script@1.8.4
- fix expanding windows-style environment variables
a8d0751e4npm-pick-manifest@6.1.1
- fix running packages with a single executable binary with npm exec
af7eaac50hosted-git-info@4.0.1
f52c51db1@npmcli/config@2.0.0

@wraithgar

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

@wraithgar

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.

@isaacs

PR-URL: #2878 Credit: @isaacsClose: #2878 Reviewed-by: @isaacs

@wraithgar

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

@varmakarthik12

PR-URL: #2860 Credit: @varmakarthik12Close: #2860 Reviewed-by: @wraithgar

@jansepke

PR-URL: #2869 Credit: @jansepkeClose: #2869 Reviewed-by: @wraithgar

@augustobmoura

PR-URL: #2872 Credit: @augustobmouraClose: #2872 Reviewed-by: @darcyclarke

This was erroneously removed during a merge conflict

@chowkapow

PR-URL: #2876 Credit: @chowkapowClose: #2876 Reviewed-by: @wraithgar

@klausbayrhammer

PR-URL: #2881 Credit: @klausbayrhammerClose: #2881 Reviewed-by: @wraithgar

@ruyadorno

- 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

@isaacs

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

@wraithgar

Base commands and `npm run` need different outputs PR-URL: #2906 Credit: @wraithgarClose: #2906 Reviewed-by: @ruyadorno

@wraithgar

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

@ruyadorno

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

@wraithgar

PR-URL: #2917 Credit: @wraithgarClose: #2917 Reviewed-by: @ruyadorno

ruyadornoand others added 30 commits March 18, 2021 13:03

npm-package-arg@8.1.2
111e284

normalize-package-data@3.0.2
33c8536

hosted-git-info@4.0.1
af7eaac

@npmcli/run-script@1.8.4
9166230

eslint@7.22.0
f06c12e

jsdom@16.5.1
966057c

yaml@1.10.2
b395763

chore(config): remove flatOptions references
46e14bd
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

Auto-generate 'npm help 7 config' from actual definitions
68db124

@npmcli/config@2.0.0
f52c51d
Eventually @npmcli/config will move back to the CLI under lib/utils/config/, so this v2 will be a short-lived release family.

update lib/*.js to use new config structures
7c89e74

Remove old config definitions and flattening logic
aaafab8
PR-URL: #2878 Credit: @isaacsClose: #2878 Reviewed-by: @isaacs

npm-pick-manifest@6.1.1
a8d0751

docs(configuring-npm): Fix broken link
ad65bd9
PR-URL: #2860 Credit: @varmakarthik12Close: #2860 Reviewed-by: @wraithgar

bump version in v7 bug template
0a331ac
PR-URL: #2869 Credit: @jansepkeClose: #2869 Reviewed-by: @wraithgar

docs: add asdf-nodejs as a viable version manager
78cb830
PR-URL: #2872 Credit: @augustobmouraClose: #2872 Reviewed-by: @darcyclarke

chore: fix rebuild win tests
7e99515

fix(tests): go back to mockNpm in test
fc8a1ff
This was erroneously removed during a merge conflict

Update test-coverage command
b419bfb
PR-URL: #2876 Credit: @chowkapowClose: #2876 Reviewed-by: @wraithgar

docs(package-json): document default main behavior
8a38afe
PR-URL: #2881 Credit: @klausbayrhammerClose: #2881 Reviewed-by: @wraithgar

restore npm.flatOptions.npmCommand
d98edd1
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

fix(suggestions): clarify Unknown command output
e94a458
Base commands and `npm run` need different outputs PR-URL: #2906 Credit: @wraithgarClose: #2906 Reviewed-by: @ruyadorno

cacache@15.0.6
629aaf3

fix(usage): add action items to error output
93a061d
PR-URL: #2917 Credit: @wraithgarClose: #2917 Reviewed-by: @ruyadorno

EMWickd mentioned this pull request Dec 1, 2023
[Snyk] Security upgrade node-gyp from 9.4.1 to 10.0.0 EMWickd/cli#63
Open

kingjay66 mentioned this pull request Dec 1, 2023
[Snyk] Fix for 1 vulnerabilities kingjay66/cli-1#10
Open

EMWickd mentioned this pull request Dec 1, 2023
[Snyk] Fix for 1 vulnerabilities EMWickd/cli#66
Open

jackromo888 mentioned this pull request Dec 1, 2023
[Snyk] Fix for 1 vulnerabilities jackromo888/cli-1#13
Open

gutwrinch mentioned this pull request Dec 1, 2023
[Snyk] Fix for 1 vulnerabilities gutwrinch/cli-1#17
Merged

leonardoadame mentioned this pull request Dec 2, 2023
[Snyk] Fix for 3 vulnerabilities leonardoadame/cli-1#29
Open

311821105 mentioned this pull request Feb 11, 2024
[Snyk] Security upgrade node-gyp from 9.4.1 to 10.0.0 311821105/cli#49
Open

CALISOULB mentioned this pull request Feb 11, 2024
[Snyk] Fix for 1 vulnerabilities CALISOULB/cli#22
Open

EMWickd mentioned this pull request Feb 11, 2024
[Snyk] Fix for 1 vulnerabilities EMWickd/cli#89
Open

LadyK-21 mentioned this pull request Feb 11, 2024
[Snyk] Fix for 1 vulnerabilities LadyK-21/cli#29
Open

Mary12jo33 mentioned this pull request Feb 11, 2024
[Snyk] Fix for 1 vulnerabilities Mary12jo33/cli#21
Open

adamlaska mentioned this pull request Feb 11, 2024
[Snyk] Fix for 1 vulnerabilities adamlaska/cli-3#29
Open

f4lco0n mentioned this pull request Feb 11, 2024
[Snyk] Fix for 1 vulnerabilities f4lco0n/npm-cli#31
Open

hojatA1 mentioned this pull request Feb 11, 2024
[Snyk] Fix for 1 vulnerabilities hojatA1/npm.cli#101
Open

soloinovator mentioned this pull request Feb 11, 2024
[Snyk] Fix for 1 vulnerabilities soloinovator/cli#40
Open

EMWickd mentioned this pull request Feb 11, 2024
[Snyk] Security upgrade node-gyp from 9.4.1 to 10.0.0 EMWickd/cli#94
Open

Billywildhig mentioned this pull request Feb 11, 2024
[Snyk] Security upgrade node-gyp from 9.4.1 to 10.0.0 Billywildhig/cli#66
Open

hojatA1 mentioned this pull request Feb 12, 2024
[Snyk] Security upgrade node-gyp from 9.4.1 to 10.0.0 hojatA1/npm.cli#103
Open

Alfred182 mentioned this pull request Feb 12, 2024
[Snyk] Fix for 1 vulnerabilities Alfred182/cli#6
Open

311821105 mentioned this pull request Feb 12, 2024
[Snyk] Fix for 1 vulnerabilities 311821105/cli#56
Open

Billywildhig mentioned this pull request Feb 12, 2024
[Snyk] Fix for 1 vulnerabilities Billywildhig/cli#76
Open

kingjay66 mentioned this pull request Feb 12, 2024
[Snyk] Fix for 1 vulnerabilities kingjay66/cli-1#18
Open

nicholaschoi168 mentioned this pull request Feb 12, 2024
[Snyk] Fix for 1 vulnerabilities nicholaschoi168/cli#23
Open

Theo13111 mentioned this pull request Feb 12, 2024
[Snyk] Fix for 1 vulnerabilities Theo13111/cli#126
Open

TheManager73 mentioned this pull request Feb 12, 2024
[Snyk] Fix for 1 vulnerabilities TheManager73/cli#21
Open

jackromo888 mentioned this pull request Feb 12, 2024
[Snyk] Fix for 1 vulnerabilities jackromo888/cli-1#22
Open

mtdev2 mentioned this pull request May 20, 2024
[Snyk] Fix for 9 vulnerabilities mtdev2/cli#96
Open

baby636 mentioned this pull request May 21, 2024
[Snyk] Fix for 15 vulnerabilities baby636/cli#81
Open

bumplzz69 mentioned this pull request May 21, 2024
[Snyk] Fix for 10 vulnerabilities bumplzz69/cli#44
Open

Bhanditz mentioned this pull request May 21, 2024
[Snyk] Fix for 10 vulnerabilities Bhanditz/cli#35
Open