React 0.13 support (conflicting peerDependency)

[RickWong]

Don't know what to fix without react-a11y telling me. 😞

[AsaAyers]

until we have a replacement for current mixin use cases and support for class property initializers in the language, we don't plan to deprecate React.createClass.

You know you don't have to stop using React.createClass. Mixins are far more powerful than inheritance, so I'm sticking with React.createClass until they solve mixins for ES6 classes.

[RickWong]

@AsaAyers Yes I know. The problem is the dependency and peerDependency on React 0.12. Sorry, the issue should have been more descriptive to begin with. :)

[NickColley]

Yeah run into this too. 👍

[dennis-johnson-dev]

+1 to this issue. It's preventing us from upgrading to react-0.13.x. Would you accept a pull request that updates the package.json? Or do you foresee incompatibilities with React 0.13.x?

[pluma]

Had to remove react-a11y because of the peerDependency conflict. Would love to see this addressed, too.

[iam4x]

until #23 is merged:

• npm install --save-dev iam4x/react-a11y#packaged

[yidea]

+1

[AsaAyers]

See #24. Instead of requiring react my branch has you pass in any version you want. It's available with several other fixes on npm as @asaayers/react-a11y

[necolas]

Same issue for us.

[bmcmahen]

Same for me -- love this tool, btw.

[AsaAyers]

@ryanflorence is react-a11y still being supported? There are 10 open PRs. 4 of them are mine and would close 4 other PRs and 1 issue including this one.

[mmrtnz]

+1 This is a great tool! I'll be using @iam4x's work around in the mean time.