coreybutler/nvm-windows

[Bug/Feature?]: pnpm leaves files in nodejs install dir, breaking nvm install

Open

#1093 opened on Jan 18, 2024

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Go (46,364 stars) (3,822 forks)batch import
consider for rtenhancement requesthelp wanted

Description

Description of the new feature / enhancement

Not sure if this is a bug or feature, but I had trouble installing nvm despite uninstalling npm because I forgot I had pnpm installed too, and it left a bunch of crap in C:\Program Files\nodejs folder. So the symlink failed and I was perplexed by nvm use not doing anything...

Suggestion: update readme to mention pnpm?

Suggestion: installer should warn about this? (nodejs existing causing symlink to fail)

Anyway, manually deleting nodejs install folder fixed this. (That's probably not how you should uninstall pnpm, but that's a problem for future me...)

Scenario when this would be used?

Upon installing, so the install actually works...

Supporting information

No response

Contributor guide

Tech stack
nodejsshellgo
Domain
documentationcli
Issue type
documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
None
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
90
Research direction
Examine the current README and installer documentation for nvm windows. Add a note about potential conflicts with pnpm, specifically that pnpm may leave files in the Node.js install directory, causing symlink failures for nvm. Consider also adding a troubleshooting step to manually delete the nodejs folder if issues occur. No code changes needed, just documentation updates.