biome-validator

To validate a Biome configuration against schema requirements, the validator checks $schema usage, Biome 2.3+ compatibility, and core sections including linter, assist, and formatter. It detects deprecated keys and missing domains, reporting issues with suggested fixes for CI readiness.

Biome linting setups fail during pre-commit checks when configuration drifts from the expected schema or uses deprecated keys. The validator identifies outdated patterns and missing domains in your config, providing suggested fixes to pass validation and maintain up-to-date configuration patterns.

The best way to audit an existing Biome configuration is running the validator script with the --strict flag from your project root. This enforces comprehensive checks on $schema, linter, assist, and formatter settings, quickly validating current setups and suggesting improvements for stale configurations.

Biome configuration validation supports strict enforcement for formatter and assist settings via the --strict flag. It checks Biome 2.3+ compatibility and enforces correct schema usage across linter, assist, and formatter sections, reporting any configuration drift with actionable suggested fixes.

Limitations of automated Biome config validation include dependency on Biome 2.3+ compatibility requirements and reliance on correct $schema declarations. The validator focuses on schema rules, deprecated keys, and core section patterns, meaning custom or undocumented configuration fields may not be fully covered.