BiomeLinterOptions
Lint with Biome — one binary for both the linter and
interface in bldr/node-tools
Lint with Biome — one binary for both the linter and
the formatter, and no type information required, which is what lets it run
over a project whose tsconfig the pod does not resolve.
Properties
configPath: string
property
A config directory to use instead of the one Biome discovers by walking up from the project.
env: Record<string, string>
property
Extra environment for the run.
linter: "biome"
property
Names this member of NodeLinterOptions.
outDir: string
property
Where the report is written. Defaults to lint-out.
paths: string[]
property
What to check, project-relative. Defaults to the whole project.
Biome honours files.includes from the config either way; this narrows
further, for a project that lints one directory and not another.
rootConfig: Record<string, unknown>
property
The root Biome config, written above the project inside the pod.
Biome 2 allows one root config per project and finds it by walking up
from the file. A member's own biome.json says root: false +
extends: "//" so the repo-root run does not see two roots — and a
config that says that is ignored entirely when nothing above it is a
root. Not warned about: ignored, silently, falling back to Biome's
defaults, which is tabs. A pod that mounts one member alone has nothing
above it, so it writes this.
Defaults to DEFAULT_BIOME_ROOT. The member's own config still
decides everything it states; this only has to exist, and to carry the
rules that are a decision for the whole repo rather than for one member.
script: string
property
Run this package.json script instead of invoking Biome directly.
For a project whose lint step is more than one command. The script must exit non-zero on a finding — this target's verdict is the exit code.