Unable to use NPM with fresh Install on Windows

[englercj]

When installing v0.10.30 on windows the npm folder in %AppData% is not created, so npm commands fail:

$ node -v
v0.10.30

$ npm -v
1.4.21

$ npm i gulp
Error: ENOENT, stat 'C:\Users\cengler\AppData\Roaming\npm'

Seems like node/npm are on the path (npm uses "C:\Program Files\nodejs\npm"), but the failure to create that directory makes it unusable until you manually go and create the folder. Hopefully this can be fixed soon.

EDIT:

Temporary workaround on this StackOverflow question.

Cross posted to npm github: npm/npm#5905

[megawac]

Wrong repo https://github.com/npm/npm. Don't see the bug there but here's the fix:

http://stackoverflow.com/questions/25093276/nodejs-windows-error-enoent-stat-c-users-rt-appdata-roaming-npm

I've put off pointing clients to 0.10.30 cause of this bug. Instead pointing them to 0.10.28

[englercj]

Wrong repo https://github.com/npm/npm. Don't see the bug there but here's the fix:

I chose to do it here because it is the installer, but I can move it if necessary.

here's the fix:

That isn't a fix, that is a workaround. I mentioned that it is "unusable until you manually go and create the folder," manually creating a folder after the installer is done to get, what you just ran an installer for, to work properly is pretty crappy.

[ghost]

+1 to this issue. Noticed in deployments today

[Arlen22]

Obviously a lot of people are running into this same problem, given the number of upvotes on the stackoverflow question and answer. So it's not isolated. Just saying... I'm sure you guys are working on it.

[tracker1]

That was fun... didn't include a test case, or bump the related versions, but at least tracked down the origin of the error, and a bypass appears to work fine (at least in windows)

[othiym23]

This is a duplicate of #8141.

[trevnorris]

Thanks @othiym23