Upgrade @babel/* to v8 - #4384
Draft
trevor-scheer wants to merge 1 commit into
Draft
Conversation
🦋 Changeset detectedLatest commit: 65a99f6 The changes in this PR will be included in the next version bump. This PR includes changesets to release 2 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 |
trevor-scheer
force-pushed
the
trevor/babel-8
branch
from
July 5, 2026 17:55
e2bc254 to
65a99f6
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Upgrades the
@babel/*toolchain from v7 to v8 across the monorepo. Supersedes #4372, which bumped only@babel/typesand left v8 types running against the v7 parser — Babel 8 packages have to move together.Bumping to v8 surfaced a pile of dead babel config and dependencies: a root
babel.config.jsleft over from the babel-jest days, plugins that v8 now folds in as always-on stable features,@babel/polyfill, and the tooling that only existed to feed the old config. Packages build with tsc/vite and test on vitest now, so none of it has a live consumer — it's all pruned here.A couple of things needed real handling rather than a version bump:
graphql-language-service-serverparses source files with@babel/parser, so itsBABEL_PLUGINSlist and thevue.tsAST types had to adapt to v8'sParserPluginunion and the@babel/typesv7/v8 skew that@vue/compiler-sfcbundles.babel-plugin-react-compilerruns through@vitejs/plugin-react's own@babel/core@7, which targets Babel 7 AST. Nothing pins@babel/traverse, so the compiler's Babel 7 stack and the monorepo's Babel 8 stack resolve side by side. Pinning@babel/traverseto v8 breaks the compiler.