Update @babel/core: 7.5.5 → 7.18.13 (minor) #42
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ @babel/core (7.5.5 → 7.18.13) · Repo · Changelog
Release Notes
Too many releases to show here. View the full release notes.
Commits
See the full diff on Github. The new version differs by 16 commits:
v7.18.13Fix: jsx with `retainLines` (#14869)chore: refine visitor typings (#14862)chore: update compat data to f4fa0361907c9e30f1409b9a43aeaf48e4ac4fbd (#14864)[parser] Improve `getPluginOptions` type (#14861)Update Rollup packages (#14860)Let `path.remove()` remove `IfStatement.alternate` (#14833)fix: ESM tests on Windows. (#14804)Fix a race condition in `@babel/core` (#14843)fix: Print build logs correctly (#14846)chore: update test262 to 747bed2e8aaafe8fdf2c65e8a10dd7ae64f66c47 (#14847)fix: Destructuring empty in nested `for` expressions (#14841)chore: Reduce debug logs (#14806)Add support for static evaluation of ?? operator (#14837)Update `jest-light-runner` (#14835)Add v7.18.12 to CHANGELOG.md [skip ci]👉 No CI detected
You don't seem to have any Continuous Integration service set up!
Without a service that will test the Depfu branches and pull requests, we can't inform you if incoming updates actually work with your app. We think that this degrades the service we're trying to provide down to a point where it is more or less meaningless.
This is fine if you just want to give Depfu a quick try. If you want to really let Depfu help you keep your app up-to-date, we recommend setting up a CI system:
depfu/.Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase.All Depfu comment commands