-
Notifications
You must be signed in to change notification settings - Fork 26
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
Peer miller-rabin@1.1.2 wants bn.js@^0.16.0 #5
Comments
Just when I deleted node_modules, npm install again :) |
I see the same, please push fix to npm. |
+1 browserify has a deep dependency on this package, so this bug is currently affecting anyone trying to install browserify :/ |
+1 never heard of this package yet my code is failing :-) |
+1 |
1 similar comment
+1 |
I'll star the package just to pay gratitude to it's relevance.. ;-) |
For anyone having this problem, you can temporary work around it by installing EDIT: Apparently it doesn't work when added as a peer dependency, my bad. Should be a normal or dev dependency. |
+1 |
+1 |
Will fix all these this evening or first thing tommorow On Fri, Jan 2, 2015, 12:47 PM Julien Noleau notifications@github.com
|
+1 |
+1 |
2 similar comments
+1 |
+1 |
@calvinmetcalf Your package is so deep in the dependency list, this issue is causing hell for basically anyone trying to do anything with Browserify and several others. Please either take time to fix (should be as easy as merging one of the three open PRs) and publishing, or granthing authority on this repo and npmjs for another to do so. |
+1 |
+1 thanks for the temporary work around @TiddoLangerak |
Got up working great indutny/miller-rabin@bb85f55 |
Good news everyone! This issue has been fixed downstream! It can now be closed! Thanks for jumping on it, @indutny! |
Awesome, thanks @indutny! |
Nice, thanks @TiddoLangerak for pointing this out. |
It is causing issue again on installing packages globally
|
@thetutlage it is 1.1.4 now, please clear your cache. |
sorry for this, was literally at the airport about to get on plain when this was raised. This plain, mind you, after take off had a flap problem and had to land but first had to spend several hours burning off fuel by flying in circles before relanding at the airport we took off from. Thank you to all that fixed this while I was circling the Atlantic specifically @guybedford and @indutny |
Glad that everything is fine. |
Hah, talk about perfect worst timing! We always used to joke about key devs getting hit by a bus, but I'll have to add this scenario to a disaster prep plan! |
No description provided.
The text was updated successfully, but these errors were encountered: