Fix hard-pinned Babel peer deps in published packages#395
Merged
yoannmoinet merged 2 commits intoJun 3, 2026
Merged
Conversation
…ges (#391) Change exact-pinned peerDependencies for @babel/parser, @babel/traverse, and @babel/types from '7.24.5' to '^7.24.5' in all 5 published packages and the live-debugger internal plugin. npm 7+ treats mismatched peer deps as hard errors, so users on a newer Babel version were blocked from installing the plugin without --legacy-peer-deps.
🎉 All green!🧪 All tests passed 🔗 Commit SHA: d8f4ec2 | Docs | Datadog PR Page | Give us feedback! |
sdkennedy2
approved these changes
Jun 3, 2026
yoannmoinet
deleted the
vitrine/fix-hard-pinned-babel-peer-deps-in-webpa-41f67b0d
branch
gh-worker-dd-devflow-36fce6
Bot
added
mergequeue-status: done
and removed
mergequeue-status: waiting
labels
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
2 participants
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.
What and why?
All 5 published packages (
webpack-plugin,esbuild-plugin,rollup-plugin,rspack-plugin,vite-plugin) and thelive-debuggerinternal plugin had exact-pinnedpeerDependenciesfor@babel/parser,@babel/traverse, and@babel/typesat"7.24.5". npm 7+ treats a mismatched peer dep as a hard error, so any user on a newer Babel version is blocked from installing the plugin without--legacy-peer-deps. Fixes #391.How?
Changed the three Babel peer dep versions from the exact pin
"7.24.5"to the caret range"^7.24.5"in every affectedpeerDependenciesblock. ThedevDependenciesexact pins inlive-debugger/package.jsonare internal to the monorepo and left untouched — they do not affect consumers.yarn cli integrityandyarn typecheck:allboth pass without changes.