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

update react & react-dom & react-test-renderer to 16.9.0 #16982

Merged
merged 2 commits into from
Sep 13, 2019

Conversation

senadir
Copy link
Contributor

@senadir senadir commented Aug 9, 2019

Updated some packages to the latest React version

changes in React includes:

  • renaming deprecated lifecycle methods
    componentWillMountUNSAFE_componentWillMount
    componentWillReceivePropsUNSAFE_componentWillReceiveProps
    componentWillUpdateUNSAFE_componentWillUpdate
  • Async act() for Testing
  • Performance Measurements with <React.Profiler>
    and some other stuff you can react in the changelog above

@senadir
Copy link
Contributor Author

senadir commented Aug 9, 2019

had to delete the node_modules folder because it was causing some cache problems with a core package from another PR, that's why the pacakge-lock is updated to this extend

@gziolo
Copy link
Member

gziolo commented Aug 9, 2019

had to delete the node_modules folder because it was causing some cache problems with a core package from another PR, that's why the pacakge-lock is updated to this extend

I don't think this is the expected number of changes for the lock file. Can you try doing it again with the original lock file? It should be no more than dozens of lines updated. Did you follow: https://github.com/WordPress/gutenberg/tree/master/packages#production-dependencies?

@gziolo gziolo added the [Package] Element /packages/element label Aug 9, 2019
@senadir
Copy link
Contributor Author

senadir commented Aug 9, 2019

@gziolo I will try again, the depencedy in question was stylelint-plugin, a package I introduced in another PR, it shouldn't even exist in master or the branch I created, yet npm kept saying he didn't find it, removing node_modules fixed the issue but caused this new lock file

@senadir
Copy link
Contributor Author

senadir commented Aug 9, 2019

@gziolo seems it worked, I should have kept the lock file & deleted the modules folder, not both

@gziolo
Copy link
Member

gziolo commented Aug 12, 2019

I nearly forgot about react-native and that we need to wait until the new version is released which works with react 16.9.x.

@koke and @hypest, do you follow progress on the next version of RN?

@gziolo gziolo added the [Type] Enhancement A suggestion for improvement. label Aug 12, 2019
@koke
Copy link
Contributor

koke commented Aug 12, 2019

It looks like React Native only upgrades the React dependency on major versions, there's a tracking issue for the next minor one (0.60.5), but I don't know of a timeline for 0.61 yet.

@gziolo gziolo added the [Status] Blocked Used to indicate that a current effort isn't able to move forward label Aug 12, 2019
Copy link
Member

@gziolo gziolo left a comment

Choose a reason for hiding this comment

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

Great work @senadir. I tested and it all looks good. I rebased to master to ensure it still passes with the latest changes in the master branch.

Can we include a note in the changelog on @wordpress/element before we proceed?

Similar to:
https://github.com/WordPress/gutenberg/blob/master/packages/scripts/CHANGELOG.md#new-features-1

It's rather internal change as we don't introduce new features.

@gziolo
Copy link
Member

gziolo commented Sep 13, 2019

It looks like React Native 0.61.0 is still not there. However, we'd like to move forward with the changes so we could properly test Gutenberg with React 16.9.0 in the upcoming release cycle of WordPress 5.3. Related RN issue: react-native-community/releases#140.

Copy link
Member

@gziolo gziolo left a comment

Choose a reason for hiding this comment

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

I added CHANGELOG entry. Let's move forward with this PR.

@gziolo gziolo added Needs Dev Note Requires a developer note for a major WordPress release cycle and removed [Status] Blocked Used to indicate that a current effort isn't able to move forward labels Sep 13, 2019
@gziolo gziolo merged commit 0458c3c into master Sep 13, 2019
@gziolo gziolo deleted the chor/update-react branch September 13, 2019 19:49
@gziolo gziolo added this to the Gutenberg 6.5 milestone Sep 13, 2019
@youknowriad youknowriad added the Backport to WP 6.7 Beta/RC Pull request that needs to be backported to the WordPress major release that's currently in beta label Sep 13, 2019
@youknowriad youknowriad removed the Needs Dev Note Requires a developer note for a major WordPress release cycle label Oct 29, 2019
@jorgefilipecosta jorgefilipecosta removed the Backport to WP 6.7 Beta/RC Pull request that needs to be backported to the WordPress major release that's currently in beta label Feb 4, 2020
@gziolo gziolo mentioned this pull request Apr 27, 2020
6 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Package] Element /packages/element [Type] Enhancement A suggestion for improvement.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants