-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Dependencies: Upgrade babel #57311
Dependencies: Upgrade babel #57311
Conversation
Size Change: +153 B (0%) Total Size: 1.73 MB
ℹ️ View Unchanged
|
Flaky tests detected in ba56f56. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/8298378677
|
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.
Thanks for this @sirreal!
I looked through and this seems like a fine update to make. I went through the Babel changelog and confirmed that there were only bug fixes and new features added.
Also, the simple-git
update is long overdue. #47478 will be closed out as a result of this PR.
I ran npm dedupe
locally before applying these updates because I wanted to see the impact of the command. This is what I got for output:
added 64 packages, removed 75 packages, changed 220 packages, and audited 4565 packages in 4m
This seems like something we should probably try running more regularly, potentially adding a pre-commit task, or creating a GitHub Action to check for a certain threshold.
I'm approving, but the merge conflicts need to be resolved. And I'd like a second look over from someone closer to the actual Gutenberg code before merging (maybe @gziolo, @ockham, or @youknowriad).
4d1b56f
to
c9a57d3
Compare
I expected this to be quick, but got stuck with failing tests 🙂 I may need to start with a deduplication only PR, I expect some of the failures are from that. I do have some other higher priority work right now so I'll get back to this when I have time. |
c9a57d3
to
8329c51
Compare
fc633a4
to
94e45da
Compare
"babel-jest": "29.6.2", | ||
"babel-loader": "8.2.3", | ||
"babel-jest": "29.7.0", | ||
"babel-loader": "9.1.3", |
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.
I think this is a major release because of changes to Node.js and webpack version support. We shouldn't be affected.
Require babel ^7.12.0 and Node.js >= 14.15.0 versions by JLHwung in babel/babel-loader#956
Remove dependency on loader-utils and drop webpack 4 support by nied in babel/babel-loader#942
94e45da
to
38bd6f6
Compare
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.
Not sure if you're ready for this to be reviewed, but it's looking good and worth a try, I think!
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.
To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
Thanks! Yes, I think we can land this 🤞 |
Upgrade babel related dependencies. Dedupe dependencies. Co-authored-by: sirreal <[email protected]> Co-authored-by: desrosj <[email protected]> Co-authored-by: gziolo <[email protected]>
What?
Why?
@babel/traverse was flagged as a security issue by dependabot.