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.

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

[BUG] Option 2 of "upgrade npm on windows" made windows not recognize npm #332

Open
Inspirateur opened this issue Dec 2, 2022 · 3 comments
Labels
content Issues or PRs related to the content of the docs

Comments

@Inspirateur
Copy link

Inspirateur commented Dec 2, 2022

What / Why

Option 2 of "upgrade npm on windows" made windows not recognize npm as a command
https://docs.npmjs.com/try-the-latest-stable-version-of-npm

How

I deleted npm and npm.cmd from nodejs/, and even though C:\Users\<username>\AppData\Roaming\npm is still listed in the path and npm config get prefix -g did return C:\Users\<username>\AppData\Roaming\npm, windows won't recognize npm as a command anymore.
(it turns out this folder is empty, I should have checked myself but I trusted the docs)

Expected Behavior

I think the doc should include a warning about this method being dangerous or just be clearer about who can apply it, because evidently I wasn't one of them.

@Austindgk2
Copy link

#449

@Austindgk2
Copy link

#332 (comment)

@Austindgk2
Copy link

#449

@lukekarrys lukekarrys added the content Issues or PRs related to the content of the docs label Oct 31, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
content Issues or PRs related to the content of the docs
Projects
None yet
Development

No branches or pull requests

5 participants
@lukekarrys @Inspirateur @Austindgk2 and others