Node.js/Windows error: ENOENT, stat 'C:\Users\RT\AppData\Roaming\npm'

1000
votes

I have Windows 7 32-bit. I installed the latest Node.js 32 bit.
When I try to run the command npm install jquery, I receive the error:

Error: ENOENT, stat 'C:\Users\RT\AppData\Roaming\npm

How does one resolve it?

7
windowsnode.jsinstallation
Try running the command prompt as administrator. – skjagini
Run command prompt as administrator, and create the folder. – James Westgate
To remember the error, you can read it like "Error: NO ENTry". So check the directory whether it exists, otherwise create a new one. If there's no access, you can run the command prompt as administrator. Though for no access error node.js normally arise EACCESS error. – codersaif
Googlers, also note, that you can get this message as an ‘not found answer’ to small path typos, i.e. res.sendfile('pathSlightlyWrong/posts.html') (experienced under Windows 7) – Frank Nocke
My Unhandled event error got fixed in this answer stackoverflow.com/a/52441411/6665568 – Natesh bhat

7 Answers

1802
votes

Manually creating a folder named 'npm' in the displayed path fixed the problem.

More information can be found on Troubleshooting page

106
votes

I ran into the same problem while installing a package via npm.

After creating the npm folder manually in C:\Users\UserName\AppData\Roaming\ that particular error was gone, but it gave similar multiple errors as it tried to create additional directories in the npm folder and failed. The issue was resolved after running the command prompt as an administrator.

88
votes

This can also be fixed by installing a node package manually.

npm install npm -g

The process of doing that will setup all the required directories.

10
votes

I recommend setting an alternative location for your npm modules.

npm config set prefix C:\Dev\npm-repository\npm --global 
npm config set cache C:\Dev\npm-repository\npm-cache --global

Of course you can set the location to wherever best suits.

This has worked well for me and gets around any permissions issues that you may encounter.

2
votes

You can go to the Start Menu and search the Node.js icon and open the shell and then install anything with

install <packagename> -g
0
votes

Install a stable version instead of the latest one, I have downgrade my version to node-v0.10.29-x86.msi from 'node-v0.10.33-x86.msi' and it is working well for me!

http://blog.nodejs.org/2014/06/16/node-v0-10-29-stable/

0
votes

I needed a package from github that was written in typscript. I did a git pull of the most recent version from the master branch into the root of my main project. I then went into the directory and did an npm install so that the gulp commands would work that generates ES5 modules. Anyway, to make the long story short, my build process was trying to build files from this new folder so I had to move it out of my root. This was causing these same errors.