Is npm 1.1.49 slightly broken for global installs on Windows?

145 views
Skip to first unread message

adrians

unread,
Aug 17, 2012, 3:00:49 PM8/17/12
to nod...@googlegroups.com

With node 0.8.7 x64 (Windows 7), npm seems to not see global modules installed under userdir/npm/... It only seems to look at the node_modules dir inside the install location. As well, when trying to install modules with -g, there are errors because it's trying to put the global module under the install dir, "c:\Program Files\nodejs\node_modules" and for this it needs permissions which it doesn't have.

Reverting back to node 0.8.6 and npm 1.1.48 shows correct behavior.

Is this a known issue?

Cheers,
Adrian

Bradley Meck

unread,
Aug 17, 2012, 3:35:56 PM8/17/12
to nod...@googlegroups.com
I have heard of a different person with what sounds like a similar problem, but no idea how wide spread it is.

Bert Belder

unread,
Aug 20, 2012, 3:33:21 PM8/20/12
to nod...@googlegroups.com

Not an issue known by be. Please file an issue on github.
Reply all
Reply to author
Forward
0 new messages