@nesvet/biome-config
v3.0.1
Published
Shareable Biome config: formatter, linter, import organization, type-aware rules
Maintainers
Readme
@nesvet/biome-config
My Biome config. Tabs, double quotes, type over interface, no trailing commas, almost no wrapping (lineWidth: 320).
Needs @biomejs/biome ^2.6.4.
Markdown and YAML are in the same check. GitHub Flavored Markdown stays, including a leading --- frontmatter block. Ordinary YAML strings use double quotes. Fenced JavaScript is formatted like the rest of your code, and those snippets are not linted. Paragraphs stay on the lines you wrote. Table columns are aligned.
bun add -d @nesvet/biome-config @biomejs/biome{
"$schema": "./node_modules/@biomejs/biome/configuration_schema.json",
"extends": ["@nesvet/biome-config/node"]
}/node requires the node: import protocol. Drop /node if you don't want that.
Bun is a known global. Imports are grouped (bun/node, packages, aliases, paths, CSS) with no blank lines between groups. Floating Promises are errors. CommonJS is an error. JSX files get React and a11y rules even if react is not in package.json.
Do not append /biome.json to extends.
Monorepo package:
{
"extends": "//"
}Override anything in your own biome.json. Files matching *.config.ts / *.config.js (and .mjs, .cjs, .mts, .cts) and *.d.ts may use a default export: noDefaultExport is off there. Tool configs need it, and declare module "*.css" is how CSS modules are typed. Those files still format and lint. Object and type property names may be CONSTANT_CASE (POSIX env keys) and may start with _ or $. A const may be PascalCase; a let may not.
Contributing
License
MIT
