-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
installing karma from the npm repository causes a 404 #840
Comments
I get the same issue.
|
Same here. Appears the tarball is missing on npmjs.
|
Hmm, even trying to go back a bit: npm install -g [email protected] (same with 0.10.4, even @canary) I get the following missing tar balls:
|
Yeah - because karma has just specified all of its dependencies as Can karma's dependencies be updated so that they're not |
Getting the exact same error and output as above that prevents me from installing my package with |
Same error here.
|
It just worked for me. Try again and see if it’s revolved for you guys as well. Probably some glitch of npmjs.org, eh? |
Looks good now for me too. |
Yep, good for me too now as well 👍 |
Guys, I'm sorry, but this is just NPM being retarded (see https://github.com/isaacs/npm/issues/4205). I have no idea what happend. I force pushed it again and it's good now. Instead of specifying versions, we gonna remove the peerDeps, see #767. |
@vojtajina I'd say your original publish must have only half-succeeded (npm has been wobbly of late) - hence the tarball not being attached. Being able to safely rollback for users in cases like this would be reeeeeally helpful, so removing any |
Thank you for resolving this so quickly. I too can confirm it's working. I think mhart has some good points though about avoiding * dependencies, so users can use older versions confidently. |
Hi Guy. I just changed the registry to http version by
|
I am having this issue now. Any suggestions? |
The text was updated successfully, but these errors were encountered: