npm install. fetch failed + ENOENT. infinite loop. #6137
Comments
|
I tried changing the registry to use http instead of https, which seemed to cut down on the number of fetches that fail, but a few still fail. I also can't get it to fail in the same order. Is the npm install multithreaded, and if so, can I force it to use a single thread for debugging? During one of my runs a fetch failed for https://github.com/btford/grunt-release/archive/feat-tag-name.tar.gz , when I did a curl, I got html saying I was being redirected (...but I don't run into this error every run). |
|
Same for me, my devDependencies looks like: {
"devDependencies": {
"faker": "^1.1.0",
"gulp": "^3.8.8",
"gulp-concat": "^2.4.0",
"gulp-less": "^1.3.5",
"gulp-sourcemaps": "^1.1.5",
"gulp-uglify": "^1.0.1",
"should": "^4.0.4",
"supertest": "^0.13.0"
}
}When running Moving those dev dependencies to normal dependencies fixed the issue for me. |
|
|
|
Is there any reason to not remove |
|
Oups, I guess that's an habit I got from when I learned |
|
However, the ENOENT issues you're seeing are due to a race condition I believe we've finally addressed in |
|
Wait what, I am to blame for I don't think I wanted that feature. 👍 on deprecation. |
|
Awesome. |
--dev is marked for deprecation. I was unable to install the node modules using `npm install --dev` because it installs the devDependencies recursively, and my machine failed at that. `npm install` will will install devDependencies (except on production). See [this issue](npm/npm#6137 (comment)) for discussion.
--dev is marked for deprecation. I was unable to install the node modules using `npm install --dev` because it installs the devDependencies recursively, and my machine failed at that. `npm install` will will install devDependencies (except on production). See [this issue](npm/npm#6137 (comment)) for discussion.
I've been having this issue as long as I've been trying to use npm. I'm not even sure what the real source of the problem is because the errors are endless.
I've read other issues [1], [2], and some suggest that I've got network issues. I've tried this on 3 networks with the same result, and am able to curl the files that npm is claiming that it can't fetch, so it's not that.
I tried removing node completely using this guide:
http://stackoverflow.com/a/11178106/1707152
And reinstalling using brew.
The dependencies that I'm trying to install are from angular-strap. I've tried removing the script attribute from package.json, and
rm -rf node_modulesdirectory beforenode install --deveach time but those don't seem to help.The text was updated successfully, but these errors were encountered: