Skip to content

npm error fetching "grunt-jade-l10n-extractor-0.1.3.tgz" --> 404 Not Found #4519

Closed
murrayf opened this Issue Jan 20, 2014 · 3 comments

4 participants

@murrayf
murrayf commented Jan 20, 2014
npm http 404 https://registry.npmjs.org/grunt-jade-l10n-extractor/-/grunt-jade-l10n-extractor-0.1.3.tgz
npm ERR! fetch failed https://registry.npmjs.org/grunt-jade-l10n-extractor/-/grunt-jade-l10n-extractor-0.1.3.tgz
npm ERR! Error: 404 Not Found
npm ERR!     at WriteStream.<anonymous> (/usr/lib/node_modules/npm/lib/utils/fetch.js:57:12)
npm ERR!     at WriteStream.EventEmitter.emit (events.js:117:20)
npm ERR!     at fs.js:1596:14
npm ERR!     at /usr/lib/node_modules/graceful-fs/graceful-fs.js:103:5
npm ERR!     at Object.oncomplete (fs.js:107:15)
npm ERR! If you need help, you may report this log at:
npm ERR!     <http://github.com/isaacs/npm/issues>
npm ERR! or email it to:
npm ERR!     <npm-@googlegroups.com>

npm ERR! System Linux 3.12.7-300.fc20.x86_64
npm ERR! command "node" "/usr/bin/npm" "install"
npm ERR! cwd /home/ripley10/appz/hot/ripple-client
npm ERR! node -v v0.10.24
npm ERR! npm -v 1.3.6
npm ERR! 
npm ERR! Additional logging details can be found in:
npm ERR!     /home/ripley10/appz/hot/ripple-client/npm-debug.log
npm ERR! not ok code 0
@iarna iarna added the support label Oct 3, 2014
@smikes
smikes commented Dec 4, 2014

Is this still a problem for you?

This looks like it might have been a transient error with the npm registry. I am able to install the grunt-jade-l10n-extractor package now.

There have been a lot of improvements to npm -- especially around conflicts and race conditions during install -- since 1.3.6. Can you try updating your npm installation?

To update npm, run npm -g install npm@latest

For some Linux distributions (Debian/Ubuntu and RedHat/CentOS), the latest node version provided by the distribution may lag behind the stable version. Here are instructions from NodeSource on getting the latest node.

We are trying to clean up older npm issues, so if we don't hear back from you within a week, we will close this issue. (Don't worry -- you can always come back again and open a new issue!)

Thanks!

@murrayf
@othiym23
othiym23 commented Dec 5, 2014

Closing as resolved!

@othiym23 othiym23 closed this Dec 5, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.