-
-
Notifications
You must be signed in to change notification settings - Fork 298
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
Fix react bridge for react 16 #3591
Fix react bridge for react 16 #3591
Conversation
🦋 Changeset detectedLatest commit: d517175 The changes in this PR will be included in the next version bump. This PR includes changesets to release 30 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
✅ Deploy Preview for module-federation-docs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
please run changeset add |
@CarltonHowell I would recommend making a more semantic commit, so it would be better visualized on the main branch. Ex: |
fix / patch is what id suggest - since we are in v0 semver range, we use the minor as "major feature / potential breaking" and we use patch for Feature/Fix |
Description
16.13.0
.ReactDom.version
property exists inisReact18
check. React versions before16.13.0
do not have this prop.Related Issue
#3592
Types of changes
Checklist