chore(biome): mark nested configs as non-root#1399
Merged
Conversation
Contributor
Chrome DevTools Protocol Tracing (Script: 116.25ms, Heap: 13.52MB)
Lighthouse (Script Eval: 133.28ms)
Platform Tests (vite-7 es2015 gzip: 69.66KB)vite-6 Platform Tests
vite-7 Platform Tests
webpack-5 Platform Tests
|
overbalance
enabled auto-merge (squash)
June 30, 2026 18:45
jpmunz
approved these changes
Jul 6, 2026
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.
What problem is this solving?
In the newest version, Biome requires nested
biome.jsoncfiles that extend the root config to explicitly opt out of being treated as roots themselves.Short description of the changes
Add
"root": falseto the three nested Biome configs (packages/web-sdk/src,tests/integration,tests/performance) so they are recognized as non-root configs extending the workspace root.This codemod was by
npx biome migrate, not manual intervention.How was this tested?
npm run lintfrom the repo root.Checklist