Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[BUG] npm update -g package@latest removes all global packages #3175

Closed
mukaschultze opened this issue May 1, 2021 · 4 comments
Closed

[BUG] npm update -g package@latest removes all global packages #3175

mukaschultze opened this issue May 1, 2021 · 4 comments
Assignees
@ruyadorno
Labels
Bug thing that needs fixing Priority 1 high priority issue Release 7.x work is associated with a specific npm 7 release

Comments

@mukaschultze
Copy link

mukaschultze commented May 1, 2021 •
edited
Loading

Current Behavior:

Attempting to update a package with a tag using the update command globally causes ALL global packages to be removed.

Expected Behavior:

Packages should not be removed when updating global packages.

Steps To Reproduce:

npm i -g typescript nodemon @angular/cli # Install some global packages
npm ls -g --depth=0 # This shows the 3 installed packages
npm update -g @angular/cli@latest # Attempt to update one of the packages with a @latest tag
# Oh no! removed 620 packages
npm ls -g --depth=0 # Shows `-- (empty)

Environment:

  • OS: Windows 10 20H2
  • Node: 15.9.0
  • npm: 7.11.2

Additional Info

This only happens on the global scope
@mukaschultze mukaschultze added Bug thing that needs fixing Needs Triage needs review for next steps Release 7.x work is associated with a specific npm 7 release labels May 1, 2021
@nxhack nxhack mentioned this issue May 6, 2021
Closed
@wraithgar
Copy link
Member

Likely related: #3159

@darcyclarke darcyclarke added Priority 1 high priority issue and removed Needs Triage needs review for next steps labels Jun 11, 2021
@darcyclarke darcyclarke removed this from the OSS - Sprint 35 milestone Aug 23, 2021
@famzah
Copy link

famzah commented Sep 6, 2021

I am astonished that this hasn't been fixed for months! NPM just removed all my global packages.

A workaround is to use install instead of update.

@wraithgar wraithgar mentioned this issue Sep 29, 2021
Closed
3 tasks
This was referenced Oct 22, 2021
Closed
Closed
Closed
Open
@rodnikovdev
Copy link

Just faced the same issue with npm update -g npx. All symlinks inside bin/ removed and lib/node_modules is empty.

Environment:

  • OS: Xubuntu 20.04
  • Node: 16.13.1
  • npm: 8.1.2 (same issue for 8.3.0)

@petebacondarwin petebacondarwin mentioned this issue Jan 5, 2022
Closed
@mnapoli mnapoli mentioned this issue Jan 18, 2022
Closed
2 tasks
@mnapoli
Copy link

mnapoli commented Jan 18, 2022 •
edited
Loading

I reported and closed #4240 as duplicate of this issue. Note that it seems to be the @ that causes issues, not specifically @latest.

I can reproduce it with any version number (all dependencies get wiped out anyway). I also reproduce it with NPM v8.

mnapoli added a commit to serverless/serverless that referenced this issue Jan 18, 2022
@mnapoli
docs: Switch to npm i instead of broken npm update
ef61d09 
See npm/cli#3175 why `npm update` is broken.
@mnapoli mnapoli mentioned this issue Jan 18, 2022
Merged
mnapoli added a commit to serverless/serverless that referenced this issue Jan 18, 2022
@mnapoli
docs: Switch to npm i instead of broken npm update
c734a6b 
See npm/cli#3175 why `npm update` is broken.
ruyadorno added a commit to ruyadorno/cli that referenced this issue Jan 21, 2022
@ruyadorno
fix(arborist): load actual tree on named updates
5186e06 
Arborist was not loading the actual tree when using named updates for
global updates, that would result in removing all previously installed
deps from a global install anytime the user would try to run
`npm update <pkgname>`.

This changeset fixes the problem by allowing the load of the actual tree
if the `global` and `update.names` options are defined.

Added a few more tests to illustrate but some of the snapshots already
included were actually demonstrating the problem by having empty trees
as result, these are now also updated with the expected tree result.

Fixes: npm#3175
@ruyadorno ruyadorno mentioned this issue Jan 21, 2022
Merged
mnapoli added a commit to serverless/serverless that referenced this issue Jan 25, 2022
@mnapoli
docs: Switch to npm i instead of broken npm update
7e4d5bf 
See npm/cli#3175 why `npm update` is broken.
mnapoli added a commit to serverless/serverless that referenced this issue Jan 25, 2022
@mnapoli
docs: Switch to npm i instead of broken npm update
0b90847 
See npm/cli#3175 why `npm update` is broken.
mnapoli added a commit to serverless/serverless that referenced this issue Jan 25, 2022
@mnapoli
docs: Switch to npm i instead of broken npm update
a9d63ab 
See npm/cli#3175 why `npm update` is broken.
mnapoli added a commit to serverless/serverless that referenced this issue Jan 25, 2022
@mnapoli
docs: Switch to npm i instead of broken npm update
028e86b 
See npm/cli#3175 why `npm update` is broken.
medikoo pushed a commit to serverless/serverless that referenced this issue Jan 25, 2022
@mnapoli @medikoo
docs: Switch to npm i instead of broken npm update
5058900 
See npm/cli#3175 why `npm update` is broken.
medikoo pushed a commit to serverless/serverless that referenced this issue Jan 27, 2022
@mnapoli @medikoo
docs: Switch to npm i instead of broken npm update
1736fc2 
See npm/cli#3175 why `npm update` is broken.
medikoo pushed a commit to serverless/serverless that referenced this issue Jan 27, 2022
@mnapoli @medikoo
docs: Switch to npm i instead of broken npm update
d5c9ae1 
See npm/cli#3175 why `npm update` is broken.
medikoo pushed a commit to serverless/serverless that referenced this issue Jan 27, 2022
@mnapoli @medikoo
docs: Switch to npm i instead of broken npm update
f11e8a6 
See npm/cli#3175 why `npm update` is broken.
rm-hull pushed a commit to rm-hull/serverless that referenced this issue Jan 28, 2022
@mnapoli @rm-hull
docs: Switch to npm i instead of broken npm update
a0d28b6 
See npm/cli#3175 why `npm update` is broken.
@asamuzaK asamuzaK mentioned this issue Feb 19, 2022
Closed
@leemcmullen leemcmullen mentioned this issue Jul 20, 2022
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ruyadorno ruyadorno

Labels
Bug thing that needs fixing Priority 1 high priority issue Release 7.x work is associated with a specific npm 7 release
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
7 participants
@wraithgar @ruyadorno @darcyclarke @mnapoli @famzah @mukaschultze @rodnikovdev