Skip to main content

Biome 2.5.7

Release Date: August 4, 2026

Biome just dropped 2.5.7, and honestly? It is a banger of a linting update. I have been poking at the new rules all morning, and this is the kind of release that quietly cleans up your codebase while you are not looking.

TL;DR: three rule additions (two in nursery, one option upgrade), a fix for Vue users, and a stdin mode fix for people with nested configs. No breaking changes. Update when you get a coffee break.

What Dropped

  • useNullishCoalescing gets an ignoreIfStatements option — Biome now flags if statements that only assign to a nullish variable, like if (!a) { a = b }, and can rewrite them to ??=. Flip the option on if you want Biome to leave those if statements alone.
  • New nursery rule: noExtendNative — Reports when you extend the prototype of a built-in object. You know, the thing we all did in 2013 and regret.
  • New nursery rule: noTailwindArbitraryValue — Flags Tailwind arbitrary values like w-[400px] in class attributes, configured utility functions, and tagged templates. Perfect for teams that want to keep utility classes in a strict allowlist.

Bug Bashes

  • Vue users, this one is for younoUnknownPseudoClass now recognizes Vue's :deep() pseudo-class inside .vue style blocks. No more false positives on your scoped styles.
  • Stdin mode + nested configs — The CLI previously ignored nested biome.json files when piping through stdin with --stdin-file-path. That is fixed now, so biome format --write --stdin-file-path=subdirectory/lib.js actually respects the config in subdirectory/biome.json.

Upgrade Path

Grab 2.5.7 from npm (npm i -D @biomejs/biome) or your package manager of choice. The new rules start in nursery, so they will not scream at you until you promote them in biome.json. Safe update, zero drama.

What is New?

By continuing to use the site, you agree to the use of cookies.