1100

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?

Improve this question
6
  • 6
    Try running the command prompt as administrator.
    – skjagini
    Aug 13, 2014 at 0:52
  • 4
    Run command prompt as administrator, and create the folder.
    – James Westgate
    Oct 29, 2014 at 9:37
  • 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
    Jul 10, 2015 at 7:11
  • 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 N
    Apr 18, 2016 at 8:37
  • My Unhandled event error got fixed in this answer stackoverflow.com/a/52441411/6665568
    – Natesh bhat
    Jan 3, 2019 at 13:42

9 Answers 9

Reset to default
2019

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

More information can be found on Troubleshooting page

Improve this answer
23
  • 34
    Seems like a bug on the instller.
    – amcdnl
    Aug 4, 2014 at 13:40
  • 44
    Is this bug in some tracker? This makes for an awful first experience with nodejs...
    – Roman Starkov
    Aug 10, 2014 at 16:32
  • 23
    This appears a bug with a recent release of Node.js. It wasn't an issue a few months ago. I had to manually create the folder to make it work on Windows 8.1 x64.
    – Sahas Katta
    Aug 20, 2014 at 19:51
  • 2
    It's being tracked by github.com/npm/npm/issues/5905, so you can subscribe to that issue to see progress.
    – David Ebbo
    Aug 21, 2014 at 17:38
  • 3
    For those who land here later, this is a reported issue at npm/npm#5905 and joyent/node#8117
    – Chad
    Sep 9, 2014 at 15:19
187

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.

Improve this answer
6
  • 2
    This is the only one that worked for me. Need to use -g for 'Global Mode' so it installs the packages into your <nodejs application path>. It will place them in the 'node_modules' folder. Otherwise, it will run in local mode and attempt to place the files and directories into the whichever path you are currently in. Sometimes, even running as administrator, you will run into directory access issues.
    – Justin Russo
    Jan 25, 2015 at 14:10
  • This is the only solution that worked for me as well running Win 8.1 with the 64-bit installer. Thanks!
    – RyGuy
    Jan 28, 2015 at 20:59
  • 7
    This is the cleanest solution!
    – Dennkster
    Feb 4, 2015 at 11:43
  • 1
    this also worked when hitting the same problem on OSX, albeit with a different file path
    – Ed Sykes
    Mar 25, 2015 at 15:27
  • I have just got the error, and found this to be the cleanest option to solve it!
    – Mohammed Noureldin
    Jun 26, 2023 at 23:19
114

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.

Improve this answer
3
  • 6
    Yeah same for me - Win7 and 64 bit. You need to create new folder and then execute npm command on command prompt run as administrator.
    – Aniket Thakur
    Oct 28, 2014 at 6:08
  • 2
    Same thing for me in Windows 10. Thanks for the tip.
    – Nate
    Jan 22, 2015 at 21:05
  • It worked after reinstalling node, removing npm and npm-cache folders in C:\Users\UserName\AppData\Roaming\ and added the folders again in command prompt as an admin.
    – Jens Stigaard
    Apr 7, 2016 at 20:11
11

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.

Improve this answer
4

you need to creating a folder named 'npm' in the displayed path C:\Users\$userName\AppData\Roaming\ fixed the problem.

enter image description here enter image description here

Improve this answer
2

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
Improve this answer
2

If you are sure about installing the Npm package, this solution worked for me Run the terminal in administrator and tun command npm install npm -g -g install package globally

Improve this answer
0

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/

Improve this answer
0
0

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.

Improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.