chore(standards): sync Biome rule policy - #39
Merged
Merged
Conversation
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
1 participant
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.
Before. The Bun 1.4 standards update also enabled new experimental Biome 2.5 rules. Some can hang while traversing Tailwind CSS imports or reject valid TypeScript and React patterns, making the quality gate unreliable.
Now. The repository uses the corrected canonical Biome policy. Stable checks remain enforced, while TypeScript handles the type questions that Biome cannot infer reliably across files.
Implementation
Sync the canonical Biome base and standards lock to standards commit
778cde05453c820add7fedbc9aea6c80f97e6fae.Verification
bun standards checkbunx turbo run lint check-types --output-logs=errors-only