-
Notifications
You must be signed in to change notification settings - Fork 3k
"npm ls -g" produces no output if global node_modules includes invalid symlink #9564
Comments
same for me on 3.3.3, Mac OSX.. no output from |
Same issue for me on ubuntu 14.04 with npm 3.3.12 and node 5. I seem to recall way back using npm link so maybe it's the same reason. Not quite sure where on linux install this link will reside that needs to me removed. Any help? |
Little rtfm and I tracked it down in /usr/local/lib/node_modules Yes there is a sym link there to my personal module. I moved it out of the directory and bingo the But HEY! I want to keep that link to my module so if I recreate it with V3.x (that was created in v2) will all be ok? |
Any progress on this? This is causing some nasty consequences down the line in projects that depend on npm, like npm-check-updates. Is there anything I can do to help? |
Hello, checking in again. Impacts npm-check-updates. Let me know if I can assist in any way. |
Hey! So, I removed the That said! We'd welcome a patch for this, @raineorshine. #12865 is a related-but-not-the-same PR open that involves links in And thank you for offering! |
Thanks! Limited in time on open source still, but am watching this issue closely. |
Just in case it may be of help, here is my system information under which this bug occured as well:
I can provide more details if it's desired. |
I did a little bit of digging and noticed that the errors are ignored when operating on the global dir. This was added 3 years back so I'm not sure if this is intended behavior or not. See 0bb08c8#diff-0d4754093eef60f5a70da5b0c6951cc6R148 and 0bb08c8#diff-0d4754093eef60f5a70da5b0c6951cc6R443 |
Environment: node v4.0.0 on Windows 7 X64.
At some point in the past, I used "npm link" and it created a symlink under %appdata%\npm\node_modules. The directory it linked to has since been renamed, so the link target is now invalid.
With npm v2.14.3, "npm ls -g" shows an empty module name for the bad symlink, but otherwise works...
npm v3.3.3 displays absolutely nothing. No directory listing and no error message.
I removed the obsolete symlink, and npm v3 started working.
The text was updated successfully, but these errors were encountered: