This week's tooling landscape is defined by a recurring theme: reducing operational overhead at the architecture level rather than patching symptoms. Biome automates away the ESLint migration you've been putting off, Rust stabilizes APIs that eliminate boilerplate test helpers, and Google's silent Imagen deprecation is a case study in how API migrations go wrong before you notice. Here's what's worth your attention.
Biome v1.7 automates ESLint and Prettier migration
Biome now ships a single-command migration path from ESLint and Prettier configs, handling rule translation automatically rather than requiring manual porting. It also adds experimental JSON reports and a --staged flag for linting only staged files — no Husky plugin or pre-commit wrapper required.
The dual ESLint+Prettier setup has been the path of least resistance for years, but it's also a slow accumulation of config debt: two runtimes, two plugin trees, two sets of ignore patterns. Biome's migration command removes the main barrier, which was always the rule-porting exercise, not the tooling swap itself.
Verdict: Ship — if your ESLint extends TypeScript, React, Unicorn, or JSX A11y plugins, you're in the supported migration window. Run the migration command, review the output, and validate your CI output matches. Skip YAML config support for now; it's not there yet. Treat the JSON reports as informational only — they're experimental and the schema will change.
