npm Error Refusing to delete: node_modules/jscs/node_modules/.bin/esparse #787
Comments
|
Haven't experienced this before. Any chance you can follow up with the npm crew to get some more insight? |
|
@Krinkle I'm going to close this for now. If anything, this is either a bug in esprima or npm. We just made a copy of the existing esprima harmony parser for sanity's sake. |
|
same problem happening on travis-ci |
|
+1. Just happened to me with Wercker. |
|
Same thing just happened again. |
|
Also happened to me on Travis CI. |
|
Also happens to us on Bamboo several times a day. We also start with a with clean working tree/node_modules and we specify a clean dir for both npm cache and the TMPDIR process. |
|
Happened locally at my Mac with the official npm. Using our internal mirror everything worked. |
|
Not much we can do here. I suggest filing an issue with esparse or npm. We've never been able to get a reliable repro, which would help a lot. |
|
same problem, node version update from 0.8.x to 0.10.x helped |
|
@othiym23 you help here would be really appreciated, it seems it affects a lot of people :-( |
|
@markelog Looking at the stack traces here, everybody encountering this error is running a very old version of npm. Several of those errors look like race condition issues that we finally got around to addressing somewhere around |
|
@othiym23 thank you for the clarification, great news and all :-). |
|
It looks like |
|
@zxqfox Please do not use |
|
Still seeing issues after upgrading to npm 2.5.0 :( @othiym23, is this an npm bug? Admittedly, I updated npm with |
|
@cjsmith It looks like you may have two dependencies trying to create the same symbolic link. There's a broader discussion of this issue on npm/npm#7130, where we're trying to figure out the best way to deal with this. The problem is only partially in npm – in general, regardless of the strategy we decide upon, there's going to have to be a way to deal with conflicts between packages wanting to grab the same binary name, and it will probably at least partially devolve to package maintainers to play nice. Unless this is something else altogether! If you like, open an issue on npm and upload your |
|
I was having the same issue, trying to install jscs through maven on jenkins using different versions of npm which all failed. I solved it by adding to the npm, command "npm jscs@(version) --no-bin-links ----no-optional". |
Ref jscs-dev/node-jscs#883 Ref jscs-dev/node-jscs#787 Ref npm/npm/#6309
Every once in a while, running
npm installcauses this error.The job has no pre-existing
node_modulesdirectory, git working tree is clean. npm does have its own global cache, naturally, which I don't usually purge:https://integration.wikimedia.org/ci/job/oojs-ui-npm/2038/consoleFull
Looks like it might be a race condition of some kind. Any ideas as to what might be causing this? So far the fix has been to just try again until it works..
The text was updated successfully, but these errors were encountered: