I've seen this in local node modules but not in global.
what is the cause and how can I prune these?
Asked
Active
Viewed 4,095 times
3
-
This question seems to cover what you need [npm windows install globally results in npm ERR! extraneous](http://stackoverflow.com/questions/22620352/npm-windows-install-globally-results-in-npm-err-extraneous) – Josh W Jan 09 '17 at 20:33
-
Can you remove them manually with `npm -g uninstall
`? – brandonscript Jan 09 '17 at 21:04 -
@JoshW I'm osx. so no it doesn't cover the issue. I'm using `n` version manager and homebrew installed original node. – Jan 09 '17 at 21:22
-
@brandonscript nope they don't go away – Jan 10 '17 at 07:56
-
Open a ticket with npm then I'd say – brandonscript Jan 10 '17 at 07:57
-
@brandonscript okay. https://github.com/npm/npm/issues/15436 – Jan 10 '17 at 08:11
1 Answers
7
reinstalling npm fixed this problem: npm i -g npm@latest
-
Don't do this with npm in plesk, after this it will not work anymore. – user706420 Mar 04 '18 at 13:10