-
-
Notifications
You must be signed in to change notification settings - Fork 10.6k
upgrade to React 0.11.0 #87
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
Comments
Tested locally and everything appears to work. Don't have time to PR, sorry |
See also a3d6e2a |
I get the following npm error when I try
Anybody know why react "does not satisfy its siblings' peerDependencies requirements"? |
I do not understand peer dependencies, somebody said it would make upgrading easier for people so I merged it. do we only support >= 0.11? |
I'd like to only support 0.11+. Anybody still on 0.10 already has their thing built and is already using v 0.2 of the router, right? |
After having thought it through, I'm not sure I was right in suggesting using >= 0.11.0. Per the semver spec, any version < 1.0.0 is considered unstable, so >= might be too relaxed? Your call there of course :) |
alright, >=0.11 sounds good. (side note, wish people would release 1.0's and not be afraid of 2.0s and (meanwhile ... my own repo is still not 1.0, SOON!) On Fri, Jul 18, 2014 at 4:18 PM, Nick Williams [email protected]
|
I'm moving this back to a normal dependency until I understand peer dependencies, but atm I can't install anything |
@rpflorence please push this to npm |
I'll publish something tomorrow when I get a chance to double check some On Sun, Jul 20, 2014 at 4:37 PM, Dharmesh Malam [email protected]
|
Would be nice to have the react dependency bumped to 0.11.0.
Is it worth having a looser version dependency, to avoid this for each release? e.g.
">= 0.11.0"
The text was updated successfully, but these errors were encountered: