-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Comments
Perhaps it works now? npm install uglify-js just worked for me (although On Thu, Nov 28, 2013 at 1:27 PM, Jorik Tangelder
Mihai Bazon, |
works now, but it fetches 2.4.4. probably a cache issue at npm's side |
Cleaned cache and now I get that too. I'm not sure what's wrong. Tried |
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. |
I can't figure it out :( Can't publish --force, can't unpublish, so I tried updating the version and now I get:
I'll submit a ticket to npm. |
Having this issue also. It seems to be missing from the registry. https://registry.npmjs.org/uglify-js/-/uglify-js-2.4.5.tgz |
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. |
@silentworks it's not just because you're downloading an error message and not getting an actual error? The contents of the downloaded file: |
@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. |
@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. |
@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 |
If you have problems installing some module that uses uglify-js as a dependency, you can cache previous version like this for time being:
This helped me to successfully install grunt-contrib-uglify |
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 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 |
@tsgautier did you clean caches on your local machine? Once the caches wiped clean it fails consistently 👍 |
Do you mean removing the node_modules directory? Or is there hidden cache somewhere else? |
v2.4.6 is not on npm :( |
it works for me now . Thanx. |
Now it's working again for me. Thank you! |
We are having this problem with Travis
|
it works for me now! |
Seem to be fixed. https://github.com/isaacs/npm/issues/4215 |
I just saw that 2.4.5 was released 9 minutes ago, but the file uglify-js-2.4.5.tgz is missing.
The text was updated successfully, but these errors were encountered: