[BUG] npm error enoent ENOENT: no such file or directory, lstat 'C:\Users\xxxx\AppData\Roaming\npm'
Open
Nobody has claimed this yet.
Bug
Needs Triage
- Dominant language
- JavaScript
- Stars
- 10.1k
- Forks
- 4.7k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 19
Description
Is there an existing issue for this?
- I have searched the existing issues
This issue exists in the latest npm version
- I am using the latest npm
Current Behavior
Installing node/npm fails to create C:\Users\<username>\AppData\Roaming\npm directory.
Expected Behavior
That MSI installer works
Steps To Reproduce
This is a duplicate of #6971
However, issue was closed without fix with no option to reopen.
See comments therein.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review duplicate issue #6971 and its comments first, then reproduce the Windows MSI installation failure described here. The issue names no files or tests; completion would mean the installer creates the AppData\Roaming\npm directory and npm installation succeeds without the ENOENT error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- cli, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100