-
Notifications
You must be signed in to change notification settings - Fork 47.4k
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
Upgrade all @babel/* packages to fix DevTools builds #19647
Conversation
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit c99301a:
|
Details of bundled changes.Comparing: 87b3e2d...c99301a react-native-renderer
eslint-plugin-react-hooks
react-art
react-test-renderer
react-dom
ReactDOM: size: 0.0%, gzip: 0.0% Size changes (stable) |
Details of bundled changes.Comparing: 87b3e2d...c99301a eslint-plugin-react-hooks
react-native-renderer
react-art
react-test-renderer
react-dom
ReactDOM: size: 0.0%, gzip: 0.0% Size changes (experimental) |
Excellent. Thanks for splitting this off. |
Confirmed I am able to build the DevTools extension using Node v12.18.3 and v14.5.0 with these deps. |
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.
These changes look good to me but I am going to run the PR by the rest of the team before landing, to make sure there are no concerns about changing deps at the moment.
I haven't heard any concerns about changing deps, and the delta between the build artifacts looks like it's strictly an improvement (although minor) so let's go! |
Summary
As discussed in #19634, DevTools packages'
yarn build
commands are failing with the following error when run with the latest versions of Node 12 and Node 14:In babel/babel#11216 (comment), Babel's maintainer's recommends that all
@babel/*
packages should be updated to fix the error. This PR does that, upgrading all@babel/*
packages across the repository, excluding fixtures.The commit in this PR is cherry picked from
a633ac3
(#19634) as @bvaughn requested.Test Plan
Gathered from discussions in #19634.
Green CI, and:
Build DevTools packages
With latest Node 12 (v12.18.3) (
yarn build
commands here fail onmaster
):Diff build artifacts to ensure that core packages are not broken
There are about 2300 lines of changes in the main React packages, but I didn't notice anything concerning. I've uploaded the diffs here: https://gist.github.com/taneliang/c193548a1d5f07f083486ce859c2edf1. Most of the differences seem to be one of the following:
Object.assign
, e.g.: