-
-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Refusing to delete global module #29
Comments
I was unable to recreate this... I was able to install successfully, reinstall successfully, and remove successfully (using npm v1.4.28). I'd suggest trying The coffee module and associated packages are fairly notorious for not following standards and being a little glitchy, especially with backwards compatibility. So, it could just be this module. |
It's not just |
I can't recreate any of these errors... which version of node and npm are you running this against? |
Sorry - should have caught that in the debug. I hate to ask a stupid question, but are you running the command prompt as an admin? The issue is pretty clear "Refusing to delete"... there are a finite number of reasons why a file cannot be deleted. Either the permissions aren't acceptable, or perhaps the file is in use. There is also the possibility this is an issue with npm. Keep in mind the version of npm that ships with At this point, I think it's unlikely this is an NVM issue. |
Yep tried it even with an elevated command prompt. Still same error.
According to the message, also tried after removing Everything will run fine if I do Can you make sense of lines 77-80 in the log? |
If an uninstall/reinstall worked, then I'm confident this is an npm issue. By reinstalling, npm was reset to the default version (1.4.8). Lines 77-78 are part of npm's process for finding the |
can this be related to #26 ? |
It's highly unlikely. npm is installed uniquely for each version of node. At one point in our dialog, you mentioned running an If you had reinstalled node and still experienced the same issues, then I'd be more suspicious of NVM, but I'm pretty certain the issue is related to npm. In fact, I'm confident enough in this that I'm going to close this issue (of course, I can reopen if necessary). If you want to experiment, you could try a fresh install of node |
Just wanted to share this link. May be you could add this to readme: |
It looks like the previous link has been moved. I think that https://npm.community/t/installing-upgrading-npm/251/2 is the new location. |
I checked the Common Issues Wiki but didn't see this issue covered there. I get a failure with both I read through this issue but I don't see a resolution. The suggestion in the link I posted above is to use https://github.com/felixrieseberg/npm-windows-upgrade#upgrade-npm-on-windows, but that doesn't seem like a good solution to me. It would require installing that NPM package globally in every NPM version that I install, plus it requires a number of extra steps and permissions. |
Per @vkbansal (moved from issue #26):
I keep getting
Error: Refusing to delete: C:\Program Files\nodejs\coffeelint.cmd not in C:\Program Files\nodejs
. when I donpm install -g coffeelint
. Any idea what may cause this ?Here's
npm-debug.log
The text was updated successfully, but these errors were encountered: