-
Notifications
You must be signed in to change notification settings - Fork 651
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
breaking: Use stable context API #471
Conversation
Duplicate of #427 |
@@ -50,8 +50,8 @@ | |||
] | |||
}, | |||
"peerDependencies": { | |||
"react": ">=15.0.0", | |||
"react-dom": ">=15.0.0" | |||
"react": ">=16.6.0", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can kill react-lifecycles-compat
now, awesome!
https://bundlephobia.com/[email protected]
6b68721
to
f175957
Compare
Cherry-picking reactjs#471
Could this be released as @3 or even beta? Current legacy context implementation has issues when used with latest react-router and react-redux both of which are using the new Context API. This pull request fixes those issues I'm seeing in my code |
we've got semantic release now, let's (talking mostly to myself) not be afraid of bumping integers |
# [3.0.0](v2.9.0...v3.0.0) (2019-04-15) ### Features * use stable context API ([#471](#471)) ([aee4901](aee4901)), closes [#429](#429) ### BREAKING CHANGES * use new style react context ```diff // package.json -"react": "^15.0.0", +"react": "^16.6.0", -"react-dom": "^15.0.0", +"react-dom": "^16.6.0", ```
🎉 This PR is included in version 3.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
@jquense So fast. I expected esm support to be released in v3 as major change. |
# [3.0.0](reactjs/react-transition-group@v2.9.0...v3.0.0) (2019-04-15) ### Features * use stable context API ([#471](reactjs/react-transition-group#471)) ([aee4901](reactjs/react-transition-group@aee4901)), closes [#429](reactjs/react-transition-group#429) ### BREAKING CHANGES * use new style react context ```diff // package.json -"react": "^15.0.0", +"react": "^16.6.0", -"react-dom": "^15.0.0", +"react-dom": "^16.6.0", ```
# [3.0.0](reactjs/react-transition-group@v2.9.0...v3.0.0) (2019-04-15) ### Features * use stable context API ([#471](reactjs/react-transition-group#471)) ([aee4901](reactjs/react-transition-group@aee4901)), closes [#429](reactjs/react-transition-group#429) ### BREAKING CHANGES * use new style react context ```diff // package.json -"react": "^15.0.0", +"react": "^16.6.0", -"react-dom": "^15.0.0", +"react-dom": "^16.6.0", ```
# [3.0.0](reactjs/react-transition-group@v2.9.0...v3.0.0) (2019-04-15) ### Features * use stable context API ([#471](reactjs/react-transition-group#471)) ([aee4901](reactjs/react-transition-group@aee4901)), closes [#429](reactjs/react-transition-group#429) ### BREAKING CHANGES * use new style react context ```diff // package.json -"react": "^15.0.0", +"react": "^16.6.0", -"react-dom": "^15.0.0", +"react-dom": "^16.6.0", ```
# [3.0.0](reactjs/react-transition-group@v2.9.0...v3.0.0) (2019-04-15) ### Features * use stable context API ([#471](reactjs/react-transition-group#471)) ([aee4901](reactjs/react-transition-group@aee4901)), closes [#429](reactjs/react-transition-group#429) ### BREAKING CHANGES * use new style react context ```diff // package.json -"react": "^15.0.0", +"react": "^16.6.0", -"react-dom": "^15.0.0", +"react-dom": "^16.6.0", ```
[email protected]
allows usage of staticcontextType
. With16.0.0
we would need a higher-order component that puts the context value into props sinceTransition
needs to have access to the context in its constructor.Partial fix for #429
breaking change