-
Notifications
You must be signed in to change notification settings - Fork 80
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
V4.0.0 #176
V4.0.0 #176
Conversation
…niversal-component into migrate-to-api-16
feat: React 16 API Implementation
# Conflicts: # src/flowTypes.js # src/requireUniversalModule.js
Moving away from deprecated willMount and to the non-deprecated lifecycle BREAKING CHANGE: Only Compatible with React 16.3 and up fix #129
Hey @ScriptedAlchemy Anyway, I've pulled your branch and used it in my project, all LGTM ! 👍 |
Hey @ScriptedAlchemy, where may I find changelog or migration guide for this version? It was major upgrade, so I assume there is some code update reqiuired on my side...? |
@erykpiast The migration is seamless, It works as such. You should not need to change anything in your code. |
Yep it’s a clean upgrade. Just the underlying React api is completely new (no more componentWillMount) |
@ScriptedAlchemy would you mind just adding a note about it being a clean upgrade in the GitHub Releases section? I was hesitant to upgrade myself until I hunted down this PR. |
Will do. Usually rely on the releases section to communicate this. I’ll update it today or tomorrow. |
No description provided.