Skip to content
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

Lock react and react-dom to a fixed version #83

Merged
merged 1 commit into from
Dec 20, 2018

Conversation

hijiangtao
Copy link
Contributor

According to React Blog, the newest version of React v16.7 doesn't include React Hooks, before they tag an extra version for upcoming hooks, we should lock the version to latest react 16.7.0 alpha version, rather than use next to specify its version info in package.json. More details can be found at https://reactjs.org/blog/2018/12/19/react-v-16-7.html#can-i-use-hooks-yet

According to React Blog, the newest version of React v16.7 doesn't include React Hooks, before they tag an extra version for upcoming hooks, we should lock the version to latest react 16.7.0 alpha version, rather than use `next` to specify its version info in `package.json`. More details can be found at https://reactjs.org/blog/2018/12/19/react-v-16-7.html#can-i-use-hooks-yet
Copy link
Owner

@streamich streamich left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! Seems like hooks are not coming to React any time soon.

@streamich streamich merged commit 455812d into streamich:master Dec 20, 2018
streamich pushed a commit that referenced this pull request Dec 20, 2018
## [5.1.1](v5.1.0...v5.1.1) (2018-12-20)

### Bug Fixes

* lock react and react-dom to a fixed version ([#83](#83)) ([455812d](455812d))
@streamich
Copy link
Owner

🎉 This PR is included in version 5.1.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants