Skip to content
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

npm missing uglify-js-2.4.5.tgz #359

Closed
jtangelder opened this issue Nov 28, 2013 · 21 comments
Closed

npm missing uglify-js-2.4.5.tgz #359

jtangelder opened this issue Nov 28, 2013 · 21 comments

Comments

@jtangelder
Copy link

I just saw that 2.4.5 was released 9 minutes ago, but the file uglify-js-2.4.5.tgz is missing.

$ npm install
npm WARN package.json nachtzonderdak@0.0.1 No repository field.
npm http GET https://registry.npmjs.org/grunt-contrib-uglify
npm http 304 https://registry.npmjs.org/grunt-contrib-uglify
npm http GET https://registry.npmjs.org/grunt-lib-contrib
npm http GET https://registry.npmjs.org/uglify-js
npm http 304 https://registry.npmjs.org/grunt-lib-contrib
npm http 304 https://registry.npmjs.org/uglify-js
npm http GET https://registry.npmjs.org/uglify-js/-/uglify-js-2.4.5.tgz
npm http 404 https://registry.npmjs.org/uglify-js/-/uglify-js-2.4.5.tgz
npm ERR! fetch failed https://registry.npmjs.org/uglify-js/-/uglify-js-2.4.5.tgz
npm ERR! Error: 404 Not Found
@mishoo
Copy link
Owner

mishoo commented Nov 28, 2013

Perhaps it works now? npm install uglify-js just worked for me (although
slow. npm acts strange lately).

On Thu, Nov 28, 2013 at 1:27 PM, Jorik Tangelder
notifications@github.comwrote:

I just saw that 2.4.5 was released 9 minutes ago, but the file
uglify-js-2.4.5.tgz is missing.

$ npm install
npm WARN package.json nachtzonderdak@0.0.1 No repository field.
npm http GET https://registry.npmjs.org/grunt-contrib-uglify
npm http 304 https://registry.npmjs.org/grunt-contrib-uglify
npm http GET https://registry.npmjs.org/grunt-lib-contrib
npm http GET https://registry.npmjs.org/uglify-js
npm http 304 https://registry.npmjs.org/grunt-lib-contrib
npm http 304 https://registry.npmjs.org/uglify-js
npm http GET https://registry.npmjs.org/uglify-js/-/uglify-js-2.4.5.tgz
npm http 404 https://registry.npmjs.org/uglify-js/-/uglify-js-2.4.5.tgz
npm ERR! fetch failed https://registry.npmjs.org/uglify-js/-/uglify-js-2.4.5.tgz
npm ERR! Error: 404 Not Found


Reply to this email directly or view it on GitHubhttps://github.com//issues/359
.

Mihai Bazon,
http://lisperator.net/

@jtangelder
Copy link
Author

works now, but it fetches 2.4.4. probably a cache issue at npm's side

@mishoo
Copy link
Owner

mishoo commented Nov 28, 2013

Cleaned cache and now I get that too. I'm not sure what's wrong. Tried npm publish --force but it refuses to overwrite. Tried npm unpublish uglify-js@2.4.5 but it doesn't remove the package. I'm recompiling Node now, though I didn't change anything in months and it used to work. :-(

@OddEssay
Copy link

I had the exact same problem on two different boxes at different locations (One in the US, one UK) - Manually doing npm install uglify-js@2.4.4 fixed the issue when npm install uglify-js was trying to download version 2.4.5 by default which wasn't been found.

I did manage to get to the file in my browser, which leads me to suspect it's some kind of sync error on the registry.npmjs.org servers.

@mishoo
Copy link
Owner

mishoo commented Nov 28, 2013

I can't figure it out :( Can't publish --force, can't unpublish, so I tried updating the version and now I get:

npm http PUT https://registry.npmjs.org/uglify-js
npm http 409 https://registry.npmjs.org/uglify-js
npm http GET https://registry.npmjs.org/uglify-js
npm http 200 https://registry.npmjs.org/uglify-js
npm http PUT https://registry.npmjs.org/uglify-js/-/uglify-js-2.4.6.tgz/-rev/132-079365a39be6137d3568e5fe39572c1c
npm http 409 https://registry.npmjs.org/uglify-js/-/uglify-js-2.4.6.tgz/-rev/132-079365a39be6137d3568e5fe39572c1c
npm ERR! publish fail Cannot publish over existing version.
npm ERR! publish fail Update the 'version' field in package.json and try again.
npm ERR! publish fail 
npm ERR! publish fail If the previous version was published in error, see:
npm ERR! publish fail     npm help unpublish
npm ERR! publish fail 
npm ERR! publish fail To automatically increment version numbers, see:
npm ERR! publish fail     npm help version

