Biome migration formatter drift during zero-downtime cutover

Formatter output divergence during incremental adoption

During zero-downtime cutover Biome and Prettier 3.x may both format overlapping files served to live traffic Divergence arises from fundamental differences in line-breaking philosophy whitespace normalization and rule ordering

Which syntax categories exhibit non-deterministic divergence?

The following syntax patterns are commonly reported to produce different formatted output between Biome and Prettier 3.x based on observed rule-set differences and formatter philosophy:

• Embedded expressions within template literals or JSX interpolations
• Multi-line TypeScript type annotations and interface definitions
• JSX children with mixed or trailing whitespace
• Regular expression literals carrying flags

These categories are not exhaustive Biome enforces stricter line-breaking defaults while Prettier operates in semi-auto mode by default and minor version shifts between Biome 1.x and Prettier 3.x releases can shift which patterns diverge

Can a pre-migration audit quantify the drift surface area without full test-suite execution?

Yes A representative file sample spanning the codebase syntax diversity can provide a divergence percentage without running the full test suite The following steps generate a concrete report for the installed versions:

git stash push --all || cp -r repo branch && biome fmt --write --output-mode=diff > biome.diff && prettier --check --list-different > prettier.diff && wc -l biome.diff prettier.diff

Normalize both outputs to a common format e.g unified diff and compute the percentage of files where normalized AST or formatted text differs This provides a sample-based metric but results depend on the representativeness of the chosen file sample and the installed Biome and Prettier patch versions

Does Biome LSP incremental mode guarantee identical formatting for unchanged files across toolchain boundaries?

No Biome LSP incremental mode preserves formatting state for unchanged files within a single toolchain However when both Biome and Prettier operate on overlapping files in CI or editor workflows rule-ordering differences and whitespace normalization at different pipeline stages can introduce cross-toolchain drift even for files that appear unchanged Incremental state does not synchronize between independent formatter processes

To finalize the recommended audit steps and verify version-specific parity I need to know the exact Biome and Prettier patch versions currently installed Providing those versions would allow me to adjust the divergence thresholds and confirm whether the sample-based audit generalizes to your environment