-
Notifications
You must be signed in to change notification settings - Fork 619
chore: install biomejs cli #7139
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
"maxSize": 16000000, | ||
"includes": ["{packages,lib,scripts,tests}/**/*.{mjs,js,ts,json}", "!**/dist-{cjs,es,types}/**", "!**/ruleset.ts"] | ||
}, | ||
"formatter": { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've turned many rules off initially because we need to establish that biome is runnable in our build systems before reintroducing rules that would lead to code changes.
bae8ce1
to
6a36ea7
Compare
"suspicious": "off" | ||
} | ||
} | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
because biome requires that subconfiguration must also be named biome.json
rather than allowing a pointer to a custom config file, and that it must sit in the folder it has control over, I had to edit several scripts that scan the clients folder to exclude this file.
Co-authored-by: Trivikram Kamat <[email protected]>
This PR installs biomejs v2.0.0 and a preliminary configuration, but does not use it in any build steps.
Prior experimentation:
#7134