-
-
Notifications
You must be signed in to change notification settings - Fork 10.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
Bad npm package for 2.0.0-rc2 #2785
Comments
Is this the issue you are referring to?
If so, I am experiencing this as well. |
@ryanflorence What version of npm are you on? |
Contra the npm3 release notes, it looks like this fix wasn't applied to npm3 because the relevant check got vendored. I backed out my build tooling change: #2789. I guess we'll have to re-release. Sorry. |
If it ain't broke... :P
|
@mjackson The npm release notes claimed it was fixed. I even checked that it was... just not for npm3, which I don't use. Oops. The relevant npm issue is npm/npm#10445, for those interested. |
It's ok :) I break stuff all the time. nbd
|
2.0.0-rc3 looks good 👍 |
If you don't ship 4 rc's in one day, then you just aren't shipping enough. |
We should ship a 5th w/a |
soon as @mjackson ships it, will do. |
i'm on it On Thu, Dec 31, 2015 at 9:22 AM Ryan Florence notifications@github.com
|
The
node_modules/history
issue is back in the 2.0.0-rc2 npm package:http://registry.npmjs.org/react-router/-/react-router-2.0.0-rc2.tgz
The text was updated successfully, but these errors were encountered: