Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

fetch failed https://registry.npmjs.org/grunt-zip/-/grunt-zip-0.10.2.tgz #4325

Closed
tideman opened this Issue Dec 16, 2013 · 4 comments

Comments

Projects
None yet
4 participants

tideman commented Dec 16, 2013

npm ERR! fetch failed https://registry.npmjs.org/grunt-zip/-/grunt-zip-0.10.2.tgz
npm ERR! Error: 404 Not Found
npm ERR!     at WriteStream.<anonymous> (/usr/local/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/local/lib/node_modules/npm/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 *entire* log,
npm ERR! including the npm and node versions, at:
npm ERR!     <http://github.com/isaacs/npm/issues>

npm ERR! System Darwin 13.0.0
npm ERR! command "node" "/usr/local/bin/npm" "install"
npm ERR! cwd /Users/tkroon/Sites/e-magazineV4/app-skeleton
npm ERR! node -v v0.10.22
npm ERR! npm -v 1.3.15
npm ERR! 
npm ERR! Additional logging details can be found in:
npm ERR!     /Users/tkroon/Sites/e-magazineV4/app-skeleton/npm-debug.log
npm ERR! not ok code 0

I am pretty new to node. Sorry if I ask something that is really easy to solve. Should I change the version in my package.json?

Member

timoxley commented Jan 9, 2014

@tideman This doesn't appear to be an npm issue directly, looks to be a broken publish from the npm server glitches from a few weeks ago. I've opened an issue on grunt-zip for this.

#4430

Member

timoxley commented Feb 21, 2014

@tideman with the package republished this appears fixed:

npm install grunt-zip@0.10.2                                                                                                                                                                    
npm WARN package.json update-save-test@0.5.0 No description
npm WARN package.json update-save-test@0.5.0 No repository field.
npm WARN package.json update-save-test@0.5.0 No README data
npm http GET https://registry.npmjs.org/grunt-zip/0.10.2
npm http 200 https://registry.npmjs.org/grunt-zip/0.10.2
npm http GET https://registry.npmjs.org/grunt-zip/-/grunt-zip-0.10.2.tgz
npm http 200 https://registry.npmjs.org/grunt-zip/-/grunt-zip-0.10.2.tgz
npm http GET https://registry.npmjs.org/grunt-retro
npm http GET https://registry.npmjs.org/node-zip/0.0.2
npm http 200 https://registry.npmjs.org/node-zip/0.0.2
npm http GET https://registry.npmjs.org/node-zip/-/node-zip-0.0.2.tgz
npm http 200 https://registry.npmjs.org/grunt-retro
npm http 200 https://registry.npmjs.org/node-zip/-/node-zip-0.0.2.tgz
grunt-zip@0.10.2 node_modules/grunt-zip
├── node-zip@0.0.2
└── grunt-retro@0.6.4
Contributor

othiym23 commented Nov 27, 2014

Closing as resolved – the npm registry had some growing pains around the beginning of the year, which have subsequently been addressed.

@othiym23 othiym23 closed this Nov 27, 2014

tideman commented Nov 27, 2014

Thanks.
Tijmen

On Nov 27, 2014, at 1:16 AM, Forrest L Norvell notifications@github.com wrote:

Closing as resolved – the npm registry had some growing pains around the beginning of the year, which have subsequently been addressed.


Reply to this email directly or view it on GitHub #4325 (comment).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment