update create-react-class package.json to use latest react

[elijahsmith]

Before submitting a pull request, please make sure the following is done:

1. Fork the repository and create your branch from master.
2. If you've added code that should be tested, add tests!
3. If you've changed APIs, update the documentation.
4. Ensure the test suite passes (npm test).
5. Make sure your code lints (npm run lint).
6. Format your code with prettier (npm run prettier).
7. Run the Flow typechecks (npm run flow).
8. If you added or removed any tests, run ./scripts/fiber/record-tests before submitting the pull request, and commit the resulting changes.
9. If you haven't already, complete the CLA.

[facebook-github-bot]

Thank you for your pull request and welcome to our community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. In order for us to review and merge your code, please sign up at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need the corporate CLA signed.

If you have received this in error or have any questions, please contact us at cla@fb.com. Thanks!

[facebook-github-bot]

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Facebook open source project. Thanks!

[elijahsmith]

this is an attempt to address #9750.

The issue is that the create-react-class npm package has been built with an old version of React in it, which causes GCC to choke when it tries to compile anything that uses it. I'm not sure how the npm package is generated -- the command isn't in the package.json, for instance -- but this PR updates the versions of the react packages that are referenced in the package.json.

I'm not sure what needs to happen with the yarn.lock file -- should I update that as well?

[gaearon]

I believe I fixed this in #9933.

[elijahsmith]

I saw that -- I wasn't convinced that would address the issue but I'm hoping I'm wrong.

To find out -- can you please republish the create-react-class npm package with these changes in it?

[gaearon]

Not yet. We'll publish it soon after 15.6. If something's missing by then I'm happy to follow up.

I'm pretty sure this will address the issue though. (The addon is using a copy of that code, changing it in React or bumping React package will have no effect.)

[elijahsmith]

ok thank you for the clarification.