What does one Biome check cover?
A combined check can report formatting, lint rules and enabled code assists, such as import organization. An import tells one file where to find code from another. Check your settings and Biome’s language matrix because support varies by file type and feature.
Run a check before enabling writes. Biome distinguishes fixes it labels safe from additional fixes allowed by the unsafe option. Review proposed changes and verify the behavior you care about either way.
What should you check before replacing your current linter or formatter?
Biome can migrate some existing settings. Some rules have no equivalent or behave differently, and migrated output can replace existing linter settings. Keep the old checks while you compare a small set of files and a known finding from your project.
A passing result on the new tool could mean a rule was never enabled. If a rule you rely on is missing, keep the old check for that job until you have a replacement.
What do you keep to rerun the same check?
Biome is open source under MIT or Apache 2.0. Keep the version, configuration, included file types and check commands with your project. A package-manager install and a standalone install are both documented.
Budget for the time to review changes and any hosted build minutes you use. The checker runs where you install it. Other services in your editor or build have their own data and access settings.
How would you tell if a new check lost an existing rule?
Make two fictional report cards on paper. Do not install software or change an existing project.
- Name what must still be caughtMark a style difference and a known lint finding from an imaginary project. Give them separate rows.
- Compare the old and new reportsWrite that both find the style difference but only the old check sees the required lint finding.
- Decide what can moveKeep the old rule active in this example. Replace that check only after a new run on equivalent isolated files catches the required case.