linter biome type-checking plugins monorepo

Biome 2.0 beta adds plugins, multi-file linting

GritQL plugins, domain-based rule grouping, and cross-file analysis replace ESLint + typescript-eslint setup, but project scanning adds latency.

Summary

Multi-file linting and type-aware rules (noFloatingPromises) eliminate typescript-eslint overhead; automatic domain detection cuts configuration friction for React/Next projects.

Why it matters

Multi-file linting and type-aware rules (noFloatingPromises) eliminate typescript-eslint overhead; automatic domain detection cuts configuration friction for React/Next projects.

Implementation verdict

Replaces ESLint + typescript-eslint for JS/TS projects. Requires npm install --save-exact @biomejs/biome@beta and pre-release IDE extensions. Worth testing now on non-critical projects; performance regression likely in large repos until scanner optimization lands.

Sources

1.You can write custom lint rules using GritQL
2.Scanning projects means that Biome has become slower for many projects
3.Biome's total set of recommended rules should be most relevant to your specific project needs
4.noFloatingPromises rule, one of the most-requested rules that relies on type information
5.npm install --save-dev --save-exact @biomejs/biome@beta

Dev Signal

Get briefs like this in your inbox — free, every weekday.

100+ sources compressed into one 4-minute read. Ranked, cited, implementation-ready.

Read the full issue →All briefs