npm ERR! System Linux 3.5.0-42-generic
npm ERR! command "/usr/local/bin/node" "/usr/local/bin/npm" "publish"
npm ERR! cwd /home/mishoo/work/my/uglifyjs2
npm ERR! node -v v0.10.22
npm ERR! npm -v 1.3.14
npm ERR! code EPUBLISHCONFLICT
npm ERR! Error: write EPIPE
npm ERR!     at errnoException (net.js:901:11)
npm ERR!     at Object.afterWrite (net.js:718:19)
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.5.0-42-generic
npm ERR! command "/usr/local/bin/node" "/usr/local/bin/npm" "publish"
npm ERR! cwd /home/mishoo/work/my/uglifyjs2
npm ERR! node -v v0.10.22
npm ERR! npm -v 1.3.14
npm ERR! syscall write
npm ERR! code EPIPE
npm ERR! errno EPIPE

I'll submit a ticket to npm.

@silentworks
Copy link

Having this issue also. It seems to be missing from the registry. https://registry.npmjs.org/uglify-js/-/uglify-js-2.4.5.tgz

@silentworks
Copy link

Weirdly enough, I just tested the link after posting it and it seems to be downloading the file now, but doing npm install still doesn't fetch the file.

@phloe
Copy link

phloe commented Nov 28, 2013

@silentworks it's not just because you're downloading an error message and not getting an actual error? The contents of the downloaded file: {"error":"not_found","reason":"Document is missing attachment"}

@OddEssay
Copy link

@silentworks The joy of cloud computing - I had the same result. "registery.npmjs.org" is load balanced across multiple machines, so it seems to be luck of the draw as to weather you hit one which has the file or not.

@OddEssay
Copy link

@rasmusfl0e I definatly managed to download https://registry.npmjs.org/uglify-js/-/uglify-js-2.4.5.tgz with my browser, I've extracted the contents and checked package.json to confim it is very much version 2.4.5.

But, doing wget on the command line from several machines still fails with 404 errors.

@mishoo Perhaps publishing a fresh 2.4.6 version would help? Which would avoid some parts thinking 2.4.5 is there and some thinking its missing.

@mishoo
Copy link
Owner

mishoo commented Nov 28, 2013

@OddEssay I tried, but it fails with “can't publish over existing version” even before a successful push (as I said above). Something seems seriously broken with npm, I won't attempt anything else before we get some answer to https://github.com/isaacs/npm/issues/4215

@max-degterev
Copy link

If you have problems installing some module that uses uglify-js as a dependency, you can cache previous version like this for time being:

    "uglify-js":                       "2.4.4",
    "grunt-contrib-uglify":                       "~0.2.7",

This helped me to successfully install grunt-contrib-uglify

@tsgautier
Copy link

I would suspect npm is at fault here, coffeelint went from 1.0.1 to 1.0.2 a few hours ago, and is also suffering from the same problem. 👎 That doesn't help any of us that are affected by this bug.

Does anyone know how to force downgrade a transitive dependency? Jade specifies "*" for the version of uglify, so it's the one that's giving me trouble.

UPDATE
I have no issues from my laptop at home. registry.npmjs.org resolves as 165.225.131.92.

however from machines running in joyent, registry.npmjs.org resolves as 67.228.31.146 and continues to have the problem as of 08:00 PST.

UPDATE 2
The ip doesn't seem to be the issue, my local machine is now resolving to the same one. npm install still works fine locally but does not work for me either in ec2 or joyent.

@max-degterev
Copy link

@tsgautier did you clean caches on your local machine? Once the caches wiped clean it fails consistently 👍

@tsgautier
Copy link

Do you mean removing the node_modules directory? Or is there hidden cache somewhere else?

@gregberge
Copy link

v2.4.6 is not on npm :(

@jmvandamme
Copy link

it works for me now . Thanx.

@bbshopadmin
Copy link

Now it's working again for me. Thank you!

@LaurentGoderre
Copy link

We are having this problem with Travis

npm http GET https://registry.npmjs.org/uglify-js/-/uglify-js-2.4.5.tgz
npm http 200 https://registry.npmjs.org/uglify-js/-/uglify-js-2.4.5.tgz
npm ERR! Error: shasum check failed for /home/travis/tmp/npm-1382-uRbt5GAI/1385659726715-0.6672039364930242/tmp.tgz
npm ERR! Expected: 3bc46a71c14287cd94b6f111aec252fe50315c3a
npm ERR! Actual: f76ec91151482e3cea49a0b1d461d86836d91ac9
npm ERR! at /home/travis/.nvm/v0.10.22/lib/node_modules/npm/node_modules/sha/index.js:38:8
npm ERR! at ReadStream.<anonymous> (/home/travis/.nvm/v0.10.22/lib/node_modules/npm/node_modules/sha/index.js:85:7)
npm ERR! at ReadStream.EventEmitter.emit (events.js:117:20)
npm ERR! at _stream_readable.js:920:16
npm ERR! at process._tickCallback (node.js:415:13)
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>

@fuechter
Copy link

it works for me now!

@mishoo
Copy link
Owner

mishoo commented Nov 28, 2013

Seem to be fixed. https://github.com/isaacs/npm/issues/4215

@mishoo mishoo closed this as completed Nov 28, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests