Biome

Developer ToolsApache-2.0

One toolchain for web projects — a formatter and linter for JavaScript, TypeScript, JSX, CSS and JSON.

Latest 2.5.13 · by BiomeWritten in RustWebsitebiomejs/biomeRSS

Release activity

Release activity — 51 releases across 50 days in the last year. Each cell is one day; darker means more releases that day. Older weeks are hidden at this screen width.
JunJulAugSep
SundayNo releases on May 24, 2026No releases on May 31, 2026No releases on Jun 7, 2026No releases on Jun 14, 2026No releases on Jun 21, 2026No releases on Jun 28, 2026No releases on Jul 5, 2026No releases on Jul 12, 2026No releases on Jul 19, 2026No releases on Jul 26, 2026No releases on Aug 2, 2026No releases on Aug 9, 2026No releases on Aug 16, 2026No releases on Aug 23, 2026No releases on Aug 30, 2026No releases on Sep 6, 2026
MondayNo releases on May 25, 2026No releases on Jun 1, 2026No releases on Jun 8, 2026No releases on Jun 15, 2026No releases on Jun 22, 2026No releases on Jun 29, 2026No releases on Jul 6, 2026No releases on Jul 13, 2026No releases on Jul 20, 2026No releases on Jul 27, 2026No releases on Aug 3, 2026No releases on Aug 10, 20261 release on Aug 17, 2026No releases on Aug 24, 2026No releases on Aug 31, 2026No releases on Sep 7, 2026
TuesdayNo releases on May 26, 2026No releases on Jun 2, 2026No releases on Jun 9, 2026No releases on Jun 16, 20261 release on Jun 23, 2026No releases on Jun 30, 2026No releases on Jul 7, 2026No releases on Jul 14, 20261 release on Jul 21, 20261 release on Jul 28, 20261 release on Aug 4, 20261 release on Aug 11, 2026No releases on Aug 18, 2026No releases on Aug 25, 2026No releases on Sep 1, 2026No releases on Sep 8, 2026
Wednesday1 release on May 27, 2026No releases on Jun 3, 2026No releases on Jun 10, 2026No releases on Jun 17, 2026No releases on Jun 24, 20261 release on Jul 1, 20261 release on Jul 8, 20261 release on Jul 15, 2026No releases on Jul 22, 2026No releases on Jul 29, 2026No releases on Aug 5, 2026No releases on Aug 12, 2026No releases on Aug 19, 2026No releases on Aug 26, 2026No releases on Sep 2, 2026No releases on Sep 9, 2026
ThursdayNo releases on May 28, 2026No releases on Jun 4, 2026No releases on Jun 11, 2026No releases on Jun 18, 2026No releases on Jun 25, 2026No releases on Jul 2, 2026No releases on Jul 9, 2026No releases on Jul 16, 2026No releases on Jul 23, 2026No releases on Jul 30, 2026No releases on Aug 6, 2026No releases on Aug 13, 2026No releases on Aug 20, 20261 release on Aug 27, 20261 release on Sep 3, 20261 release on Sep 10, 2026
FridayNo releases on May 29, 2026No releases on Jun 5, 20261 release on Jun 12, 2026No releases on Jun 19, 2026No releases on Jun 26, 2026No releases on Jul 3, 2026No releases on Jul 10, 2026No releases on Jul 17, 2026No releases on Jul 24, 2026No releases on Jul 31, 2026No releases on Aug 7, 2026No releases on Aug 14, 20261 release on Aug 21, 2026No releases on Aug 28, 2026No releases on Sep 4, 2026
SaturdayNo releases on May 30, 2026No releases on Jun 6, 2026No releases on Jun 13, 2026No releases on Jun 20, 2026No releases on Jun 27, 2026No releases on Jul 4, 2026No releases on Jul 11, 2026No releases on Jul 18, 2026No releases on Jul 25, 2026No releases on Aug 1, 2026No releases on Aug 8, 2026No releases on Aug 15, 2026No releases on Aug 22, 2026No releases on Aug 29, 2026No releases on Sep 5, 2026

51 releases in the last year, busiest day 2

Changelog

2.5.13Latest

Biome CLI v2.5.13

Added 3
  • Add the nursery rule useLayeredStyles, which enforces that style rules are defined within a cascade layer and import rules to import its styles into a cascade layer
  • Add the nursery rule useBetterDomTraversing, which prefers .firstChild, .firstElementChild, .closest(), and merged .querySelector() calls over positional DOM traversal
  • Add the nursery rule noXorAsExponentiation, which reports the bitwise XOR operator ^ between two decimal integer literals where the exponentiation operator ** was likely intended
Fixed 7
  • Improve type-aware lint performance for large libraries such as Zod by no longer fully inferring imported generic declarations just to apply their type arguments
  • Fix noUselessConstructor to ignore TypeScript constructors that forward at least one argument to super, preserving constructors that narrow the subclass's accepted parameter types
  • Fix useAriaPropsForRole and useFocusableInteractive to no longer report non-focusable elements with role="separator"
  • Fix Grit plugins to capture and inspect multiple named import specifiers
  • Reduce unnecessary type inference when type-aware lint rules inspect members of namespace imports from libraries such as Zod
  • Fix noUnusedPrivateClassMembers to consider compound assignments such as ??= to read and use private class members
  • Fix useReactCompiler by disabling the experimental capitalized-call and effect-dependency checks to match upstream's recommended lint preset

From Biome

2.5.13
Patch Changes
What's Changed
New Contributors

Full Changelog: https://github.com/biomejs/biome/compare/@biomejs/biome@2.5.12...@biomejs/biome@2.5.13

View originalPermalink
How 2.5.13 went
2.5.12

Biome CLI v2.5.12

Added 3
  • Support for template literal attribute values inside an Astro expression
  • Added nursery rule `useFlatMathMinMax` that reports unnecessary nested calls to Math.min() and Math.max()
  • Added nursery rule `noThisOutsideOfClass` that reports `this` outside class members and TypeScript functions with an explicit `this` parameter
Fixed 12
  • Astro attribute expressions now accept TypeScript and JSX syntax that is accepted in text expressions
  • Astro attribute names are no longer split on `:` and `.` inside an expression
  • A bare `>` in the children of an Astro expression is no longer treated as markup
  • HTML comments inside an Astro expression now parse correctly and are read as trivia
  • Children of `is:raw` inside an Astro expression are no longer read as JSX
  • An apostrophe or quote in the text of a JSX element inside an Astro expression no longer ends the expression early

From Biome

2.5.12
Patch Changes

  • #11440 b88f1ea Thanks @Princesseuh! - Fixed Astro attribute expressions rejecting TypeScript and JSX syntax that is accepted in text expressions.

    <Component icon={<Icon />} count={total as number} onSelect={(e: Event) => e} />

  • #11440 b88f1ea Thanks @Princesseuh! - Fixed Astro attribute names being split on : and . inside an expression, such as {x && <button x-on:keyup.enter={go} client:load.foo />}.

  • #11440 b88f1ea Thanks @Princesseuh! - Fixed a bare > in the children of an Astro expression being treated as markup, such as {x && <div>a > b</div>}.

  • #11440 b88f1ea Thanks @Princesseuh! - Fixed HTML comments inside an Astro expression failing to parse. They are now read as trivia, wherever they appear among the children.

    {x && <div><!-- first -->text<!-- last --></div>}
{cond && <a></a><!-- c --><b></b>}

  • #11440 b88f1ea Thanks @Princesseuh! - Fixed is:raw children inside an Astro expression being read as JSX, such as {x && <div is:raw>{not js} < & text</div>}.

  • #11440 b88f1ea Thanks @Princesseuh! - Fixed an apostrophe or quote in the text of a JSX element inside an Astro expression ending the expression early, such as {items.map((i) => <li>it's {i}</li>)}.

  • #11440 b88f1ea Thanks @Princesseuh! - Fixed the children of a <script> or <style> inside an Astro expression being read as JSX. Their contents are text, so braces and comparisons no longer have to be escaped.

    {cond && <style>a { color: red }</style>}
{cond && <script>let x = {a: 1};</script>}

  • #11440 b88f1ea Thanks @Princesseuh! - Added support for template literal attribute values inside an Astro expression, such as {x && <C data-x=`t${x}` />}.

  • #11440 b88f1ea Thanks @Princesseuh! - Fixed unquoted attribute values being rejected inside an Astro expression, such as {x && <a class=foo maxlength=255 href=/about>go</a>}.

  • #11440 b88f1ea Thanks @Princesseuh! - Fixed a template literal nested inside ${} breaking the rest of an Astro file, such as const href = `/blog${page === 0 ? '' : `/${page + 1}`}`;.

  • #11440 b88f1ea Thanks @Princesseuh! - Fixed a quote inside a regex character class breaking the rest of an Astro file, such as const unsafe = /[/"]/;.

  • #11508 54f3a2e Thanks @dyc3! - Added the nursery rule useFlatMathMinMax. Because Math.min() and Math.max() accept any number of arguments, the rule reports unnecessary nested calls to the same method:

    Math.max(Math.max(a, b), c);

    The fix flattens this expression to Math.max(a, b, c).

  • #11585 c5c8315 Thanks @Netail! - Fixed #11475: noUnresolvedImports no longer reports Bun runtime built-in modules (bun, bun:bundle, bun:ffi, bun:jsc, bun:sqlite, bun:test).

  • #11368 52a57b3 Thanks @Austin1serb! - Fixed #6830: Biome now reports a diagnostic for excessively deep syntax instead of overflowing the native stack while releasing the parsed tree.

  • #11596 1fc42ed Thanks @dyc3! - Added the nursery rule noThisOutsideOfClass. The rule reports this outside class members and TypeScript functions with an explicit this parameter.

    function Person(name) {
    this.name = name;
}

  • #11555 2516335 Thanks @dyc3! - Fixed #11529, where noFloatingPromises missed unhandled Promise chains when the imported function's module belonged to an import cycle. Cyclic modules now preserve types for exports that do not participate in recursive type dependencies.

  • #11518 0fee70c Thanks @HarperZ9! - Fixed #11500: the formatter now prints the declare modifier before accessibility modifiers on class properties. private declare readonly name: string is now formatted as declare private readonly name: string, matching Prettier and TypeScript's canonical modifier order.

  • #11580 1277af2 Thanks @ematipico! - Fixed #5091: Biome no longer moves comments next to the < of a generic, which causes invalid TypeScript syntax:

    - Generic<// a comment
+ Generic<
+   // a comment

  • #11577 42995d2 Thanks @ematipico! - Fixed #4592. Biome no longer crashes while parsing malformed delete expressions.

  • #11590 67963b4 Thanks @ematipico! - Fixed #6427 so Grit plugins can use function = ... as a node argument.

  • #11600 a689cb5 Thanks @ematipico! - Fixed #6644: noUnusedVariables now recognizes all interface declarations in a TypeScript declaration-merging group when the interface is referenced.

    The following snippet no longer triggers the rule.

    interface Things {
    foo: string;
}

interface Things {
    bar: string;
}

export type Key = keyof Things;

interface Things {
    baz: string;
}

  • #11591 d4a0716 Thanks @ematipico! - Fixed #6615. noDuplicateProperties no longer reports declarations nested in block at-rules as duplicates of declarations in their parent block.

  • #11492 f2a07aa Thanks @santichausis! - Fixed #11454: noMisplacedAssertion now recognises @fast-check/vitest's test.prop(...) (and .concurrent.prop, .skip.prop, etc.) as a test function, the same way it already recognises test.each. The JS formatter picks up the same recognition, so a curried test.prop(...)(...) call is now formatted with the regular breakable argument layout used for test.each/test.for, instead of the single-line-hugging layout used for plain it/test calls.

    For example, Biome no longer reports the assertion below as misplaced:

    import { fc, test } from "@fast-check/vitest";

test.prop([fc.string()])("round-trips", (s) => {
  expect(s).toBe(s);
});

  • #11589 65742b3 Thanks @ematipico! - Fixed #4928: noUnusedVariables no longer reports a value declaration as unused when its merged namespace is referenced.

  • #11559 472dbc2 Thanks @levrik! - Fixed a false positive in noVueDuplicateKeys where a <script setup> variable initialized from props was reported as a duplicate of the prop it derives from. Biome now exempts any variable whose initializer references props, instead of only recognizing defineProps() and toRefs(props).

    For example, Biome no longer reports foo below as a duplicate key:

    <script setup>
import { toRef } from 'vue';
const props = defineProps(['foo']);
const foo = toRef(props, 'foo');
</script>

  • #11594 6586ceb Thanks @ematipico! - Fixed #6640. Biome no longer crashes when linting malformed for...of statements.

  • #11571 85b197d Thanks @ematipico! - Fixed #10838: useSortedAttributes no longer corrupts JSX attributes when nested JSX elements also require sorting.

  • #11533 97e76c0 Thanks @ematipico! - Fixed #11520, where the Biome scanner would start analysing dependencies multiple times, leading to long and unresponsive sessions.

  • #11564 18a0e1f Thanks @Netail! - Fixed the diagnostic range of noInferrableTypes so it now highlights only the type instead of including the leading : colon, spaces and comments.

  • #11540 124fdaa Thanks @ematipico! - Fixed #11537: noShorthandPropertyOverrides now compares declarations only within the same block. The rule no longer reports @supports feature queries and correctly checks nested, @keyframes, and @page blocks.

  • #11532 7ceb0ee Thanks @dyc3! - Fixed #11528: noFloatingPromises no longer reports statement-level await expressions that handle Promise values, including overloaded calls returning Promise aliases. Awaited values that resolve to arrays of Promises remain reported because their element Promises are not handled by await.

  • #11474 3c6412e Thanks @dyc3! - Fixed #10241. Biome no longer reports unsupported text expression diagnostics for double-curly text in vanilla HTML, and the formatter preserves adjacent curly-brace text.

  • #11593 6c7fd27 Thanks @dyc3! - Added the nursery rule noVueDeprecatedScopedSlots. It reports deprecated $scopedSlots references in Vue templates and component objects, and offers an unsafe replacement with $slots. For example, Biome now reports this.$scopedSlots.default inside a Vue component.

  • #11440 b88f1ea Thanks @Princesseuh! - Fixed the formatter crashing on an Astro or Svelte expression spanning several lines in a file with CRLF line endings, such as <p>{a +\r\n b}</p>.

  • #11581 f4e5ebb Thanks @dyc3! - Added the nursery rule useModernMathApis. The rule reports legacy mathematical patterns that have direct modern Math equivalents.

    Math.sqrt(a * a + b * b);

  • #11597 a20f44a Thanks @Netail! - Added the nursery rule noBunModules, which forbids the use of Bun builtin modules (e.g. bun:sqlite, bun:ffi).

  • #11545 7d54688 Thanks @dyc3! - Fixed #11542: Biome now reports HTML comments between Svelte tag attributes as parse errors.

  • #11582 b6611dd Thanks @ematipico! - Fixed #3862. Biome now parses legacy Internet Explorer filter and -ms-filter values such as progid:DXImageTransform... and alpha(opacity=40).

  • #11575 65da251 Thanks @dyc3! - Improved the Tailwind parser's ability to recover from parsing failures. Whitespace now always allows the parser to recover and start parsing a new class.

  • #11576 0f78499 Thanks @ematipico! - Fixed #3515 and #10395, where Biome could corrupt Unicode characters while writing source received through standard input to standard output. Characters such as ⚠ and ✔ are now preserved.

  • #11539 0fca643 Thanks @ematipico! - Fixed #11512, where style/noDescendingSpecificity missed lower-specificity selectors after a later higher-specificity selector with the same tail selector.

  • #11544 040f867 Thanks @dyc3! - Fixed #11541: formatting a Svelte render tag followed by an HTML comment no longer duplicates the comment.

     <div>
   {@render children?.()}
   <!-- comment -->
-  <!-- comment -->
 </div>

  • #11565 ee69e0e Thanks @ematipico! - Fixed #11525. Now the configuration schema correctly provides auto-completion for linter domains.

  • #11583 b19390c Thanks @dyc3! - Fixed #11352: useExplicitLengthCheck no longer reports length-like properties used as value-producing || fallbacks or optional chains, and it no longer offers fixes for value-producing && checks or unsafe negations.

  • #11562 753e955 Thanks @ematipico! - Fixed an issue where the Biome Language Server would start with logging level set to debug. This would cause logs to grow exponentially in long sessions.

  • #11217 7d3ee9c Thanks @dyc3! - Fixed handling of biome-ignore format suppression comments on TypeScript declared class properties with string literal names.

    class A {
	declare /* biome-ignore format: exercise suppression checking */ 'a-b': 0;
}

  • #11497 f5d7896 Thanks @dyc3! - Added the noInvalidFileInputAccept nursery rule. The rule reports invalid literal accept values on file inputs in JSX and HTML, and normalizes common mistakes.

    <input type="file" accept="image/jpg" />

  • #11345 ac58958 Thanks @jakeleventhal! - Improved type inference performance by avoiding resolution of unused members in object arguments.

  • #11554 2d55931 Thanks @Netail! - Added the new nursery rule useReactNamingConvention, which enforces naming conventions for React values assigned from createContext, useId, and useRef. A value from createContext must be a PascalCase component name ending with Context, a value from useId must be named id or end with Id, and a value from useRef must be named ref or end with Ref.

  • #11491 1d6210b Thanks @dyc3! - Added the nursery rule noUnmodifiedLoopCondition, which reports variables in loop conditions that are never modified in the loop.

    let node = getNode();
while (node) {
    process(node);
}
What's Changed
New Contributors

Full Changelog: https://github.com/biomejs/biome/compare/@biomejs/biome@2.5.11...@biomejs/biome@2.5.12

View originalPermalink
How 2.5.12 went
2.5.11

Biome CLI v2.5.11

Added 1
  • Added noAstroSetHtmlDirective nursery rule to disallow Astro's set:html directive because untrusted content can introduce cross-site scripting vulnerabilities
Fixed 11
  • useValidAnchor now treats Astro JSX shorthand attributes like <a {href}> as a valid href
  • Adjacent elements inside an Astro expression now parse as an implicit fragment instead of raising an error
  • Astro templates now accept unclosed HTML void elements such as {cond && <br>}
  • noUnusedVariables no longer reports Vue <script setup> bindings used by CSS v-bind() as unused
  • Files passed through --stdin-file-path now use full HTML support for Astro, Svelte, and Vue when it is enabled
  • noVueRefAsOperand now tracks Vue refs through declaration aliases and toRefs() properties, recognizes useTemplateRef() results, and eliminates false positives

From Biome

2.5.11
Patch Changes

  • #11499 9743d0c Thanks @scs0209! - Fixed #11496: useValidAnchor now treats Astro JSX shorthand attributes like <a {href}> as a valid href.

  • #11437 88f805e Thanks @Princesseuh! - Fixed #9944: adjacent elements inside an Astro expression now parse as an implicit fragment instead of raising an error.

    {options.map(() =>
  <div />
  <div />
)}

  • #11437 88f805e Thanks @Princesseuh! - Fixed Astro templates rejecting unclosed HTML void elements, such as {cond && <br>}.

  • #11507 e2fc036 Thanks @dyc3! - Fixed #11157: noUnusedVariables no longer reports Vue <script setup> bindings used by CSS v-bind() as unused.

  • #11398 afc4615 Thanks @dyc3! - Fixed #11389: Files passed through --stdin-file-path now use full HTML support for Astro, Svelte, and Vue when it is enabled.

  • #11526 372cd68 Thanks @dyc3! - Fixed noVueRefAsOperand to track Vue refs through declaration aliases and toRefs() properties, and to recognize useTemplateRef() results. The rule no longer reports false positives such as plain ref transfers, plain toRefs() property access, defineModel() modifiers, or the supported .effect member as operands.

    The refactor enabling these fixes also improves the performance of the rule.

  • #11458 a7cd286 Thanks @dyc3! - Fixed #11436: GritQL snippets such as export { $specifiers } from $source now match named re-exports with aliases, inline type modifiers, and multiple specifiers.

  • #11515 382b15d Thanks @dyc3! - Fixed #11390, where noFloatingPromises performed expensive full type inference for calls to non-Promise methods declared on third-party TypeScript classes. The rule now classifies those calls using targeted type information.

  • #11516 6f40e82 Thanks @levrik! - Fixed noVueRefAsOperand so it no longer reports a callback parameter (e.g. from .find(), .map()) as an unwrapped ref value just because it's nested inside a ref(), computed(), or similar call.

    const result = computed(() => list.find((item) => item.label === "a"));

    Previously, item here was incorrectly treated as a ref value because the rule attributed it to the outer computed() call.

  • #11495 496268d Thanks @Netail! - Fixed useGraphqlNamingConvention so it no longer reports GraphQL enum value definitions with comments & descriptions and now displays a more accurate diagnostic range.

  • #11407 6ef52b0 Thanks @1678092075! - Fixed #11214: noUnusedVariables no longer reports type parameters declared by non-default function overload signatures that have an implementation.

  • #11322 5c353e6 Thanks @jp-knj! - Added a new nursery rule noAstroSetHtmlDirective, which disallows Astro's set:html directive because untrusted content can introduce cross-site scripting vulnerabilities.

    For example, the following snippet triggers the rule:

    <div set:html={content} />

  • #11462 18883b7 Thanks @dyc3! - Fixed #10776: useVueHyphenatedAttributes no longer reports lowercase attribute names containing punctuation, such as pt:header:data-test-id and some_attr.

  • #11476 3270ca4 Thanks @dyc3! - Fixed #10330: Vue interpolation delimiters now stay attached to whitespace-sensitive element boundaries and adjacent inline siblings, wrapping their expression when needed to fit the configured line width. Interpolations followed by text now also converge after one formatting pass.

    -<v-btn v-if="store.state.user" variant="text" to="/my-rooms"
-  >{{ $t("nav.my-rooms") }}</v-btn
->
+<v-btn v-if="store.state.user" variant="text" to="/my-rooms">{{
+  $t("nav.my-rooms")
+}}</v-btn>

  • #11191 3e5367f Thanks @ematipico! - Added the nursery rule noUndeclaredCustomProperties, which reports references to custom properties that are not defined in available CSS, static HTML-like style attributes, or JSX string style attributes.

    For example, the following snippet triggers the rule:

    a { color: var(--undefined-color); }

  • #11435 7754894 Thanks @levrik! - Fixed: Variables and imports used as custom Vue directives are no longer reported as unused.

    For example:

    <script setup>
const vHighlight = {
  mounted: (element) => {
    element.style.color = "red";
  },
};
</script>

<template>
  <p v-highlight>Hello</p>
</template>

  • #11501 e6acded Thanks @aminya! - Improved the performance of useArraySortCompare by skipping type inference for calls to unrelated methods.

  • #11467 66b282c Thanks @dyc3! - Fixed #11464: Biome now parses parenthesized object literals returned from arrow functions when they contain a conditional expression and a nested arrow function.

  • #11456 db9aa2a Thanks @dyc3! - Fixed #10278: Marked the fix for noThisInStatic as unsafe by default.

  • #11502 652aedb Thanks @levrik! - noGlobalAssign no longer reports assignments to a Vue <script setup> binding from a template expression, when the binding's name happens to match a built-in global (e.g. open, parent, top).

    For example, this no longer triggers a diagnostic:

    <script setup>
const open = defineModel();
</script>

<template>
  <button @click="open = !open">Toggle</button>
</template>
What's Changed
New Contributors

Full Changelog: https://github.com/biomejs/biome/compare/@biomejs/biome@2.5.10...@biomejs/biome@2.5.11

View originalPermalink
How 2.5.11 went
2.5.10

Biome CLI v2.5.10

Added 1
  • Added support for Astro's fragment shorthand
Fixed 13
  • Fixed Astro rejecting JavaScript comments between attributes
  • Fixed a bare `<` in Astro text being treated as the start of a tag
  • Fixed an Astro expression holding only a comment being reported as a parse error
  • Fixed an empty Astro expression such as `<div>{}</div>` failing to parse
  • Fixed Astro expressions containing a comment failing to parse
  • Fixed an Astro frontmatter block being cut short by a closing tag inside a string or comment

From Biome

2.5.10
Patch Changes

  • #11403 8f7786f Thanks @Princesseuh! - Fixed Astro rejecting JavaScript comments between attributes.

    <div /* block comment */ class="something"></div>
<Component /* c */ client:load />

  • #11403 8f7786f Thanks @Princesseuh! - Fixed a bare < in Astro text being treated as the start of a tag, such as <p>5 < 6 and 7 > 6</p>. As in HTML, a < that cannot open a tag is text and needs no escaping.

  • #11438 3133ffa Thanks @Princesseuh! - Fixed #8294: an Astro expression holding only a comment is no longer reported as a parse error, which also stopped the whole file from being formatted.

    <div>{/* a note */}</div>
<div class={/* a note */}>x</div>

  • #11403 8f7786f Thanks @Princesseuh! - Fixed #9165: an empty Astro expression such as <div>{}</div> no longer fails to parse. Astro renders {} as nothing.

  • #11403 8f7786f Thanks @Princesseuh! - Fixed Astro expressions containing a comment failing to parse.

    <div>{/* block comment */ x}</div>
<div>{/* only a comment */}</div>

  • #11403 8f7786f Thanks @Princesseuh! - Added support for Astro's fragment shorthand.

    <>
  <p>a</p>
</>

  • #11403 8f7786f Thanks @Princesseuh! - Fixed an Astro frontmatter block being cut short by a closing tag inside a string or comment.

    ---
const a = "</script>";
// </script> in a comment
---

  • #11403 8f7786f Thanks @Princesseuh! - Fixed --- being read as an Astro frontmatter fence when markup precedes it. Astro only recognizes frontmatter at the very start of a file, so a file opening with a comment now has no frontmatter, and its --- lines are content.

    <!-- c -->
---
this is text, not frontmatter
---

  • #11403 8f7786f Thanks @Princesseuh! - Fixed an Astro frontmatter block ending early on a line that merely starts with a dash.

    ---
--count;
---

  • #11403 8f7786f Thanks @Princesseuh! - Fixed the children of an Astro element carrying is:raw being parsed as markup instead of raw text. This now also covers <script> and <style>, whose contents Astro emits verbatim rather than processing, so they are no longer linted as JavaScript or CSS.

    <article is:raw><% awesome %></article>
<script is:raw>{{ mustache }}</script>

  • #11403 8f7786f Thanks @Princesseuh! - Fixed Astro rejecting attribute names that start with a colon, such as :href.

  • #11403 8f7786f Thanks @Princesseuh! - Fixed the Astro parser failing to recover from a malformed closing tag such as <div></{<//, so that a later mistake is reported where it happens rather than cascading.

  • #11403 8f7786f Thanks @Princesseuh! - Fixed { inside an Astro <math> element opening an expression. MathML is foreign content where Astro parses no expressions, so LaTeX such as R^{2x} now survives as text. <svg> is unaffected.

  • #11403 8f7786f Thanks @Princesseuh! - Fixed {{ at the start of an Astro expression being read as an interpolation. Astro has no {{ }} syntax, so {{ a: 1 }} and <Comp a={{ b: 1 }} /> are object literals.

  • #11403 8f7786f Thanks @Princesseuh! - Fixed expressions inside an Astro <pre> or <textarea> being read as raw text. Astro parses both as ordinary elements, so their markup and interpolations are now parsed, and a variable used only inside one is no longer reported as unused.

    <pre>{value}</pre>
<textarea><div>{value}</div></textarea>

  • #11403 8f7786f Thanks @Princesseuh! - Added support for template literal attribute values in Astro, such as <div class=`a ${b} c`>.

  • #11403 8f7786f Thanks @Princesseuh! - Fixed Astro rejecting HTML5 unquoted attribute values that contain `, =, ' or ", such as <a href=a=b> and <a href=a'b>.

  • #11393 dec5a8f Thanks @1678092075! - Fixed #11207: useStrictMode no longer reports Vue event handlers such as @click="count++".

  • #11431 c065f99 Thanks @levrik! - Fixed #11429: Variables and imports used by Vue same-name bindings such as :disabled or v-bind:disabled are no longer reported as unused.

  • #11409 405dedb Thanks @ematipico! - Fixed a memory leak in the LSP server where memory usage kept growing over long editor sessions.

  • #11422 a51eff7 Thanks @dyc3! - Fixed #11416: Biome no longer crashes when parsing incomplete {let} or {const} declarations in Svelte files.

  • #11378 34b715c Thanks @Netail! - Added extra rule sources from @eslint/css. biome migrate eslint detects rules in your eslint configurations more reliably.

  • #11403 8f7786f Thanks @Princesseuh! - Fixed {#, {/, {: and {@ being read as Svelte block openings in every HTML-like file. They are now Svelte-only, so in HTML, Vue and Angular files a sequence such as {#if x} is ordinary text instead of a parse error.

  • #11443 8d45229 Thanks @ematipico! - Fixed #11390: noFloatingPromises no longer performs unnecessary type inference on call arguments when checking methods of non-generic class instances created with new.

  • #11425 9c2667b Thanks @dyc3! - Fixed #6426: GritQL plugins now match and rewrite metavariables embedded in quoted strings.

  • #11441 00317c3 Thanks @dyc3! - Improved performance of useNamedCaptureGroup, noMisplacedAssertion, noSkippedTests, noExportsInTest, noDuplicateTestHooks, noIdenticalTestTitle, useTestHooksInOrder, and useTestHooksOnTop.

What's Changed
New Contributors

Full Changelog: https://github.com/biomejs/biome/compare/@biomejs/biome@2.5.9...@biomejs/biome@2.5.10

View originalPermalink
How 2.5.10 went
2.5.9

Biome CLI v2.5.9

Added 3
  • Added a new nursery rule useNamedLayer which disallows anonymous cascade layers
  • Added the nursery rule useTailwindShorthandClasses, which suggests shorter Tailwind utility classes
  • Added the nursery rule useAstroClientOnlyDirectiveValue, which reports Astro client:only directives without an initializer
Changed 2
  • Expanded the environment variable metadata used by biome rage to include BIOME_BINARY, BIOME_LOG_FILE, and RUST_BACKTRACE
  • The HTML formatter now preserves meaningful blank lines in HTML, including spacing after elements with trailing spaces and blank lines between comment groups
Fixed 7
  • The CSS parser now recovers at declaration boundaries after bogus declarations, allowing subsequent valid declarations to be parsed
  • The lint/nursery/useExpect rule now recognizes Vitest Browser Mode expect.element() calls as assertions
  • The CSS parser now accepts Tailwind container-query variant names in @variant, such as @xl and @max-xl
  • The noUndeclaredVariables, noUnusedImports, and noUnusedVariables rules now correctly recognise exported variables and functions declared in one embedded script block as usable from a sibling script block in Svelte and Vue components
  • Fixed the HTML formatter's whitespace handling for marquee, noscript, video, audio, and object elements
  • The useGenericFontNames rule now treats math as a valid generic font family
  • The noComponentHookFactories rule now reports a use-prefixed variable only when a function is assigned to it directly

From Biome

2.5.9
Patch Changes

  • #11321 41386f3 Thanks @dyc3! - Fixed #11315: The CSS parser now recovers at declaration boundaries after bogus declarations, allowing subsequent valid declarations to be parsed.

  • #11248 57b197e Thanks @yanthomasdev! - Expanded the environment variable metadata used by biome rage to include BIOME_BINARY, BIOME_LOG_FILE, and RUST_BACKTRACE as well as reworded explanations for better readability.

  • #11377 a8798ea Thanks @Netail! - Added a new nursery rule useNamedLayer which disallows anonymous cascade layers.

    @layer {
  a {
    color: red;
  }
}

  • #11327 6771cf5 Thanks @dyc3! - The HTML formatter now preserves meaningful blank lines in HTML, including spacing after elements with trailing spaces and blank lines between comment groups.

     <div>
   <!-- first group -->
+
   <!-- second group -->
 </div>

  • #10312 ba8aa18 Thanks @dyc3! - Added the nursery rule useTailwindShorthandClasses, which suggests shorter Tailwind utility classes. For example, the rule suggests replacing w-4 h-4 with size-4.

  • #11333 715e0cd Thanks @kkkhs! - Fixed #11328: lint/nursery/useExpect now recognizes Vitest Browser Mode expect.element() calls as assertions.

  • #11343 9b98211 Thanks @johncarmack1984! - Fixed #11311: the CSS parser now accepts Tailwind container-query variant names in @variant, such as @xl and @max-xl. These previously produced a parse error and a noUnknownAtRules diagnostic.

    @variant @xl {
  div {
    background: red;
  }
}

  • #11220 3e8c488 Thanks @santichausis! - Fixed #9541: noUndeclaredVariables, noUnusedImports, and noUnusedVariables now correctly recognise exported variables and functions declared in one embedded <script> block as usable from a sibling <script> block, in Svelte's <script module>/<script> pair and Vue's non-setup <script> blocks.

    For example, Biome no longer reports greet as undeclared in the following Svelte component:

    <script module>
  export function greet() {
    console.log("Hello!");
  }
</script>

<script>
  greet();
</script>

  • #11300 36430eb Thanks @dyc3! - Fixed the HTML formatter's whitespace handling for marquee, noscript, video, audio, and object elements.

    - <marquee behavior="alternate"> This text will bounce </marquee>
+ <marquee behavior="alternate">This text will bounce</marquee>

  • #11299 6559e6c Thanks @jp-knj! - Added the nursery rule useAstroClientOnlyDirectiveValue, which reports Astro client:only directives without an initializer.

    For example, <Component client:only /> triggers the rule.

  • #11365 7529811 Thanks @MHJahanbakhsh! - Fixed #11229: The useGenericFontNames rule now treats math as a valid generic font family.

  • #11346 674f5f4 Thanks @Jayllyz! - Fixed #11335: noComponentHookFactories now reports a use-prefixed variable only when a function is assigned to it directly.

    function factory() {
  const useColors = true; // no longer reported
  const useStore = createStore({ count: 0 }); // no longer reported
  const useData = () => useState(null); // still reported
  return useColors;
}

  • #11334 c87c46a Thanks @zkasuran! - Fixed #11317: noSvgWithoutTitle no longer reports an svg that uses the boolean shorthand aria-hidden (equivalent to aria-hidden={true} in React).

  • #11364 13853b1 Thanks @ematipico! - Fixed a bug where useJsxKeyInIterable incorrectly flagged Astro files.

  • #11321 41386f3 Thanks @dyc3! - Fixed #11315: Invalid CSS declarations in HTML style attributes now produce parser diagnostics instead of causing a panic.

  • #11325 67c3bf0 Thanks @dyc3! - Fixed HTML text wrapping to account for the width of an adjacent closing tag, avoiding lines that exceed the configured width when the final word and tag must move together.

     <a-long-long-long-element
-  >foo bar foo bar foo bar foo bar foo bar foo bar foo bar</a-long-long-long-element
+  >foo bar foo bar foo bar foo bar foo bar foo
+  bar</a-long-long-long-element
 >

  • #11367 fe5b5d4 Thanks @ematipico! - Fixed TypeScript compilerOptions.paths resolution when mapping targets omit ./. Biome now resolves these targets relative to their configured path base.

  • #11316 17e48d6 Thanks @wanxiankai! - Fixed #11289: the safe fix for noExtraBooleanCast now preserves parentheses around nested conditional expressions.

  • #11254 d25d113 Thanks @dyc3! - Fixed #11242: Biome no longer crashes with an access violation when analysing files on Windows ARM64.

  • #11221 85aac73 Thanks @freeatnet! - Added the nursery rule noUnsafeTypeAssertion, which disallows TypeScript type assertions while allowing const assertions.

    const value = input as SomeType;

  • #11314 7ffb677 Thanks @ematipico! - Fixed #11310: Restored the performance of noMisusedPromises and noFloatingPromises when analyzed expressions share deep imported type paths.

  • #11356 6cd3263 Thanks @johncarmack1984! - The Tailwind parser now understands modifiers on bare utilities (@container/sidebar, shadow/50).

  • #11318 76059e9 Thanks @johncarmack1984! - The Tailwind parser now understands container-query variants (@sm:, @max-lg:, @min-[400px]:) and child and descendant variants (*:, **:).

  • #11357 faa2074 Thanks @johncarmack1984! - The Tailwind parser now accepts the legacy leading ! important marker (!flex, hover:!p-4).

  • #11344 f34e15c Thanks @johncarmack1984! - The Tailwind parser now understands combinator selectors in arbitrary variants (has-[>svg]:, has-[+p]:), modifiers on variants (group-hover/menu:, @sm/main:), and arbitrary container-query sizes (@[400px]:).

  • #11324 2f5d452 Thanks @dyc3! - Fixed HTML formatting that inserted rendered whitespace between an element and touching text when the line wrapped.

      <div>
-   before<meter value=".5"></meter>
-   after
+   before<meter value=".5"></meter
+   >after
  </div>

  • #11312 e65f07e Thanks @xosnos! - Added a new nursery rule useControlLabel for both HTML and JSX, which reports interactive control elements (button, menuitem) without an accessible label.

    <button />

  • #11364 13853b1 Thanks @ematipico! - Fixed SVG parsing for files with an XML declaration followed by a PUBLIC doctype, such as <?xml version="1.0"?><!DOCTYPE svg PUBLIC "a" "b">.

  • #11301 610ee28 Thanks @dyc3! - Fixed parent tag wrapping when an HTML element starts or ends with a block-like or hidden child such as source, track, or param.

    - <video src="brave.webm"><track kind="subtitles" src="brave.en.vtt"></video>
+ <video src="brave.webm">
+   <track kind="subtitles" src="brave.en.vtt">
+ </video>
What's Changed
New Contributors

Full Changelog: https://github.com/biomejs/biome/compare/@biomejs/biome@2.5.8...@biomejs/biome@2.5.9

View originalPermalink
How 2.5.9 went
2.5.8

Biome CLI v2.5.8

Added 3
  • Add a new nursery rule useReactCompiler which reports diagnostics from React Compiler lint mode
  • Add the nursery rule noSvelteLegacyConst which disallows legacy Svelte {@const} tags and recommends declaration tags with $derived()
  • Add the nursery rule noInvalidPropertyInitValue which reports an @property whose initial-value does not match its syntax descriptor
Changed 4
  • Improve performance of noImportCycles
  • Parse HTML style attribute values as CSS and apply all Biome CSS lint rules to style attributes
  • Improve the diagnostic emitted by noRootType
  • Improve the performance of noMisusedPromises when analyzing async class methods that call other methods through this
Fixed 6
  • Fix useAwait to no longer report async functions that contain an await using declaration
  • Fix noUselessUndefined to no longer report return undefined when the enclosing function has a return type annotation other than undefined or void
  • Fix CSS block comments between a declaration colon and value to preserve their source indentation
  • Fix CSS formatting to keep comments inside functional pseudo-classes and pseudo-elements instead of moving them before the function name
  • Fix Svelte files failing to parse when an expression begins with an object literal
  • Fix JavaScript GritQL patterns with multiple metavariables to match snippets consistently in WebAssembly

From Biome

2.5.8
Patch Changes

  • #10710 0a0fbc1 Thanks @dyc3! - Added a new nursery rule useReactCompiler, which reports diagnostics from React Compiler lint mode.

  • #11251 ea9dd8a Thanks @dyc3! - Improved performance of noImportCycles.

  • #11247 52b44d6 Thanks @dyc3! - Added the nursery rule noSvelteLegacyConst, which disallows legacy Svelte {@const} tags and recommends declaration tags with $derived().

    Invalid:

    {#each boxes as box}
  {@const area = box.width * box.height}
  <p>{area}</p>
{/each}

    Valid:

    {#each boxes as box}
  {const area = $derived(box.width * box.height)}
  <p>{area}</p>
{/each}

  • #11252 d5f5704 Thanks @Turtle-Hwan! - Fixed #11250: useAwait no longer reports async functions that contain an await using declaration.

  • #11143 6be7be1 Thanks @vznh! - Fixed #11017: noUselessUndefined no longer reports return undefined when the enclosing function has a return type annotation other than undefined or void.

  • #11234 caefe39 Thanks @subotac! - Fixed #11228: CSS block comments between a declaration colon and value now preserve their source indentation.

     :root {
   --font-stack:
-/* comment */
+    /* comment */
     system-ui;
 }

  • #11285 bca1f73 Thanks @denbezrukov! - Fixed #11280: CSS formatting keeps comments inside functional pseudo-classes and pseudo-elements instead of moving them before the function name.

    -:/* comment */ where(div) {}
+:where(/* comment */ div) {}

  • #11080 af16a0b Thanks @dyc3! - HTML style attribute values are now parsed as CSS. All Biome CSS lint rules are applied to the style attributes.

  • #11195 6a85588 Thanks @dyc3! - Fixed Svelte files failing to parse when an expression begins with an object literal.

    Now the following snippet is correctly parsed:

    <p>{{ a: true }}</p>
<div class={{ active: isActive }}></div>

  • #11173 481d008 Thanks @Austin1serb! - Fixed #10242: JavaScript GritQL patterns with multiple metavariables now match snippets consistently in WebAssembly.

  • #11187 23c0369 Thanks @ematipico! - Added the nursery rule noInvalidPropertyInitValue, which reports an @property whose initial-value does not match its syntax descriptor. For example, the following declaration triggers the rule because red is not a <length>:

    @property --size {
  syntax: "<length>";
  inherits: false;
  initial-value: red;
}

  • #11272 73896e6 Thanks @ematipico! - Improved the diagnostic emitted by noRootType.

  • #11240 bd0b68d Thanks @ematipico! - Fixed #11223: Improved the performance of noMisusedPromises when analyzing async class methods that call other methods through this.

  • #11172 4a0bc5c Thanks @saberoueslati! - Fixed #10806: noUselessFragments no longer causes Biome to panic when its unsafe fix removes a fragment used as a JSX attribute value.

  • #11227 4d603b0 Thanks @saberoueslati! - Fixed #11178: noUndeclaredVariables no longer reports Vue's built-in instance properties, such as $slots and $attrs, in template expressions or $event in inline event-handler expressions. The instance properties are still reported inside <script setup>, where they are not defined.

  • #11187 23c0369 Thanks @ematipico! - Fixed CSS parsing of registered custom properties: Biome now correctly validates the syntax descriptor of @property rules.

What's Changed
New Contributors

Full Changelog: https://github.com/biomejs/biome/compare/@biomejs/biome@2.5.7...@biomejs/biome@2.5.8

View originalPermalink
How 2.5.8 went
2.5.7

Biome CLI v2.5.7

Added 3
  • Added the option ignoreIfStatements to useNullishCoalescing rule
  • Added a new nursery rule noExtendNative which reports extending the prototype of a built-in object
  • Added the nursery rule noTailwindArbitraryValue to report Tailwind CSS arbitrary values in HTML/JSX class attributes, configured utility functions, and tagged templates
Changed 1
  • Changed HTML formatter to lay out the srcset attribute of img and source as a list of candidates with proper alignment
Fixed 6
  • Fixed noUnknownPseudoClass to recognize Vue's :deep() pseudo-class inside .vue style blocks
  • Fixed CLI stdin mode to correctly use nested configurations when handling files with --stdin-file-path in projects with nested biome.json files
  • Fixed noUnnecessaryConditions to choose the same function overload as TypeScript when an argument is a callback
  • Fixed noUnnecessaryConditions to no longer report optional chains and nullish coalescing whose receiver can be nullish
  • Fixed HTML formatter to preserve the configured trailing newline when a file ends with a comment
  • Fixed suppression comments for noPositiveTabindex to suppress the rule in HTML files when element attributes span multiple lines

From Biome

2.5.7
Patch Changes

  • #10822 c171b3b Thanks @pkallos! - Added the option ignoreIfStatements to useNullishCoalescing. Biome now flags if statements that only assign to a nullish variable (such as if (!a) { a = b }) and can rewrite them to ??=. When enabled, Biome ignores those if statements.

  • #11136 e63354c Thanks @AkashNaickar! - Added a new nursery rule noExtendNative, which reports extending the prototype of a built-in object.

  • #10094 e007143 Thanks @THEjacob1000! - Added the nursery rule noTailwindArbitraryValue. Biome now reports Tailwind CSS arbitrary values such as w-[400px], including in HTML/JSX class attributes, configured utility functions, and tagged templates.

  • #11184 135f476 Thanks @subotac! - Fixed #11176: noUnknownPseudoClass now recognizes Vue's :deep() pseudo-class inside .vue style blocks.

  • #8239 a519f9d Thanks @cormacrelf! - Fixed #8233, where Biome CLI in stdin mode didn't work correctly when handling files in projects with nested configurations. For example, with the following structure, --stdin-file-path=subdirectory/... would not use the nested configuration in subdirectory/biome.json:

    ├── biome.json
└── subdirectory
    ├── biome.json
    └── lib.js

    biome format --write --stdin-file-path=subdirectory/lib.js < subdirectory/lib.js

    Now, the nested configuration is correctly picked up and applied.

    In addition, Biome now shows a warning if --stdin-file-path is provided but that path is ignored and therefore not formatted or fixed.

  • #11138 8c2c6bd Thanks @ematipico! - Fixed noUnnecessaryConditions: Biome now chooses the same function overload as TypeScript when an argument is a callback, so conditions that were previously missed are reported.

    The following code is now invalid, because a parameter typed () => void accepts an async callback and schedule therefore returns string:

    declare function schedule(handler: () => void): string;
declare function schedule(handler: () => Promise<void>): string | undefined;

schedule(async () => {}) ?? "fallback";

    The following code is also now invalid, because map(() => 42) returns 42:

    type Mapper<T> = () => T;
declare function map<T>(mapper: Mapper<T>): T;

map(() => 42) || flag;

  • #11138 8c2c6bd Thanks @ematipico! - Fixed #11087: noUnnecessaryConditions no longer reports optional chains and nullish coalescing whose receiver can be nullish.

    For example, the optional chain and fallback in the following code are no longer reported:

    declare const usage: { range: { startDate: string } } | null;
const startDate = usage?.range.startDate ?? "N/A";

  • #11118 9c16840 Thanks @subotac! - Fixed #11098: The HTML formatter now preserves the configured trailing newline when a file ends with a comment.

    -<!-- trailing comment -->
\ No newline at end of file
+<!-- trailing comment -->

  • #11201 0e80610 Thanks @Bishwas-py! - Fixed #11182: suppression comments for noPositiveTabindex now suppress the rule in HTML files when the attributes of the element span multiple lines.

  • #11079 607afd2 Thanks @dyc3! - The HTML formatter now lays out the srcset attribute of <img> and <source> as the list of candidates it is. Runs of whitespace between candidates collapse, and once the list no longer fits on one line each candidate goes on its own line with the descriptors aligned:

    - <img srcset="/visual@0.5.png  400w, /visual.png 805w, /visual@2x.png 1610w, /visual@3x.png 2415w" />
+ <img
+   srcset="
+     /visual@0.5.png  400w,
+     /visual.png      805w,
+     /visual@2x.png  1610w,
+     /visual@3x.png  2415w
+   "
+ />

  • #11156 fed72c7 Thanks @saberoueslati! - Fixed #11129: noUnusedVariables no longer reports Vue bindings as unused when they are assigned through automatically unwrapped template refs.

  • #11124 d890b39 Thanks @denbezrukov! - Fixed CSS formatting of line comments between a declaration colon and value to preserve their source indentation.

     .test {
   background:
-  /////// foo
-  // bar
+        /////// foo
+        // bar
     radial-gradient(circle, #000, transparent);
 }

  • #11113 3d8ab73 Thanks @denbezrukov! - Fixed CSS formatting of long block comments between comma-separated property values:

     .foo {
   box-shadow:
-    1000px /* long long long long long long long long long long long long comment */ 1000px /* long long long long long long long long long comment */ 2px color(srgb 0.555555555 0.555555555 0.555555555),
+    1000px
+      /* long long long long long long long long long long long long comment */
+      1000px /* long long long long long long long long long comment */ 2px
+      color(srgb 0.555555555 0.555555555 0.555555555),
     1px 1px black;
 }

  • #11127 da5c1a5 Thanks @dyc3! - The HTML formatter now picks the quote character for an attribute by counting the quotes in the value rather than looking only for a double quote. &apos; and &quot; count as the characters they stand for, and only the character that ends up as the delimiter stays escaped:

    - <div title='123 &apos;&quot; 456'></div>
+ <div title="123 '&quot; 456"></div>

    Entities that are not quotes, such as &amp; or &[#39](https://github.com/biomejs/biome/issues/39);, are left exactly as written.

  • #11193 77035bb Thanks @dyc3! - Fixed the HTML formatter collapsing the blank line between an element and the text that follows it. A blank line before text is now kept, the way one before another element already was:

      <div>foo</div>
-
  text

  • #11106 ad80f57 Thanks @dyc3! - The HTML formatter now writes the HTML5 doctype in lowercase, matching Prettier:

    - <!DOCTYPE html>
+ <!doctype html>

    This only applies to a plain .html file whose doctype stands alone. A doctype that names a DTD keeps the case it was written with, since the rest of the declaration is not lowercased either:

    <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">

    A .vue, .svelte, or .astro file keeps whatever the author wrote.

  • #11188 60679db Thanks @dyc3! - Fixed the HTML formatter printing a comment twice when it ended the line of the last element in a document:

    - text<!-- a --><!-- a -->
+ text<!-- a -->

  • #11077 4dcd0d9 Thanks @dyc3! - Fixed a bug where the HTML formatter collapsed the whitespace inside <textarea>, <xmp> and <plaintext>, changing what the page renders.

    - <textarea>
-  line one
- line two </textarea>
+ <textarea>line one line two</textarea>

    Biome now prints the content of these elements exactly as it appears in the source, matching the existing behavior for <pre>.

  • #11194 abfbb11 Thanks @dyc3! - Fixed the HTML formatter refusing to format a Svelte file containing an array pattern that skips a position:

    {#each animals as [, value]}
	<p>{value}</p>
{/each}

  • #10094 e007143 Thanks @THEjacob1000! - Fixed useSortedClasses to correctly detect unsorted classes in static member expression tagged templates (e.g. tw.div\...``). Previously, these were silently skipped due to surrounding whitespace trivia not being stripped from the tag name.

  • #11078 10da30e Thanks @dyc3! - Fixed Vue single-file components failing to parse when they contain a custom block such as <i18n> or <docs>, or a <template> written in another language. Their content is no longer read as HTML, so a block may hold whatever its own tooling expects:

    <docs>
This block is prose, and it may mention a `<my-component>` without closing it.
</docs>

<template lang="pug">
  .test
    #foo
</template>

    Previously both blocks produced a parse error and the whole file was left unformatted. Biome now prints their content unchanged while still formatting the opening tag.

  • #11231 4afd901 Thanks @ematipico! - Improved the performance of the following lint rules:

  • #11134 2fa0a62 Thanks @yanthomasdev! - Clarified the warning emitted when using the experimental json and json-pretty reporters.

  • #11198 ed88b13 Thanks @saberoueslati! - Fixed #11171: variables referenced only inside a Svelte attachment ({@attach ...}) are no longer reported as unused by noUnusedVariables and noUnusedImports.

  • #11155 6ee17ea Thanks @dyc3! - Improved performance when printing diagnostics to the console.

  • #11160 217f8ad Thanks @dyc3! - Improved the performance of noFloatingPromises by skipping type inference for assignment statements, which are always considered handled.

  • #11159 26c23d9 Thanks @saberoueslati! - Fixed #11144: noFloatingPromises no longer reports already-awaited optional Promise values.

  • #11138 8c2c6bd Thanks @ematipico! - Fixed #11121: noUnnecessaryConditions no longer reports conditions based on an inapplicable function overload.

    For example, the condition in the following code is no longer reported because query({}) selects the overload that returns boolean:

    declare function query(options: { initial: string }): { isPending: false };
declare function query(options: { initial?: string }): { isPending: boolean };

const { isPending } = query({});
isPending || fallback;

  • #11152 c4fc6a9 Thanks @dyc3! - Improved the performance of collecting rule timings with --profile-rules in heavily multithreaded environments.

  • #11128 4d3ff76 Thanks @ematipico! - Fixed #7635: noDeprecatedImports now detects deprecated ambient declarations that are exported separately.

  • #11117 01f7ef5 Thanks @subotac! - Fixed #11014: noDelete no longer reports process.env["FOO"] style property deletions.

  • #11168 9847e68 Thanks @saberoueslati! - Added the nursery rule noNonScalableViewport, which reports viewport metadata that disables user scaling with user-scalable=no.

    For example:

    <meta name="viewport" content="width=device-width, user-scalable=no" />

  • #11154 a1d6b1f Thanks @dyc3! - Improved the performance of noImportCycles by skipping graph traversals for imports that cannot be part of a cycle.

  • #11175 d96d6dd Thanks @ematipico! - Fixed CSS parsing of registered custom properties: Biome now correctly validates the syntax descriptor of @property rules.

What's Changed
New Contributors

Full Changelog: https://github.com/biomejs/biome/compare/@biomejs/biome@2.5.6...@biomejs/biome@2.5.7

View originalPermalink
How 2.5.7 went
2.5.6

Biome CLI v2.5.6

Changed 3
  • Improved accuracy of type-aware lint rules by resolving more inferred types, including floating Promises returned by aliased callbacks and arrays of Promises created by async mapping callbacks
  • HTML parser now accepts mixed-case doctype declarations
  • The rdjson reporter now populates the severity field of each diagnostic (ERROR, WARNING, or INFO)
Fixed 9
  • Fixed a performance regression in noMisusedPromises that caused type inference to run repeatedly while linting a file
  • Fixed CSS formatting for multiline function arguments preceded by comments
  • Fixed useHookAtTopLevel to no longer report hooks in named forwardRef components that receive a ref parameter
  • Fixed parsing of curried arrow functions in ternary consequents when the inner arrow's parameters use a destructuring pattern
  • Fixed noUselessTernary quick fix to preserve operator spacing when simplifying or inverting boolean ternary expressions
  • Fixed biome check --write to be idempotent on Svelte files where multi-line template literals in script blocks and block comments in style blocks were gaining extra indent levels on every run

From Biome

2.5.6
Patch Changes

  • #11035 0e4b03b Thanks @ematipico! - Fixed a performance regression in noMisusedPromises that caused type inference to run repeatedly while linting a file.

  • #11043 22ec076 Thanks @denbezrukov! - Fixed CSS formatting for multiline function arguments preceded by comments:

     .example {
   value: outer(
     1,
     /* comment */
     nested(
-      first,
-      second
-    )
+        first,
+        second
+      )
   );
 }

  • #11007 c9acb25 Thanks @BTF-Kabir-2020! - Fixed #9195: useHookAtTopLevel no longer reports hooks in named forwardRef components that receive a ref parameter.

  • #10152 50a9bd8 Thanks @Zelys-DFKH! - Fixed #10131: Biome now correctly parses curried arrow functions in ternary consequents when the inner arrow's parameters use a destructuring pattern, e.g. cond ? (x) => ({ a, b }) => body : alt.

  • #11105 8ffe2b9 Thanks @dadavidtseng! - Fixed #11092: The noUselessTernary quick fix now preserves operator spacing when simplifying or inverting boolean ternary expressions.

  • #10533 5809875 Thanks @Mokto! - Fixed #10515: biome check --write was not idempotent on Svelte files — multi-line template literals in <script> blocks and block comments in <style> blocks gained an extra indent level on every run.

  • #11040 0abb620 Thanks @Mokto! - Fixed an issue where the HTML formatter would duplicate a comment placed directly before a Svelte {@const ...} or {@debug ...} block. The duplication compounded on every subsequent --write, causing the file to grow exponentially.

  • #10858 6d18204 Thanks @ruidosujeira! - Fixed #10839: Svelte {#each} array destructuring no longer includes spaces inside square brackets, and multiline bind function expressions now indent their getter, setter, and function body correctly.

  • #11009 2c36626 Thanks @ematipico! - Improved the accuracy of type-aware lint rules by resolving more inferred types. For example, noFloatingPromises now detects floating Promises returned by aliased callbacks and arrays of Promises created by async mapping callbacks.

    The following statements are now reported:

    type AsyncCallback = () => Promise<void>;
declare const callback: AsyncCallback;
callback();

[1, 2, 3].map(async (value) => value);

  • #10973 9cb044c Thanks @ematipico! - Fixed false positives in noMisleadingReturnType when generic-constraint, normalization, substitution, or structural return-type comparison cannot complete. The rule now suppresses diagnostics rather than suggesting a return type derived from partial information. For example, this unresolved return type is no longer reported:

    function unresolvedReturnType(): MissingType {
  return "value" as const;
}

  • #11071 15047a2 Thanks @dyc3! - The HTML parser now accepts mixed-case doctype declarations.

  • #11030 cc90e65 Thanks @marschattha! - The rdjson reporter now populates the severity field of each diagnostic (ERROR, WARNING, or INFO), so tools consuming Reviewdog Diagnostic Format output no longer need to assume a default severity.

  • #11009 2c36626 Thanks @ematipico! - Fixed a performance regression in type-aware JavaScript lint rules by inferring only requested types and memoizing export resolution.

  • #11056 903b177 Thanks @dyc3! - Added support for Svelte declaration tags using let and const. Biome can now parse, format, and lint bindings declared in these tags.

  • #11045 89c27c6 Thanks @ematipico! - Improved the performance of Biome formatter up to ~7% across the board.

  • #9806 781d68d Thanks @dyc3! - Added the nursery rule noJsRestrictedProperties, which ports ESLint's no-restricted-properties rule. Biome now flags restricted member access and object destructuring, and biome migrate eslint preserves the rule's options.

What's Changed
New Contributors

Full Changelog: https://github.com/biomejs/biome/compare/@biomejs/biome@2.5.5...@biomejs/biome@2.5.6

View originalPermalink
How 2.5.6 went
2.5.5

Biome CLI v2.5.5

Fixed 11
  • Fixed useExhaustiveSwitchCases for unions of bigint literals to report missing bigint cases and compare bigint literals by value
  • Fixed false positives in noBaseToString and useNullishCoalescing when member, stringification, or nullish inference cannot complete
  • Fixed useSortedAttributes action no longer triggering for HTML instructions
  • Fixed noThenProperty failing to detect Object.fromEntries, Object.defineProperty, and Reflect.defineProperty calls with comments between their tokens
  • Fixed useAriaPropsSupportedByRole no longer reporting false positives for shorthand attributes that determine an element's implicit ARIA role
  • Fixed CSS formatter casing for syntax-owned names while preserving author-defined names, including scoped keyframes and container scroll-state queries

From Biome

2.5.5
Patch Changes

  • #10972 ab8c21b Thanks @ematipico! - Fixed useExhaustiveSwitchCases for unions of bigint literals. The rule now reports missing bigint cases and compares bigint literals by value, including binary, octal, hexadecimal, and separator-containing spellings. For example, this switch now reports the missing 2n case:

    declare const value: 1n | 2n;
switch (value) {
  case 1n:
    break;
}

  • #10972 ab8c21b Thanks @ematipico! - Fixed false positives in noBaseToString and useNullishCoalescing when member, stringification, or nullish inference cannot complete. These rules now suppress diagnostics instead of reporting from partial type information. For example, neither expression is reported when a recursive type cannot be fully resolved:

    type Recursive = Recursive;
declare const value: Recursive;

String(value);
value || "fallback";

  • #10977 0bf7486 Thanks @ematipico! - Fixed #10922: the action useSortedAttributes no longer triggers for HTML instructions.

  • #10957 cf263c4 Thanks @dyc3! - Fixed noThenProperty failing to detect Object.fromEntries, Object.defineProperty, and Reflect.defineProperty calls with comments between their tokens.

  • #10983 edc0ed7 Thanks @ayaangazali! - Fixed #10980: useAriaPropsSupportedByRole no longer reports false positives when the attribute that determines an element's implicit ARIA role is written as a shorthand attribute, such as <a {href} aria-label="..."> in Astro and Svelte files.

    Shorthand attributes are now taken into account when computing the implicit role, so the anchor above correctly resolves to the link role instead of generic.

  • #10889 89526e3 Thanks @denbezrukov! - Fixed CSS formatter casing for syntax-owned names while preserving author-defined names, including scoped keyframes and container scroll-state queries.

    - A:HOVER { COLOR: INITIAL; }
+ A:hover { color: initial; }
- @KEYFRAMES :GLOBAL KeepFrames { FROM { COLOR: RED; } }
+ @keyframes :GLOBAL KeepFrames { from { color: RED; } }
- @CONTAINER scroll-state((SCROLLED: TOP) AND (STUCK)) { A:HOVER { COLOR: RED; } }
+ @container scroll-state((SCROLLED: TOP) AND (STUCK)) { A:hover { color: RED; } }

  • #10964 794ccd0 Thanks @denbezrukov! - Fixed CSS formatting for comments between declaration values and !important.

    -a { color: /* before */ /* after */ red !important; }
+a { color: /* before */ red /* after */ !important; }

  • #10993 b7a9694 Thanks @denbezrukov! - Fixed the CSS formatter to preserve comments on the correct side of selector combinators and before declaration blocks.

    -.before > /* comment */ .after {}
+.before /* comment */ > .after {}

    It now also keeps selectors with escaped newlines in attribute values inline when they fit.

    -div
-  span[foo="bar\
+div span[foo="bar\
 value"] {}

  • #10978 8ebafe1 Thanks @ematipico! - Fixed #10870: noUnresolvedImports no longer reports false positives such as import type { NextRequest } from "next/server".

  • #10901 68c10e6 Thanks @Socialpranker! - Fixed #10622: the HTML/Vue parser no longer panics on the argument-less v-bind shorthand (:="props").

    This syntax is valid Vue and equivalent to v-bind="props", so the parser now accepts it (along with the longhand v-bind:="props") instead of crashing while building a diagnostic for a missing argument.

  • #10936 7df46f5 Thanks @ematipico! - Improved generic tuple inference for useIncludes. The rule now recognizes specialised tuple element types returned through generic aliases.

  • #10941 f787725 Thanks @siketyan! - Fixed #10855: Biome now supports parsing and formatting CSS custom media queries declared with @custom-media.

  • #10969 72d309b Thanks @ematipico! - Fixed an issue where Biome logs became too verbose, dumping information not relevant to user's operations.

  • e62f6b6 Thanks @ematipico! - Fixed #10963: Biome no longer panics when a type-aware rule such as noFloatingPromises checks a call to a function with multiple call signatures imported from another module.

  • #10931 899c60d Thanks @ematipico! - Fixed check --write command. Now the command reports code frame of the formatted code, if the formatter is enabled.

  • #10904 ceee4f4 Thanks @qzwxsaedc! - Fixed #10892: noUnnecessaryConditions no longer reports a false positive when checking a member of a discriminated union that is accessed through a default type-only namespace import. The following code is no longer flagged:

    import type Types from "./types";

declare function parse(): Types.Result<string>;
const result = parse();
if (!result.success) {
}

  • #10962 f0a67f2 Thanks @ematipico! - Biome no longer removes embedded styles and scripts in HTML files.

  • #11000 5039a1e Thanks @ematipico! - Fixed a bug where closing one editor stopped a shared Biome daemon used by other editors. LSP proxy processes now exit when either the editor or daemon disconnects.

  • #10957 cf263c4 Thanks @dyc3! - Improved the performance of the noThenProperty lint rule by about 50%.

  • #10992 4bf9b21 Thanks @ematipico! - Fixed noMisusedPromises: The rule now reports Promise-returning callbacks where a synchronous callback is expected when calls use tuple spreads or tuple rest parameters, including generic and deeply nested tuples, and when constructor signatures come from interface or object types. Recursive or excessively nested tuple spreads use a conservative fallback so analysis terminates.

    For example, the following callback is now reported.

    declare function consume(...args: [number, () => void]): void;
const prefix: [number] = [1];

consume(...prefix, async () => {});

  • #10915 b3b12b3 Thanks @Functionhx! - Added the rule noNegationInEqualityCheck. The rule flags negated expressions on the left side of strict equality checks like !foo === bar — due to operator precedence this evaluates as (!foo) === bar which is almost always a mistake for foo !== bar.

    The rule provides an unsafe fix that flips the operator.

    // Invalid
!foo === bar;
!foo !== bar;

// Valid
foo !== bar;
foo === bar;

  • #10970 bd1038b Thanks @ematipico! - Improved overload selection for noMisusedPromises. Biome now handles overloaded calls, overloaded constructors, rest parameters, union arguments, and generic constraints without selecting an incompatible signature. For example, noMisusedPromises now reports the async callback passed to the synchronous overload:

    declare function consume(kind: "async", callback: () => Promise<void>): void;
declare function consume(kind: "sync", callback: () => void): void;
consume("sync", async () => {});

  • #10933 48a4abb Thanks @ematipico! - Fixed useArrayFind to recognize bigint zero indexes.

  • #10931 899c60d Thanks @ematipico! - Fixed an orchestration issue that could lead to deadlocks when type-aware rules are enabled.

  • #10969 72d309b Thanks @ematipico! - Hardened the Biome Language Server by improving its synchronisation logic.

  • #10972 ab8c21b Thanks @ematipico! - Fixed false positives in noMisusedPromises and useAwaitThenable when Promise or thenable inference cannot complete. These rules now suppress diagnostics instead of treating incomplete type information as a definite result. For example, useAwaitThenable no longer reports await value when the value's thenability is unknown:

    declare const value: unknown;

async function consume() {
  await value;
}
What's Changed
New Contributors

Full Changelog: https://github.com/biomejs/biome/compare/@biomejs/biome@2.5.4...@biomejs/biome@2.5.5

View originalPermalink
How 2.5.5 went
2.5.4

Biome CLI v2.5.4

Added 2
  • Basic block properties support for YAML formatting
  • Inference engine via salsa
Changed 3
  • Improved the performance of the HTML parser slightly in synthetic benchmarks
  • useSortedClasses now sorts important-suffix classes in sort_v4
  • HTML/SVG tag names now use keywords for better performance
Fixed 11
  • On-type formatting no longer moves comments before an if statement into its body
  • noLabelWithoutControl now correctly detects text interpolation in Astro, Svelte & Vue as valid accessible content
  • Svelte directives no longer throw an accidental debug log
  • biome check --write --unsafe no longer hangs forever when applying the noCommentText code fix
  • Prevented a module-inference regression introduced by a housekeeping change
  • Biome now breaks the arguments of curried test.each, it.each, describe.each, and test.for calls when they exceed the configured line width

From Biome

2.5.4
Patch Changes

  • #10665 55ff995 Thanks @dyc3! - Improved the performance of the HTML parser slightly in our synthetic benchmarks.

  • #10894 f4fb10e Thanks @ematipico! - Fixed #6392: On-type formatting no longer moves comments before an if statement into its body.

  • #10939 f2799db Thanks @Netail! - Fixed #10930: noLabelWithoutControl now correctly detects text interpolation in Astro, Svelte & Vue as valid accessible content.

  • #10945 ae15d98 Thanks @Netail! - Fixed #10942: Svelte directives don't throw an accidental debug log anymore.

  • #10842 5e1abfe Thanks @JamBalaya56562! - Fixed #9196: biome check --write --unsafe no longer hangs forever when applying the noCommentText code fix.

    The rule's fix now wraps the comment in a real JSX expression container ({/* comment */}) instead of re-inserting the braces as plain JSX text, so the fixed code is no longer reported again by the same rule.

  • #10891 ecca79e Thanks @ematipico! - Fixed #10885: prevented a module-inference regression introduced by a housekeeping change.

  • #10886 60c8043 Thanks @dyc3! - Fixed #10727: Biome now breaks the arguments of curried test.each, it.each, describe.each, and test.for calls when they exceed the configured line width.

    - test.each([[1, 2]])("a description that is long enough to push the hugged opening line beyond the print width", (a, b) => {
-   expect(a).toBe(b);
- });
+ test.each([[1, 2]])(
+   "a description that is long enough to push the hugged opening line beyond the print width",
+   (a, b) => {
+     expect(a).toBe(b);
+   },
+ );

  • #10895 01a85f0 Thanks @ematipico! - Biome will now remove stale Unix daemon sockets from older Biome versions when starting a newer daemon.

What's Changed

Full Changelog: https://github.com/biomejs/biome/compare/@biomejs/biome@2.5.3...@biomejs/biome@2.5.4

View originalPermalink
How 2.5.4 went
2.5.3

Biome CLI v2.5.3

Added 1
  • The useDomQuerySelector rule now supports an ignore option for receiver identifiers that should not be reported
Changed 1
  • Improved type-aware lint rule inference for built-in globals and indexed function calls
Fixed 10
  • Biome now recovers when unsupported CSS Modules @value rules or scoped @keyframes names end at EOF
  • Fixed noUnusedVariables false positives in Svelte files for store subscriptions and bindable props that are only written to
  • The noUnsafeOptionalChaining rule now reports unsafe optional chains wrapped in TypeScript as, satisfies, type assertion, and instantiation expressions
  • The useVueValidVOn rule no longer reports a missing handler for v-on directives using a verb modifier without an expression and accepts the arg-less object syntax
  • Biome Language Server no longer goes in deadlock when the scanner is enabled
  • Astro shorthand attribute syntax is now correctly being parsed from embedded nodes

From Biome

2.5.3
Patch Changes

  • #10815 86613d5 Thanks @WaterWhisperer! - Fixed a parser panic reported in #10708: Biome now recovers when unsupported CSS Modules @value rules or scoped @keyframes names end at EOF.

  • #10534 da9b403 Thanks @Mokto! - Fixed noUnusedVariables false positives in Svelte files: Svelte store subscriptions ($store references in templates now keep the underlying store binding from being flagged), and $bindable() props that are only written to in the script block (write-only is intentional for bindable props) are no longer reported as unused.

  • #10827 098ba41 Thanks @Aqu1bp! - Fixed #10698: The noUnsafeOptionalChaining rule now reports unsafe optional chains wrapped in TypeScript as, satisfies, type assertion, and instantiation expressions, such as new (value?.constructor as Constructor)().

  • #10773 3c6513d Thanks @otkrickey! - Fixed #10772: useVueValidVOn no longer reports a missing handler for v-on directives using a verb modifier (.stop / .prevent) without an expression, e.g. <div @click.stop></div>. The rule also accepts the arg-less object syntax <div v-on="$listeners"></div> instead of reporting a missing event name.

  • #10721 d83c66b Thanks @minseong0324! - Improved type-aware lint rule inference for built-in globals and indexed function calls. Biome now resolves Error(...), new Error(...), optional Error#stack, and calls through indexed function values such as handlers[0]() more accurately.

  • #10865 6450276 Thanks @ematipico! - Fixed #10845. Biome Language Server no longer goes in deadlock when the scanner is enabled.

  • #10853 93d8e53 Thanks @Netail! - Fixed #10840: Astro shorthand attribute syntax is now correctly being parsed from embedded nodes.

  • #10820 bba3092 Thanks @JamBalaya56562! - Fixed #10619: noProcessEnv now also reports computed (bracket) member access. Previously only dot access was checked, so process["env"] and env["NODE_ENV"] (where env is imported from node:process) were missed. Both static and computed accesses are now reported.

  • #10835 3447b2f Thanks @dyc3! - Fixed #10824: useDomQuerySelector now supports an ignore option for receiver identifiers that should not be reported.

  • #10875 b12e486 Thanks @dyc3! - Fixed #10795: --profile-rules now reports timings for each plugin separately as plugin/<pluginName>, matching the naming used by plugin suppressions, instead of aggregating all plugins under a single plugin/plugin entry.

  • #10877 d6bc447 Thanks @ematipico! - Fixed biome-zed#164: Biome no longer inserts stray whitespace when format-on-type runs after closing delimiters such as ), ], and }.

  • #10867 a21463e Thanks @dyc3! - Fixed #10864: Biome no longer crashes when checking or linting HTML files with unquoted attribute values such as <textarea rows=4></textarea>.

What's Changed
New Contributors

Full Changelog: https://github.com/biomejs/biome/compare/@biomejs/biome@2.5.2...@biomejs/biome@2.5.3

View originalPermalink
How 2.5.3 went
2.5.2

Biome CLI v2.5.2

Added 3
  • Added the option ignoreBooleanCoercion to useNullishCoalescing rule to ignore || and ||= used inside a Boolean() call
  • Added the option ignorePrimitives to useNullishCoalescing rule to ignore ||, ||=, and ternary expressions whose non-nullish operands are primitives
  • Added the new nursery rule noSvelteUnnecessaryStateWrap to report unnecessary $state() wrapping of classes from svelte/reactivity
Fixed 8
  • Fixed useValidAutocomplete rule to correctly flag the autoComplete attribute
  • Improved performance of the Biome Language Server by cancelling in-flight operations when there are fast updates
  • Fixed noMisleadingReturnType false positive on returns using widening type assertions and now reports literal-pinning assertions
  • Fixed CSS parser to correctly parse nesting selectors when & appears as a trailing sub-selector after a type selector
  • Fixed CSS formatter output for selector lists with allowWrongLineComments and // comments after a selector comma
  • Fixed CSS parser to accept Tailwind @variant and @utility names that start with a digit
  • Fixed GitLab reporter to handle --verbose diagnostics filtering correctly
  • Fixed a bug where GritQL patterns rejected positional unkeyed arguments

From Biome

2.5.2
Patch Changes

  • #10595 f458028 Thanks @pkallos! - Added the option ignoreBooleanCoercion to useNullishCoalescing. When enabled, Biome ignores || and ||= used inside a Boolean() call, where coalescing on falsy values is intentional.

  • #10798 4a32b63 Thanks @pkallos! - Added the option ignorePrimitives to useNullishCoalescing. When enabled, Biome ignores ||, ||=, and ternary expressions whose non-nullish operands are all primitives the option opts out of. Use true to ignore all primitives, or an object selecting string, number, boolean, or bigint.

  • #10545 f3d4c00 Thanks @Mokto! - Added the new nursery rule noSvelteUnnecessaryStateWrap, which reports unnecessary $state() wrapping of classes from svelte/reactivity that are already reactive.

    <script>
import { SvelteMap } from "svelte/reactivity";
const map = $state(new SvelteMap()); // redundant
</script>

  • #10752 f62fb8b Thanks @ematipico! - Fixed #10739. Now the rule useValidAutocomplete correctly flags the autoComplete attribute.

  • #10796 f1b3ab2 Thanks @ematipico! - Fixed #10768. Improved the performance of the Biome Language Server by cancelling certain in-flight operations when there are fast updates.

  • #10719 aa649b5 Thanks @minseong0324! - Fixed noMisleadingReturnType false positive on returns that use a widening type assertion: "a" as string is no longer reported as misleading. The rule now also reports a literal-pinning assertion such as false as false, matching the existing as const behavior.

    // No longer flagged (returns are `string`):
function getValue(b: boolean): string {
  if (b) return "a" as string;
  return "b" as string;
}

// Now also reported, like `as const` (returns `false`):
function isReady(): boolean {
  return false as false;
}

  • #10678 8f073a7 Thanks @PranavAchar01! - Fixed #7718: Biome now correctly parses CSS nesting selectors when & appears as a trailing sub-selector after a type selector, e.g. h1& { color: red; }.

  • #10756 5ec965a Thanks @denbezrukov! - Fixed CSS formatter output for selector lists with allowWrongLineComments and // comments after a selector comma. Biome now keeps the selector before the line comment inline instead of breaking it across descendant combinators.

    -.powerPathNavigator
-  .helm
-  button.pressedButton, // pressed
+.powerPathNavigator .helm button.pressedButton, // pressed
 .powerPathNavigator .helm button:active:not(.disabledButton) {
 }

  • #10757 6232fcd Thanks @PranavAchar01! - Fixed #8269: the CSS parser now accepts Tailwind @variant and @utility names that start with a digit, such as the 2xl breakpoint.

    @utility container {
  @variant 2xl {
    max-width: 1400px;
  }
}

  • #10777 575ced6 Thanks @WaterWhisperer! - Fixed an issue reported in #10708: the GitLab reporter now handles --verbose diagnostics filtering correctly.

  • #10281 0efe244 Thanks @Zelys-DFKH! - Fixed a bug where GritQL patterns rejected positional (unkeyed) arguments.

  • #10758 e36fd8a Thanks @henrybrewer00-dotcom! - Fixed #10697: The formatter no longer removes the parentheses around an await or yield expression used as the target of a TypeScript instantiation expression. For example, (await makeFactory)<Value> is no longer reformatted to await makeFactory<Value>, which would change the meaning of the code.

  • #10586 3617094 Thanks @IxxyDev! - Fixed #9568: noFloatingPromises no longer reports a false positive when calling an overloaded function and the selected overload does not return a promise.

    function bestEffort(cb: () => Promise<number>): Promise<number>;
function bestEffort(cb: () => number): number;
function bestEffort(
  cb: () => number | Promise<number>,
): Promise<number> | number {
  return cb() as Promise<number> | number;
}

// This resolves to the second overload, which returns `number`, so it is no
// longer flagged as a floating promise.
bestEffort(() => 42);

  • #10766 7aff4c1 Thanks @JamBalaya56562! - Fixed #2862: noInteractiveElementToNoninteractiveRole no longer reports custom elements (a tag name containing a dash, e.g. <my-button role="img" />). Per the W3C HTML-ARIA specification, a custom element may be given any role or none.

  • #10680 771daa4 Thanks @WaterWhisperer! - Fixed #10635: Biome now recognizes chained table tests such as test.concurrent.each() and it.concurrent.each() as test calls, fixing noMisplacedAssertion false positives and improving formatting for those test declarations.

  • #10759 34570b5 Thanks @henrybrewer00-dotcom! - Fixed #10636: noStaticElementInteractions no longer reports a false positive for event handlers on Svelte special elements such as <svelte:window>, <svelte:document>, and <svelte:body>. These are not real DOM elements, so they are now ignored by the rule.

  • #10741 bd2364e Thanks @JamBalaya56562! - Fixed #6686: the rage command now respects the --config-path option and the BIOME_CONFIG_PATH environment variable when loading the Biome configuration. Previously it always used the default configuration resolution and reported the configuration as Not set when no biome.json existed in the working directory.

  • #10763 2c3e82d Thanks @Aqu1bp! - Fixed #10742: noSolidDestructuredProps now reports destructured props in Solid function components and JSX children.

  • #10606 a4cc4ab Thanks @Mokto! - Fixed false positives in noUnusedImports, noUnusedVariables, and useImportType for Svelte components that use both a <script module> and a <script> block. The two blocks compile to a single module and share a top-level scope, so a binding (import, function, or variable) declared in one block and used only in the other is no longer reported as unused.

  • #10767 36d5aa7 Thanks @otkrickey! - Fixed #10754: useVueValidVBind no longer reports the Vue 3.4+ same-name shorthand as missing a value. :foo and v-bind:foo are now accepted as equivalent to :foo="foo", while v-bind, v-bind:[dynamicArg], and :[dynamicArg] without a value continue to be reported.

  • #10775 a918af0 Thanks @WaterWhisperer! - Fixed an issue reported in #10708: biome rage didn't detect running Biome daemon pipes on Windows.

  • #10730 5a2e65b Thanks @dinocosta! - Fixed an issue where Biome was resolving the well-known Zed settings file from the wrong location on macOS and Windows.

  • #10807 d97fffe Thanks @ematipico! - Fixed an issue where .scss files were incorrectly analyzed when running biome check.

  • #10672 53c6efc Thanks @ematipico! - Fixed a bug where Biome incorrectly formatted snippets that have parsing errors.

  • #10719 aa649b5 Thanks @minseong0324! - Fixed useAwaitThenable false positive when awaiting a custom thenable that is not the global Promise. A value with a callable then member is now recognized as awaitable.

    interface Thenable<T> {
  then(onfulfilled: (value: T) => void): void;
}
declare const t: Thenable<number>;
async function f() {
  await t;
}

  • #10734 4396496 Thanks @BangDori! - Fixed #10708: biome migrate now preserves trivia when migrating the deprecated recommended option to preset.

  • #10683 ae31a00 Thanks @Netail! - Fixed #10657 #10671 #10661 #10637 #10718: HTML rules now correctly handle dynamic attributes.

  • #10746 54e8239 Thanks @ematipico! - Fixed an issue where noUndeclaredClasses didn't correctly detect styles defined inside the Astro directive is:global.

  • #10770 dd1429c Thanks @ematipico! - Improved the Biome Language Server DX by orchestrating certain operations, so that they won't block the editor during typing. This improvement is more visible in large documents.

  • #10473 d9b5133 Thanks @Mokto! - Improved noUnusedImports, noUnusedVariables, noUnusedFunctionParameters, and useImportType for Svelte, Vue, and Astro files (with html.experimentalFullSupportEnabled). Bindings used only in the template — including component tags, attribute interpolations, directives, bind: shorthand, and snippet parameters — are no longer reported as unused, while genuinely unused ones still are.

  • #10796 f1b3ab2 Thanks @ematipico! - Fixed an issue where the Biome Language Server didn't enable project or type-aware lint rules, even when they were explicitly enabled.

  • #10746 54e8239 Thanks @ematipico! - Fixed an issue where noUndeclaredClasses didn't detect styles declared inside HTML documents.

  • #10774 bde945b Thanks @pattrickrice! - Fixed #10268 where a race condition resulted in internal errors such as: The file biome.json does not exist in the workspace.

What's Changed
New Contributors

Full Changelog: https://github.com/biomejs/biome/compare/@biomejs/biome@2.5.1...@biomejs/biome@2.5.2

View originalPermalink
How 2.5.2 went
2.5.1

Biome CLI v2.5.1

Changed 4
  • Updated biome init command to include more up-to-date URL to the first-party extensions page
  • Disabled Go-to definition editor feature by default due to memory leak issues
  • Improved the diagnostic and documentation of useFlatMap rule
  • Improved DX of the JSON schema when used by code editors like VSCode
Fixed 10
  • Fixed CSS formatter output for comments between import media queries
  • Fixed json and json-pretty reporters to escape backslashes in diagnostic location paths
  • Fixed biome migrate to no longer emit invalid trailing comma when a renamed rule is the last member of its rule group
  • Fixed false positive in noUnusedVariables for Svelte files where variables referenced inside {@html expr} blocks were incorrectly reported as unused
  • Fixed useErrorCause rule to correctly detect shorthand properties
  • Improved how the Biome Language Server loads multiple configuration files inside a workspace

From Biome

2.5.1
Patch Changes

  • #10722 f8a303d Thanks @denbezrukov! - Fixed CSS formatter output for comments between import media queries.

    -@import url("print.css") print,
-/* comment */
-screen;
+@import url("print.css") print, /* comment */ screen;

  • #10738 9fdc560 Thanks @JamBalaya56562! - Fixed #9899: the json and json-pretty reporters now escape backslashes in a diagnostic's location.path. Previously, paths containing backslashes (such as Windows-style paths) were emitted unescaped, producing invalid JSON.

    -    "path": "src\account\setup-passkey.tsx",
+    "path": "src\\account\\setup-passkey.tsx",

  • #10626 5f837df Thanks @tom-groves! - Fixed #10625: biome migrate no longer emits an invalid trailing comma when a renamed rule (such as noConsoleLog → noConsole) is the last member of its rule group. Previously this produced malformed output that aborted the migration of a strict-JSON biome.json with a parsing error.

  • #10535 c245f9d Thanks @Mokto! - Fixed a false positive in noUnusedVariables for Svelte files where variables referenced inside {@html expr} blocks were incorrectly reported as unused.

  • #10668 a0f197e Thanks @Netail! - The biome init command has been updated to include a more up-to-date URL to the first-party extensions page.

  • #10667 d8c3e87 Thanks @Netail! - Fixed #10664: useErrorCause now correctly detects a shorthand property.

  • #10696 ef2373f Thanks @ematipico! - Fixed #9566. Improved how the Biome Language Server loads multiple configuration files inside a workspace.

  • #10705 4ccb410 Thanks @ematipico! - Fixed #10652. Biome plugins are now properly filtered when using --only and --skip flags.

  • #10669 aa0a6eb Thanks @Netail! - Fixed #10651: useInlineScriptId now correctly trims trivia to detect if an id attribute has been set.

  • #10689 844b1be Thanks @ematipico! - Fixed #10658. The issue was caused by the "Go-to definition" editor feature, which was enabled by default. The feature is now disabled by default. To work, the feature triggers the scanner to build the module graph. This caused memory leak issues in cases where Biome starts in the home directory to modify files.

    If you relied on this new feature, you must now turn on using the [editor settings] of the extension e.g. Zed and VSCode.

  • #10695 043fbb5 Thanks @ematipico! - Fixed #10674. Biome now throws an error when the field level is missing from a rule option.

  • #10712 5941df2 Thanks @Conaclos! - Improved the diagnostic and the documentation of useFlatMap.

  • #10615 23814f1 Thanks @qwertycxz! - Improved the DX the JSON schema when it's used by certain code editors like VSCode.

  • #10688 ec69489 Thanks @ematipico! - Fixed a bug where the Biome Daemon did not correctly shut down when the editor was closed during an in-progress operation, especially while scanning.

  • #10701 6c2e0d7 Thanks @ematipico! - Fixed #10694. The Biome Language Server no longer prints an error when the user hovers a variable imported from node_modules.

  • #10681 888515b Thanks @Conaclos! - Fixed useExportType that reported useless details in some diagnostics.

  • #10220 3694a13 Thanks @theBGuy! - Fixed useAnchorContent false positive for <a> elements used as render prop values (e.g. render={<a href="..." />}), a pattern where the receiving component renders its children inside the anchor element.

  • #10702 98823fb Thanks @ematipico! - Fixed #10612. The Biome parser now correctly parses processing instructions. The following SVG doesn't throw errors anymore:

    <?xml version="1.0" encoding="UTF-8" ?>

<svg></svg>
What's Changed
New Contributors

Full Changelog: https://github.com/biomejs/biome/compare/@biomejs/biome@2.5.0...@biomejs/biome@2.5.1

View originalPermalink
How 2.5.1 went
2.5.0

Biome CLI v2.5.0

Added 8
  • Added a new `concise` reporter that prints diagnostics in a compact manner when passed to `format`, `lint`, `check`, and `ci` commands
  • Added `useKeyWithClickEvents` a11y lint rule for HTML files to enforce keyboard accessibility alongside click handlers
  • Added `noUndeclaredClasses` nursery lint rule for HTML, JSX, and SFC files to detect CSS class names used but not defined
  • Added `noUnusedClasses` nursery lint rule for CSS to detect class selectors never referenced in importing HTML or JSX files
  • Added `biome upgrade` command for standalone installations to upgrade Homebrew installs and manually installed binaries
  • Added HTML version of `useHeadingContent` rule to enforce that heading elements have accessible content in HTML, Vue, Svelte, and Astro files
  • Added HTML version of `useKeyWithMouseEvents` rule to enforce that `onmouseover` is accompanied by `onfocus` and `onmouseout` by `onblur` in HTML, Vue, Svelte, and Astro files
  • Added `useSortedTypeFields` assist action to sort GraphQL object type, interface type, and input object type fields alphabetically

From Biome

2.5.0
Minor Changes

  • #9539 f0615fd Thanks @ematipico! - Added a new reporter called concise. When --reporter=concise is passed the commands format, lint, check and ci, the diagnostics are printed in a compact manner:

    ! index.ts:2:10: lint/correctness/noUnusedImports: Several of these imports are unused.
! main.ts:9:7: lint/correctness/noUnusedVariables: This variable f is unused.
× index.ts:8:5: lint/suspicious/noImplicitAnyLet: This variable implicitly has the any type.
× main.ts:2:10: lint/suspicious/noRedeclare: Shouldn't redeclare 'z'. Consider to delete it or rename it.

  • #9495 2056b23 Thanks @aviraldua93! - Added the useKeyWithClickEvents a11y lint rule for HTML files (.html, .vue, .svelte, .astro). This is a port of the existing JSX rule. The rule enforces that elements with an onclick handler also have at least one keyboard event handler (onkeydown, onkeyup, or onkeypress) to ensure keyboard accessibility.

    Inherently keyboard-accessible elements (<a>, <button>, <input>, <select>, <textarea>, <option>) are excluded, as are elements hidden from assistive technologies (aria-hidden) or with role="presentation" / role="none".

    <!-- Invalid: no keyboard handler -->
<div onclick="handleClick()">Click me</div>

<!-- Valid: has keyboard handler -->
<div onclick="handleClick()" onkeydown="handleKeyDown()">Click me</div>

<!-- Valid: inherently keyboard-accessible -->
<button onclick="handleClick()">Submit</button>

  • #9152 9ec8500 Thanks @ematipico! - Added new nursery lint rule noUndeclaredClasses for HTML, JSX, and SFC files (Vue, Astro, Svelte). The rule detects CSS class names used in class="..." (or className) attributes that are not defined in any <style> block or linked stylesheet reachable from the file.

    <!-- .typo is used but never defined -->
<html>
  <head>
    <style>
      .button {
        color: blue;
      }
    </style>
  </head>
  <body>
    <div class="button typo"></div>
  </body>
</html>

  • #9152 9ec8500 Thanks @ematipico! - Added new nursery lint rule noUnusedClasses for CSS. The rule detects CSS class selectors that are never referenced in any HTML or JSX file that imports the stylesheet. This is a project-domain rule that requires the module graph.

    /* styles.css — .ghost is never used in any importing file */
.button {
  color: blue;
}
.ghost {
  color: red;
}

    /* App.jsx */
import "./styles.css";
export default () => <div className="button" />;

  • #9546 6567efa Thanks @nhedger! - Added a biome upgrade command for standalone installations. It upgrades Homebrew installs with brew upgrade biome, updates manually installed binaries from the latest GitHub release, and tells npm users to upgrade with their package manager instead.

  • #9716 701767a Thanks @faizkhairi! - Added the HTML version of the useHeadingContent rule. The rule now enforces that heading elements (h1-h6) have content accessible to screen readers in HTML, Vue, Svelte, and Astro files.

    <!-- Invalid: empty heading -->
<h1></h1>

<!-- Invalid: heading hidden from screen readers -->
<h1 aria-hidden="true">invisible content</h1>

<!-- Valid: heading with text content -->
<h1>heading</h1>

<!-- Valid: heading with accessible name -->
<h1 aria-label="Screen reader content"></h1>

  • #9582 f437ef8 Thanks @rahuld109! - Added the HTML version of the useKeyWithMouseEvents rule. The rule now enforces that onmouseover is accompanied by onfocus and onmouseout is accompanied by onblur in HTML, Vue, Svelte, and Astro files.

    <!-- Invalid: onmouseover without onfocus -->
<div onmouseover="handleMouseOver()"></div>

<!-- Valid: onmouseover paired with onfocus -->
<div onmouseover="handleMouseOver()" onfocus="handleFocus()"></div>

  • #9275 1fdbcee Thanks @ff1451! - Added the new assist action useSortedTypeFields, which sorts the fields of GraphQL object types, interface types and input object types alphabetically, e.g. name, age, id becomes age, id, name.

  • #10561 78075b7 Thanks @Conaclos! - Added a new style option to useExportType, which enforces a style for exporting types. This is the same option as the one provided by useImportType.

  • #8987 d16e32b Thanks @DerTimonius! - Ported the useValidAnchor rule to HTML. This rule enforces that all anchors are valid and that they are navigable elements.

  • #9533 4d251d4 Thanks @ematipico! - The init command now prints the Biome logo.

  • #10069 0eb9310 Thanks @Netail! - Added the HTML lint rule noStaticElementInteractions, which enforces that static, visible elements (such as <div>) that have click handlers use the valid role attribute.

    Invalid:

    <div onclick="myFunction()"></div>

  • #9134 2a43488 Thanks @ematipico! - Added the assist action useSortedPackageJson.

    This action organizes package.json fields according to the same conventions as the popular sort-package-json tool.

  • #9309 7daa18b Thanks @Bertie690! - The allowDoubleNegation option has been added to noImplicitCoercions to allow ignoring double negations inside code.

    With the option enabled, the following example is considered valid and is ignored by the rule:

    const truthy = !!value;

  • #9700 894f3fb Thanks @ematipico! - The Biome Language server now supports the "go-to definition" feature.

    When the cursor of the mouse is hovering an entity (variable, CSS class, type, etc.), and the command CTRL + click is triggered, the editor jumps to where this entity is defined, if the language server can find it.

    Here's what Biome is able to resolve:

    • Variables and types used in JavaScript modules, defined in the same file or imported from another module.
    • JSX Components used in JavaScript modules, defined in the same file or imported from another module.
    • CSS classes used in JSX and HTML-ish files (Vue, Svelte and Astro), and defined in CSS files.
    • Components used in HTML-ish files and defined in other HTML-ish.
    • Variables used in HTML-ish files and defined in the same file or imported from another module (JavaScript or HTML-ish).

  • #10070 bae0710 Thanks @Conaclos! - Added the :STYLE: group matcher for organizeImports that matches style imports.

    For example, the following configuration...

    {
  "assist": {
    "actions": {
      "source": {
        "organizeImports": {
          "level": "on",
          "options": {
            "groups": ["**", "!:STYLE:"],
            "sortBareImports": true
          }
        }
      }
    }
  }
}

    ...places style imports last:

    - import "./style.css"
  import A from "./a.js"
+ import "./style.css"

  • #9170 e3107de Thanks @mdrobny! - Added bundleDependencies option to NoUndeclaredDependencies rule.

    This rule now supports imports of packages that are defined only in bundleDependencies and bundledDependencies arrays.

  • #9547 01f8473 Thanks @mujpao! - Added new assist rule useSortedAttributes for HTML, porting the existing JSX rule. This rule enforces sorted HTML attributes.

    Invalid

    <input type="text" id="name" name="name" />

  • #9366 2ca1117 Thanks @dyc3! - Added the html.parser.vue configuration option. When enabled, it adds support for the parsing of Vue in .html files. Most Vue users don't need to enable this option since Vue files typically use the .vue extension, but it can be useful for projects that embed Vue syntax in regular HTML files.

  • #9073 74b20ee Thanks @chocky335! - Added support for applying GritQL plugin rewrites as code actions. GritQL plugins that use the rewrite operator (=>) now produce fixable diagnostics for JavaScript, CSS, and JSON files. By default, plugin rewrites are treated as unsafe fixes and require --write --unsafe to apply. Plugin authors can pass fix_kind = "safe" to register_diagnostic() to mark a fix as safe, allowing it to be applied with just --write.

    Example plugin (useConsoleInfo.grit):

    language js

`console.log($msg)` as $call where {
    register_diagnostic(span = $call, message = "Use console.info instead of console.log.", severity = "warn", fix_kind = "safe"),
    $call => `console.info($msg)`
}

    Running biome check --write applies safe rewrites. Unsafe rewrites (the default, or fix_kind = "unsafe") still require --write --unsafe.

  • #9384 f4c9edc Thanks @Conaclos! - Added the sortBareImports option to organizeImports, which allows bare imports to be sorted within other imports when set to false.

    {
  "assist": {
    "actions": {
      "source": {
        "organizeImports": {
          "level": "on",
          "options": { "sortBareImports": true }
        }
      }
    }
  }
}

    - import "b";
  import "a";
+ import "b";
  import { A } from "a";
+ import "./file";
  import { Local } from "./file";
- import "./file";

  • #8731 e7872bf Thanks @siketyan! - Added the watch mode (--watch) to the CLI for check/format/lint commands. By enabling this option, Biome will re-run the check automatically when any file in the workspace has changed after the first run.

  • #10106 9b35f78 Thanks @ematipico! - Biome can now format and lint .svg files.

  • #9967 e9b6c17 Thanks @dyc3! - Added HTML support for noExcessiveLinesPerFile. Biome now reports HTML files that exceed the configured line limit, including when skipBlankLines is enabled.

  • #9491 b3eb63c Thanks @IxxyDev! - Added the HTML lint rule noAriaUnsupportedElements. This rule enforces that elements that do not support ARIA roles, states, and properties (meta, html, script, style) do not have role or aria-* attributes.

    <!-- Invalid: meta does not support aria attributes -->
<meta charset="UTF-8" role="meta" />

  • #9306 afd57a6 Thanks @viraxslot! - Added the noNoninteractiveTabindex lint rule for HTML. This rule enforces that tabindex is not used on non-interactive elements, as it can cause usability issues for keyboard users.

    <div tabindex="0">Invalid: non-interactive element</div>
`

  • #9276 6d041d9 Thanks @IxxyDev! - Added the HTML lint rule noRedundantRoles. This rule enforces that explicit role attributes are not the same as the implicit/default role of an HTML element. It supports HTML, Vue, Svelte, and Astro files.

    <!-- Invalid: role="button" is redundant on <button> -->
<button role="button"></button>

  • #9813 69aadc2 Thanks @ematipico! - Added a new linter configuration called preset. With the new option, users can enable different kinds of rules at once.

    The following presets are available:

    • "recommended": it enables all Biome-recommended rules, or recommended rules of a group;
    • "all": it enables all Biome rules, or enables all rules of a group;
    • "none": it disables all Biome rules, or disable all rules of a group.

    You can enable recommended rules:

    {
  "linter": {
    "rules": {
      "preset": "recommended"
    }
  }
}

    You can enable all rules at once:

    {
  linter: {
    rules: {
      preset: "all", // enables all rules
    },
  },
}

    Or enable all rules for a group:

    {
  linter: {
    rules: {
      style: {
        preset: "all", // enables all rules in the style group
      },
    },
  },
}

    This new option, however, doesn't affect how nursery rules work. Nursery rules must be enabled singularly, due to their nature.

    This new option is meant to replace recommended, so make sure to run the migrate command.

  • #10022 3422d71 Thanks @Netail! - Added the HTML lint rule noNoninteractiveElementToInteractiveRole, which enforces that interactive ARIA roles are not assigned to non-interactive HTML elements.

    Invalid:

    <h1 role="checkbox"></h1>

  • #8396 13785fc Thanks @apple-yagi! - Biome now supports pnpm catalogs (default and named) when resolving dependencies for linting. This behavior is opt-in and requires setting javascript.resolver.experimentalPnpmCatalogs to true.

  • #10028 1009414 Thanks @Netail! - Added the HTML lint rule noInteractiveElementToNoninteractiveRole, which enforces that non-interactive ARIA roles are not assigned to interactive HTML elements.

    Invalid:

    <input role="img" />

  • #9853 816302f Thanks @Netail! - Added the new assist action useSortedSelectionSet, which sorts GraphQL selection sets alphabetically, e.g. name, age, id becomes age, id, name.

    Invalid:

    query {
  name
  age
  id
}

  • #10074 9c7c6eb Thanks @georgephillips! - Added a kind field to the ImportMatcher used by the organizeImports assist action. The new field selects imports by their syntactic kind and currently supports bare (matching side-effect imports such as import "polyfill") with optional ! negation (!bare). The matcher composes with the existing type and source fields, so users can express patterns such as "only bare imports that import a CSS file" ({ "kind": "bare", "source": "**/*.css" }).

    For example, with the following configuration:

    {
  "assist": {
    "actions": {
      "source": {
        "organizeImports": {
          "level": "on",
          "options": {
            "sortBareImports": true,
            "groups": [
              { "kind": "!bare" },
              ":BLANK_LINE:",
              { "kind": "bare" }
            ]
          }
        }
      }
    }
  }
}

    ...the following code:

    import "./register-my-component";
import { render } from "react-dom";
import "./polyfill";
import { Button } from "@/components/Button";

    ...is organized as:

    import { render } from "react-dom";
import { Button } from "@/components/Button";

import "./polyfill";
import "./register-my-component";

  • #9171 ce65710 Thanks @chocky335! - Added includes option for plugin file scoping. Plugins can now be configured with glob patterns to restrict which files they run on. Use negated globs for exclusions.

    {
  "plugins": [
    "global-plugin.grit",
    {
      "path": "scoped-plugin.grit",
      "includes": ["src/**/*.ts", "!**/*.test.ts"]
    }
  ]
}

  • #9617 dcb99ef Thanks @faizkhairi! - Ported useAriaActivedescendantWithTabindex a11y rule to HTML.

  • #9496 1dfb829 Thanks @aviraldua93! - Added HTML support for the noAriaHiddenOnFocusable accessibility lint rule, which enforces that aria-hidden="true" is not set on focusable elements. Focusable elements include native interactive elements (<button>, <input>, <select>, <textarea>), elements with href (<a>, <area>), elements with tabindex >= 0, and editing hosts (contenteditable). Includes an unsafe fix to remove the aria-hidden attribute.

    <!-- Invalid: aria-hidden on a focusable element -->
<button aria-hidden="true">Submit</button>

<!-- Valid: aria-hidden on a non-focusable element -->
<div aria-hidden="true">decorative content</div>

  • #9792 f516854 Thanks @Maximiliano-Zeballos! - Added the useSemanticElements lint rule for HTML. The rule now detects the use of role attributes in HTML elements and suggests using semantic elements instead.

    For example, the following code is now flagged:

    <div role="navigation"></div>

    The rule suggests using <nav> instead.

  • #9761 cbbb7d5 Thanks @Maximiliano-Zeballos! - Ported the useValidAriaProps lint rule to HTML. This rule checks that all aria-* attributes used in HTML elements are valid ARIA attributes as defined by the WAI-ARIA specification.

  • #9928 aa82576 Thanks @aviraldua93! - Ported useValidAriaValues to HTML. Biome now validates static aria-* attribute values in HTML elements against WAI-ARIA types, catching invalid values such as aria-hidden="yes".

  • #10562 6642895 Thanks @ematipico! - Promoted 73 nursery rules to stable groups.

    Four rules were renamed as part of the promotion:

    Correctness

    Promoted the following rules to the correctness group:

    Suspicious

    Promoted the following rules to the suspicious group:

    Style

    Promoted the following rules to the style group:

    Complexity

    Promoted the following rules to the complexity group:

    Performance

    Promoted the following rules to the performance group:

    Security

    Promoted the following rules to the security group:

    A11y

    Promoted the following rules to the a11y group:

  • #10121 450f8e1 Thanks @jongwan56! - Biome now applies Git's local exclude file when VCS ignore files are enabled. Files listed in .git/info/exclude are skipped the same way as files listed in .gitignore, including in linked worktrees.

  • #9397 d5913c9 Thanks @mvarendorff! - Added ignore option to the noUnusedVariables rule. The option allows excluding identifiers by providing a list of ignored names. It also allows excluding kinds of identifiers from this rule entirely, which may be useful when loading classes dynamically.

    For example, unused classes as well as all unused variables, functions, etc. called "unused" may be ignored entirely with the following configuration:

    {
  "ignore": {
    "*": ["unused"],
    "class": ["*"]
  }
}

  • #10089 71a21f0 Thanks @Netail! - Added the lint rule noLabelWithoutControl to HTML, which enforces that a label element or component has a text label and an associated input.

    <label></label>

  • #10015 1828261 Thanks @Netail! - Added the HTML lint rule useAriaPropsSupportedByRole, which enforces that ARIA properties are valid for the roles that are supported by the element.

    <a href="#" aria-checked></a>

  • #10234 1a51569 Thanks @ematipico! - Added the delimiterSpacing formatter option. This option inserts spaces inside delimiters (after the opening delimiter and before the closing delimiter) when the content fits on a single line. Empty delimiters are not affected, and no space is added before the opening delimiter. The specific delimiters affected depend on the language. It can be configured globally via formatter.delimiterSpacing or per-language via javascript.formatter.delimiterSpacing, json.formatter.delimiterSpacing, and css.formatter.delimiterSpacing. Defaults to false.

    - callFn(foo)
+ callFn( foo )

    - const arr = [1, 2, 3];
+ const arr = [ 1, 2, 3 ];
    JavaScript

    When enabled, Biome inserts spaces inside parentheses (e.g., foo( a, b )), square brackets (e.g., [ a, b ]), template literal interpolations (e.g., ${ expr }), and the logical NOT operator (e.g., ! x, but in chains only after the last one: !! x). Only applies when the content fits on a single line. Empty delimiters and the space before the opening delimiter are not affected.

    - if (condition) {}
+ if ( condition ) {}

    - `Hello ${name}!`
+ `Hello ${ name }!`
    JSX

    When enabled, Biome inserts spaces inside JSX expression braces (e.g., attr={ value }) and spread attributes (e.g., { ...props }). Only applies when the content fits on a single line. Empty delimiters are not affected.

    - <Foo bar={value} />
+ <Foo bar={ value } />
    TypeScript

    When enabled, Biome inserts spaces inside TypeScript angle brackets (e.g., foo< T >()), indexed access types (e.g., T[ K ]), mapped types, tuple types, type parameters, and index signatures. Only applies when the content fits on a single line. Empty delimiters are not affected.

    - type Result = Map<string, number>;
+ type Result = Map< string, number >;
    JSON

    When enabled, Biome inserts spaces inside square brackets when the content fits on a single line. Empty brackets are not affected.

    - [1, 2, 3]
+ [ 1, 2, 3 ]
    CSS

    When enabled, Biome inserts spaces inside parentheses and square brackets when the content fits on a single line. Empty delimiters are not affected.

    - rgba(0, 0, 0, 1)
+ rgba( 0, 0, 0, 1 )

    - [data-attr]
+ [ data-attr ]

  • #10461 6bac1c3 Thanks @TXWSLYF! - Implements #9445. Added the allowImplicit option to useIterableCallbackReturn. When enabled, callbacks can use return; to implicitly return undefined, matching ESLint's array-callback-return rule.

  • #9571 5a8eb75 Thanks @dyc3! - Added configurable options to the useNumericSeparators rule. Users can now customize the minimum number of digits required before adding separators and the group length for each type of numeric literal (binary, octal, decimal, hexadecimal).

    {
  "linter": {
    "rules": {
      "style": {
        "useNumericSeparators": {
          "level": "error",
          "options": {
            "decimal": {
              "minimumDigits": 7,
              "groupLength": 3
            },
            "hexadecimal": {
              "minimumDigits": 4,
              "groupLength": 2
            }
          }
        }
      }
    }
  }
}

  • #10067 6064312 Thanks @Netail! - Added the lint rule useFocusableInteractive to HTML, which enforces elements with an interactive role and interaction handler to be focusable.

    Invalid:

    <div role="button"></div>

  • #10026 fb42ac4 Thanks @Netail! - Added the HTML lint rule noNoninteractiveElementInteractions, which disallows use event handlers on non-interactive elements.

    Invalid:

    <div onclick="myFunction()">button</div>

  • #10000 2093e3e Thanks @Netail! - Added the new assist action useSortedEnumMembers, which sorts TypeScript & GraphQL enum members.

    Invalid:

    enum Role {
  SUPER_ADMIN
  ADMIN
  USER
  GOD
}

  • #10013 ad01d3d Thanks @Netail! - Added the HTML lint rule useValidAutocomplete, which enforces using valid values for the autocomplete attribute on input elements.

    <input autocomplete="incorrect" />
Patch Changes

  • #10498 995c1ff Thanks @citadelgrad! - Added the nursery rule useReactFunctionComponentDefinition, which enforces a consistent function type for named React function components.

    For example, the following snippet triggers the rule by default.

    const MyComponent = (props) => {
  return <div>{props.name}</div>;
};

  • #9974 ff635a9 Thanks @pkallos! - Added ignoreMixedLogicalExpressions to useNullishCoalescing, partially addressing #9232. When enabled, Biome ignores || and ||= mixed with && in the same expression tree.

  • #10503 c656679 Thanks @Mokto! - Added the new nursery rule useSvelteRequireEachKey, a Svelte lint rule that reports {#each} blocks with item bindings that are missing a key.

  • #10516 0f29b83 Thanks @Dotify71! - Added useIncludes to the nursery group. This rule flags comparisons of String.prototype.indexOf() or Array.prototype.indexOf() against -1 and suggests replacing them with the clearer includes() / !includes() form.

  • #10487 0c03ee3 Thanks @Mokto! - Fixed a Svelte parser error that incorrectly required a binding variable after {:then} and {:catch}. Biome now correctly accepts {:then} and {:catch} without a binding, as well as the {#await expr then} and {#await expr catch} shorthand forms.

  • #10566 a4a294c Thanks @dyc3! - Fixed useVueHyphenatedAttributes: The rule now only reports diagnostics in Vue files and ignores SVG elements.

  • #10565 72ccf3b Thanks @dyc3! - Fixed useVueConsistentVBindStyle: The rule no longer reports argument-less v-bind directives because they cannot be converted to shorthand syntax.

  • #10591 6e8557b Thanks @xsourabhsharma! - Fixed #10563: Biome now parses comma-separated CSS Modules composes values, such as composes: classA from "./a.css", classB from "./b.css";.

  • #10603 174b21b Thanks @denbezrukov! - Fixed CSS formatting for grid-template-areas declarations with comments before multiline values. Biome now keeps grid area rows aligned instead of adding an extra declaration-boundary indent.

     .grid {
   grid-template-areas:
 /* row */
-      "header header"
-      "footer footer";
+    "header header"
+    "footer footer";
 }

  • #10542 c3f07f7 Thanks @dyc3! - Fixed #10513: Biome no longer rejects literal \u sequences in quoted HTML attribute values.

  • #10108 24e51d6 Thanks @IxxyDev! - Fixed #6611: noUnnecessaryConditions now uses type information to detect more redundant conditions, including ?., ??, ||, &&, comparisons against null/undefined on non-nullish operands, and case clauses that can never match the switch value.

  • #10568 eb1ed0e Thanks @harsha-cpp! - Fixed #10564: useAriaPropsForRole no longer reports false positives for Vue v-bind shorthand bindings (:aria-checked, :aria-level, etc.).

  • #10570 2ceb4fe Thanks @Conaclos! - Improved noTsIgnore. The rule now reports more precisely the range of the @ts-ignore comment.

  • #10520 b55d10f Thanks @dyc3! - Fixed #10519: Vue v-on event handlers with multiple inline statements are now parsed consistently with Vue.

  • #10204 ebbf0bd Thanks @ematipico! - Improved the performance of the Biome linter. The improvements are more visible in bigger projects that have more than ~1k files. Early tests showed that in a code base with ~2k files, Biome took less than 26% of time to finish the command.

  • #10546 e39bb2c Thanks @tim-we! - Fixed #10536: noUnknownFunction no longer flagged CSS contrast-color() as unknown. contrast-color() is Baseline 2026.

  • #8012 2be0264 Thanks @denbezrukov! - Improved the performance of the formatter in some cases. The formatter is now up to ~20% faster at formatting files.

  • #10467 9a5855e Thanks @Netail! - Added a new nursery rule noRestrictedDependencies, which flags imports and package.json dependency entries that have better alternatives in e18e's module replacement data.

    For example, the package globby is reported because there's a better alternative:

    import glob from "globby";

    {
  "dependencies": {
    "globby": "x.x.x"
  }
}

  • #10470 84b43c5 Thanks @ShaharAviram1! - Fixed #10447: now the rule noProcessEnv detects the use of env when it's imported from process and node:process.

  • #10556 7ff6b16 Thanks @ematipico! - Fixed #10492: Biome no longer crashes with a stack overflow on certain code when a type-aware rule such as noFloatingPromises, noMisusedPromises, or noUnnecessaryConditions is enabled. For example, the following code used to crash Biome:

    function f(visitor) {
  let ctrl = visitor();
  for (const x of [0]) ctrl = ctrl();
}

  • #10532 1da3c75 Thanks @denbezrukov! - CSS declarations with comments before : or after !important now preserve spaces before : and ;.

     .selector {
-  padding/* name */: 1px;
-  color: red !important /* note */;
+  padding/* name */ : 1px;
+  color: red !important /* note */ ;
 }

  • #10491 a1b5834 Thanks @Mokto! - Fixed the Svelte parser rejecting {#each} blocks where the binding uses object destructuring with property renaming, e.g. {#each items as { id, component: Filter }}. Biome now correctly parses and formats these rename bindings.

  • #10490 99bc7df Thanks @Mokto! - Fixed the CSS parser rejecting comma-separated selector lists inside :global() and :local() pseudo-class functions. Biome now correctly parses :global(.foo, .bar).

  • #10543 c394fae Thanks @mangod12! - Fixed #10477: The RDJSON reporter now emits code replacement text for fix suggestions instead of the human-readable fix description.

  • #10530 e8e1e6a Thanks @Conaclos! - Fixed #10493: useImportType now correctly separates types from a default named import when all imports are types and the style option is set to separatedType.

  • #10555 263c7cc Thanks @Mokto! - Improved Svelte lint rule accuracy for quoted attribute values containing {expression} interpolations.

    • noRedundantAlt no longer emits false positives when the alt text contains an interpolation, e.g. alt="image of {person}".
    • useButtonType no longer emits false positives for dynamic button types written as type="{dynamicType}".
    • noScriptUrl no longer emits false positives for dynamic hrefs such as href="{url}".

  • #10489 96ef9a4 Thanks @Mokto! - Fixed Svelte {#each} parser incorrectly rejecting TypeScript as const type assertions in the iterable expression. Biome now correctly parses {#each arr as const as item}.

  • #10539 935c59a Thanks @dyc3! - Improved how diagnostics print long lines of code, for example minified files where the entire source code is printed in one line.

What's Changed
New Contributors

Full Changelog: https://github.com/biomejs/biome/compare/@biomejs/biome@2.4.16...@biomejs/biome@2.5.0

View originalPermalink
How 2.5.0 went
2.4.16

Biome CLI v2.4.16

Added 1
  • Added support for formatter.trailingCommas in overrides
Changed 1
  • Updated useDestructuring rule to provide variableDeclarator and assignmentExpression options to control which contexts enforce destructuring, with diagnostic for object destructuring in assignment expressions now instructing users to wrap the assignment in parentheses
Fixed 11
  • Fixed diagnostics showing incorrect location in Astro files
  • Fixed HTML formatting where comments could cause the formatter to split up closing tags and produce syntactically invalid HTML
  • Fixed diagnostics emitted by the noUntrustedLicenses rule
  • Fixed biome rage --linter to display rules enabled through linter domains in the enabled rules list
  • Fixed parsing of Svelte function bindings such as bind:value={get, set} to prevent false positives from noCommaOperator rule
  • Fixed useOptionalChain rule to detect negated guard inequality chains like !foo || foo.bar !== "x"

From Biome

2.4.16
Patch Changes

  • #10329 ef764d5 Thanks @Conaclos! - Fixed an issue where diagnostics showed an incorrect location in Astro files.

  • #10363 50aa415 Thanks @dyc3! - Fixed HTML formatting for a case where comments could cause the formatter to split up a closing tag, which would cause the resulting HTML to be syntactically invalid.

    Input:

    <span
  ><!-- 1
--><span>a</span
  ><!-- 2
--><span>b</span
  ><!-- 3
--></span>

    Output:

      <span
	  ><!-- 1
- --> <span>a</span<!-- 2
- --> ><span>b</span><!-- 3
+ --><span>a</span><!-- 2
+ --><span>b</span><!-- 3
  --></span
  >

  • #10465 0c718da Thanks @dfedoryshchev! - Fixed diagnostics emitted by the noUntrustedLicenses rule.

  • #10358 05c2617 Thanks @dyc3! - Fixed #10356: biome rage --linter now displays rules enabled through linter domains in the enabled rules list.

  • #10300 950247c Thanks @dyc3! - Fixed #10265: Svelte function bindings such as bind:value={get, set} are now parsed more precisely, so noCommaOperator won't emit false positives for that syntax anymore.

  • #9786 e71f584 Thanks @MeGaNeKoS! - Fixed #8480: useDestructuring now provides variableDeclarator and assignmentExpression options to control which contexts enforce destructuring, matching ESLint's prefer-destructuring configuration. Both default to {array: true, object: true}. The diagnostic for object destructuring in assignment expressions now instructs users to wrap the assignment in parentheses.

  • #10425 1948b72 Thanks @sjh9714! - Fixed #10244: The useOptionalChain rule now detects negated guard inequality chains like !foo || foo.bar !== "x".

  • #10442 001f94f Thanks @ematipico! - Fixed #10411: noMisusedPromises no longer causes a stack overflow when a nested function returns an object with shorthand properties that shadow destructured variables from an outer scope.

  • #10318 9b1577f Thanks @dyc3! - Added support for formatter.trailingCommas in overrides. This option was previously available in the top-level formatter configuration but missing from formatter overrides.

  • #10319 2e37709 Thanks @dyc3! - Fixed Vue and Svelte formatting for standalone interpolations in inline elements. Biome now preserves existing newlines in cases like:

    - <span> {{ value }} </span>
+ <span>
+   {{ value }}
+ </span>

  • #10365 0a58eb0 Thanks @Netail! - Fixed #10361: noUnusedFunctionParameters now mentions the parameter name in the diagnostic.

  • #10439 df6b867 Thanks @denbezrukov! - Fixed CSS and SCSS formatting for comments around declaration colons so comments between property names, colons, and values stay at the same boundary as Prettier.

     .selector {
-  color: /* red, */
-    blue;
+  color: /* red, */ blue;
 }

  • #10344 b30208c Thanks @siketyan! - Fixed #10123: Corrected the noReactNativeDeepImports source rule to point to the proper upstream rule, so users can migrate from the original rule correctly.

  • #10328 b59133f Thanks @dyc3! - Fixed #10309: Biome no longer adds newlines to Astro frontmatter when linter or assist --write mode is enabled.

What's Changed
New Contributors

Full Changelog: https://github.com/biomejs/biome/compare/@biomejs/biome@2.4.15...@biomejs/biome@2.4.16

View originalPermalink
How 2.4.16 went
2.4.15

Biome CLI v2.4.15

Added 5
  • Add the nursery rule useTestHooksInOrder in the test domain to enforce that Jest/Vitest lifecycle hooks are declared in the order they execute
  • Add the nursery rule useVueNextTickPromise to enforce Promise syntax when using Vue nextTick
  • Add the nursery rule noVueVOnNumberValues to disallow deprecated number modifiers on Vue v-on directives
  • Add the nursery rule useVueValidVFor to validate Vue v-for directives and report invalid aliases, missing component keys, and keys that do not use iteration variables
  • Add the recommended nursery rule noVueImportCompilerMacros to disallow importing Vue compiler macros such as defineProps from vue because they are automatically available
Changed 2
  • Improve noMisleadingReturnType to flag union annotations whose extra variants are never returned and suggest the narrower type
  • Enhance noMisleadingReturnType to detect misleading return type annotations when object literal properties are initialized with as const
Fixed 5
  • Fix style/useReadonlyClassProperties no longer reporting class properties as readonly-able when they are assigned inside arrow callbacks nested in class property initializers
  • Make organizeImports diagnostics more detailed and more precise with better localization of issues
  • Make organizeImports error when it encounters an unknown predefined group in configuration
  • Preserve child line breaks in HTML and Vue element formatting when an element contains another element child on its own line
  • Fix Svelte templates with missing expressions no longer parsed as HtmlBogusElement

From Biome

2.4.15
Patch Changes

  • #9394 ba3480e Thanks @dyc3! - Added the nursery rule useTestHooksInOrder in the test domain. The rule enforces that Jest/Vitest lifecycle hooks (beforeAll, beforeEach, afterEach, afterAll) are declared in the order they execute, making test setup and teardown easier to reason about.

  • #10254 e0a54cc Thanks @dyc3! - Added a new nursery rule useVueNextTickPromise, which enforces Promise syntax when using Vue nextTick.

    For example, the following snippet triggers the rule:

    import { nextTick } from "vue";

nextTick(() => {
  updateDom();
});

  • #10219 64aee45 Thanks @dyc3! - Added a new nursery rule noVueVOnNumberValues, that disallows deprecated number modifiers on Vue v-on directives.

    For example, the following snippet triggers the rule:

    <input @keyup.13="submit" />

  • #10195 7b8d4e1 Thanks @dyc3! - Added the new nursery rule useVueValidVFor, which validates Vue v-for directives and reports invalid aliases, missing component keys, and keys that do not use iteration variables.

  • #10238 1110256 Thanks @dyc3! - Added the recommended nursery rule noVueImportCompilerMacros, which disallows importing Vue compiler macros such as defineProps from vue because they are automatically available.

  • #10201 1a08f89 Thanks @realknove! - Fixed #10193: style/useReadonlyClassProperties no longer reports class properties as readonly-able when they are assigned inside arrow callbacks nested in class property initializers.

  • #9574 3bd2b6a Thanks @Conaclos! - Fixed #9530. The diagnostics of organizeImports are now more detailed and more precise. They are also better at localizing where the issue is.

  • #10205 a704a6c Thanks @Conaclos! - Fixed #10185. `organizeImports now errors when it encounters an unknown predefined group.

    The following configuration is now reported as invalid because :INEXISTENT: is an unknown predefined group.

    {
  "assist": {
    "actions": {
      "source": {
        "organizeImports": { "options": { "groups": [":INEXISTENT:"] } }
      }
    }
  }
}

  • #10052 b565bed Thanks @minseong0324! - Improved noMisleadingReturnType: it now flags union annotations whose extra variants are never returned, and suggests the narrower type (e.g. string | null → string).

    These functions are now reported because null and number are included in the return annotations but never returned:

    function getUser(): string | null {
  return "hello";
} // null is never returned
function getCode(): string | number {
  return "hello";
} // number is never returned

  • #10213 ac30057 Thanks @dyc3! - Fixed #9450: HTML and Vue element formatting now preserves child line breaks when an element contains another element child on its own line, instead of collapsing the child element onto the same line.

  • #10275 9ee6c03 Thanks @solithcy! - Fixed #10274: Svelte templates with missing expressions no longer parsed as HtmlBogusElement

  • #10143 56798a7 Thanks @minseong0324! - noMisleadingReturnType now detects misleading return type annotations when object literal properties are initialized with as const.

    This function is now reported because the return annotation widens a property initialized with as const:

    function f(): { value: string } {
  return { value: "text" as const };
}

  • #10143 56798a7 Thanks @minseong0324! - noUselessTypeConversion now detects redundant conversions on object literal properties initialized with as const.

    This conversion is now reported because message.value is inferred as a string literal:

    const message = { value: "text" as const };
String(message.value);

  • #9807 0ae5840 Thanks @dyc3! - Added the new nursery rule useThisInClassMethods, based on ESLint's class-methods-use-this.

    The rule now reports instance methods, getters, setters, and function-valued instance fields that do not use this, and biome migrate eslint preserves the supported ignoreMethods, ignoreOverrideMethods, and ignoreClassesWithImplements options.

    Invalid:

    class Foo {
  bar() {
    // does not use `this`, invalid
    console.log("Hello Biome");
  }
}

  • #10258 e7b18f7 Thanks @ematipico! - Improved linter performance by narrowing the query nodes for several lint rules, reducing how often they are evaluated.

  • #10273 04e22a1 Thanks @dyc3! - Fixed #10271: The HTML parser now correctly parses of as text content when in text contexts.

  • #9838 83f7385 Thanks @dyc3! - Added the nursery rule noBaseToString, which reports stringification sites that fall back to Object's default "[object Object]" formatting. The rule also supports the ignoredTypeNames option.

  • #10143 56798a7 Thanks @minseong0324! - useExhaustiveSwitchCases now checks switch statements over object literal properties initialized with as const.

    This switch is now reported because status.kind is inferred as the string literal "ready" but no case handles it:

    const status = { kind: "ready" as const };
switch (status.kind) {
}

  • #10143 56798a7 Thanks @minseong0324! - useStringStartsEndsWith now detects string index comparisons on object literal properties initialized with as const.

    This comparison is now reported because message.value is inferred as a string literal:

    const message = { value: "hello" as const };
message.value[0] === "h";
What's Changed
New Contributors

Full Changelog: https://github.com/biomejs/biome/compare/@biomejs/biome@2.4.14...@biomejs/biome@2.4.15

View originalPermalink
How 2.4.15 went
2.4.14

Biome CLI v2.4.14

Added 2
  • Added the nursery rule useTestHooksOnTop in the test domain to flag lifecycle hooks that appear after test cases in the same block
  • Added the new nursery rule noReactStringRefs to disallow legacy React string refs and template-literal refs
Fixed 8
  • The HTML parser now emits better diagnostics when it encounters a void element with a closing tag, emitting a single diagnostic instead of multiple conflicting ones
  • noMisleadingReturnType no longer misses widening from concrete object types, class instances, object literals, tuples, functions, and regular expressions to : object
  • noUselessEscapeInRegex no longer flags an escaped backslash followed by - as a useless escape
  • organizeImports no longer adds a blank line between a never-matched group and a matched group
  • Fixed Vue v-for handling for noUndeclaredVariables and noUnusedVariables to recognize variables declared by v-for directives
  • noMisleadingReturnType no longer reports false positives when a union return type's boolean variant is covered by both true and false returns
  • Fixed LSP file watcher registration so Biome now watches .biome.json and .biome.jsonc configuration files and reloads workspace settings when they change
  • The noThisInStatic rule no longer reports this when it is used as the constructor target in new this(...), which is required for inherited static factory methods

From Biome

2.4.14
Patch Changes

  • #9393 491b171 Thanks @dyc3! - Added the nursery rule useTestHooksOnTop in the test domain. The rule flags lifecycle hooks (beforeEach, beforeAll, afterEach, afterAll) that appear after test cases in the same block, enforcing that hooks are defined before any test case.

  • #10157 eefc5ab Thanks @dyc3! - Fixed #7882: The HTML parser will now emit better diagnostics when it encounters a void element with a closing tag, such as <br></br>. Previously, the parser would emit multiple diagnostics with conflicting advice. Now it emits a single diagnostic that clearly states that void elements should not have closing tags.

  • #10054 0e9f569 Thanks @minseong0324! - noMisleadingReturnType no longer misses widening from concrete object types, class instances, object literals, tuples, functions, and regular expressions to : object.

    A function annotated : object returning an object literal:

    function f(): object {
  return { retry: true };
}

  • #10116 53269eb Thanks @jiwon79! - Fixed #6201: noUselessEscapeInRegex no longer flags an escaped backslash followed by - as a useless escape. Patterns like /[\\-]/ are now considered valid because the second \ is the escaped backslash, not an unnecessary escape of the trailing dash.

  • #10092 33d8543 Thanks @Conaclos! - Fixed #9097: organizeImports no longer adds a blank line between a never-matched group and a matched group.

    Given the following organizeImports options:

    {
  "groups": [":NODE:", ":BLANK_LINE:", ":PACKAGE:", ":BLANK_LINE:", ":PATH:"]
}

    The following code...

    // Comment
import "package";
import "./file.js";

    ...was organized as:

    +
  // Comment
  import "package";
+
  import "./file.js";

    A blank line was added even though the group ':NODE:' doesn't match any imports here. :BLANK_LINE: between never-matched groups and matched groups are now ignored. The code is now organized as:

      // Comment
  import "package";
+
  import "./file.js";

  • #10138 a10b6c1 Thanks @dyc3! - Fixed Vue v-for handling for noUndeclaredVariables and noUnusedVariables. Biome now recognizes variables declared by v-for directives and references to iterated values in Vue templates.

  • #10115 d428d76 Thanks @minseong0324! - noMisleadingReturnType no longer reports false positives when a union return type's boolean variant is covered by both true and false returns.

  • #9922 7acf1e0 Thanks @dyc3! - Added the new nursery rule noReactStringRefs, which disallows legacy React string refs such as ref="hello" and this.refs.hello.

    Biome also reports template-literal refs such as ref={`hello`}, so React code can consistently migrate to callback refs, createRef(), or useRef().

  • #10010 f3e76ab Thanks @dyc3! - Fixed a bug in the LSP file watcher registration so Biome now watches .biome.json and .biome.jsonc configuration files and reloads workspace settings when they change.

  • #10176 8a40ef8 Thanks @dyc3! - Fixed #10011: The noThisInStatic rule no longer reports this when it is used as the constructor target in new this(...), which is required for inherited static factory methods.

  • #10163 6867e96 Thanks @jiwon79! - Fixed #9884: The useSortedAttributes auto-fix no longer corrupts source code when both an outer JSX element and a nested JSX-valued attribute have unsorted attributes in the same pass. Multiple unsorted groups separated by spread or shorthand attributes within the same JSX element are now reported as a single diagnostic.

  • #10079 d29dd19 Thanks @Damix48! - Fixed false positive in noAssignInExpressions for Svelte {@const} blocks. Assignments in {@const name = value} are now correctly recognized as declarations rather than accidental assignments in expressions.

  • #10080 5d8fdac Thanks @Damix48! - Fixed parsing of closing parentheses in Svelte {#each} block key expressions. Biome now correctly parses method calls and other parenthesised expressions used as keys.

    For example, the following snippets are now parsed correctly:

    {#each numbers as number, index (number.toString())}
  <p>{number}</p>
{/each}

{#each numbers as number (key(number))}
  <p>{number}</p>
{/each}

  • #10140 e7024b9 Thanks @solithcy! - Fixed #10135: Biome no longer crashes on missing Svelte template expressions.

    The following code snippet longer panics:

    {#if }
 <p>^ this would previously crash</p>
{/if}
{@const }
<p>    ^ this would also crash</p>

  • #10111 7818009 Thanks @jiwon79! - Fixed #9997: noDuplicateSelectors no longer reports false positives for selectors inside @scope queries. Biome now treats @scope as a separate at-rule context, like @media, @supports, @container, and @starting-style.

    The following snippet is no longer flagged as a duplicate:

    .Example {
  padding: 0;
}

@scope (.theme-dark) {
  .Example {
    color: white;
  }
}

  • #9926 d62b331 Thanks @dyc3! - Added the nursery lint rule useMathMinMax, which prefers Math.min() and Math.max() over equivalent ternary comparisons.

    For example, this code:

    const min = a < b ? a : b;

    is much more readable when rewritten as:

    const min = Math.min(a, b);

  • #10115 d428d76 Thanks @minseong0324! - useExhaustiveSwitchCases now flags missing true/false cases for boolean discriminants, including when boolean is a union variant.

  • #10125 a55a0b6 Thanks @bmish! - Fixed a resolver bug where packages that define a typed entry point through package.json's main field but omit types were ignored during type-aware resolution. Type-aware rules such as noFloatingPromises can now inspect imports from those packages.

  • #10117 895e809 Thanks @denizdogan! - Added support for the corner-shape family of CSS properties and the superellipse()/squircle() value functions, so noUnknownProperty and noUnknownFunction no longer flag them as unknown.

    New known properties: corner-shape, corner-block-end-shape, corner-block-start-shape, corner-bottom-left-shape, corner-bottom-right-shape, corner-bottom-shape, corner-end-end-shape, corner-end-start-shape, corner-inline-end-shape, corner-inline-start-shape, corner-left-shape, corner-right-shape, corner-start-end-shape, corner-start-start-shape, corner-top-left-shape, corner-top-right-shape, corner-top-shape.

    New known value functions: superellipse(), squircle().

  • #8620 8df8f73 Thanks @dyc3! - Fixed #8062: Added support for parsing Vue v-for directives more accurately.

  • #10191 aa055cd Thanks @guney! - Now the rule noStaticElementInteractions doesn't trigger custom elements.

  • #9757 2c62594 Thanks @dyc3! - Fixed #9099: the HTML formatter collapsing non-text children (inline elements, Svelte expressions, comments) onto a single line when the source had them on separate lines. Biome now preserves the user's intended line breaks for exclusively non-text children.

    For example, the following Svelte snippet is now preserved instead of being collapsed to <div>{name}<!-- comment --></div>:

    <div>
  {name}<!-- comment -->
</div>

    Similarly, HTML elements like <span> inside a <div> are now preserved when written on their own line:

    <div>
  <span>text</span>
</div>

  • #10105 e7c1a6d Thanks @jiwon79! - Fixed #10039: useReadonlyClassProperties now detects unreassigned private members in class expressions and export default classes, not only in class declarations.

    The following patterns are now correctly flagged:

    const AnonClass = class {
  #prop = 123;
  constructor() {
    console.log(this.#prop);
  }
};

export default class {
  #prop = 123;
  constructor() {
    console.log(this.#prop);
  }
}

  • #10141 46a77d0 Thanks @minseong0324! - Improved noUnnecessaryConditions to detect conditions that are always truthy because they check built-in global class instances such as Date, Map, Set, WeakMap, and Error.

  • #10178 7b05a89 Thanks @dyc3! - Fixed #10177: The HTML parser no longer reports lowercase html or doctype text as invalid after void elements such as <br>.

  • #10155 0d4595d Thanks @jiwon79! - Fixed #10045: the CSS formatter no longer compounds indentation inside nested functional pseudo-classes such as :not(:where(...)), :is(:where(...)), and similar combinations. The same fix also removes one level of unnecessary indentation that was added inside any pseudo-class function whose argument list wrapped onto multiple lines, including :nth-child(... of ...), ::part(...), and :active-view-transition-type(...). The following snippet is now correctly formatted, matching Prettier.

    input:not(
  :where(
    [type="submit"],
    [type="checkbox"],
    [type="radio"],
    [type="button"],
    [type="reset"]
  )
) {
  inline-size: 100%;
}

  • #10112 6f0251e Thanks @dyc3! - Fixed #10110: Biome's parser now accepts surrogate code points in JavaScript string \u{...} escapes.

  • #10141 46a77d0 Thanks @minseong0324! - Improved noMisleadingReturnType to detect object return annotations that hide built-in global class instances such as Date, Map, Set, WeakMap, and Error.

  • #10083 4a664c1 Thanks @ematipico! - Added two new options to noShadow, both defaulting to true to match typescript-eslint's behavior.

    Fixed #9482: Added ignoreFunctionTypeParameterNameValueShadow option. When enabled, parameter names inside function type annotations (e.g. (options: unknown) => void) are not flagged as shadowing outer variables.

    Fixed #7812: Added ignoreTypeValueShadow option. When enabled, a value binding that shares its name with a type-only declaration (type alias or interface) is not flagged, since types and values occupy separate namespaces in TypeScript.

  • #9286 52695cf Thanks @Hugo-Polloli! - Fixed #6316: Biome now resolves Svelte $store references to the underlying store binding in semantic analysis, preventing false noUndeclaredVariables diagnostics when the store is declared.

  • #10188 ae659dd Thanks @dyc3! - Added a new nursery rule noExcessiveNestedCallbacks, which disallows callbacks nested deeper than the configured maximum.

  • #9757 2c62594 Thanks @dyc3! - Fixed #9450: the HTML formatter now correctly preserves multiline formatting for nested <template> elements (e.g. <template #body>) when the source has children on separate lines. Previously, the children were collapsed onto a single line.

     <template>
   <UModal>
-    <template #body> <p>content</p> </template>
+    <template #body>
+      <p>content</p>
+    </template>
   </UModal>
 </template>

  • #10118 c6edcb4 Thanks @Netail! - Fixed #10024: biome migrate eslint correctly migrates eslint rules that belong to multiple Biome rules.

What's Changed
New Contributors

Full Changelog: https://github.com/biomejs/biome/compare/@biomejs/biome@2.4.13...@biomejs/biome@2.4.14

View originalPermalink
How 2.4.14 went
2.4.13

Biome CLI v2.4.13

Added 5
  • Add the nursery rule noUnnecessaryTemplateExpression, which disallows template literals that only contain string literal expressions
  • Add extra rule sources from ESLint CSS to improve biome migrate eslint detection
  • Add the new nursery rule useDomNodeTextContent, which prefers textContent over innerText for DOM node text access
  • Add the new nursery rule noReactNativeDeepImports that disallows deep imports from the react-native package
  • Add the new nursery rule useDomQuerySelector that prefers querySelector() and querySelectorAll() over older DOM query methods
Changed 1
  • Tweak the diagnostics range for useAltText, useButtonType, useHtmlLang, useIframeTitle, useValidAriaRole, and useIframeSandbox to report on the opening tag instead of the full tag
Fixed 5
  • Fix noMisleadingReturnType to no longer report false positives on a getter with a matching setter in the same namespace
  • Fix noUselessEscapeInRegex to no longer flag escapes of ClassSetReservedPunctuator characters inside v-flag character classes as useless
  • Fix useIframeSandbox to flag if there's no initializer value
  • Fix parsing of nested CSS rules correctly when declarations follow them inside embedded snippets
  • Fix noComponentHookFactories to no longer report false positives for object methods and class methods

From Biome

2.4.13
Patch Changes

  • #9969 c5eb92b Thanks @officialasishkumar! - Added the nursery rule noUnnecessaryTemplateExpression, which disallows template literals that only contain string literal expressions. These can be replaced with a simpler string literal.

    For example, the following code triggers the rule:

    const a = `${"hello"}`; // can be 'hello'
const b = `${"prefix"}_suffix`; // can be 'prefix_suffix'
const c = `${"a"}${"b"}`; // can be 'ab'

  • #10037 f785e8c Thanks @minseong0324! - Fixed #9810: noMisleadingReturnType no longer reports false positives on a getter with a matching setter in the same namespace.

    class Store {
  get status(): string {
    if (Math.random() > 0.5) return "loading";
    return "idle";
  }
  set status(v: string) {}
}

  • #10084 5e2f90c Thanks @jiwon79! - Fixed #10034: noUselessEscapeInRegex no longer flags escapes of ClassSetReservedPunctuator characters (&, !, #, %, ,, :, ;, <, =, >, @, `, ~) inside v-flag character classes as useless. These characters are reserved as individual code points in v-mode, so the escape is required.

    The following pattern is now considered valid:

    /[a-z\&]/v;

  • #10063 c9ffa16 Thanks @Netail! - Added extra rule sources from ESLint CSS. biome migrate eslint should do a bit better detecting rules in your eslint configurations.

  • #10035 946b50e Thanks @Netail! - Fixed #10032: useIframeSandbox now flags if there's no initializer value.

  • #9865 68fb8d4 Thanks @dyc3! - Added the new nursery rule useDomNodeTextContent, which prefers textContent over innerText for DOM node text access and destructuring.

    For example, the following snippet triggers the rule:

    const foo = node.innerText;

  • #10023 bd1e74f Thanks @ematipico! - Added a new nursery rule noReactNativeDeepImports that disallows deep imports from the react-native package. Internal paths like react-native/Libraries/... are not part of the public API and may change between versions.

    For example, the following code triggers the rule:

    import View from "react-native/Libraries/Components/View/View";

  • #9885 3dce737 Thanks @dyc3! - Added a new nursery rule useDomQuerySelector that prefers querySelector() and querySelectorAll() over older DOM query methods such as getElementById() and getElementsByClassName().

  • #9995 4da9caf Thanks @siketyan! - Fixed #9994: Biome now parses nested CSS rules correctly when declarations follow them inside embedded snippets.

  • #10009 b41cc5a Thanks @Jayllyz! - Fixed #10004: noComponentHookFactories no longer reports false positives for object methods and class methods.

  • #9988 eabf54a Thanks @Netail! - Tweaked the diagnostics range for useAltText, useButtonType, useHtmlLang, useIframeTitle, useValidAriaRole & useIfameSandbox to report on the opening tag instead of the full tag.

  • #10043 fc65902 Thanks @mujpao! - Fixed #10003: Biome no longer panics when parsing Svelte files containing {#}.

  • #9815 5cc83b1 Thanks @dyc3! - Added the new nursery rule noLoopFunc. When enabled, it warns when a function declared inside a loop captures outer variables that can change across iterations.

  • #9702 ef470ba Thanks @ryan-m-walker! - Added the nursery rule useRegexpTest that enforces RegExp.prototype.test() over String.prototype.match() and RegExp.prototype.exec() in boolean contexts. test() returns a boolean directly, avoiding unnecessary computation of match results.

    Invalid

    if ("hello world".match(/hello/)) {
}

    Valid

    if (/hello/.test("hello world")) {
}

  • #9743 245307d Thanks @leetdavid! - Fixed #2245: Svelte <script> tag language detection when the generics attribute contains > characters (e.g., <script lang="ts" generics="T extends Record<string, unknown>">). Biome now correctly recognizes TypeScript in such script blocks.

  • #10046 0707de7 Thanks @Conaclos! - Fixed #10038: organizeImports now sorts imports in TypeScript modules and declaration files.

      declare module "mymodule" {
-  	import type { B } from "b";
  	import type { A } from "a";
+  	import type { B } from "b";
  }

  • #10012 94ccca9 Thanks @ematipico! - Added the nursery rule noReactNativeLiteralColors, which disallows color literals inside React Native styles.

    The rule belongs to the reactNative domain. It reports properties whose name contains color and whose value is a string literal when they appear inside a StyleSheet.create(...) call or inside a JSX attribute whose name contains style.

    // Invalid
const Hello = () => <Text style={{ backgroundColor: "#FFFFFF" }}>hi</Text>;

const styles = StyleSheet.create({
  text: { color: "red" },
});

    // Valid
const red = "#f00";
const styles = StyleSheet.create({
  text: { color: red },
});

  • #10005 131019e Thanks @ematipico! - Added the nursery rule noReactNativeRawText, which disallows raw text outside of <Text> components in React Native.

    The rule belongs to the new reactNative domain.

    // Invalid
<View>some text</View>
<View>{'some text'}</View>

    // Valid
<View>
  <Text>some text</Text>
</View>

    Additional components can be allowlisted through the skip option:

    {
  "options": {
    "skip": ["Title"]
  }
}

  • #9911 1603f78 Thanks @Netail! - Added the nursery rule noJsxLeakedDollar, which flags text nodes with a trailing $ if the next sibling node is a JSX expression. This could be an unintentional mistake, resulting in a '$' being rendered as text in the output.

    Invalid:

    function MyComponent({ user }) {
  return <div>Hello ${user.name}</div>;
}

  • #9999 f42405f Thanks @minseong0324! - Fixed noMisleadingReturnType incorrectly flagging functions with reassigned let variables.

  • #10075 295f97f Thanks @ematipico! - Fixed #9983: Biome now parses functions declared inside Svelte #snippet blocks without throwing errors.

  • #10006 cf4c1c9 Thanks @minseong0324! - Fixed #9810: noMisleadingReturnType incorrectly flagging nested object literals with widened properties.

  • #10033 11ddc05 Thanks @ematipico! - Added the nursery rule useReactNativePlatformComponents that ensures platform-specific React Native components (e.g. ProgressBarAndroid, ActivityIndicatorIOS) are only imported in files with a matching platform suffix. It also reports when Android and iOS components are mixed in the same file.

    The following code triggers the rule when the file does not have an .android.js suffix:

    // file.js
import { ProgressBarAndroid } from "react-native";
What's Changed
New Contributors

Full Changelog: https://github.com/biomejs/biome/compare/@biomejs/biome@2.4.12...@biomejs/biome@2.4.13

View originalPermalink
How 2.4.13 went
2.4.12

Biome CLI v2.4.12

Added 4
  • Added the nursery/noIdenticalTestTitle lint rule that disallows using the same title for two describe blocks or two test cases at the same nesting level
  • Added the nursery rule noComponentHookFactories that disallows defining React components or custom hooks inside other functions
  • Added the nursery rule useIframeSandbox which enforces the sandbox attribute for iframe tags
  • Added the nursery rule noJsxNamespace which disallows JSX namespace syntax
Changed 5
  • Improved the diagnostics for useForOf to better explain the problem, why it matters, and how to fix it
  • Improved the noGlobalObjectCalls diagnostic to better explain why calling global objects like Math or JSON is invalid and how to fix it
  • Improved the noMultiStr diagnostic to explain why escaped multiline strings are discouraged and what to use instead
  • Improved the noSelfCompare diagnostic to better explain why comparing a value to itself is suspicious and what to use for NaN checks
  • The noFloatingPromises rule now detects floating promises through cross-module generic wrapper functions
Fixed 5
  • Fixed issue #9941: Biome now emits a warning diagnostic when a file exceeds the files.maxSize limit
  • Fixed issue #9918: useConsistentTestIt no longer panics when applying fixes to chained calls such as test.for([])('x', () => {})
  • Fixed issue #9901: the command lint --write is now idempotent when it's run against HTML-ish files that contains scripts and styles
  • Fixed issue #9113: Biome now parses and formats @media and other conditional blocks correctly inside embedded CSS snippets
  • Fixed issue #9975: Biome now parses nested CSS selectors correctly inside embedded snippets without requiring an explicit &

From Biome

2.4.12
Patch Changes

  • #9376 9701a33 Thanks @dyc3! - Added the nursery/noIdenticalTestTitle lint rule. This rule disallows using the same title for two describe blocks or two test cases at the same nesting level.

    describe("foo", () => {});
describe("foo", () => {
  // invalid: same title as previous describe block
  test("baz", () => {});
  test("baz", () => {}); // invalid: same title as previous test case
});

  • #9889 7ae83f2 Thanks @dyc3! - Improved the diagnostics for useForOf to better explain the problem, why it matters, and how to fix it.

  • #9916 27dd7b1 Thanks @Jayllyz! - Added a new nursery rule noComponentHookFactories, that disallows defining React components or custom hooks inside other functions.

    For example, the following snippets trigger the rule:

    function createComponent(label) {
  function MyComponent() {
    return <div>{label}</div>;
  }
  return MyComponent;
}

    function Parent() {
  function Child() {
    return <div />;
  }
  return <Child />;
}

  • #9980 098f1ff Thanks @ematipico! - Fixed #9941: Biome now emits a warning diagnostic when a file exceed the files.maxSize limit.

  • #9942 9956f1d Thanks @dyc3! - Fixed #9918: useConsistentTestIt no longer panics when applying fixes to chained calls such as test.for([])("x", () => {});.

  • #9891 4d9ac51 Thanks @dyc3! - Improved the noGlobalObjectCalls diagnostic to better explain why calling global objects like Math or JSON is invalid and how to fix it.

  • #9902 3f4d103 Thanks @ematipico! - Fixed #9901: the command lint --write is now idempotent when it's run against HTML-ish files that contains scripts and styles.

  • #9891 4d9ac51 Thanks @dyc3! - Improved the noMultiStr diagnostic to explain why escaped multiline strings are discouraged and what to use instead.

  • #9966 322675e Thanks @siketyan! - Fixed #9113: Biome now parses and formats @media and other conditional blocks correctly inside embedded CSS snippets.

  • #9835 f8d49d9 Thanks @bmish! - The noFloatingPromises rule now detects floating promises through cross-module generic wrapper functions. Previously, patterns like export const fn = trace(asyncFn) — where trace preserves the function signature via a generic <F>(fn: F): F — were invisible to the rule when the wrapper was defined in a different file.

  • #9981 02bd8dd Thanks @siketyan! - Fixed #9975: Biome now parses nested CSS selectors correctly inside embedded snippets without requiring an explicit &.

  • #9949 e0ba71d Thanks @Netail! - Added the nursery rule useIframeSandbox, which enforces the sandbox attribute for iframe tags.

    Invalid:

    <iframe></iframe>

  • #9913 d417803 Thanks @Netail! - Added the nursery rule noJsxNamespace, which disallows JSX namespace syntax.

    Invalid:

    <ns:testcomponent />

  • #9892 e75d70e Thanks @dyc3! - Improved the noSelfCompare diagnostic to better explain why comparing a value to itself is suspicious and what to use for NaN checks.

  • #9861 2cff700 Thanks @dyc3! - Added the new nursery rule useVarsOnTop, which requires var declarations to appear at the top of their containing scope.

    For example, the following code now triggers the rule:

    function f() {
  doSomething();
  var value = 1;
}

  • #9892 e75d70e Thanks @dyc3! - Improved the noThenProperty diagnostic to better explain why exposing then can create thenable behavior and how to avoid it.

  • #9892 e75d70e Thanks @dyc3! - Improved the noShorthandPropertyOverrides diagnostic to explain why later shorthand declarations can unintentionally overwrite earlier longhand properties.

  • #9978 4847715 Thanks @mdevils! - Fixed #9744: useExhaustiveDependencies no longer reports false positives for variables obtained via object destructuring with computed keys, e.g. const { [KEY]: key1 } = props.

  • #9892 e75d70e Thanks @dyc3! - Improved the noRootType diagnostic to better explain that the reported root type is disallowed by project configuration and how to proceed.

  • #9927 7974ab7 Thanks @dyc3! - Added eslint-plugin-unicorn's no-nested-ternary as a rule source for noNestedTernary

  • #9873 19ff706 Thanks @minseong0324! - noMisleadingReturnType now checks class methods, object methods, and getters in addition to functions.

  • #9888 362b638 Thanks @dyc3! - Updated metadata for biome migrate eslint to better reflect which ESLint rules are redundant versus unsupported versus unimplemented.

  • #9892 e75d70e Thanks @dyc3! - Improved the noAutofocus diagnostic to better explain why autofocus harms accessibility outside allowed modal contexts.

  • #9982 d6bdf4a Thanks @dyc3! - Improved performance of noMagicNumbers. Biome now maps ESLint no-magic-numbers sources more accurately during biome migrate eslint.

  • #9889 7ae83f2 Thanks @dyc3! - Improved the diagnostics for noConstantCondition to better explain the problem, why it matters, and how to fix it.

  • #9866 40bd180 Thanks @dyc3! - Added a new nursery rule noExcessiveSelectorClasses, which limits how many class selectors can appear in a single CSS selector.

  • #9796 f1c1363 Thanks @dyc3! - Added a new nursery rule useStringStartsEndsWith, which prefers startsWith() and endsWith() over verbose string prefix and suffix checks.

    The rule uses type information, so it only reports on strings and skips array lookups such as items[0] === "a".

  • #9942 9956f1d Thanks @dyc3! - Fixed the safe fix for noSkippedTests so it no longer panics when rewriting skipped test function names such as xit(), xtest(), and xdescribe().

  • #9874 9e570d1 Thanks @minseong0324! - Type-aware lint rules now resolve members through Pick<T, K> and Omit<T, K> utility types.

  • #9909 0d0e611 Thanks @Netail! - Added the nursery rule useReactAsyncServerFunction, which requires React server actions to be async.

    Invalid:

    function serverFunction() {
  "use server";
  // ...
}

  • #9925 29accb3 Thanks @ematipico! - Fixed #9910: added support for parsing member expressions in Svelte directive properties. Biome now correctly parses directives like in:renderer.in|global, use:obj.action, and deeply nested forms like in:a.b.c|global.

  • #9904 e7775a5 Thanks @ematipico! - Fixed #9626: noUnresolvedImports no longer reports false positives for named imports from packages that have a corresponding @types/* package installed. For example, import { useState } from "react" with @types/react installed is now correctly recognised.

  • #9942 9956f1d Thanks @dyc3! - Fixed the safe fix for noFocusedTests so it no longer panics when rewriting focused test function names such as fit() and fdescribe().

  • #9577 c499f46 Thanks @tt-a1i! - Added the nursery rule useReduceTypeParameter. It flags type assertions on the initial value passed to Array#reduce and Array#reduceRight and recommends using a type parameter instead.

    // before: type assertion on initial value
arr.reduce((sum, num) => sum + num, [] as number[]);

// after: type parameter on the call
arr.reduce<number[]>((sum, num) => sum + num, []);

  • #9895 1c8e1ef Thanks @Netail! - Added extra rule sources from react-xyz. biome migrate eslint should do a bit better detecting rules in your eslint configurations.

  • #9891 4d9ac51 Thanks @dyc3! - Improved the noInvalidUseBeforeDeclaration diagnostic to better explain why using a declaration too early is problematic and how to fix it.

  • #9889 7ae83f2 Thanks @dyc3! - Improved the diagnostics for noRedeclare to better explain the problem, why it matters, and how to fix it.

  • #9875 a951586 Thanks @minseong0324! - Type-aware lint rules now resolve members through Partial<T>, Required<T>, and Readonly<T> utility types, preserving optional, readonly, and nullable member flags.

What's Changed
New Contributors

Full Changelog: https://github.com/biomejs/biome/compare/@biomejs/biome@2.4.11...@biomejs/biome@2.4.12

View originalPermalink
How 2.4.12 went
2.4.11

Biome CLI v2.4.11

Added 4
  • Added the new nursery rule useConsistentTestIt in the test domain to enforce consistent use of either it or test for test functions in Jest/Vitest suites
  • Added the new nursery lint rule useExplicitReturnType to report TypeScript functions and methods that omit an explicit return type
  • Added the rule noMisleadingReturnType to detect when a function's return type annotation is wider than what the implementation actually returns
  • Added a new lint rule useDisposables for JavaScript to detect disposable objects assigned to variables without using or await using syntax
Changed 2
  • Improved the diagnostics for useFind to better explain the problem, why it matters, and how to fix it
  • Improved performance of fix-all operations by running only rules that have code fixes first, then running the rest of the rules
Fixed 5
  • Fixed the formatter to no longer panic when formatting files that contain graphql tagged template literals combined with parenthesized expressions
  • Fixed an issue where bindings and references were not properly tracked, causing false positives from noUnusedVariables and noUndeclaredVariables in Svelte, Vue, and Astro files
  • Fixed the noDelete rule to no longer trigger for delete process.env.FOO, since delete is the documented way to remove environment variables in Node.js
  • Fixed support for CSS scroll-driven animation timeline-range-name keyframe selectors so Biome no longer reports parse errors on keyframes like entry 0% or exit 100%
  • Fixed Astro frontmatter to correctly parse regular expression literals like /\d{4}/

From Biome

2.4.11
Patch Changes

  • #9350 4af4a3a Thanks @dyc3! - Added the new nursery rule useConsistentTestIt in the test domain. The rule enforces consistent use of either it or test for test functions in Jest/Vitest suites, with separate control for top-level tests and tests inside describe blocks.

    Invalid:

    test("should fly", () => {}); // Top-level test using 'test' flagged, convert to 'it'

describe("pig", () => {
  test("should fly", () => {}); // Test inside 'describe' using 'test' flagged, convert to 'it'
});

  • #9429 a2f3f7e Thanks @ematipico! - Added the new nursery lint rule useExplicitReturnType. It reports TypeScript functions and methods that omit an explicit return type.

    function toString(x: any) {
  // rule triggered, it doesn't declare a return type
  return x.toString();
}

  • #9828 9e40844 Thanks @ematipico! - Fixed #9484: the formatter no longer panics when formatting files that contain graphql tagged template literals combined with parenthesized expressions.

  • #9886 e7c681e Thanks @ematipico! - Fixed an issue where, occasionally, some bindings and references were not properly tracked, causing false positives from noUnusedVariables and noUndeclaredVariables in Svelte, Vue, and Astro files.

  • #9760 5b16d18 Thanks @myx0m0p! - Fixed #4093: the noDelete rule no longer triggers for delete process.env.FOO, since delete is the documented way to remove environment variables in Node.js.

  • #9799 2af8efd Thanks @minseong0324! - Added the rule noMisleadingReturnType. The rule detects when a function's return type annotation is wider than what the implementation actually returns.

    // Flagged: `: string` is wider than `"loading" | "idle"`
function getStatus(b: boolean): string {
  if (b) return "loading";
  return "idle";
}

  • #9880 7f67749 Thanks @dyc3! - Improved the diagnostics for useFind to better explain the problem, why it matters, and how to fix it.

  • #9755 bff7bdb Thanks @ematipico! - Improved performance of fix-all operations (--write). Biome is now smarter when it runs lint rules and assist actions. First, it runs only rules that have code fixes, and then runs the rest of the rules.

  • #8651 aafca2d Thanks @siketyan! - Add a new lint rule useDisposables for JavaScript, which detects disposable objects assigned to variables without using or await using syntax. Disposable objects that implement the Disposable or AsyncDisposable interface are intended to be disposed of after use. Not disposing them can lead to resource or memory leaks, depending on the implementation.

    Invalid:

    function createDisposable(): Disposable {
  return {
    [Symbol.dispose]() {
      // do something
    },
  };
}

const disposable = createDisposable();

    Valid:

    function createDisposable(): Disposable {
  return {
    [Symbol.dispose]() {
      // do something
    },
  };
}

using disposable = createDisposable();

  • #9788 53b8e57 Thanks @MeGaNeKoS! - Fixed #7760: Added support for CSS scroll-driven animation timeline-range-name keyframe selectors (cover, contain, entry, exit, entry-crossing, exit-crossing). Biome no longer reports parse errors on keyframes like entry 0% { ... } or exit 100% { ... }.

  • #9728 5085424 Thanks @mkosei! - Fixed #9696: Astro frontmatter now correctly parses regular expression literals like /\d{4}/.

  • #9261 16b6c49 Thanks @ematipico! - Fixed #8409: CSS formatter now correctly places comments after the colon in property declarations.

    Previously, comments that appeared after the colon in CSS property values were incorrectly moved before the property name:

    [lang]:lang(ja) {
-  /* system-ui,*/ font-family:
+  font-family: /* system-ui,*/
    Hiragino Sans,
    sans-serif;
}

  • #9441 957ea4c Thanks @soconnor-seeq! - Fixed #1630: LSP project selection now prefers the most specific project root in nested workspaces.

  • #9878 de6210f Thanks @ematipico! - Fixed #9118: noUnusedImports no longer reports false positives for default imports used inside Svelte, Vue and Astro components.

  • #9879 ce7e2b7 Thanks @dyc3! - Fixed a parser diagnostic's message when vue syntax is disabled so that it no longer references the non-existant html.parser.vue option. This option will become available in 2.5.

  • #9880 7f67749 Thanks @dyc3! - Improved the diagnostics for useRegexpExec to better explain the problem, why it matters, and how to fix it.

  • #9846 b7134d9 Thanks @ematipico! - Fixed #9140: Biome now parses Astro's attribute shorthand inside .astro files. The following snippet no longer reports a parse error:

    ---
const items = ['a', 'b'];
---
<ul>
  {items.map((item) => <li {item}>row</li>)}
</ul>

  • #9790 67df09d Thanks @dyc3! - Fixed #9781: Trailing comments after a top-level biome-ignore-all format suppression are now preserved instead of being dropped. This applies to JavaScript, CSS, HTML, JSONC, GraphQL, and Grit files.

  • #9745 d87073e Thanks @ematipico! - Fixed #9741: the LSP server now correctly returns the organizeImports code action when the client requests it via source.organizeImports.biome in the only filter. Previously, editors with codeAction/resolve support (e.g. Zed) received an empty response because the action was serialized with the wrong kind (source.biome.organizeImports instead of source.organizeImports.biome).

  • #9880 7f67749 Thanks @dyc3! - Improved the diagnostics for useArraySome to better explain the problem, why it matters, and how to fix it.

  • #9795 1d09f0f Thanks @dyc3! - Relaxed useExplicitType for trivially inferrable types.

    Type annotations can now be omitted when types are trivially inferrable from:

    • Binary expressions (const sum = 1 + 1)
    • Comparison expressions (const isEqual = 'a' === 'b', const isTest = process.env.NODE_ENV === 'test')
    • Logical expressions (const and = true && false)
    • Class instantiation (const date = new Date())
    • Array literals (const arr = [1, 2, 3])
    • Conditional expressions (const val = true ? 'yes' : 'no')
    • Function calls (const num = Math.random())
    • Parameter defaults - any expression is now allowed (const fn = (max = MAX_ATTEMPTS) => ...)

    Comparison expressions always return boolean, so any operands are now allowed (including property access like process.env.NODE_ENV).

    Parameters with default values no longer require type annotations, as TypeScript can infer the type from the default value (even when referencing variables).

    Also removed the redundant any type validation from this rule. The any type is now only validated by the dedicated noExplicitAny rule, following the Single Responsibility Principle.

  • #9809 e8cad58 Thanks @Netail! - Added the new nursery rule useQwikLoaderLocation, which enforces that Qwik loader functions are declared in the correct location.

  • #9877 fc9d715 Thanks @ematipico! - Fixed #9136 and #9653: noUndeclaredVariables and noUnusedVariables no longer report false positives on several Svelte template constructs that declare or reference bindings in the host grammar:

    • {#snippet name(params)} — the snippet name and its parameters (including object, array, rest, and nested destructuring) are now tracked.
    • {@render name(args)} — the snippet name used at the render site is now resolved against the snippet declaration.
    • {#each items as item, index (key)} — the item binding (plain identifier or destructured), the optional index, and the optional key expression are now tracked.
    • {@const name = value} — the declared name is now tracked as a binding and the initializer is analyzed for undeclared references.
    • {@debug a, b, c} — each debugged identifier is now analyzed and reported if undeclared.
    • Shorthand attributes <img {src} /> — the curly-shorthand attribute is now analyzed as an expression, so undeclared references inside it are reported.

    For example, the following template no longer triggers either rule:

    <script>
let items = [];
let total = 0;
</script>

{#snippet figure(image)}
    <figure>
        <img src={image.src} alt={image.caption} />
        <figcaption>{image.caption}</figcaption>
    </figure>
{/snippet}

{#each items as item}
    {@const price = item.price}
    {@render figure(item)}
    <span>{price}</span>
{/each}

{@debug items, total}

  • #9869 78bce77 Thanks @Netail! - Updated noDuplicateFieldDefinitionNames to also flag duplicate fields within type extensions, interface extensions & input extensions.

  • #9739 0bc2198 Thanks @dyc3! - Fixed Grit queries that use native Biome AST node names with the native field names that are in our .ungram grammar files. Queries such as JsConditionalExpression(consequent = $cons, alternate = $alt) now compile successfully in biome search and grit plugins.

  • #9811 2dddca3 Thanks @dyc3! - Updated noImpliedEval to flag new Function() usages, as its a form of indirect eval, and to include no-new-func as a rule source.

  • #9870 ccf9770 Thanks @Netail! - Marked eslint-qwik-plugin's unused-server as redundant since it was covered by noUnusedVariables.

  • #9701 1417c3b Thanks @dyc3! - Added the new nursery rule noUselessTypeConversion, which reports redundant primitive conversion patterns such as String(value) when value is already a string.

  • #9248 49f00a3 Thanks @pkallos! - useNullishCoalescing now also detects ternary expressions that check for null or undefined and suggests rewriting them with ??. A new ignoreTernaryTests option allows disabling this behavior.

  • #9863 6a44619 Thanks @ematipico! - Fixed #9690: biome check --write is now idempotent on HTML files that contain embedded <style> or <script> blocks. Previously, each run reported "Fixed 1 file" even when the file content did not actually change, because the embedded language formatter's output was not re-indented to match the surrounding HTML block.

What's Changed
New Contributors

Full Changelog: https://github.com/biomejs/biome/compare/@biomejs/biome@2.4.10...@biomejs/biome@2.4.11

View originalPermalink
How 2.4.11 went
2.4.10

Biome CLI v2.4.10

Added 2
  • Added new lint nursery rule noImpliedEval that detects implied eval() usage through functions like setTimeout, setInterval, and setImmediate when called with string arguments
  • Added the new nursery rule noUnsafePlusOperands, which reports + and += operations that use object-like, symbol, unknown, or never operands, or that mix number with bigint
Changed 1
  • Improved the performance of the commands lint and check when they are called with --write
Fixed 10
  • Fixed noUnusedVariables to no longer report false positives for TypeScript namespace declarations that participate in declaration merging with an exported or used value declaration of the same name
  • Fixed noNegationElse to keep ternary branch comments attached to the correct branch when applying its fixer
  • Fixed noProcessEnv to detect process.env when process is imported from the process or node:process modules
  • Fixed Svelte #each destructuring parsing and formatting for nested patterns such as [key, { a, b }]
  • Improved the performance of how the Biome Language Server pulls code actions and diagnostics by computing them lazily instead of all at once
  • Fixed useVueValidVBind to no longer report valid object bindings like v-bind="props"

From Biome

2.4.10
Patch Changes

  • #8838 f3a6a6b Thanks @baeseokjae! - Added new lint nursery rule noImpliedEval.

    The rule detects implied eval() usage through functions like setTimeout, setInterval, and setImmediate when called with string arguments.

    // Invalid
setTimeout("alert('Hello');", 100);

// Valid
setTimeout(() => alert("Hello"), 100);

  • #9320 93c3b6c Thanks @taberoajorge! - Fixed #7664: noUnusedVariables no longer reports false positives for TypeScript namespace declarations that participate in declaration merging with an exported or used value declaration (const, function, or class) of the same name. The reverse direction is also handled: a value declaration merged with an exported namespace is no longer flagged.

  • #9630 1dd4a56 Thanks @raashish1601! - Fixed #9629: noNegationElse now keeps ternary branch comments attached to the correct branch when applying its fixer.

  • #9216 04243b0 Thanks @FrederickStempfle! - Fixed #9061: noProcessEnv now also detects process.env when process is imported from the "process" or "node:process" modules.

    Previously, only the global process object was flagged:

    import process from "node:process";
// This was not flagged, but now it is:
console.log(process.env.NODE_ENV);

  • #9692 61b7ec5 Thanks @mkosei! - Fixed Svelte #each destructuring parsing and formatting for nested patterns such as [key, { a, b }].

  • #9627 06a0f35 Thanks @ematipico! - Fixed #191: Improved the performance of how the Biome Language Server pulls code actions and diagnostics.

    Before, code actions were pulled and computed all at once in one request. This approach couldn't work in big files, and caused Biome to stale and have CPU usage spikes up to 100%.

    Now, code actions are pulled and computed lazily, and Biome won't choke anymore in big files.

  • #9643 5bfee36 Thanks @dyc3! - Fixed #9347: useVueValidVBind no longer reports valid object bindings like v-bind="props".

  • #9627 06a0f35 Thanks @ematipico! - Fixed assist diagnostics being invisible when using --diagnostic-level=error. Enforced assist violations (e.g. useSortedKeys) were filtered out before being promoted to errors, causing biome check to incorrectly return success.

  • #9695 9856a87 Thanks @dyc3! - Added the new nursery rule noUnsafePlusOperands, which reports + and += operations that use object-like, symbol, unknown, or never operands, or that mix number with bigint.

  • #9627 06a0f35 Thanks @ematipico! - Fixed duplicate parse errors in check and ci output. When a file had syntax errors, the same parse error was printed twice and the error count was inflated.

  • #9627 06a0f35 Thanks @ematipico! - Improved the performance of the commands lint and check when they are called with --write.

  • #9627 06a0f35 Thanks @ematipico! - Fixed --diagnostic-level not fully filtering diagnostics. Setting --diagnostic-level=error now correctly excludes warnings and infos from both the output and the summary counts.

  • #9623 13b3261 Thanks @ematipico! - Fixed #9258: --skip no longer causes suppressions/unused warnings for suppression comments targeting skipped rules or domains.

  • #9631 599dd04 Thanks @raashish1601! - Fixed #9625: experimentalEmbeddedSnippetsEnabled no longer crashes when a file mixes formatable CSS-in-JS templates with tagged templates that the embedded formatter can't currently delegate, such as a styled-components interpolation returning `css```.

What's Changed
New Contributors

Full Changelog: https://github.com/biomejs/biome/compare/@biomejs/biome@2.4.9...@biomejs/biome@2.4.10

View originalPermalink
How 2.4.10 went
2.4.9

Biome CLI v2.4.9

Added 1
  • Add a new nursery CSS rule noDuplicateSelectors that disallows duplicate selector lists within the same at-rule context
Fixed 10
  • useOptionalChain now detects negated logical OR chains
  • useAdjacentOverloadSignatures no longer reports false positives for static and instance methods with the same name
  • Fix a panic when Biome analyzed ambient TypeScript modules containing class constructor, getter, or setter signatures that reference local type aliases
  • Fix a bug where enabling the rules of a whole group would enable rules that belonged to a domain under the same group
  • Grit patterns using export { $foo } from $source now match named re-exports in JavaScript and TypeScript files
  • Biome now parses conditional expressions whose consequent is an arrow function returning a parenthesized object expression

From Biome

2.4.9
Patch Changes

  • #9315 085d324 Thanks @ematipico! - Added a new nursery CSS rule noDuplicateSelectors, that disallows duplicate selector lists within the same at-rule context.

    For example, the following snippet triggers the rule because the second selector and the first selector are the same:

    /* First selector */
.x .y .z {
}

/* Second selector */
.x {
  .y {
    .z {
    }
  }
}

  • #9567 b7ab931 Thanks @ematipico! - Fixed #7211: useOptionalChain now detects negated logical OR chains. The following code is now considered invalid:

    !foo || !foo.bar;

  • #8670 607ebf9 Thanks @tt-a1i! - Fixed #8345: useAdjacentOverloadSignatures no longer reports false positives for static and instance methods with the same name. Static methods and instance methods are now treated as separate overload groups.

    class Kek {
  static kek(): number {
    return 0;
  }
  another(): string {
    return "";
  }
  kek(): number {
    return 1;
  } // no longer reported as non-adjacent
}

  • #9476 97b80a8 Thanks @masterkain! - Fixed #9475: Fixed a panic when Biome analyzed ambient TypeScript modules containing class constructor, getter, or setter signatures that reference local type aliases. Biome now handles these declarations without crashing during semantic analysis.

  • #9553 0cd5298 Thanks @dyc3! - Fixed a bug where enabling the rules of a whole group, would enable rules that belonged to a domain under the same group.

    For example, linter.rules.correctness = "error" no longer enables React- or Qwik-specific correctness rules unless linter.domains.react, linter.domains.qwik, or an explicit rule config also enables them, or their relative dependencies are installed.

  • #9586 4cafb71 Thanks @dyc3! - Fixed #8828: Grit patterns using export { $foo } from $source now match named re-exports in JavaScript and TypeScript files.

  • #9550 d4e3d6e Thanks @dyc3! - Fixed #9548: Biome now parses conditional expressions whose consequent is an arrow function returning a parenthesized object expression.

  • #8696 a7c19cc Thanks @Faizanq! - Fixed #8685 where noUselessLoneBlockStatements would remove empty blocks containing comments. The rule now preserves these blocks since comments may contain important information like TODOs or commented-out code.

  • #9557 6671ac5 Thanks @datalek! - Fixed #9557: Biome's LSP server no longer crashes on startup when used with editors that don't send workspaceFolders during initialization. This affected any LSP client that only sends rootUri, which is valid per the LSP specification.

  • #9455 1710cf1 Thanks @omar-y-abdi! - Fixed #9174: useExpect now correctly rejects asymmetric matchers in Vitest or Jest like expect.stringContaining(), expect.objectContaining(), and utilities like expect.extend() that are not valid assertions. Previously these constructs caused false negatives, allowing tests without real assertions to pass the lint rule.

  • #9584 956e367 Thanks @ematipico! - Fixed a bug where Vue directive attribute values like v-bind:class="{'dynamic': true}" were incorrectly parsed as JavaScript statements instead of expressions. Object literals inside directive values like :class, v-if, and v-html are now correctly parsed as expressions, preventing spurious parse errors.

  • #9474 e168494 Thanks @ematipico! - Added the new nursery rule noUntrustedLicenses. This rule disallows dependencies that ship with invalid licenses or licenses that don't meet the criteria of your project/organisation.

    The rule has the following options:

    • allow: a list of licenses that can be allowed. Useful to bypass possible invalid licenses from downstream dependencies.
    • deny: a list of licenses that should trigger the rule. Useful to deny licenses that don't fit your project/organisation. When both deny and allow are provided, deny takes precedence.
    • requireOsiApproved: whether the licenses need to be approved by the Open Source Initiative.
    • requireFsfLibre: whether the licenses need to be approved by the Free Software Foundation.

  • #9544 723798b Thanks @ViniciusDev26! - Added an unsafe fix to useConsistentMethodSignatures that automatically converts between method-style and property-style signatures.

  • #9555 8a3647b Thanks @ematipico! - Fixed #188: the Biome Language Server no longer panics when open files change abruptly, such as during git branch checkouts.

  • #9605 f65c637 Thanks @ematipico! - Fixed #9589. Now Biome correctly parses object expressions inside props and directives. The following code doesn't emit errors anymore:

    <style is:global define:vars={{ bgLight: light }}>
<Component name={{ first, name }} />

  • #9565 ccb249e Thanks @eyupcanakman! - Fixed #9505: noUselessStringConcat no longer reports tagged template literals as useless string concatenations. Tagged templates invoke a function and can return non-string values, so combining them with + is not equivalent to a single template literal.

  • #9534 4d050df Thanks @Netail! - Added the nursery rule noInlineStyles. The rule disallows the use of inline style attributes in HTML and the style prop in JSX, including React.createElement calls. Inline styles make code harder to maintain and can interfere with Content Security Policy.

  • #9611 cddaa44 Thanks @gaauwe! - Fixed a regression where Biome LSP could misread editor settings sent through workspace/didChangeConfiguration when the payload was wrapped in a top-level biome key. This caused requireConfiguration and related settings to be ignored in some editors.

What's Changed
New Contributors

Full Changelog: https://github.com/biomejs/biome/compare/@biomejs/biome@2.4.8...@biomejs/biome@2.4.9

View originalPermalink
How 2.4.9 went
2.4.8

Biome CLI v2.4.8

Added 2
  • Added the rule `noDrizzleUpdateWithoutWhere` to prevent accidental full-table updates when using Drizzle ORM without a `.where()` clause
  • Added support for modern CSS properties, pseudo-classes, and pseudo-elements
Fixed 12
  • The "Biome found a configuration file outside of the current working directory" diagnostic now includes the configuration file path and the working directory
  • TypeScript arrow function formatting when a comment appears after `=>`
  • Astro frontmatter containing regex literals with quotes or dashes no longer causes parse errors
  • Remove extra space before `>` when `bracketSameLine` is true and the self-closing slash is absent in HTML formatter
  • The HTML parser no longer incorrectly reports `---` inside element content as an "Unexpected value or character" error
  • `biome check --write` no longer falsely reports Svelte and Vue files as changed when `html.formatter.indentScriptAndStyle` is enabled and the files are already correctly formatted

From Biome

2.4.8
Patch Changes

  • #9488 bc709f6 Thanks @mvanhorn! - Fixed #9463: the "Biome found a configuration file outside of the current working directory" diagnostic now includes the configuration file path and the working directory, giving users actionable information to debug the issue.

  • #9527 2f8bf80 Thanks @mdm317! - Fixed #8959: Fixed TypeScript arrow function formatting when a comment appears after =>.

  • #9525 e7b3b10 Thanks @ViniciusDev26! - Added the rule noDrizzleUpdateWithoutWhere to prevent accidental full-table updates when using Drizzle ORM without a .where() clause.

  • #9531 1302740 Thanks @ematipico! - Fixed #9187: Astro frontmatter containing regex literals with quotes (/'/, /"/) or dashes (/---/) no longer causes parse errors.

  • #9535 b630d93 Thanks @leno23! - Fixed #9524: remove extra space before > when bracketSameLine is true and the self-closing slash is absent in HTML formatter.

  • #9537 81e6306 Thanks @ematipico! - Fixed #9238: The HTML parser no longer incorrectly reports --- inside element content (e.g. <td>---</td>) as an "Unexpected value or character" error.

  • #9532 4b64145 Thanks @ematipico! - Fixed #9117: biome check --write no longer falsely reports Svelte and Vue files as changed when html.formatter.indentScriptAndStyle is enabled and the files are already correctly formatted.

  • #9528 61451ef Thanks @ematipico! - Fixed #9341: Fixed an LSP crash that could corrupt file content when saving with format-on-save enabled.

  • #9538 794f79c Thanks @ematipico! - Fixed #9279: The rule noSubstr now detects .substr() and .substring() calls in all expression contexts, including variable declarations, function arguments, return statements, and arrow function bodies.

  • #9462 c23272c Thanks @ematipico! - Fixed #9370: The resolver now correctly prioritizes more specific exports patterns over less specific ones. Previously, a pattern like "./*" could match before "./features/*", causing resolution failures for packages with overlapping subpath patterns.

  • #9515 f85c069 Thanks @shivamtiwari3! - Fixed #9506 and #9479: Biome no longer reports false parse errors on <script type="speculationrules"> and <script type="application/ld+json"> tags. These script types contain non-JavaScript content and are now correctly skipped by the embedded language detector.

  • #9514 7fe43c8 Thanks @ematipico! - Fixed #6964: Biome now correctly resolves the .gitignore file relative to vcs.root when configured. Previously, the vcs.root setting was ignored and Biome always looked for the ignore file in the workspace directory.

  • #9521 af39936 Thanks @ematipico! - Fixed #9483. Now the rule noRedeclare doesn't panic when it encounters constructor overloads.

  • #9490 60cf024 Thanks @willfarrell! - Added support for modern CSS properties, pseudo-classes, and pseudo-elements.

    New known properties: dynamic-range-limit, overlay, reading-flow, reading-order, scroll-marker-group, scroll-target-group.

    New pseudo-elements: ::checkmark, ::column, ::picker, ::picker-icon, ::scroll-button, ::scroll-marker, ::scroll-marker-group.

    New pseudo-classes: :active-view-transition-type, :has-slotted, :target-after, :target-before, :target-current.

  • #9526 4d42823 Thanks @ematipico! - Fixed #9358 and #9375. Now attributes that have text expressions such as class={buttonClass()} are correctly tracked in Svelte files.

  • #9520 61f53ee Thanks @ematipico! - Fixed #9519. Now noUnusedVariables doesn't flag variables that are used as typeof type.

  • #9487 331dc0d Thanks @mvanhorn! - Fixed #9477: source.fixAll.biome no longer sorts imports when source.organizeImports.biome is disabled in editor settings. The organize imports action is now excluded from the fix-all pass unless explicitly requested.

  • #9525 e7b3b10 Thanks @ViniciusDev26! - Added the rule noDrizzleDeleteWithoutWhere to prevent accidental full-table deletes when using Drizzle ORM without a .where() clause.

What's Changed
New Contributors

Full Changelog: https://github.com/biomejs/biome/compare/@biomejs/biome@2.4.7...@biomejs/biome@2.4.8

View originalPermalink
How 2.4.8 went
2.4.7

Biome CLI v2.4.7

Added 2
  • Added new nursery lint rule `useBaseline` for CSS that reports when CSS properties, property values, at-rules, media conditions, functions, or pseudo-selectors are not part of the configured Baseline tier
  • Added the nursery rule `useImportsFirst` that enforces all import statements appear before any non-import statements in a module
Changed 1
  • Improved `biome migrate eslint` to better detect rules in ESLint configurations by adding extra rule source references
Fixed 9
  • Fixed `noUndeclaredVariables` from erroneously flagging props only used in the template section in Vue SFCs
  • Fixed values referenced as a JSX element in Astro/Vue/Svelte templates no longer being incorrectly detected by `noUnusedImports` and `useImportType` rules
  • Fixed LSP now correctly resolving project directory when `configurationPath` points to a configuration file outside the workspace
  • Fixed `noUselessEscapeInString` no longer incorrectly flagging valid CSS hex escapes as useless and now recognizes all hex digits as valid escape characters in CSS strings
  • Fixed formatter no longer crashing or producing corrupt output when a JS file with `experimentalEmbeddedSnippetsEnabled` contains non-embedded template literals alongside embedded ones
  • Fixed `noShadow` no longer incorrectly flagging destructured variable bindings in sibling scopes as shadowing

From Biome

2.4.7
Patch Changes

  • #9318 3ac98eb Thanks @ematipico! - Added new nursery lint rule useBaseline for CSS. The rule reports when CSS properties, property values, at-rules, media conditions, functions, or pseudo-selectors are not part of the configured Baseline tier.

    For example, at the time of writing, the rule will trigger for the use of accent-color because it has limited availability:

    a {
  accent-color: bar;
}

  • #9272 2de8362 Thanks @terror! - Added the nursery rule useImportsFirst that enforces all import statements appear before any non-import statements in a module. Inspired by the eslint-plugin-import import/first rule.

    // Invalid
import { foo } from "foo";
const bar = 1;
import { baz } from "baz"; // ← flagged

// Valid
import { foo } from "foo";
import { baz } from "baz";
const bar = 1;

  • #9285 93ea495 Thanks @dyc3! - Fixed noUndeclaredVariables from erroneously flagging props only used in the template section in Vue SFCs

  • #9435 6c5a8f2 Thanks @siketyan! - Fixed #9432: Values referenced as a JSX element in Astro/Vue/Svelte templates are now correctly detected; noUnusedImports and useImportType rules no longer reports these values as false positives.

  • #9362 fc9ca4c Thanks @Netail! - Extra rule source references. biome migrate eslint should do a bit better detecting rules in your eslint configurations.

  • #9392 b881fea Thanks @g-ortuno! - Fixed biomejs/biome-vscode#959: LSP now correctly resolves project directory when configurationPath points to a configuration file outside the workspace.

  • #9420 a1c46af Thanks @ematipico! - Fixed #9385: noUselessEscapeInString no longer incorrectly flags valid CSS hex escapes (e.g. \e7bb) as useless. The rule now recognizes all hex digits (0-9, a-f, A-F) as valid escape characters in CSS strings.

  • #9416 f2581b8 Thanks @ematipico! - Fixed #9131, #9112, #9166: the formatter no longer crashes or produces corrupt output when a JS file with experimentalEmbeddedSnippetsEnabled contains non-embedded template literals alongside embedded ones (e.g. console.log(\test`)next tographql(`...`)`).

  • #9344 cb4d7d7 Thanks @ematipico! - Fixed #6921: noShadow no longer incorrectly flags destructured variable bindings in sibling scopes as shadowing. Object destructuring, array destructuring, nested patterns, and rest elements are now properly recognized as declarations.

  • #9360 bc5dd99 Thanks @ematipico! - Fixed #7125: The rule noShadow no longer incorrectly flags parameters in TypeScript constructor and method overload signatures.

  • #9371 29cac17 Thanks @ematipico! - Fixed #5279: Tabs in diagnostic diff output are now rendered at a consistent width across context and changed lines, fixing visual misalignment when source files use tab indentation.

  • #9043 61e2a02 Thanks @dyc3! - Fixed #8897: Biome now parses @utility names containing / when Tailwind directives are enabled.

  • #9354 930c858 Thanks @denbezrukov! - Improved CSS parser recovery for invalid unicode-range values that mix wildcard ranges with range intervals. For example, Biome now reports clearer diagnostics for invalid syntax like:

    unicode-range: U+11???-2??;
unicode-range: U+11???-;

    with diagnostics such as:

    × Wildcard ranges cannot be combined with a range interval.
  > unicode-range: U+11???-2??;
                            ^

× Expected a codepoint but instead found ';'.
  > unicode-range: U+11???-;
                             ^

  • #9355 78e74a2 Thanks @SchahinRohani! - Fixed #9349: Biome now correctly handles Vue dynamic :alt and v-bind:alt bindings in useAltText, preventing false positives in .vue files.

  • #9369 b309dde Thanks @costajohnt! - Fixed #9210: useAnchorContent no longer reports an accessibility error for Astro Image components inside links when they provide non-empty alt text.

  • #9345 70c2d4e Thanks @ematipico! - Fixed #7214: useOptionalChain now detects optional chain patterns that don't start at the beginning of a logical AND expression. For example, bar && foo && foo.length is now correctly flagged and fixed to bar && foo?.length.

  • #9311 78c4e9b Thanks @ruidosujeira! - Fixed #9245: the useSemanticElements rule no longer suggests <output> for role="status" and role="alert". The <output> element is only a relatedConcept of these roles, not a direct semantic equivalent. These roles are now excluded from suggestions, aligning with the intended behavior of the upstream prefer-tag-over-role rule.

  • #9363 b2ffb4a Thanks @ematipico! - Fixed #5212: useSemanticElements no longer reports a diagnostic when a semantic element already has its corresponding role attribute (e.g. <nav role="navigation">, <footer role="contentinfo">). These cases are now correctly left to noRedundantRoles.

  • #9364 1bb9edc Thanks @xvchris! - Fixed #9357. Improved the information emitted by some diagnostics.

  • #9434 bf12092 Thanks @siketyan! - Fixed #9433: noBlankTarget now correctly handles dynamic href attributes, such as <a href={company?.website} target="_blank">.

  • #9351 5046d2b Thanks @Netail! - Expanded the noNegationElse rule to cover the inequality & strict inequality operator.

  • #9353 2a29e0d Thanks @Conaclos! - Fixed #7583: organizeImports now sorts named specifiers inside bare exports and merges bare exports.

    - export { b, a };
- export { c };
+ export { a, b, c };

    Also, organizeImports now correctly adds a blank line between an import chunk and an export chunk.

      import { A } from "package";
+
  export { A };

  • #8658 bdcc934 Thanks @rksvc! - When the domains field is set in the configuration file, domains is now automatically enabled when Biome detects certain dependencies in package.json.

  • #9383 f5c8bf0 Thanks @ematipico! - Fixed #6606: The type inference engine now resolves Record<K, V> types, synthesizing them as object types with index signatures. This improves accuracy for type-aware lint rules such as noFloatingPromises, noMisusedPromises, useAwaitThenable, and useArraySortCompare when operating on Record-typed values.

  • #9359 701ddd3 Thanks @ematipico! - Fixed #7516: noUnusedImports no longer reports a false positive when a local variable shadows an imported type namespace that is still used in a type annotation.

  • #9473 50e93bd Thanks @ematipico! - Improved the detection of variables inside Astro files. Now the rule noUnusedVariables and others will trigger fewer false positives.

  • #9459 171b2ee Thanks @ematipico! - Fixed #9314. Now Biome doesn't panic when useAriaPropsForRole is configured using an object.

  • #9465 c8918d6 Thanks @Netail! - Fixed #9464: Temporal is now correctly detected as a global.

  • #9367 722f0da Thanks @Netail! - Added the nursery rule noTopLevelLiterals. It requires the root-level value to be an array or object.

    Invalid:

    "just a string"

  • #9333 a294b89 Thanks @terror! - Fixed #9310. Now the HTML formatter doesn't mangle elements that are followed by self-closing elements such as <br> or <img>.

  • #9391 4bffb66 Thanks @ematipico! - Slightly increased the performance of the CLI in projects that have more than ~2K files.

  • #9365 776cb64 Thanks @Netail! - Added the nursery rule noEmptyObjectKeys, which disallows the use of empty keys in JSON objects.

    Invalid:

    {
  "": "value"
}
What's Changed
New Contributors

Full Changelog: https://github.com/biomejs/biome/compare/@biomejs/biome@2.4.6...@biomejs/biome@2.4.7

View originalPermalink
How 2.4.7 went
2.4.6

Biome CLI v2.4.6

Changed 2
  • Improved performance of the `noEmptyBlockStatements` rule with smarter short-circuiting logic
  • Improved performance for `noImportCycles` by explicitly excluding node_modules from cycle detection
Fixed 6
  • The `noUnreachable` rule no longer reports code inside `finally` blocks as unreachable when there is a `break`, `continue`, or `return` in the corresponding `try` body
  • The formatter no longer produces different output on subsequent runs when a `case` clause has a trailing line comment followed by a single block statement
  • The `useAnchorContent` rule now recognises SolidJS's `innerHTML` the same way as React's `dangerouslySetInnerHTML`
  • Comments are now moved along with the attributes in the `useSortedAttributes` assist rule code fix
  • The Biome language server now correctly resolves the editor setting `configurationPath` when the provided value is a relative path
  • Lowercase component member expressions like `<form.Field>` in Svelte and Astro files are now correctly formatted

From Biome

2.4.6
Patch Changes

  • #9305 40869b5 Thanks @ematipico! - Fixed #4946: noUnreachable no longer reports code inside finally blocks as unreachable when there is a break, continue, or return in the corresponding try body.

  • #9303 464910c Thanks @ematipico! - Fixed #2786: The formatter no longer produces different output on subsequent runs when a case clause has a trailing line comment followed by a single block statement.

  • #9324 6294aa2 Thanks @arendjr! - Fixed #7730: useAnchorContent now recognises SolidJS's innerHTML the same way as React's dangerouslySetInnerHTML.

  • #9298 1003229 Thanks @Netail! - Fixed #9296, so comments are moved along with the attributes in the useSortedAttributes assist rule code fix.

  • #9329 855b451 Thanks @dyc3! - Improved performance of noEmptyBlockStatements. The rule is now smarter about short-circuiting its logic.

  • #9326 85dfe9b Thanks @dyc3! - Improved performance for noImportCycles by explicitly excluding node_modules from the cycle detection. The performance improvement is directly proportional to how big your dependency tree is.

  • #9323 d5ee469 Thanks @ematipico! - Fixed #9217 and biomejs/biome-vscode#959, where the Biome language server didn't correctly resolve the editor setting configurationPath when the provided value is a relative path.

  • #9302 86fbc70 Thanks @sepagian! - Fixed #9300: Lowercase component member expressions like <form.Field> in Svelte and Astro files are now correctly formatted.

    -<form .Field></form.Field>
+<form.Field></form.Field>
What's Changed
New Contributors

Full Changelog: https://github.com/biomejs/biome/compare/@biomejs/biome@2.4.5...@biomejs/biome@2.4.6

View originalPermalink
How 2.4.6 went
2.4.5

Biome CLI v2.4.5

Added 4
  • Added the nursery rule `useVueScopedStyles` for Vue SFCs to enforce that `<style>` blocks have the `scoped` attribute or `module` for CSS Modules
  • Added parsing support for Svelte's comments-in-tags feature to accept JavaScript style comments in tags
  • Added the nursery rule `useNullishCoalescing` to suggest using the nullish coalescing operator (`??`) instead of logical OR (`||`) when the left operand may be nullish
  • Added the nursery rule `noVueRefAsOperand` to disallow cases where a ref is used as an operand
Changed 2
  • Improved plugin performance by batching all plugins into a single syntax visitor with a kind-to-plugin lookup map, reducing per-node dispatch overhead from O(N) to O(1)
  • Improved `biome migrate eslint` to better detect rules in ESLint configurations
Fixed 5
  • Fixed `noUndeclaredVariables` erroneously flagging functions and variables defined in the `<script setup>` section of Vue SFCs
  • Fixed an issue where the JSON reporter did not contain the duration of the command
  • Fixed false positives in test assertion rules by recognizing `assert`, `expectTypeOf`, and `assertType` as valid test assertions
  • Improved the diagnostic of the rule `useExhaustiveDependencies` to show the name of the variable to add to the dependency array
  • Fixed parsing of `@container scroll-state(...)` queries in CSS

From Biome

2.4.5
Patch Changes

  • #9185 e43e730 Thanks @dyc3! - Added the nursery rule useVueScopedStyles for Vue SFCs. This rule enforces that <style> blocks have the scoped attribute (or module for CSS Modules), preventing style leakage and conflicts between components.

  • #9184 49c8fde Thanks @chocky335! - Improved plugin performance by batching all plugins into a single syntax visitor with a kind-to-plugin lookup map, reducing per-node dispatch overhead from O(N) to O(1) where N is the number of plugins.

  • #9283 071c700 Thanks @dyc3! - Fixed noUndeclaredVariables erroneously flagging functions and variables defined in the <script setup> section of Vue SFCs.

  • #9221 4612133 Thanks @ematipico! - Fixed an issue where the JSON reporter didn't contain the duration of the command.

  • #9294 1805c8f Thanks @Netail! - Extra rule source reference. biome migrate eslint should do a bit better detecting rules in your eslint configurations.

  • #9178 101b3bb Thanks @Bertie690! - Fixed #9172 and #9168: Biome now considers more constructs as valid test assertions.

    Previously, assert, expectTypeOf and assertType were not recognized as valid assertions by Biome's linting rules, producing false positives in lint/nursery/useExpect and other similar rules.

    Now, these rules will no longer produce errors in test cases that used these constructs instead of expect:

    import { expectTypeOf, assert, assertType } from "vitest";

const myStr = "Hello from vitest!";
it("should be a string", () => {
  expectTypeOf(myStr).toBeString();
});
test("should still be a string", () => {
  assertType<string>(myStr);
});
it.todo("should still still be a string", () => {
  assert(typeof myStr === "string");
});

  • #9173 32dad2d Thanks @dyc3! - Added parsing support for Svelte's new comments-in-tags feature.

    The HTML parser will now accept JS style comments in tags in Svelte files.

    <button
  // single-line comment
  onclick={doTheThing}
>click me</button>

<div
  /* block comment */
  class="foo"
>text</div>

  • #8952 1d2ca15 Thanks @pkallos! - Added the nursery rule useNullishCoalescing. This rule suggests using the nullish coalescing operator (??) instead of logical OR (||) when the left operand may be nullish. This prevents bugs where falsy values like 0, '', or false are incorrectly treated as missing. Addresses #8043

    // Invalid
declare const x: string | null;
const value = x || "default";

// Valid
const value = x ?? "default";

  • #9243 1992a85 Thanks @Netail! - Fixed #7813: improved the diagnostic of the rule useExhaustiveDependencies. The diagnostic now shows the name of the variable to add to the dependency array.

  • #9063 3d0648f Thanks @taga3s! - Added the nursery rule noVueRefAsOperand. This rule disallows cases where a ref is used as an operand.

    The following code is now flagged:

    import { ref } from "vue";

const count = ref(0);
count++; // Should be: count.value++

    import { ref } from "vue";

const ok = ref(false);
if (ok) {
  // Should be: if (ok.value)
  //
}

  • #9273 f239e20 Thanks @denbezrukov! - Fixed #9253: parsing of @container scroll-state(...) queries.

    @container scroll-state(scrolled: bottom) {
}
@container scroll-state(stuck) {
}
@container scroll-state(not (stuck)) {
}
@container scroll-state((stuck) and (scrolled: bottom)) {
}
@container scroll-state((stuck) or (snapped: x)) {
}
@container main-layout scroll-state(not ((stuck) and (scrolled: bottom))) {
}

  • #9259 96939c0 Thanks @ematipico! - Fixed CSS formatter incorrectly collapsing selectors when a BOM (Byte Order Mark) character is present at the start of the file. The formatter now correctly preserves line breaks between comments and selectors in BOM-prefixed CSS files, matching Prettier's behavior.

  • #9251 59e33fb Thanks @ematipico! - Fixed #9249: The CSS formatter no longer incorrectly breaks ratio values (like 1 / -1) across lines when followed by comments.

  • #9284 ec3a17f Thanks @denbezrukov! - Fixed #9253: removed false-positive diagnostics for valid @container/@supports general-enclosed queries.

    @container scroll-state(scrolled: bottom) {
}
@supports foo(bar: baz) {
}

  • #9215 b2619a1 Thanks @FrederickStempfle! - Fixed #9189: biome ci in GitHub Actions now correctly disables colors so that ::error/::warning workflow commands are not wrapped in ANSI escape codes.

  • #9256 65ae4c1 Thanks @ematipico! - Fixed JSON reporter escaping of special characters in diagnostic messages. The JSON reporter now properly escapes double quotes, backslashes, and control characters in error messages and advice text, preventing invalid JSON output when diagnostics contain these characters.

  • #9223 5b9da81 Thanks @ematipico! - Fixed an issue where the JSON reporter didn't write output to a file when --reporter-file was specified. The output is now correctly written to the specified file instead of always going to stdout.

  • #9154 c487e54 Thanks @abossenbroek! - Fixed #9115: The noPlaywrightMissingAwait rule no longer produces false positives on jest-dom matchers like toBeVisible, toBeChecked, toHaveAttribute, etc. For matchers shared between Playwright and jest-dom, the rule now checks whether expect()'s argument is a Playwright locator or page object before flagging. Added semantic variable resolution so that extracted Playwright locators (e.g. const loc = page.locator('.item'); expect(loc).toBeVisible()) are still correctly flagged.

  • #9269 33e5cdf Thanks @dyc3! - Fixed a false positive where noUndeclaredVariables reported bindings from Vue <script setup> as undeclared when used in <template>.

    This change ensures embedded bindings collected from script snippets (like imports and defineModel results) are respected by the rule.

  • #9267 2c2e060 Thanks @ematipico! - Fixed #9143 and #8849: The noUnresolvedImports rule no longer reports false positives for several common patterns:

    • node:fs, node:path, node:url, and other Node.js built-in modules with the node: prefix are now accepted.
    • Packages that declare their TypeScript entry point via "typings" (instead of "types") in package.json now resolve correctly.
    • Named imports from aliased re-export chains (e.g. export { x as y } from "...") are now resolved correctly through the alias.
    • Namespace re-exports (e.g. export * as Ns from "...") are now recognized as own exports of the barrel module.

  • #9254 f7bf12b Thanks @ematipico! - Fixed #8842: The CSS formatter now correctly formats @container scroll-state() without adding an unwanted space between the function name and opening parenthesis.

  • #9211 2d0b8e6 Thanks @ematipico! - Fixed #7905. Improved the accuracy of type-aware lint rules when analyzing re-exported functions and values.

    Previously, when a binding was imported from another module, its type was not correctly inferred during the type analysis phase. This caused type-aware lint rules to fail to detect issues when working with re-exported imports.

    The following rules now correctly handle re-exported imports:

    Example of now-working detection:

    // getValue.ts
export async function getValue(): Promise<number> {
  return 42;
}

// reexport.ts
export { getValue } from "./getValue";

// index.ts
import { getValue } from "./reexport";

// Previously: no diagnostic (type was unknown)
// Now: correctly detects that getValue() returns a Promise
await getValue(); // Valid - properly awaited
getValue(); // Diagnostic - floating promise

  • #8934 b49707c Thanks @tim-we! - Fixed #8265: Biome now correctly detects test framework calls that use three arguments (label, options, callback) (e.g., describe("foo", { retry: 2 }, () => {})). This fixes both formatting and the noDuplicateTestHooks lint rule for test frameworks like Vitest.

  • #9191 688fd34 Thanks @dyc3! - Fixed #9180: fixed a panic caused by an interaction between noRedundantUseStrict and the formatter

  • #9048 9bbdf4d Thanks @ff1451! - Added the nursery rule useNamedCaptureGroup. The rule enforces using named capture groups in regular expressions instead of numbered ones. It supports both regex literals and RegExp constructor calls.

    // Invalid: unnamed capture group
/(foo)/;
new RegExp("(foo)");

// Valid: named capture group
/(?<id>foo)/;
new RegExp("(?<id>foo)");

  • #9255 9b6685b Thanks @ematipico! - Fixed #9234, where some nursery rules panicked when they were configured with the option level without the corresponding options.

  • #8968 a2b4494 Thanks @LouisLau-art! - Fixed #8812: lint/suspicious/noArrayIndexKey will now report index usage anywhere in JSX key template or binary expressions, not only in the last visited identifier.

  • #9266 84935a4 Thanks @dyc3! - Fixed #9250: noVueDuplicateKeys will no longer flag keys under watch, preventing false positives.

  • #9056 1f2fe2e Thanks @ruidosujeira! - Added the nursery rule useArraySome to prefer .some() over verbose existence checks like filter(...).length > 0 and findIndex(...) !== -1, with suggestions for find/findLast existence checks. This also applies to ES2025 iterator helpers such as Iterator.prototype.find.

  • #9163 f87acf6 Thanks @JUSTIVE! - Added graphql to valid embedded graphql template tags inside JavaScript files, when the feature javascript.experimentalEmbeddedSnippetsEnabled is enabled. This allows proper support for graphql tags used in RelayJS.

    Now, code snippets like the following are correctly formatted and limited:

    import { graphql } from "react-relay";

const query = graphql`
  query {
    user(id: 1) {
      id
      name
    }
  }
`;

  • #8773 6b01778 Thanks @xcb3d! - Added the new nursery rule useUnicodeRegex.

    The rule enforces the use of the u or v flag for regular expressions. This ensures proper handling of Unicode characters like emoji.

    // Invalid
/foo/;
new RegExp("foo", "gi");

// Valid
/foo/u;
new RegExp("foo", "giu");
What's Changed
New Contributors

Full Changelog: https://github.com/biomejs/biome/compare/@biomejs/biome@2.4.4...@biomejs/biome@2.4.5

View originalPermalink
How 2.4.5 went
2.4.4

Biome CLI v2.4.4

Fixed 5
  • Astro files containing `---` in HTML content are now parsed correctly, both when a frontmatter block is present and when there is no frontmatter at all
  • The HTML parser now correctly parses bracket characters (`[` and `]`) in text content
  • Fixed parsing of Svelte directive keywords (`use`, `style`) when used as plain text content in HTML/Svelte files
  • The Vue parser now correctly handles colon attributes like `xlink:href` and `xmlns:xlink` by parsing them as single attributes instead of splitting them into separate tokens
  • The `noAssignInExpressions` rule no longer flags assignments in Vue v-on directives

From Biome

2.4.4
Patch Changes

  • #9150 6946835 Thanks @dyc3! - Fixed #9138: Astro files containing --- in HTML content (e.g., <h1>---Hi</h1>) are now parsed correctly, both when a frontmatter block is present and when there is no frontmatter at all.

  • #9150 aa6f837 Thanks @dyc3! - Fixed #9138: The HTML parser incorrectly failing to parse bracket characters ([ and ]) in text content (e.g. <div>[Foo]</div>).

  • #9151 c0d4b0c Thanks @dyc3! - Fixed parsing of Svelte directive keywords (use, style) when used as plain text content in HTML/Svelte files. Previously, <p>use JavaScript</p> or <p>style it</p> would incorrectly produce a bogus element instead of proper text content.

  • #9162 7f1e060 Thanks @dyc3! - Fixed #9161: The Vue parser now correctly handles colon attributes like xlink:href and xmlns:xlink by parsing them as single attributes instead of splitting them into separate tokens.

  • #9164 458211b Thanks @dyc3! - Fixed #9161: The noAssignInExpressions rule no longer flags assignments in Vue v-on directives (e.g., @click="counter += 1"). Assignments in event handlers are idiomatic Vue patterns and are now skipped by the rule.

What's Changed

Full Changelog: https://github.com/biomejs/biome/compare/@biomejs/biome@2.4.3...@biomejs/biome@2.4.4

View originalPermalink
How 2.4.4 went
2.4.3

Biome CLI v2.4.3

Added 2
  • The HTML parser can now correctly parse Astro directives (client/set/class/is/server)
  • Added missing Mocha globals to the `Test` domain: `context`, `run`, `setup`, `specify`, `suite`, `suiteSetup`, `suiteTeardown`, `teardown`, `xcontext`, `xdescribe`, `xit`, and `xspecify`
Changed 1
  • Improved performance of `noIrregularWhitespace` by adding early return optimization and simplifying character detection logic
Fixed 5
  • The GitHub reporter is now correctly enabled when `biome ci` runs on GitHub Actions
  • The Astro frontmatter lexer now correctly identifies the closing `---` fence when the frontmatter contains multi-line block comments with quote characters, strings that mix quote types, or escaped quote characters
  • The `noUnknownAttribute` rule no longer reports `closedby` as an unknown attribute on `<dialog>` elements
  • The Biome CSS parser now correctly parses `not + scroll-state` inside `@container` queries
  • The `useDestructuring` rule no longer suggests destructuring when the variable has a type annotation

From Biome

2.4.3
Patch Changes

  • #9120 aa40fc2 Thanks @ematipico! - Fixed #9109, where the GitHub reporter wasn't correctly enabled when biome ci runs on GitHub Actions.

  • #9128 8ca3f7f Thanks @dyc3! - Fixed #9107: The HTML parser can now correctly parse Astro directives (client/set/class/is/server), which fixes the formatting for Astro directives.

  • #9124 f5b0e8d Thanks @ematipico! - Fixed #8882 and #9108: The Astro frontmatter lexer now correctly identifies the closing --- fence when the frontmatter contains multi-line block comments with quote characters, strings that mix quote types (e.g. "it's"), or escaped quote characters (e.g. "\").

  • #9142 3ca066b Thanks @THernandez03! - Fixed #9141: The noUnknownAttribute rule no longer reports closedby as an unknown attribute on <dialog> elements.

  • #9126 792013e Thanks @ematipico! - Added missing Mocha globals to the Test domain: context, run, setup, specify, suite, suiteSetup, suiteTeardown, teardown, xcontext, xdescribe, xit, and xspecify. These are injected by Mocha's BDD and TDD interfaces and were previously flagged as undeclared variables in projects using Mocha.

  • #8855 6918c9e Thanks @ruidosujeira! - Fixed #8840. Now the Biome CSS parser correctly parses not + scroll-state inside @container queries.

  • #9111 4fb55cf Thanks @Jayllyz! - Slightly improved performance of noIrregularWhitespace by adding early return optimization and simplifying character detection logic.

  • #8975 086a0c5 Thanks @FrankFMY! - Fixed #8478: useDestructuring no longer suggests destructuring when the variable has a type annotation, like const foo: string = object.foo.

What's Changed
New Contributors

Full Changelog: https://github.com/biomejs/biome/compare/@biomejs/biome@2.4.2...@biomejs/biome@2.4.3

View originalPermalink
How 2.4.3 went
2.4.2

Biome CLI v2.4.2

Added 11
  • Added the nursery rule noConditionalExpect to disallow conditional expect() calls inside tests
  • Added the nursery rule noPlaywrightElementHandle to prefer locators to element handles
  • Added the nursery rule noPlaywrightEval to disallow page.$eval() and page.$$eval() methods
  • Added the nursery rule noPlaywrightForceOption to disallow the force option on user interactions
  • Added the nursery rule noPlaywrightMissingAwait to enforce awaiting async Playwright APIs
  • Added the nursery rule noPlaywrightNetworkidle to disallow deprecated networkidle wait option
Changed 1
  • Updated rule source metadata for rules from html-eslint
Fixed 1
  • useImportType no longer incorrectly flags imports used in Svelte control flow blocks ({#if}, {#each}, {#await}, {#key}) as type-only imports

From Biome

2.4.2
Patch Changes
What's Changed
New Contributors

Full Changelog: https://github.com/biomejs/biome/compare/@biomejs/biome@2.4.1...@biomejs/biome@2.4.2

View originalPermalink
How 2.4.2 went
2.4.1

Biome CLI v2.4.1

Fixed 4
  • Fixed path resolution that was broken by recent changes
  • Fixed incorrect processing of SCSS files
  • Fixed `noUnknownPseudoElement` rule reporting false positives for known pseudo elements in CSS modules
  • Fixed Biome not printing anything in stdin mode

From Biome

2.4.1
Patch Changes
What's Changed

Full Changelog: https://github.com/biomejs/biome/compare/@biomejs/biome@2.4.0...@biomejs/biome@2.4.1

View originalPermalink
How 2.4.1 went
2.4.0

Biome CLI v2.4.0

Added 9
  • Added `ignore` option to the `useHookAtTopLevel` rule to specify function names that should not be treated as hooks even if they follow the `use*` naming convention
  • Added the `useAnchorContent` rule for HTML to enforce that anchor elements have accessible content for screen readers
  • Added the `useMediaCaption` rule for HTML to enforce that `audio` and `video` elements have a `track` element with `kind="captions"` for accessibility
  • Added support for multiple reporters and the ability to save reporters to arbitrary files using the `--reporter-file` CLI option
  • The Biome CSS parser can now parse Vue SFC syntax such as `:slotted` and `:deep` pseudo functions when `experimentalFullHtmlSupportedEnabled` is set to `true`
  • Added support for Cursor files with comments and trailing commas enabled in Cursor configuration directories

From Biome

2.4.0
Minor Changes

  • #8964 0353fa0 Thanks @dyc3! - Added ignore option to the useHookAtTopLevel rule.

    You can now specify function names that should not be treated as hooks, even if they follow the use* naming convention.

    Example configuration:

    {
  "linter": {
    "rules": {
      "correctness": {
        "useHookAtTopLevel": {
          "options": {
            "ignore": ["useDebounce", "useCustomUtility"]
          }
        }
      }
    }
  }
}

  • #8769 d0358b0 Thanks @rahuld109! - Added the rule useAnchorContent for HTML to enforce that anchor elements have accessible content for screen readers. The rule flags empty anchors, anchors with only whitespace, and anchors where all content is hidden with aria-hidden. Anchors with aria-label or title attributes providing a non-empty accessible name are considered valid.

  • #8742 6340ce6 Thanks @rahuld109! - Added the rule useMediaCaption to the HTML language. Enforces that audio and video elements have a track element with kind="captions" for accessibility. Muted videos are allowed without captions.

  • #8621 d11130b Thanks @Netail! - Added support for multiple reporters, and the ability to save reporters on arbitrary files.

    Combine two reporters in CI

    If you run Biome on GitHub, take advantage of the reporter and still see the errors in console, you can now use both reporters:

    biome ci --reporter=default --reporter=github
    Save reporter output to a file

    With the new --reporter-file CLI option, it's now possible to save the output of all reporters to a file. The file is a path, so you can pass a relative or an absolute path:

    biome ci --reporter=rdjson --reporter-file=/etc/tmp/report.json
biome ci --reporter=summary --reporter-file=./reports/file.txt

    You can combine these two features. For example, have the default reporter written on terminal, and the rdjson reporter written on file:

    biome ci --reporter=default --reporter=rdjson --reporter-file=/etc/tmp/report.json

    The --reporter and --reporter-file flags must appear next to each other, otherwise an error is thrown.

  • #8399 ab88099 Thanks @ematipico! - The Biome CSS parser is now able to parse Vue SFC syntax such as :slotted and :deep. These pseudo functions are only correctly parsed when the CSS is defined inside .vue components. Otherwise, Biome will a emit a parse error.

    This capability is only available when experimentalFullHtmlSupportedEnabled is set to true.

  • #8663 3dfea16 Thanks @ematipico! - Added support for Cursor files. When Biome sees a Cursor JSON file, it will parse it with comments enabled and trailing commas enabled:

    • $PROJECT/.cursor/
    • %APPDATA%\Cursor\User\ on Windows
    • ~/Library/Application Support/Cursor/User/ on macOS
    • ~/.config/Cursor/User/ on Linux

  • #8723 fe2c642 Thanks @cbstns! - Added JSON as a target language for GritQL pattern matching. You can now write Grit plugins for JSON files.

    This enables users to write GritQL patterns that match against JSON files, useful for:

    • Searching and transforming JSON configuration files
    • Enforcing patterns in package.json and other JSON configs
    • Writing custom lint rules for JSON using GritQL

    Example patterns:

    Match all key-value pairs:

    language json

pair(key = $k, value = $v)

    Match objects with specific structure:

    language json

JsonObjectValue()

    Supports both native Biome AST names (JsonMember, JsonObjectValue) and TreeSitter-compatible names (pair, object, array) for compatibility with existing Grit patterns.

    For more details, see the GritQL documentation.

  • #8814 4d9c676 Thanks @Netail! - Added ignore option to noUnknownProperty. If an unknown property name matches any of the items provided in ignore, a diagnostic won't be emitted.

  • #8631 4d8f19d Thanks @Netail! - Add a new reporter --reporter=sarif, that emits diagnostics using the SARIF format.

  • #8270 4f7909d Thanks @lucasweng! - Added the useIframeTitle lint rule for HTML. The rule enforces the usage of the title attribute for the iframe element.

    Invalid:

    <iframe></iframe> <iframe title=""></iframe>

    Valid:

    <iframe title="title"></iframe>

  • #8164 1d25856 Thanks @ematipico! - Added a new assist action useSortedInterfaceMembers that sorts TypeScript interface members, for readability.

    It includes an autofix.

    Invalid example.

    interface MixedMembers {
  z: string;
  a: number;
  (): void;
  y: boolean;
}

    Valid example (after using the assist).

    interface MixedMembers {
  a: number;
  y: boolean;
  z: string;
  (): void;
}

  • #8647 4c7c06f Thanks @siketyan! - It's now possible to provide the stacktrace for a fatal error. The stacktrace is only available when the environment variable RUST_BACKTRACE=1 is set, either via the CLI or exported $PATH. This is useful when providing detailed information for debugging purposes:

    RUST_BACKTRACE=1 biome lint

  • #7961 a04c8df Thanks @siketyan! - The Biome Language Server now reports progress while scanning files and dependencies in the project.

  • #8289 a9025d4 Thanks @theshadow27! - Fixed #8024. The rule useIterableCallbackReturn now supports a checkForEach option. When set to false, the rule will skip checking for forEach() callbacks for returning values.

  • #8690 e06e5d1 Thanks @ematipico! - Added the rule useValidLang to the HTML language.

  • #7847 e90b14f Thanks @Jagget! - Added support for jsxFactory and jsxFragmentFactory.Biome now respects jsxFactory and jsxFragmentFactory settings from tsconfig.json when using the classic JSX runtime, preventing false positive noUnusedImports errors for custom JSX libraries like Preact.

    // tsconfig.json
{
  compilerOptions: {
    jsx: "react",
    jsxFactory: "h",
    jsxFragmentFactory: "Fragment",
  },
}

    // Component.jsx
import { h, Fragment } from "preact";

function App() {
  return <div>Hello</div>;
}

  • #8071 7f5bcf4 Thanks @ematipico! - Added new CLI options to the commands lsp-proxy and start that allow to control the Biome file watcher.

    --watcher-kind

    Controls how the Biome file watcher should behave. By default, Biome chooses the best watcher strategy for the current OS, however sometimes this could result in some issues, such as folders locked.

    The option accepts the current values:

    • recommended: the default option, which chooses the best watcher for the current platform.
    • polling: uses the polling strategy.
    • none: it doesn't enable the watcher. When the watcher is disabled, changes to files aren't recorded anymore by Biome. This might have repercussions on some lint rules that might rely on updated types or updated paths.

    The environment variable BIOME_WATCHER_KIND can be used as alias.

    --watcher-polling-interval

    The polling interval in milliseconds. This is only applicable when using the polling watcher. It defaults to 2000 milliseconds.

    The environment variable BIOME_WATCHER_POLLING_INTERVAL can be used as alias.

  • #8262 4186b83 Thanks @lucasweng! - Added the useHtmlLang lint rule for HTML. The rule enforces that the html element has a lang attribute.

    Invalid:

    <html></html>
<html lang></html>
<html lang=""></html>

    Valid:

    <html lang="en"></html>

  • #8376 1a9334c Thanks @siketyan! - Added support for formatting and linting embedded GraphQL snippets in JavaScript.

    For example, the following snippets are now formatted:

    import gql from "graphql-tag";

const PeopleCountQuery = gql`
  query PeopleCount {
    allPeople {
      totalCount
    }
  }
`;

    import { graphql } from "./graphql";

const PeopleCountQuery = graphql(`
  query PeopleCount {
    allPeople {
      totalCount
    }
  }
`);

    This feature is experimental and must be enabled explicitly in the configuration:

    {
  "javascript": {
    "experimentalEmbeddedSnippetsEnabled": true
  }
}

  • #7799 54682aa Thanks @PaulRBerg! - Added groupByNesting option to the useSortedKeys assist. When enabled, object keys are grouped by their value's nesting depth before sorting alphabetically.

    Simple values (primitives, single-line arrays, and single-line objects) are sorted first, followed by nested values (multi-line arrays and multi-line objects).

    Example

    To enable this option, configure it in your biome.json:

    {
  "linter": {
    "rules": {
      "source": {
        "useSortedKeys": {
          "options": {
            "groupByNesting": true
          }
        }
      }
    }
  }
}

    With this option, the following unsorted object:

    const object = {
  name: "Sample",
  details: {
    description: "nested",
  },
  id: 123,
};

    Will be sorted as:

    const object = {
  id: 123,
  name: "Sample",
  details: {
    description: "nested",
  },
};

  • #8641 1dc8dc2 Thanks @tt-a1i! - Added the noAutofocus lint rule for HTML. This rule enforces that the autofocus attribute is not used on elements, as it can cause usability issues for sighted and non-sighted users. The rule allows autofocus inside dialog elements or elements with the popover attribute, as these are modal contexts where autofocus is expected.

  • #8501 8eb3f19 Thanks @tt-a1i! - Added noPositiveTabindex to HTML. This rule prevents the usage of positive integers on the tabindex attribute, which can disrupt natural keyboard navigation order.

  • #8661 b36ff03 Thanks @tt-a1i! - Added the useAltText lint rule for HTML. This rule enforces that elements requiring alternative text (<img>, <area>, <input type="image">, <object>) provide meaningful information for screen reader users via alt, title (for objects), aria-label, or aria-labelledby attributes. Elements with aria-hidden="true" are exempt.

  • #7749 1c59333 Thanks @andogq! - Implements #1984. Updated useHookAtTopLevel to better catch invalid hook usage.

    This rule is now capable of finding invalid hook usage in more locations. A diagnostic will now be generated if:

    • A hook is used at the module level (top of the file, outside any function).
    • A hook is used within a function or method which is not a hook or component, unless it is a function expression (such as arrow functions commonly used in tests).

    Invalid:

    // Invalid: hooks cannot be called at the module level.
useHook();

    // Invalid: hooks must be called from another hook or component.
function notAHook() {
  useHook();
}

    Valid:

    // Valid: hooks may be called from function expressions, such as in tests.
test("my hook", () => {
  renderHook(() => useHook());

  renderHook(function () {
    return useHook();
  });
});

  • #8307 789b0e7 Thanks @mehm8128! - Added the useValidAriaRole lint rule for HTML. The rule enforces that elements with ARIA roles must use a valid, non-abstract ARIA role.

  • #8814 4d9c676 Thanks @Netail! - Added ignore option to noUnknownFunction. If an unknown function name matches any of the items provided in ignore, a diagnostic won't be emitted.

  • #8814 4d9c676 Thanks @Netail! - Added ignore option to noUnknownPseudoClass. If an unknown pseudo-class name matches any of the items provided in ignore, a diagnostic won't be emitted.

  • #8623 dc1f94e Thanks @mldangelo! - Added the noDuplicateClasses assist action to detect and remove duplicate CSS classes.

    For JSX files: Supports class, className attributes and utility functions like clsx, cn, cva.

    For HTML files: Checks class attributes. This is the first assist action for HTML.

    // Before
<div class="flex p-4 flex" />;

// After
<div class="flex p-4" />;

  • #8399 ab88099 Thanks @ematipico! - Improved the CSS parser for CSS modules. Biome now automatically enables CSS modules parsing for *.module.css files.

    If your codebase has only *.module.css files, you can remove the parser feature as follows, because now Biome does it for you:

    {
  "css": {
    "parser": {
-      "cssModules": true
    }
  }
}

  • #8399 ab88099 Thanks @ematipico! - Added support for parsing :global and :local inside .astro, .svelte and .vue files, in <style> portion of the file.

    This capability is only available when experimentalFullHtmlSupportedEnabled is set to true.

  • #9011 e014336 Thanks @ematipico! - Promoted 21 nursery rules to stable groups.

    Correctness

    Promoted the following rules to the correctness group:

    • noUnresolvedImports. The rule reports imports that cannot be resolved. The default rule severity is set to error.
    • noVueReservedProps. The rule reports Vue reserved props usage. The default rule severity is set to error.
    • noVueReservedKeys. The rule reports Vue reserved keys usage. The default rule severity is set to error.
    • noVueDataObjectDeclaration. The rule reports Vue 2 data declared as an object instead of a function. The default rule severity is set to warn.
    • noNextAsyncClientComponent. The rule reports async Next.js client components. The default rule severity is set to warn.
    • noVueDuplicateKeys. The rule reports duplicate keys in Vue component options. The default rule severity is set to error.
    • noVueSetupPropsReactivityLoss. The rule reports destructuring of props in Vue 3 setup which causes reactivity loss. The default rule severity is set to error.
    • useQwikMethodUsage. The rule enforces correct Qwik framework method usage. The default rule severity is set to error.
    • useQwikValidLexicalScope. The rule enforces valid lexical scope in Qwik framework. The default rule severity is set to error.
    Suspicious

    Promoted the following rules to the suspicious group:

    • noImportCycles. The rule reports circular imports. The default rule severity is set to warn.
    • noDeprecatedImports. The rule reports imports of deprecated symbols. The default rule severity is set to warn.
    • noReactForwardRef. The rule reports usage of React.forwardRef. The default rule severity is set to warn.
    • noUnusedExpressions. The rule reports expressions that are never used. The default rule severity is set to warn.
    • noEmptySource. The rule reports empty source files. The default rule severity is set to warn.
    • useDeprecatedDate. The rule enforces use of GraphQL @deprecated directive with date. The default rule severity is set to warn.
    • noDuplicateDependencies. The rule reports duplicate dependencies in package.json. The default rule severity is set to warn.
    Complexity

    Promoted the following rules to the complexity group:

    • noUselessUndefined. The rule reports useless undefined initialization and returns. The default rule severity is set to info.
    • useMaxParams. The rule enforces a maximum number of function parameters. The default rule severity is set to warn.
    • noUselessCatchBinding. The rule reports useless catch binding parameters. The default rule severity is set to info.
    Style

    Promoted the following rules to the style group:

    • useConsistentArrowReturn. The rule enforces consistent return in arrow functions. The default rule severity is set to info.
    • noJsxLiterals. The rule reports literal strings in JSX. The default rule severity is set to info.

  • #8695 d8f0309 Thanks @ematipico! - Added support for the top-level suppression comment biome-ignore-all format: <explanation>.

    When the comment biome-ignore-all format: <explanation> is placed at the beginning of the document, Biome won't format the code.

    The feature works for all supported languages. In the following JavaScript snippet, the code isn't formatted and will stay as is.

    // biome-ignore-all format: generated

const a = [];

const a = [];

const a = [];

  • #8255 da85e3c Thanks @ryan-m-walker! - Added support for the typed attr function. Addresses issue #6183.

    Example

    .btn {
  width: attr(data-size type(<length> | <percentage>), 0px);
}

  • #8165 e0b3f62 Thanks @lucasweng! - Added the noAccessKey lint rule for HTML. The rule enforces that the accesskey attribute is not used on any HTML element, as it can conflict with keyboard commands used by screen readers and keyboard-only users.

    Invalid:

    <input type="submit" accesskey="s" value="Submit" />
<a href="https://webaim.org/" accesskey="w">WebAIM.org</a>
<button accesskey="n">Next</button>

    Valid:

    <input type="submit" value="Submit" />
<a href="https://webaim.org/">WebAIM.org</a>
<button>Next</button>

  • #8278 7207eff Thanks @ematipico! - Added a feature that allows editors to inject a Biome configuration to the Biome Language Server without affecting the configuration of the project.

    If you have a Biome extension that is compatible with your preferred LSP-ready editor, you can map inlineConfig. The configuration will be merged with the configuration of the project (or the default configuration):

    For example, with the Zed editor, you would have the following configuration, which will format all files using four spaces as indentation style:

    // .zed/settings.json
{
  lsp: {
    biome: {
      settings: {
        inline_config: {
          formatter: {
            indentStyle: "space",
            indentWidth: 4,
          },
        },
      },
    },
  },
}

  • #8368 8aa5f5b Thanks @Bertie690! - Added 2 options from typescript-eslint (ignoreDifferentlyNamedParameters and ignoreDifferentJsDoc) to useUnifiedTypeSignatures.

    Each option makes the rule ignore overload signatures whose parameter names or JSDoc comments differ.

    Examples

    Valid code with ignoreDifferentlyNamedParameters set to true:

    function cook(scoops: IceCreamScoop[]): void;
function cook(cakeType: string): void;

    Valid code with ignoreDifferentJsDoc set to true:

    /** Does objs have "cow" inside it? */
function hasCow(objs: string[]): boolean;
/** @deprecated - convert to array */
function hasCow(objs: string): boolean;

  • #8562 361350e Thanks @dyc3! - Added the rule profiler behind the --profile-rules cli flag. You can now see a report of which lint rules took the longest to execute.

  • #8234 e2e6e66 Thanks @ongyuxing! - Updated the CSS properties ordering to align with stylelint-config-recess-order v7.4.0.

    It adds support for:

    • Containment properties
    • Font synthesis properties
    • Ruby properties
    • Color adjustment properties
    • View transitions properties
    • Shapes properties
    • Motion path properties
    • etc.

    For the complete list of changes, see: https://github.com/stormwarning/stylelint-config-recess-order/compare/v6.0.0...v7.4.0.

  • #8814 4d9c676 Thanks @Netail! - Added ignore option to noUnknownPseudoElement. If an unknown pseudo-element name matches any of the items provided in ignore, a diagnostic won't be emitted.

  • #8663 3dfea16 Thanks @ematipico! - Added the ability to load the configuration from new known paths. Biome now attempts to load the configuration files from the following locations:

    • $XDG_CONFIG_HOME or $HOME/.config/biome on Linux
    • /Users/$USER/Library/Application Support/biome on macOS
    • C:\Users\$USER\AppData\Roaming\biome\config on Windows

    The priority how Biome will attempt to load the configuration files is the following:

    1. project folder (working directory)
    2. parent folders
    3. config home
      1. $XDG_CONFIG_HOME or $HOME/.config/biome on Linux
      2. /Users/$USER/Library/Application Support/biome on macOS
      3. C:\Users\$USER\AppData\Roaming\biome\config on Windows

  • #7973 bc0e8b4 Thanks @siketyan! - Added support for formatting and linting embedded CSS snippets in JavaScript.

    For example, the following snippets are now formatted and linted:

    import styled from "styled-components";

const Foo = styled.div`
  display: flex;
  color: red;
`;

    import styled from "@emotion/styled";

const Foo = styled(Box)`
  display: flex;
  color: red;
`;

    import { css } from "@emotion/react";

const style = css`
  display: flex;
  color: red;
`;

    However, snippets with interpolations are not supported yet. For example, the following snippet isn't formatted:

    import styled from "@emotion/styled";

const Foo = styled.div<{ color: string }>`
  display: flex;
  color: ${(props) => props.color};
`;

    This feature is experimental and must be enabled explicitly in the configuration:

    {
  "javascript": {
    "experimentalEmbeddedSnippetsEnabled": true
  }
}

  • #8381 50c3513 Thanks @mehm8128! - Added the useAriaPropsForRole lint rule for HTML. The rule enforces that elements with ARIA roles must have all required ARIA attributes for that role.

  • #7762 5901d79 Thanks @dyc3! - Added the extensionMappings option to useImportExtensions. This allows users to specify custom file extensions for different module types.

    For example, if you want to ban all .ts imports in favor of .js imports, you can now do so with this option:

    {
  "options": {
    "extensionMappings": {
      "ts": "js"
    }
  }
}

  • #8532 01bccc8 Thanks @jonaylor89! - Added --only and --skip options to biome check and biome ci, covering both lint diagnostics and assist actions. Biome now lets you run or exclude specific lint rules, assist actions, group or rules and actions, or domains when running these commands.

    Examples:

    biome check --only=suspicious/noDebugger src/**/*.js
biome ci --skip=project src/**

  • #8666 7733f90 Thanks @ematipico! - Added the rule noRedundantAlt to HTML. The rule enforces that the img element alt attribute does not contain the words “image”, “picture”, or “photo”.

  • #8287 a248e88 Thanks @mehm8128! - Added the noDistractingElements lint rule for HTML. The rule enforces that no distracting elements like <marquee> or <blink> are used.

  • #8564 adcce82 Thanks @ematipico! - Added the new linter domain types. This is a domain that enables all rules that require the type inference engine.

    As opposed to the project domain, which only enables rules that require the module graph to function.

    The following nursery rules have been moved to the types domain:

    • useArraySortCompare
    • useAwaitThenable
    • useFind
    • useRegexpExec
    • noUnnecessaryConditions
    • noMisusedPromises
    • noFloatingPromises

  • #8556 47a79f1 Thanks @mehm8128! - Added two new behaviors to the noSvgWithoutTitle rule.

    • Support for graphics-document and graphics-symbol roles.
    • Support for multiple role specifications.

  • #8663 3dfea16 Thanks @ematipico! - Added the ability to load the hidden files .biome.json and .biome.jsonc. This is the order how Biome will attempt the configuration file is:

    1. biome.json
    2. biome.jsonc
    3. .biome.json
    4. .biome.jsonc

  • #8334 ae8ac8e Thanks @ematipico! - Added the formatter option trailingNewline.

    When set to false, the formatter will remove the trailing newline at the end of formatted files. The default value is true, which preserves the current behavior of adding a trailing newline.

    This option is available globally and for each language-specific formatter configuration:

    {
  "formatter": {
    "trailingNewline": false
  },
  "javascript": {
    "formatter": {
      "trailingNewline": true
    }
  }
}

    The following CLI flags have been added. They accept true or false as value:

    • --formatter-trailing-newline
    • --javascript-formatter-trailing-newline
    • --json-formatter-trailing-newline
    • --graphql-formatter-trailing-newline
    • --css-formatter-trailing-newline
    • --html-formatter-trailing-newline

  • #8854 1469968 Thanks @ematipico! - Formatting is now applied when applying safe/unsafe fixes via biome check.

  • #8642 46f33a7 Thanks @ematipico! - Improved the rule noUnusedVariables in Svelte files, by correctly detecting variables defined in the JavaScript blocks, and used inside the templates.

  • #8839 79b38aa Thanks @ryan-m-walker! - Added support for parsing and formatting the CSS @function at-rule from the CSS Mixins Module Level 1 specification. Addresses issue #8184.

    @function --transparent(--color <color>, --alpha <number>: 0.5) returns
  <color> {
  result: oklch(from var(--color) l c h / var(--alpha));
}

  • #8412 73f4f53 Thanks @mehm8128! - Added the noSvgWithoutTitle lint rule to HTML. The rule enforces the usage of the title element for the svg element.

  • #8243 4291ff3 Thanks @ashnewmanjones! - Added the useButtonType lint rule for HTML. The rule enforces that the type attribute is present and valid on all button elements.

    Invalid:

    <button>Do something</button>
<button type="incorrectType">Do something</button>
<button type>Do something</button>
<button type />

    Valid:

    <button type="button">Do something</button>
<button type="reset">Do something</button>
<button type="submit" />
Patch Changes

  • #8898 7e48bd4 Thanks @ematipico! - Added e18e ESLint plugin as a recognized rule source. Six Biome rules now reference their e18e equivalents: useAtIndex, useExponentiationOperator, noPrototypeBuiltins, useDateNow, useSpread, and useObjectSpread.

  • #8719 a215408 Thanks @ematipico! - Added proper parsing and formatting for Svelte directives when the html.experimentalFullSupportEnabled is set to true.

  • #8071 7f5bcf4 Thanks @ematipico! - Revamped the logging options for all Biome commands. Now the commands format, lint, check, ci, search, lsp-proxy and start accept the following CLI options.

    Some options might have been present before, but they were inconsistent. Plus, all new options have an environment variable as aliases.

    --log-file

    Optional path/file to redirect log messages to. This option is applicable only to the CLI. If omitted, logs are printed to stdout.

    Environment variable alias: BIOME_LOG_FILE

    --log-prefix-name

    Allows changing the prefix applied to the file name of the logs. This option is applicable only to the daemon.

    Environment variable alias: BIOME_LOG_PREFIX_NAME

    --log-path

    Allows changing the folder where logs are stored. This option is applicable only to the daemon.

    Environment variable alias: BIOME_LOG_PATH

    --log-level

    The level of logging. In order, from the most verbose to the least verbose: debug, info, warn, error

    The value none won't show any logging.

    Environment variable alias: BIOME_LOG_LEVEL

    --log-kind

    What the log should look like.

    Environment variable alias: BIOME_LOG_KIND

    Reduce dumping of LSP logs

    When you use a Biome editor extension, Biome's Daemon dumps its logs using the debug level. If you want to reduce the quantity of these logs, you can now customize it:

    BIOME_LOG_LEVEL=info biome lsp-proxy

  • #8663 3dfea16 Thanks @ematipico! - Fixed #901. Biome now allows trailing commas in inside Zed settings.json and VSCode settings.json.

  • #8669 683f50d Thanks @tt-a1i! - Fixed #8628: useComponentExportOnlyModules now allows components referenced as object property values in exported expressions. This fixes false positives for TanStack Router patterns.

    export const Route = createFileRoute('/')({
  component: HomeComponent,
})

function HomeComponent() { ... } // no longer reported as "should be exported"

  • #9060 0e47f5a Thanks @dyc3! - Fixed #9057: Incorrect diagnostic spans for suppression comments and other raw diagnostics in HTML-ish files (Vue, Svelte, Astro). Previously, diagnostics like "unused suppression" pointed to the wrong location in the document due to the diagnostic offset not being applied.

  • #9028 5ac2ad6 Thanks @LouisLau-art! - Fixed #9024: Biome no longer reports <hr role="presentation"> under noInteractiveElementToNoninteractiveRole.

  • #9072 8656fc0 Thanks @dyc3! - Fixed #9068: The noVueDuplicateKeys rule now correctly handles toRefs(props) patterns and no longer produces false positives when destructuring props, particularly in <script setup> blocks.

  • #9049 c0ab6dd Thanks @ematipico! - Fixed #7138. Now the Biome language server correctly handles the configurationPath setting coming from the editor extension.

  • #8556 47a79f1 Thanks @mehm8128! - Fixed the noSvgWithoutTitle rule not to recursively traverse title elements.

  • #8894 6bf1b09 Thanks @ematipico! - Added proper parsing for spread attributes {...props} in Svelte and Astro files.

  • #8833 375792e Thanks @dyc3! - Fixed #4927, #6407: The HTML formatter will now correctly break a block-like element if it has more than 2 children, and at least one of them is another block-like element.

    -<div>a<div>b</div> c</div>
+<div>
+  a
+  <div>b</div>
+  c
+</div>

  • #8854 1469968 Thanks @ematipico! - Fixed #7912, where Biome incorrectly added a leading newline to the code contained inside the Astro frontmatter.

  • #8806 cb112ce Thanks @dyc3! - Major Breaking Changes to the HTML formatter only

    The HTML formatter (which is still experimental) has been completely overhauled from the ground up to more closely resemble Prettier's formatting. If you have opted in to the HTML formatter, you may see large formatting diffs for your HTML, Vue, Svelte, and Astro files.

    This overhaul fixes several issues (#5150, #6625, #8437) around whitespace sensitivity that were causing incorrect formatting in certain scenarios that were difficult or impossible to fully address before.

  • #8700 0f5a05b Thanks @ematipico! - Improved the rules useConst, noUnusedImports, useImportTypes and noUnusedVariables inside Vue, Svelte and Astro files when experimentalFullSupportEnabled is set to true.

    Now variables and components that are imported or defined inside the files won't trigger false positives.

    Until now, we suggested disabling these rules with an override. Now the rules are more stable; however, you might still experience a few false positives. Those are probably issues caused by our parser.

    If you use experimentalFullSupportEnabled, you can remove the following override:

    {
-  "overrides": [
-    {
-      "includes": ["**/*.svelte", "**/*.astro", "**/*.vue"],
-      "linter": {
-        "rules": {
-          "style": {
-            "useConst": "off",
-            "useImportType": "off"
-          },
-          "correctness": {
-            "noUnusedVariables": "off",
-            "noUnusedImports": "off"
-          }
-        }
-      }
-    }
-  ]
}

  • #8485 bf02ba6 Thanks @ematipico! - Fixed an issue where some info diagnostics weren't tracked by the final summary.

  • #8846 5701ead Thanks @dyc3! - Fixed #8692: Biome now accepts Vue's v-bind() function in CSS when Vue CSS modules parsing is enabled.

  • #9012 18cdd45 Thanks @kiroushi! - Fixed plugin diagnostics showing incorrect line numbers in Vue, Astro, and Svelte files. Plugin diagnostics now correctly account for the template/frontmatter offset, pointing to the right location in the <script> block.

What's Changed
New Contributors

Full Changelog: https://github.com/biomejs/biome/compare/@biomejs/biome@2.3.15...@biomejs/biome@2.4.0

View originalPermalink
How 2.4.0 went
2.3.15

Biome CLI v2.3.15

Added 2
  • Added the lint rule noNestedPromises that detects nested .then() or .catch() calls that could be refactored into flat promise chains
  • Added the nursery rule noUselessReturn that reports redundant return statements that don't affect the function's control flow
Changed 1
  • Updated the useJsxKeyInIterable rule to not run inside Map constructors
Fixed 8
  • Reverted a behavior change in useExhaustiveDependencies that made method calls on objects report only the object as a missing dependency instead of the full member expression
  • Fixed noAssignInExpressions rule no longer reporting a false positive when an assignment is used as the expression body of an arrow function
  • Fixed globally excluded files in a monorepo still being processed when using extends: //
  • Fixed useExhaustiveDependencies no longer reporting false positives for variables destructured from a rest pattern
  • Fixed noUnusedImports and useImportType rules to allow importing the React identifier from a package other than react when javascript.jsxRuntime is set to reactClassic
  • Fixed text expressions in some template languages at the top level of an HTML document no longer causing panicking
  • Fixed useExhaustiveDependencies now correctly detects JSX component identifiers as hook dependencies
  • Fixed typo in noPositiveTabindex's quick fix text

From Biome

2.3.15
Patch Changes

  • #9019 043b67c Thanks @dyc3! - Added the lint rule noNestedPromises. This rule detects nested .then() or .catch() calls that could be refactored into flat promise chains.

    // Invalid: nested promise that can be flattened
doThing().then(function () {
  return doOtherThing().then(console.log);
});

// Valid: flat promise chain
doThing()
  .then(() => doOtherThing())
  .then(console.log);

    The rule intelligently allows nesting when the inner callback references variables from the outer scope, as these cases cannot be safely flattened.

  • #9029 6ebf6c6 Thanks @ff1451! - Added the nursery rule noUselessReturn. The rule reports redundant return; statements that don't affect the function's control flow.

    // Invalid: return at end of function is redundant
function foo() {
  doSomething();
  return;
}

  • #9017 8bac2da Thanks @mdevils! - Reverted a behavior change in useExhaustiveDependencies that was accidentally included as part of the #8802 fix. The change made method calls on objects (e.g., props.data.forEach(...)) report only the object (props.data) as a missing dependency instead of the full member expression. This behavior change will be reconsidered separately.

  • #9005 c8dbbbe Thanks @corvid-agent! - Fixed #8790: The noAssignInExpressions rule no longer reports a false positive when an assignment is used as the expression body of an arrow function (e.g., const f = b => a += b).

  • #8519 ccdc602 Thanks @ruidosujeira! - Fixed #8518, where globally excluded files in a monorepo were still being processed when using "extends": "//".

    When a package-level configuration extends the root configuration with "extends": "//", glob patterns (such as those in files.includes) are now correctly resolved relative to the project root directory, instead of the current workspace directory.

  • #9033 0628e0a Thanks @mdevils! - Fixed #8967. useExhaustiveDependencies no longer reports false positives for variables destructured from a rest pattern.

  • #9023 8ef9d1d Thanks @siketyan! - Fixed #9020: When javascript.jsxRuntime is set to reactClassic, noUnusedImports and useImportType rules now allow importing the React identifier from a package other than react. This aligns the behavior with tsc (--jsx=react), which also allows importing React from any package.

  • #8646 16fd71d Thanks @siketyan! - Fixed #8605: Text expressions in some template languages ({{ expr }} or { expr }) at the top level of an HTML document no longer causes panicking.

  • #8930 51c158e Thanks @ANKANJAGTAP! - Fixed #8917 useExhaustiveDependencies now correctly detects JSX component identifiers as hook dependencies.

  • #9009 7d229c7 Thanks @Netail! - Fixed typo in noPositiveTabindex's quick fix text.

  • #8758 8c789f1 Thanks @Pranav2612000! - Updated the useJsxKeyInIterable rule to not run inside Map constructors

  • #8977 bbe0e0c Thanks @FrankFMY! - Fixed #4888. noUnusedImports now adds export {} when removing the last import in a TypeScript file to prevent it from becoming an ambient module. This does not apply to embedded scripts in Vue, Svelte, or Astro files, which are already in a module context.

  • #9016 9d4cfa3 Thanks @dyc3! - Added eslint migration metadata for the rules @typescript/no-var-requires, @typescript/keyword-spacing, @typescript/func-call-spacing, vue/keyword-spacing, vue/func-call-spacing, and unicorn/empty-brace-spaces,

  • #8848 2cba2b3 Thanks @LouisLau-art! - Fixed #8845. Now useGenericFontNames doesn't trigger when font is declared inside the @supports at-rule.

  • #8997 a5f3212 Thanks @mldangelo! - Fixed #8476. useAwaitThenable no longer reports false positives for await on call expressions whose return type cannot be resolved (e.g., cross-module function calls to Node.js builtins or npm packages).

  • #8978 cc7a478 Thanks @FrankFMY! - Fixed #8645. useAwait no longer reports async generator functions that use yield*, since yield* in an async generator delegates to an AsyncIterable and requires the async modifier.

What's Changed
New Contributors

Full Changelog: https://github.com/biomejs/biome/compare/@biomejs/biome@2.3.14...@biomejs/biome@2.3.15

View originalPermalink
How 2.3.15 went
2.3.14

Biome CLI v2.3.14

Added 3
  • Add the nursery rule useGlobalThis, which enforces using globalThis over window, self and global
  • Add the new nursery rule noVueArrowFuncInWatch, which forbids using arrow functions in watchers in Vue components
  • Add the new nursery rule noRedundantDefaultExport, which flags redundant default exports where the default export references the same identifier as a named export
Fixed 8
  • The useConsistentTypeDefinitions rule no longer converts empty object type declarations into interfaces, as it will conflict with the noEmptyInterface rule and can cause an infinite loop when both rules are enabled
  • Improve parsing recovery when encountering qualified rules inside CSS @page at-rule blocks
  • useExhaustiveDependencies now correctly suggests dependencies without including callback-scoped variables or method names
  • HTML parser no longer crashes when encountering a < character followed by a digit in text content
  • Type aliases with generic parameters that have extends constraints now properly indent comments after the equals sign
  • Fix comments in member chains causing unnecessary line breaks
  • Don't remove quotes when type member is new
  • useExhaustiveDependencies now correctly recognizes stable hook results when declared with let

From Biome

2.3.14
Patch Changes

  • #8921 29e2435 Thanks @siketyan! - Fixed #8759: The useConsistentTypeDefinitions rule no longer converts empty object type declarations into interfaces, as it will conflict with the noEmptyInterface rule and can cause an infinite loop when both rules are enabled.

  • #8928 ccaeac4 Thanks @taga3s! - Added the nursery rule useGlobalThis. This rule enforces using globalThis over window, self and global.

  • #8602 9a18daa Thanks @dyc3! - Added the new nursery rule noVueArrowFuncInWatch. This rule forbids using arrow functions in watchers in Vue components, because arrow functions do not give access to the component instance (via this), while regular functions do.

  • #8905 9b1eea8 Thanks @ryan-m-walker! - Fixed #8428: Improved parsing recovery when encountering qualified rules inside CSS @page at-rule blocks.

  • #8900 f788cff Thanks @mdevils! - Fixed #8802: useExhaustiveDependencies now correctly suggests dependencies without including callback-scoped variables or method names.

    When accessing object properties with a callback-scoped variable, only the object path is suggested:

    // Now correctly suggests `props.value` instead of `props.value[day]`
useMemo(() => {
  return WeekdayValues.filter((day) => props.value[day]);
}, [props.value]);

    When calling methods on objects, only the object is suggested as a dependency:

    // Now correctly suggests `props.data` instead of `props.data.forEach`
useMemo(() => {
  props.data.forEach((item) => console.log(item));
}, [props.data]);

  • #8913 e1e20ea Thanks @dyc3! - Fixed #8363: HTML parser no longer crashes when encountering a < character followed by a digit in text content (e.g., <12 months). The parser now correctly emits an "Unescaped < bracket character" error instead of treating <12 as a tag name and crashing.

  • #8910 2fb63a4 Thanks @dyc3! - Fixed #8774: Type aliases with generic parameters that have extends constraints now properly indent comments after the equals sign.

    Previously, comments after the = in type aliases with extends constraints were not indented:

    -type A<B, C extends D> = // Some comment
-undefined;
+type A<B, C extends D> =
+    // Some comment
+    undefined;

  • #8916 ea4bd04 Thanks @ryan-m-walker! - Fixed #4013, where comments in member chains caused unnecessary line breaks.

    // Before
aFunction.b().c.d();

// After
aFunction.b().c.d();

  • #8945 fa66fe3 Thanks @fireairforce! - Fixed #8354: Don't remove quotes when type memeber is new.

    // Input:
type X = {
  "new"(): string;
  "foo"(): string;
};

// Format Output:
type X = {
  "new()": string;
  foo(): string;
};

  • #8927 0ef3da5 Thanks @littleKitchen! - Fixed #8907: useExhaustiveDependencies now correctly recognizes stable hook results (like useState setters and useRef values) when declared with let.

  • #8931 4561751 Thanks @koshin01! - Added the new nursery rule noRedundantDefaultExport, which flags redundant default exports where the default export references the same identifier as a named export.

  • #8900 f788cff Thanks @mdevils! - Fixed #8883: useExhaustiveDependencies no longer produces false positives when props are destructured in the function body of arrow function components without parentheses around the parameter.

    type Props = { msg: string };

// Arrow function without parentheses around `props`
const Component: React.FC<Props> = (props) => {
  const { msg } = props;
  // Previously, this incorrectly reported `msg` as unnecessary
  useEffect(() => console.log(msg), [msg]);
};

  • #8861 3531687 Thanks @dyc3! - Added the noDeprecatedMediaType CSS rule to flag deprecated media types like tv and handheld.

  • #8775 7ea71cd Thanks @igas! - Fixed the noUnnecessararyConditions rule to prevent trigger for optional fallback patterns.

  • #8860 95f1eea Thanks @dyc3! - Added the nursery rule noHexColors, which flags the use of hexadecimal color codes in CSS and suggests using named colors or RGB/RGBA/HSL/HSLA formats instead.

  • #8786 d876a38 Thanks @Bertie690! - Added the nursery rule useConsistentMethodSignatures.
    Inspired by the similarly named version from typescript-eslint, this rule aims to enforce a consistent style for methods used inside object types and interfaces.

    Examples

    Invalid code with style set to "property" (the default):

    interface Foo {
  method(a: string): void;
}

    Invalid code with style set to "method":

    type Bar = {
  prop: (a: string) => void;
}

  • #8864 5e97119 Thanks @dyc3! - Improved the summary provided by biome migrate eslint to be clearer on why rules were not migrated. Biome now specifies a reason when a rule is not migrated, such as being incompatible with the formatter or not implemented yet. This helps users make more informed decisions when migrating their ESLint configurations to Biome.

  • #8924 99b4cd1 Thanks @tmohammad78! - Fixed #8920: noUnknownFunction now knows about sibling-count, and sibling-index css functions

  • #8900 f788cff Thanks @mdevils! - Fixed #8885: useExhaustiveDependencies no longer incorrectly reports variables as unnecessary dependencies when they are derived from expressions containing post/pre-increment operators (++/--) or compound assignment operators (+=, -=, etc.).

    let renderCount = 0;

export const MyComponent = () => {
  // `count` is now correctly recognized as a required dependency
  // because `renderCount++` can produce different values between renders
  const count = renderCount++;

  useEffect(() => {
    console.log(count);
  }, [count]); // no longer reports `count` as unnecessary
};

  • #8619 d78e01d Thanks @Netail! - Added the nursery rule useInputName. Require mutation arguments to be called “input”, and the input type to be called Mutation name + “Input”.

    Invalid:

    type Mutation {
  SetMessage(message: String): String
}

  • #8922 871b45e Thanks @siketyan! - Fixed #8829: Revamped the noGlobalDirnameFilename rule to catch many false negatives that have not been reported.

What's Changed
New Contributors

Full Changelog: https://github.com/biomejs/biome/compare/@biomejs/biome@2.3.13...@biomejs/biome@2.3.14

View originalPermalink
How 2.3.14 went
2.3.13

Biome CLI v2.3.13

Added 1
  • Added new nursery rule use-consistent-enum-value-type that disallows enums from having both number and string members
Changed 1
  • Improved useVueValidVOn rule to be more closely aligned with the source rule and properly allow modifiers for all possible keyboard events
Fixed 4
  • Biome now parses Vue dynamic slot shorthand arguments that use template literals in brackets
  • Tailwind @utility directives now parse functional utility names like px-* when Tailwind directives are enabled
  • Fixed biome migrate eslint command not detecting rules for CSS, GraphQL, and HTML
  • Fixed --reporter=summary output incorrectly merging and displaying wrong issue counts for different rules

From Biome

2.3.13
Patch Changes

  • #8815 f924f23 Thanks @dyc3! - Improved useVueValidVOn to be more closely aligned with the source rule. It will now properly allow modifiers for all possible keyboard events. It should have better performance when there are no violations of the rule as well.

    Now treated valid:

    <div @keydown.arrow-down="handler"></div>
<div @keydown.a="handler"></div>
<div @keydown.b="handler"></div>
<div @keydown.27="foo"></div>

  • #8856 85f81f9 Thanks @dyc3! - Fixed #8710: Biome now parses Vue dynamic slot shorthand arguments that use template literals in [].

  • #8850 2a190e0 Thanks @dyc3! - Fixed #8708: Tailwind @utility directives now parse functional utility names like px-* when Tailwind directives are enabled.

  • #8863 79386e0 Thanks @dyc3! - Fixed an issue with biome migrate eslint where it couldn't detect rules for CSS, GraphQL, and HTML.

  • #8771 6f56b6e Thanks @lghuahua! - Fix the --reporter=summary output incorrectly merging and displaying wrong issue counts for different rules. Fixes #8730

  • #8714 ac3a71f Thanks @Netail! - Added new nursery rule use-consistent-enum-value-type. This rule disallows enums from having both number and string members.

What's Changed
New Contributors

Full Changelog: https://github.com/biomejs/biome/compare/@biomejs/biome@2.3.12...@biomejs/biome@2.3.13

View originalPermalink
How 2.3.13 went
2.3.12

Biome CLI v2.3.12

Added 4
  • Add new nursery rule noDuplicateAttributes to forbid duplicate attributes in HTML elements
  • Add new nursery rule noVueOptionsApi to detect Vue Options API usage incompatible with Vue 3.6 Vapor Mode
  • Add nursery rule noRootType to disallow usage of specified root types in GraphQL
  • Add nursery lint rule useErrorCause to enforce wrapping caught errors in new Error objects with original error as cause
Changed 1
  • Rename GraphQL nursery rules to match Biome standard: useUniqueArgumentNames to noDuplicateArgumentNames, useUniqueFieldDefinitionNames to noDuplicateFieldDefinitionNames, useUniqueGraphqlOperationName to noDuplicateGraphqlOperationName, useUniqueInputFieldNames to noDuplicateInputFieldNames, useUniqueVariableNames to noDuplicateVariableNames
Fixed 5
  • Fix noSecrets rule to eliminate false positives on common CamelCase identifiers by using average run length in entropy calculation
  • Fix biome search to properly handle parameters metavariables for arrow_function GritQL queries
  • Fix noUnusedVariables to ignore type parameters declared in ambient contexts such as declare module blocks
  • Fix HTML parser to parse directive modifiers with a single colon
  • Improve CSS parser recovery when semicolon is missing from Tailwind @apply at-rule

From Biome

2.3.12
Patch Changes

  • #8653 047576d Thanks @dyc3! - Added new nursery rule noDuplicateAttributes to forbid duplicate attributes in HTML elements.

  • #8648 96d09f4 Thanks @BaeSeokJae! - Added a new nursery rule noVueOptionsApi.

    Biome now reports Vue Options API usage, which is incompatible with Vue 3.6's Vapor Mode. This rule detects Options API patterns in <script> blocks, defineComponent(), and createApp() calls, helping prepare codebases for Vapor Mode adoption.

    For example, the following now triggers this rule:

    <script>
export default {
  data() {
    return { count: 0 };
  },
};
</script>

  • #8832 b08270b Thanks @Exudev! - Fixed #8809, #7985, and #8136: the noSecrets rule no longer reports false positives on common CamelCase identifiers like paddingBottom, backgroundColor, unhandledRejection, uncaughtException, and IngestGatewayLogGroup.

    The entropy calculation algorithm now uses "average run length" to distinguish between legitimate CamelCase patterns (which have longer runs of same-case letters) and suspicious alternating case patterns (which have short runs).

  • #8793 c19fb0e Thanks @TheBaconWizard! - Properly handle parameters metavariables for arrow_function GritQL queries. The following biome search command no longer throws an error:

    biome search 'arrow_function(parameters=$parameters, body=$body)'

  • #8561 981affb Thanks @wataryooou! - Fixed noUnusedVariables to ignore type parameters declared in ambient contexts such as declare module blocks.

  • #8817 652cfbb Thanks @dyc3! - Fixed #8765: The HTML parser can now parse directive modifiers with a single colon, e.g. @keydown.:.

  • #8704 a1914d4 Thanks @Netail! - Added the nursery rule noRootType. Disallow the usage of specified root types. (e.g. mutation and/or subscription)

    Invalid:

    {
  "options": {
    "disallow": ["mutation"]
  }
}

    type Mutation {
  SetMessage(message: String): String
}

  • #8712 251b47b Thanks @Netail! - Renamed the following GraphQL nursery rules to match the Biome standard:

    • useUniqueArgumentNames -> noDuplicateArgumentNames
    • useUniqueFieldDefinitionNames -> noDuplicateFieldDefinitionNames
    • useUniqueGraphqlOperationName -> noDuplicateGraphqlOperationName
    • useUniqueInputFieldNames -> noDuplicateInputFieldNames
    • useUniqueVariableNames -> noDuplicateVariableNames

    Run the biome migrate --write command to automatically update the configuration file.

  • #7602 957cd8e Thanks @kedevked! - Added the nursery lint rule useErrorCause.

    This rule enforces that errors caught in a catch clause are not rethrown without wrapping them in a new Error object and specifying the original error as the cause. This helps preserve the error’s stack trace and context for better debugging.

    It can be configured with the following option:

    • requireCatchParameter: (default: true)
      • When true, the rule requires that catch clauses have a parameter. If a throw statement appears inside a catch clause without a parameter, it will be flagged.

    Invalid examples:

    try {
  foo();
} catch {
  throw new Error("fail");
}

    try {
  foo();
} catch (err) {
  throw new Error(err.message);
}

    Valid examples:

    try {
  foo();
} catch (err) {
  throw new Error("fail", { cause: err });
}

    try {
  foo();
} catch (error) {
  throw new Error("Something went wrong", { cause: error });
}

    Valid example when requireCatchParameter is false:

    Valid:

    try {
  foo();
} catch {
  throw new Error("fail");
}

  • #8725 95aba98 Thanks @dyc3! - Fixed #8715: The CSS parser will now recover slightly better if a semicolon is missing from Tailwind's @apply at-rule.

  • #8616 4ee3bda Thanks @Netail! - Added the nursery rule useLoneAnonymousOperation. Disallow anonymous operations when more than one operation specified in document.

    Invalid:

    query {
  fieldA
}

query B {
  fieldB
}

  • #8624 291c9f2 Thanks @taga3s! - Added the nursery rule useInlineScriptId to the Next.js domain. This rule enforces id attribute on next/script components with inline content or dangerouslySetInnerHTML.

    The following code is invalid:

    import Script from "next/script";

export default function Page() {
  return (
    <Script>{`console.log('Hello');`}</Script> // must have `id` attribute
  );
}

  • #8767 0d15370 Thanks @mdevils! - Fixed #3512: useExhaustiveDependencies now properly handles nested destructuring patterns from hook results.

    const [[x, y], setXY] = useState([1, 2]);
useEffect(() => {
  console.log(x, y);
}, [x, y]); // x and y are now correctly recognized as unstable

  • #8757 17ed9d3 Thanks @Netail! - Added the nursery rule noDivRegex. Disallow equal signs explicitly at the beginning of regular expressions.

    Invalid:

    var f = function () {
  return /=foo/;
};

  • #8836 aab1d17 Thanks @dyc3! - Fixed #7858: Biome now parses Astro files with empty frontmatter blocks.

  • #8755 3a15c29 Thanks @arturalkaim! - Fixed #6670. The $filename metavariable can now be used in GritQL where clauses to filter matches by filename.

  • #8821 63e68a1 Thanks @playhardgopro! - Fixed several bugs in Vue conditional rules (useVueValidVIf, useVueValidVElse, and useVueValidVElseIf) related to whitespace handling, newlines, and self-closing tags.

  • #8767 0d15370 Thanks @mdevils! - Fixed #3685: useExhaustiveDependencies now properly handles transparent expression wrappers like non-null assertions and type assertions in dependency comparisons.

    useMemo(() => Boolean(myObj!.x), [myObj!.x]); // No longer reports incorrect diagnostics
useMemo(() => myObj!.x?.y === true, [myObj!.x?.y]); // Now correctly matches dependencies

  • #8597 f764007 Thanks @Netail! - Added the nursery rule noDuplicateEnumValueNames. Enforce unique enum value names.

    Invalid:

    enum A {
  TEST
  TesT
}

  • #8679 33dfd7c Thanks @ematipico! - Fixed #8678. Now Biome correctly parses components inside Vue, Svelte and Astro files when they have the same name of self-closing elements.

  • #8617 31a9bfe Thanks @Netail! - Added the nursery rule useLoneExecutableDefinition. Require queries, mutations, subscriptions or fragments to be located in separate files.

    Invalid:

    query Foo {
  id
}

fragment Bar on Baz {
  id
}

  • #8697 8519669 Thanks @Faizanq! - Added the nursery lint rule noExcessiveLinesPerFile to CSS and GraphQL.

  • #8711 365f7aa Thanks @Netail! - Added new nursery rule noDuplicateEnumValues, which disallows defining an enum with multiple members initialized to the same value.

  • #8767 0d15370 Thanks @mdevils! - Fixed #5914: useExhaustiveDependencies now properly handles variables declared in the same statement.

    const varA = Math.random(),
  varB = useMemo(() => varA, [varA]); // varA is now correctly recognized as needed

  • #8767 0d15370 Thanks @mdevils! - Fixed #8427: useExhaustiveDependencies now properly resolves variable references to detect captured dependencies.

    const fe = fetchEntity;
useEffect(() => {
  fe(id);
}, [id, fe]); // fe is now correctly detected as needed

  • #8767 0d15370 Thanks @mdevils! - Fixed #8484: useExhaustiveDependencies now properly handles member access on stable hook results.

    const stableObj = useStable();
useMemo(() => {
  return stableObj.stableValue; // stableObj.stableValue is now correctly recognized as stable
}, []);

  • #8767 0d15370 Thanks @mdevils! - Fixed #7982: useExhaustiveDependencies now properly handles callback expressions with type assertions.

    const callback = useCallback(
  (() => {
    return count * 2;
  }) as Function,
  [count], // count is now correctly detected
);

  • #8766 39eb545 Thanks @Netail! - Fixed #8761: Reverted wrapping the URL of rule descriptions with <>, causing broken URLs in VSCode.

  • #8767 0d15370 Thanks @mdevils! - Fixed #3080: useExhaustiveDependencies now properly analyzes captures within referenced functions passed to hooks.

    function myEffect() {
  console.log(foo, bar);
}
useEffect(myEffect, [foo, bar]); // foo and bar are now correctly detected

  • #8740 4962ed0 Thanks @Netail! - Extra rule source references. biome migrate eslint should do a bit better detecting rules in your eslint configurations.

  • #8776 395746f Thanks @codiini! - Fixed #6003: noUselessUndefinedInitialization no longer reports exported variables initialized to undefined. In Svelte 4, this pattern is used to declare optional component props.

  • #8767 0d15370 Thanks @mdevils! - Fixed #4248: useExhaustiveDependencies now correctly handles function props passed as callbacks.

    const data = React.useMemo(getData, [getData]); // getData is now correctly recognized as needed

  • #8819 bc191ff Thanks @Netail! - Fixed #6567: noUnknownProperty now ignores unknown properties in at-rules which support descriptors.

  • #8787 adb652f Thanks @tuyuritio! - Fixed #8777: Add support for :active-view-transition pseudo-class.

  • #8639 6577e32 Thanks @ohnoah! - Added the nursery lint rule noExcessiveLinesPerFile. Biome now reports files that exceed a configurable line limit.

    // maxLines: 2
const a = 1;
const b = 2;
const c = 3;

  • #8753 71b5c6e Thanks @Netail! - Added the nursery rule noExcessiveClassesPerFile. Enforce a maximum number of classes per file.

    Invalid:

    class Foo {}
class Bar {}

  • #8754 d6b2bda Thanks @Netail! - Added the nursery rule noFloatingClasses. Disallow new operators outside of assignments or comparisons.

    Invalid:

    new Date();
What's Changed
New Contributors

Full Changelog: https://github.com/biomejs/biome/compare/@biomejs/biome@2.3.11...@biomejs/biome@2.3.12

View originalPermalink
How 2.3.12 went
2.3.11

Biome CLI v2.3.11

Added 8
  • Added the new nursery rule useVueValidTemplateRoot which validates root-level <template> elements in Vue single-file components
  • Added a new nursery rule useVueConsistentVBindStyle which enforces consistent v-bind style (shorthand vs longhand)
  • Added the rule useVueVForKey which enforces that any element using v-for also specifies a key
  • Added a new nursery rule useVueConsistentVOnStyle which enforces consistent v-on style (shorthand vs longhand)
  • Added the new nursery rule useVueValidVOnce which enforces that usages of the v-once directive in Vue.js SFC are valid
  • Added support for parsing and formatting the Svelte {#await} syntax when html.experimentalFullSupportEnabled is set to true
  • Added the new nursery rule noMultiAssign which helps prevent multiple chained assignments
  • Added the nursery rule useUniqueInputFieldNames which requires fields within an input object to be unique
Changed 1
  • Extended noUndeclaredEnvVars to support bracket notation, Bun runtime, and Deno runtime
Fixed 3
  • Fixed relative plugin paths to be resolved from the configuration file directory, including when configurations are merged
  • Fixed Biome's CSS formatter to break comma-separated declaration values at top-level commas when wrapping
  • Fixed false positive errors for safe boolean expressions in variable declarations

From Biome

2.3.11
Patch Changes

  • #8583 83be210 Thanks @dyc3! - Added the new nursery rule useVueValidTemplateRoot.

    This rule validates only root-level <template> elements in Vue single-file components. If the <template> has a src attribute, it must be empty. Otherwise, it must contain content.

    Invalid examples:

    <template src="./foo.html">content</template>

    <template></template>

    Valid examples:

    <template>content</template>

    <template src="./foo.html"></template>

  • #8586 df8fe06 Thanks @dyc3! - Added a new nursery rule useVueConsistentVBindStyle. Enforces consistent v-bind style (:prop shorthand vs v-bind:prop longhand). Default prefers shorthand; configurable via rule options.

  • #8587 9a8c98d Thanks @dyc3! - Added the rule useVueVForKey, which enforces that any element using v-for also specifies a key.

    Invalid

    <li v-for="item in items">{{ item }}</li>

    Valid

    <li v-for="item in items" :key="item.id">{{ item }}</li>

  • #8586 df8fe06 Thanks @dyc3! - Added a new nursery rule useVueConsistentVOnStyle. Enforces consistent v-on style (@event shorthand vs v-on:event longhand). Default prefers shorthand; configurable via rule options.

  • #8583 83be210 Thanks @dyc3! - Added the new nursery rule useVueValidVOnce. Enforces that usages of the v-once directive in Vue.js SFC are valid.

    <!-- Valid -->
<div v-once />

<!-- Invalid -->
<div v-once:aaa />
<div v-once.bbb />
<div v-once="ccc" />

  • #8498 d80fa41 Thanks @tt-a1i! - Fixed #8494. Extended noUndeclaredEnvVars to support bracket notation (process.env["VAR"], import.meta.env["VAR"]), Bun runtime (Bun.env.VAR, Bun.env["VAR"]), and Deno runtime (Deno.env.get("VAR")).

  • #8509 574a909 Thanks @ematipico! - Added support for parsing and formatting the Svelte {#await} syntax, when html.experimentalFullSupportEnabled is set to true.

    -{#await promise  then name }
+{#await promise then name}

-{:catch    name}
+{:catch name}

{/await}

  • #8316 d64e92d Thanks @washbin! - Added the new nursery rule noMultiAssign. This rule helps to prevent multiple chained assignments.

    For example, the following code triggers because there are two assignment expressions in the same statement.

    const a = (b = 0);

  • #8592 a5f59cd Thanks @Netail! - Added the nursery rule useUniqueInputFieldNames. Require fields within an input object to be unique.

    Invalid:

    query A($x: Int, $x: Int) {
  field
}

  • #8524 17a6156 Thanks @JacquesLeupin! - Fixed #8488: Relative plugin paths are now resolved from the configuration file directory, including when configurations are merged (e.g. extends: "//").

  • #8655 3260ec9 Thanks @JacquesLeupin! - Fixed #8636: Biome's CSS formatter now breaks comma-separated declaration values at top-level commas when wrapping.

  • #8537 cc3e851 Thanks @dibashthapa! - Fixed #8491: Resolved false positive errors for safe boolean expressions. There are still pending fixes. Head to #8491 (comment) for more details

    This new change will check for safe boolean expressions in variable declarations.

    For example,

    Valid:

    let isOne = 1;
let isPositiveNumber = number > 0;

return (
  <div>
    {" "}
    {isOne && "One"} {isPositiveNumber && "Is positive"}
  </div>
);

    Invalid:

    let emptyStr = "";
let isZero = 0;

return (
  <div>
    {emptyStr && "Empty String"} {isZero && "Number is zero"}{" "}
  </div>
);

  • #8511 16a9036 Thanks @ematipico! - Improved the diagnostics of the rules useSortedClasses and noUnnecessaryConditions. The diagnostics now state that these rules are a work in progress and link to the relevant GitHub issue.

  • #8521 a704be9 Thanks @ToBinio! - Added the nursery rule useVueConsistentDefinePropsDeclaration, which enforces consistent defineProps declaration style.

    Invalid
    <script setup lang="ts">
const props = defineProps({
  kind: { type: String },
});
</script>
    Valid
    <script setup lang="ts">
const props = defineProps<{
  kind: string;
}>();
</script>

  • #8595 7c85bf0 Thanks @dyc3! - Fixed #8584: The HTML formatter will preserve whitespace after some elements and embedded expressions, which more closely aligns with Prettier's behavior.

    - <h1>Hello, {framework}and Svelte!</h1>
+ <h1>Hello, {framework} and Svelte!</h1>

  • #8598 5e85d43 Thanks @Netail! - Added the nursery rule useUniqueFieldDefinitionNames. Require all fields of a type to be unique.

    Invalid:

    type SomeObject {
  foo: String
  foo: String
}

  • #8495 b573d14 Thanks @taga3s! - Fixed #8405: noMisusedPromises now emits warnings/errors when a function returns union types such as T | Promise<T> which is used in conditionals.

    const a = (): boolean | Promise<boolean> => Promise.resolve(true);
if (a()) {
} // Now correctly flagged

  • #8632 0be7d12 Thanks @Bertie690! - The documentation & rule sources for lint/complexity/noBannedTypes have been updated to fix a few oversights.

    In addition to some general typo fixes:

    • The rule now recommends Record<keyof any, never> instead of Record<string, never> (the latter of which incorrectly allows symbol-keyed properties).

    • The rule mentions an alternate method to enforce object emptiness involving unique symbol-based guards used by type-fest and many other packages:

      declare const mySym: unique symbol;

// Since this type's only property is an unexported `unique symbol`, nothing that imports it can specify any properties directly
// (as far as excess property checks go)
export type EmptyObject = { [mySym]?: never };
export type IsEmptyObject<T> = T extends EmptyObject ? true : false;

    The rule's listed sources have been updated as well to reflect the original source rule (ban-types) having been split into 3 separate rules circa April 2024.

  • #8580 a3a1ad2 Thanks @taga3s! - Added the nursery rule noBeforeInteractiveScriptOutsideDocument to the Next.js domain. This rule prevents usage of next/script's beforeInteractive strategy outside of pages/_document.js.

  • #8493 5fc24f4 Thanks @ematipico! - Added support for parsing and formatting the Svelte {#each} syntax, when html.experimentalFullSupportEnabled is set to true.

    - {#each items   as item  }
+ {#each items as item}

{/each}

  • #8546 0196c0e Thanks @Zaczero! - Hardened union static-member type flattening in edge cases (e.g. unions containing unknown or inferred expression types). This keeps inference conservative and avoids unstable type growth in node = node.parent-style loops.

  • #8569 1022c76 Thanks @ematipico! - Fixed an issue where the Biome HTML parser would emit a parse error when certain keywords are inside the text of HTML tags.

  • #8606 f50723b Thanks @dyc3! - Fixed #8563: fixed a bounds check on bogus regex literals that caused panics when doing type inference

  • #7410 ab9af9a Thanks @sgarcialaguna! - Added the new nursery rule noJsxPropsBind. This rule disallows .bind(), arrow functions, or function expressions in JSX props.

    Invalid:

    <Foo onClick={() => console.log("Hello!")}></Foo>

  • #8523 5f22f1c Thanks @ematipico! - Improved the diagnostics of nursery rules. Added a message to diagnostics emitted by nursery rules, so that users are aware of nature of nursery rules.

  • #8571 03666fd Thanks @dyc3! - Improved the performance of noRedeclare by eliminating string allocations

  • #8591 9dd9ca7 Thanks @Netail! - Added the nursery rule useUniqueArgumentNames. Enforce unique arguments for GraphQL fields & directives.

    Invalid:

    query {
  field(arg1: "value", arg1: "value")
}

  • #8521 a704be9 Thanks @ToBinio! - Update useVueDefineMacrosOrder to only run on blocks.

  • #8344 7b982ba Thanks @ematipico! - Reduced the system calls when running the CLI. The performances might be noticeable in big projects that have multiple libraries and enable project rules.

  • #8588 958e24b Thanks @Netail! - Added the nursery rule useUniqueVariableNames. Enforce unique variable names for GraphQL operations.

    Invalid:

    query ($x: Int, $x: Int) {
  field
}

  • #8529 8794883 Thanks @mdevils! - Fixed #8499: useExhaustiveDependencies properly handles aliased destructured object keys when using stableResult configuration.

  • #8557 4df2f4d Thanks @dyc3! - Fixed an issue with the HTML formatter where it wouldn't add a space before the /> in self closing elements. This brings the HTML formatter more in line with Prettier.

    -<Component/>
+<Component />

  • #8509 574a909 Thanks @ematipico! - Added support for parsing and formatting the Svelte {#snippet} syntax, when html.experimentalFullSupportEnabled is set to true.

    -{#snippet    foo() }
+{#snippet foo()}

{/snippe}

  • #8248 1231a5c Thanks @emilyinure! - Added new nursery rule noReturnAssign, which disallows assignments inside return statements.

    Invalid:

    function f(a) {
  return (a = 1);
}

  • #8531 6b09620 Thanks @taga3s! - Fixed #8472: The CSS parser can now accept multiple comma separated parameters in :active-view-transition-type.

  • #8615 b9da66d Thanks @taga3s! - Remove next/script component name check from noBeforeInteractiveScriptOutsideDocument since it is a default export.

  • #8536 efbfbe2 Thanks @dyc3! - Fixed #8527: Improved type inference where analyzing code with repeated object property access and assignments (e.g. node = node.parent, a pattern common when traversing trees in a while loop) could hit an internal type limit. Biome now handles these cases without exceeding the type limit.

  • #8583 83be210 Thanks @dyc3! - Added the new nursery rule useVueValidVCloak. Enforces that usages of the v-cloak directive in Vue.js SFC are valid.

    <!-- Valid -->
<div v-cloak />

<!-- Invalid -->
<div v-cloak:aaa />
<div v-cloak.bbb />
<div v-cloak="ccc" />

  • #8583 83be210 Thanks @dyc3! - Added the new nursery rule useVueValidVPre. Enforces that usages of the v-pre directive in Vue.js SFC are valid.

    <!-- Valid -->
<div v-pre />

<!-- Invalid -->
<div v-pre:aaa />
<div v-pre.bbb />
<div v-pre="ccc" />

  • #8644 a3a27a7 Thanks @JacquesLeupin! - Added the nursery rule useVueVapor to enforce <script setup vapor> in Vue SFCs. For example <script setup> is invalid.

  • #8508 b86842c Thanks @tt-a1i! - Fixed #6783: now, when a path is provided via --stdin-file-path, Biome checks whether the file exists on disk. If the path doesn't exist (virtual path), ignore checks (files.includes and VCS ignore rules) are skipped.

What's Changed
New Contributors

Full Changelog: https://github.com/biomejs/biome/compare/@biomejs/biome@2.3.10...@biomejs/biome@2.3.11

View originalPermalink
How 2.3.11 went
2.3.10

Biome CLI v2.3.10

Added 2
  • Added a Turborepo domain and a new noUndeclaredEnvVars rule for warning users of unsafe environment variable usage in Turborepos
  • Added the nursery rule noAmbiguousAnchorText which disallows ambiguous anchor descriptions
Changed 1
  • Improved handling of defineProps() macro in Vue components to avoid false positives in noVueReservedKeys rule in non-setup scripts
Fixed 5
  • noRedeclare rule no longer reports redeclarations for infer type in conditional types
  • Fixed a regression in how noExtraNonNullAssertion flags extra non-null assertions
  • The semantic model now indexes TypeScript constructor method definitions and no longer panics if you use one
  • Fixed the nursery rule noLeakedRender and the biome migrate eslint command now correctly detects the rule react/jsx-no-leaked-render
  • Fixed handling of characters that contain multiple code points when running in stdin mode

From Biome

2.3.10
Patch Changes

  • #8417 c3a2557 Thanks @taga3s! - Fixed #7809: noRedeclare no longer reports redeclarations for infer type in conditional types.

  • #8477 90e8684 Thanks @dyc3! - Fixed #8475: fixed a regression in how noExtraNonNullAssertion flags extra non-null assertions

  • #8479 250b519 Thanks @dyc3! - Fixed #8473: The semantic model now indexes typescript constructor method definitions, and no longer panics if you use one (a regression in 2.3.9).

  • #8448 2af85c1 Thanks @mdevils! - Improved handling of defineProps() macro in Vue components. The noVueReservedKeys rule now avoids false positives in non-setup scripts.

  • #8420 42033b0 Thanks @vsn4ik! - Fixed the nursery rule noLeakedRender.

    The biome migrate eslint command now correctly detects the rule react/jsx-no-leaked-render in your eslint configurations.

  • #8426 285d932 Thanks @anthonyshew! - Added a Turborepo domain and a new "noUndeclaredEnvVars" rule in it for warning users of unsafe environment variable usage in Turborepos.

  • #8410 a21db74 Thanks @ematipico! - Fixed #2988 where Biome couldn't handle properly characters that contain multiple code points when running in stdin mode.

  • #8372 b352ee4 Thanks @Netail! - Added the nursery rule noAmbiguousAnchorText, which disallows ambiguous anchor descriptions.

    Invalid
    <a>learn more</a>
What's Changed
New Contributors

Full Changelog: https://github.com/biomejs/biome/compare/@biomejs/biome@2.3.9...@biomejs/biome@2.3.10

View originalPermalink
How 2.3.10 went
2.3.9

Biome CLI v2.3.9

Added 4
  • Added the nursery rule noScriptUrl, which disallows the use of javascript: URLs to prevent XSS vulnerabilities
  • Added the nursery rule useAwaitThenable, which enforces that await is only used on Promise values
  • Added the nursery rule useRegexpExec, which enforces RegExp#exec over String#match when no global flag is provided
  • Added the rule useRequiredScripts, which enforces presence of configurable entries in the scripts section of package.json files
Changed 5
  • Updated the HTML formatter to match Prettier 3.7's behavior for handling iframe's allow attribute
  • Reduced the internal memory used by the Biome formatter
  • Improved the rule noBiomeFirstException to inspect if extended configurations already contain the catch-all ** inside files.includes and suggest removing it
  • Clarified diagnostic message for lint/style/useUnifiedTypeSignatures to state that multiple similar overload signatures are hard to read and maintain
  • Updated biome rage to show if experimental HTML full support is enabled
Fixed 3
  • Fixed return statements in Astro frontmatter no longer triggering Illegal return statement errors when using experimentalFullSupportEnabled
  • Fixed tracking of types of TypeScript constructor parameter properties to resolve false negatives in noFloatingPromises and other typed rules
  • Fixed the CSS parser with Tailwind directives enabled to no longer error when using things like prefix(tw) in @import at rules

From Biome

2.3.9
Patch Changes

  • #8232 84c9e08 Thanks @ruidosujeira! - Added the nursery rule noScriptUrl.

    This rule disallows the use of javascript: URLs, which are considered a form of eval and can pose security risks such as XSS vulnerabilities.

    <a href="javascript:alert('XSS')">Click me</a>

  • #8341 343dc4d Thanks @arendjr! - Added the nursery rule useAwaitThenable, which enforces that await is only used on Promise values.

    Invalid
    await "value";

const createValue = () => "value";
await createValue();
    Caution

    This is a first iteration of the rule, and does not yet detect generic "thenable" values.

  • #8034 e7e0f6c Thanks @Netail! - Added the nursery rule useRegexpExec. Enforce RegExp#exec over String#match if no global flag is provided.

  • #8137 d407efb Thanks @denbezrukov! - Reduced the internal memory used by the Biome formatter.

  • #8281 30b046f Thanks @tylersayshi! - Added the rule useRequiredScripts, which enforces presence of configurable entries in the scripts section of package.json files.

  • #8290 d74c8bd Thanks @dyc3! - The HTML formatter has been updated to match Prettier 3.7's behavior for handling <iframe>'s allow attribute.

    - <iframe allow="layout-animations 'none'; unoptimized-images 'none'; oversized-images 'none'; sync-script 'none'; sync-xhr 'none'; unsized-media 'none';"></iframe>
+ <iframe
+ 	allow="
+ 		layout-animations 'none';
+ 		unoptimized-images 'none';
+ 		oversized-images 'none';
+ 		sync-script 'none';
+ 		sync-xhr 'none';
+ 		unsized-media 'none';
+ 	"
+ ></iframe>

  • #8302 d1d5014 Thanks @mlafeldt! - Fixed #8109: return statements in Astro frontmatter no longer trigger "Illegal return statement" errors when using experimentalFullSupportEnabled.

  • #8346 f3aee1a Thanks @arendjr! - Fixed #8292: Implement tracking of types of TypeScript constructor parameter properties.

    This resolves certain false negatives in noFloatingPromises and other typed rules.

    Example
    class AsyncClass {
  async returnsPromise() {
    return "value";
  }
}

class ShouldBeReported {
  constructor(public field: AsyncClass) {}
  //          ^^^^^^^^^^^^----------------- Parameter property declaration

  async shouldBeReported() {
    // `noFloatingPromises` will now report the following usage:
    this.field.returnsPromise();
  }
}

  • #8326 153e3c6 Thanks @ematipico! - Improved the rule noBiomeFirstException. The rule can now inspect if extended configurations already contain the catch-all ** inside files.includes and, if so, the rule suggests removing ** from the user configuration.

  • #8433 397547a Thanks @dyc3! - Fixed #7920: The CSS parser, with Tailwind directives enabled, will no longer error when you use things like prefix(tw) in @import at rules.

  • #8378 cc2a62e Thanks @Bertie690! - Clarify diagnostic message for lint/style/useUnifiedTypeSignatures

    The rule's diagnostic message now clearly states that multiple similar overload signatures are hard to read & maintain, as opposed to overload signatures in general.

  • #8296 9d3ef10 Thanks @dyc3! - biome rage now shows if you have experimental HTML full support enabled.

  • #8414 09acf2a Thanks @Bertie690! - Updated the documentation & diagnostic message for lint/nursery/noProto, mentioning the reasons for its longstanding deprecation and why more modern alternatives are preferred.

    Notably, the rule clearly states that using __proto__ inside object literal definitions is still allowed, being a standard way to set the prototype of a newly created object.

  • #8445 c3df0e0 Thanks @tt-a1i! - Fix --changed and --staged flags throwing "No such file or directory" error when a file has been deleted or renamed in the working directory. The CLI now filters out files that no longer exist before processing.

  • #8459 b17d12b Thanks @ruidosujeira! - Fix #8435: resolved false positive in noUnusedVariables for generic type parameters in construct signature type members (new <T>(): T).

  • #8439 a78774b Thanks @tt-a1i! - Fixed #8011: useConsistentCurlyBraces no longer suggests removing curly braces from JSX expression children containing characters that would cause parsing issues or semantic changes when converted to plain JSX text ({, }, <, >, &).

  • #8436 a392c06 Thanks @ruidosujeira! - Fixed #8429. Formatter, linter, and assist settings now correctly inherit from global configuration when not explicitly specified in overrides.

    Before this fix, when an override specified only one feature (e.g., only linter), other features would be incorrectly disabled instead of inheriting from global settings.

    Example configuration that now works correctly:

    {
  "formatter": { "enabled": true },
  "overrides": [
    {
      "includes": ["*.vue"],
      "linter": { "enabled": false }
    }
  ]
}

    After this fix, .vue files will have the linter disabled (as specified in the override) but the formatter enabled (inherited from global settings).

  • #8411 9f1b3b0 Thanks @rriski! - Properly handle name, type_arguments, and attributes slots for JsxOpeningElement and JsxSelfClosingElement GritQL patterns.

    The following biome search commands no longer throw errors:

    biome search 'JsxOpeningElement(name = $elem_name) where { $elem_name <: "div" }'
biome search 'JsxSelfClosingElement(name = $elem_name) where { $elem_name <: "div" }'

  • #8441 cf37d0d Thanks @tt-a1i! - Fixed #6577: noUselessUndefined no longer reports () => undefined in arrow function expression bodies. Previously, the rule would flag this pattern and suggest replacing it with () => {}, which conflicts with the noEmptyBlockStatements rule.

  • #8444 8caa7a0 Thanks @tt-a1i! - Fix noUnknownMediaFeatureName false positive for prefers-reduced-transparency media feature. The feature name was misspelled as prefers-reduded-transparency in the keywords list.

  • #8443 c3fa5a1 Thanks @tt-a1i! - Fix useGenericFontNames false positive when a CSS variable is used as the last value in font-family or font. The rule now correctly ignores cases like font-family: "Noto Serif", var(--serif) and font: 1em Arial, var(--fallback).

  • #8281 30b046f Thanks @tylersayshi! - Fixed noDuplicateDependencies incorrectly triggering on files like _package.json.

  • #8315 c7915c4 Thanks @hirokiokada77! - Fixed #5213: The noDoneCallback rule no longer flags false positives when a method is called on a regular variable bound to identifiers such as before, after, beforeEach, and afterEach.

  • #8398 204844f Thanks @Bertie690! - The default value of the ignoreRestSiblings option for noUnusedVariables' has been reverted to its prior value of true after an internal refactor accidentally changed it.

    The diagnostic message has also been tweaked for readability.

  • #8242 9694e37 Thanks @dyc3! - Fixed bugs in the HTML parser so that it will flag invalid shorthand syntaxes instead of silently accepting them. For example, <Foo : foo="5" /> is now invalid because there is a space after the :.

  • #8297 efa694c Thanks @Yonom! - Added support for negative value utilities in useSortedClasses. Negative value utilities such as -ml-2 or -top-4 are now recognized and sorted correctly alongside their positive counterparts.

    // Now detected as unsorted:
<div class="-ml-2 p-4 -mt-1" />
// Suggested fix:
<div class="-mt-1 -ml-2 p-4" />

  • #8335 3710702 Thanks @dibashthapa! - Added the new nursery rule useDestructuring. This rule helps to encourage destructuring from arrays and objects.

    For example, the following code triggers because the variable name x matches the property foo.x, making it ideal for object destructuring syntax.

    var x = foo.x;

  • #8383 59b2f9a Thanks @ematipico! - Fixed #7927: noExtraNonNullAssertion incorrectly flagged separate non-null assertions on both sides of an assignment.

    The rule now correctly distinguishes between nested non-null assertions (still flagged) and separate non-null assertions on different sides of an assignment (allowed).

    Examples
    Valid (now allowed)
    arr[0]! ^= arr[1]!;
    Invalid (still flagged)
    arr[0]!! ^= arr[1];
arr[0] ^= arr[1]!!;

  • #8401 382786b Thanks @Bertie690! - useExhaustiveDependencies now correctly validates custom hooks whose dependency arrays come before their callbacks.

    Previously, a logical error caused the rule to be unable to detect dependency arrays placed before hook callbacks, producing spurious errors and blocking further diagnostics.

    {
  "linter": {
    "rules": {
      "correctness": {
        "useExhaustiveDependencies": {
          "level": "error",
          "options": {
            "hooks": [
              {
                "name": "doSomething",
                "closureIndex": 2,
                "dependenciesIndex": 0
              }
            ]
          }
        }
      }
    }
  }
}

    function component() {
  let thing = 5;
  // The rule will now correctly recognize `thing` as being specified
  // instead of erroring due to "missing" dependency arrays
  doSomething([thing], "blah", () => {
    console.log(thing);
  });
}

    The rule documentation & diagnostic messages have also been reworked for improved clarity.

  • #8365 8f36051 Thanks @JacquesLeupin! - Fixed #8360: GritQL plugins defined in child configurations with extends: "//" now work correctly.

  • #8306 8de2774 Thanks @dibashthapa! - Fixed #8288: Fixed the issue with false positive errors

    This new change will ignore attribute and only show diagnostics for JSX Expressions

    For example

    Valid:

    <Something checked={isOpen && items.length} />

    Invalid:

    const Component = () => {
  return isOpen && items.length;
};

  • #8356 f9673fc Thanks @ematipico! - Fixed #7917, where Biome removed the styles contained in a <style lang="scss">, when experimentalFullSupportEnabled is enabled.

  • #8371 d71924e Thanks @ematipico! - Fixed #7343, where Biome failed to resolve extended configurations from parent directories using relative paths.

  • #8404 6a221f9 Thanks @fireairforce! - Fixed #7826, where a class member named async will not cause the parse error.

  • #8249 893e36c Thanks @cormacrelf! - Addressed #7538. Reduced the volume of logging from the LSP server.

    Use biome clean to remove large logs.

  • #8303 db2c65b Thanks @hirokiokada77! - Fixed #8300: noUnusedImports now detects JSDoc tags on object properties.

    import type LinkOnObjectProperty from "mod";

const testLinkOnObjectProperty = {
	/**
	 * {@link LinkOnObjectProperty}
	 */
	property: 0,
};

  • #8328 9cf2332 Thanks @Netail! - Corrected rule source reference. biome migrate eslint should do a bit better detecting rules in your eslint configurations.

  • #8403 c96dcf2 Thanks @dyc3! - Fixed #8340: noUnknownProperty will no longer flag anything in @plugin when the parser option tailwindDirectives is enabled

  • #8284 4976d1b Thanks @denbezrukov! - Improved the performance of the Biome Formatter by enabling the internal source maps only when needed.

  • #8260 a226b28 Thanks @ho991217! - Fixed biome-vscode#817: Biome now updates documents when the textDocument/didSave notification is received.

  • #8183 b064786 Thanks @hornta! - Fixed #8179: The useConsistentArrowReturn rule now correctly handles multiline expressions in its autofix when the style option is set to "always".

    Previously, the autofix would incorrectly place a newline after the return keyword, causing unexpected behavior.

    Example:

    const foo = (l) => l.split("\n");

    Now correctly autofixes to:

    const foo = (l) => {
-   return
-   l.split('\n');
+   return l.split('\n');
}

  • #8382 7409cba Thanks @fireairforce! - Fixed #8338: Ignored the noUnknownTypeSelector check when the root selector is used under View Transition pseudo-elements.

    Example

    ::view-transition-old(root),
::view-transition-new(root) {
  z-index: 1;
}

  • #7513 e039f3b Thanks @AsherDe! - Added the nursery rule noVueSetupPropsReactivityLoss.

    This new rule disallows usages that cause the reactivity of props passed to the setup function to be lost.

    Invalid code example:

    export default {
  setup({ count }) {
    // `count` is no longer reactive here.
    return () => h("div", count);
  },
};
What's Changed
New Contributors

Full Changelog: https://github.com/biomejs/biome/compare/@biomejs/biome@2.3.8...@biomejs/biome@2.3.9

View originalPermalink
How 2.3.9 went
2.3.8

Biome CLI v2.3.8

Added 4
  • Added the noLeakedRender rule to prevent potential leaks when rendering components that use binary expressions or ternaries
  • Added the noDuplicatedSpreadProps nursery rule to disallow JSX prop spreading the same identifier multiple times
  • Added the noMultiStr rule which disallows creating multiline strings by escaping newlines
  • Added the noEqualsToNull rule which enforces the use of === and !== for comparison with null instead of == or !=
Changed 1
  • Added support for dollar-sign-prefixed filenames in the useFilenamingConvention rule to support frameworks like TanStack Start
Fixed 6
  • Fixed configuration not being applied correctly when passed via --config-path with multiple root configuration files
  • Fixed a bug where logs from --log-level=info were being discarded
  • Fixed HTML parser with Vue directives enabled to parse v-slot shorthand syntax
  • Fixed formatting to prefer breaking after the assignment operator for conditional types with generic parameters to match Prettier
  • Fixed noImportCycles rule to allow files to export from themselves
  • Fixed HTML parser to correctly parse Vue event handlers that contain colons

From Biome

2.3.8
Patch Changes

  • #8188 4ca088c Thanks @ematipico! - Fixed #7390, where Biome couldn't apply the correct configuration passed via --config-path.

    If you have multiple root configuration files, running any command with --config-path will now apply the chosen configuration file.

  • #8171 79adaea Thanks @dibashthapa! - Added the new rule noLeakedRender. This rule helps prevent potential leaks when rendering components that use binary expressions or ternaries.

    For example, the following code triggers the rule because the component would render 0:

    const Component = () => {
  const count = 0;
  return <div>{count && <span>Count: {count}</span>}</div>;
};

  • #8116 b537918 Thanks @Netail! - Added the nursery rule noDuplicatedSpreadProps. Disallow JSX prop spreading the same identifier multiple times.

    Invalid:

    <div {...props} something="else" {...props} />

  • #8256 f1e4696 Thanks @cormacrelf! - Fixed a bug where logs were discarded (the kind from --log-level=info etc.). This is a regression introduced after an internal refactor that wasn't adequately tested.

  • #8226 3f19b52 Thanks @dyc3! - Fixed #8222: The HTML parser, with Vue directives enabled, can now parse v-slot shorthand syntax, e.g. <template #foo>.

  • #8007 182ecdc Thanks @brandonmcconnell! - Added support for dollar-sign-prefixed filenames in the useFilenamingConvention rule.

    Biome now allows filenames starting with the dollar-sign (e.g. $postId.tsx) by default to support naming conventions used by frameworks such as TanStack Start for file-based-routing.

  • #8218 91484d1 Thanks @hirokiokada77! - Added the noMultiStr rule, which disallows creating multiline strings by escaping newlines.

    Invalid:

    const foo =
  "Line 1\n\
Line 2";

    Valid:

    const foo = "Line 1\nLine 2";
const bar = `Line 1
Line 2`;

  • #8225 98ca2ae Thanks @ongyuxing! - Fixed #7806: Prefer breaking after the assignment operator for conditional types with generic parameters to match Prettier.

    -type True = unknown extends Type<
-  "many",
-  "generic",
-  "parameters",
-  "one",
-  "two",
-  "three"
->
-  ? true
-  : false;
+type True =
+  unknown extends Type<"many", "generic", "parameters", "one", "two", "three">
+    ? true
+    : false;

  • #6765 23f7855 Thanks @emilyinure! - Fixed #6569: Allow files to export from themselves with noImportCycles.

    This means the following is now allowed:

    // example.js
export function example() {
  return 1;
}

// Re-exports all named exports from the current module under a single namespace
// and then imports the namespace from the current module.
// Allows for encapsulating functions/variables into a namespace instead
// of using a static class.
export * as Example from "./example.js";

import { Example } from "./example.js";

  • #8214 68c052e Thanks @hirokiokada77! - Added the noEqualsToNull rule, which enforces the use of === and !== for comparison with null instead of == or !=.

    Invalid:

    foo == null;
foo != null;

    Valid:

    foo === null;
foo !== null;

  • #8219 793bb9a Thanks @dyc3! - Fixed #8190: The HTML parser will now parse Vue event handlers that contain : correctly, e.g. @update:modelValue="onUpdate".

  • #8259 4a9139b Thanks @hirokiokada77! - Fixed #8254: The noParameterAssign rule with propertyAssignment: "deny" was incorrectly reporting an error when a function parameter was used on the right-hand side of an assignment to a local variable's property.

    The rule should only flag assignments that modify the parameter binding or its properties (L-value), not the use of its value.

    Valid:

    (input) => {
  const local = { property: 0 };
  local.property = input;
};

  • #8201 cd2edd7 Thanks @Netail! - Added the nursery rule noTernary. Disallow ternary operators.

    Invalid:

    const foo = isBar ? baz : qux;

  • #8172 de98933 Thanks @JeremyMoeglich! - Fixed #8145: handling of large hex literals, which previously caused both false positives and false negatives.

    This affects noPrecisionLoss and noConstantMathMinMaxClamp.

  • #8210 7b44e9e Thanks @Netail! - Corrected rule source reference. biome migrate eslint should do a bit better detecting rules in your eslint configurations.

  • #8213 e430555 Thanks @ruidosujeira! - Fixed #8209: Recognized formatting capability when either range or on-type formatting is supported, not only full-file formatting. This ensures editors and the language server correctly detect formatting support in files like JSONC.

  • #8202 6f49d95 Thanks @hirokiokada77! - Fixed #8079: Properly handle name and value metavariables for JsxAttribute GritQL queries.

    The following biome search command no longer throws an error:

    biome search 'JsxAttribute($name, $value) as $attr where { $name <: "style" }'

  • #8276 f7e836f Thanks @hirokiokada77! - Added the noProto rule, which disallows the use of the __proto__ property for getting or setting the prototype of an object.

    Invalid:

    obj.__proto__ = a;
const b = obj.__proto__;

    Valid:

    const a = Object.getPrototypeOf(obj);
Object.setPrototypeOf(obj, b);
What's Changed
New Contributors

Full Changelog: https://github.com/biomejs/biome/compare/@biomejs/biome@2.3.7...@biomejs/biome@2.3.8

View originalPermalink
How 2.3.8 went
2.3.7

Biome CLI v2.3.7

Added 2
  • Added support for parsing and formatting the CSS if function
  • Added useVueValidVText lint rule to enforce valid v-text directives
Changed 2
  • Improved detection of noUnnecessaryConditions rule to not trigger for variables that are mutated inside a module, now marked as inspired
  • Improved type inference engine to resolve types for variables that are assigned to multiple values
Fixed 9
  • Correctly place await after leading comment in auto-fix action from noFloatingPromises rule
  • noInvalidUseBeforeDeclaration no longer reports some valid use before declarations
  • HTML parser now correctly rejects whitespace in Vue directives to prevent merging multiple directives into one
  • noUnusedImports rule now ignores imports that are used by @linkcode and @linkplain JSDoc tags
  • noSyncScripts rule now ignores script tags with type="module" as these are always non-blocking
  • Range suppressions now handle suppressed categories properly

From Biome

2.3.7
Patch Changes

  • #8169 7fdcec8 Thanks @arendjr! - Fixed #7999: Correctly place await after leading comment in auto-fix action from noFloatingPromises rule.

  • #8157 12d5b42 Thanks @Conaclos! - Fixed #8148. noInvalidUseBeforeDeclaration no longer reports some valid use before declarations.

    The following code is no longer reported as invalid:

    class classA {
  C = C;
}
const C = 0;

  • #8178 6ba4157 Thanks @dyc3! - Fixed #8174, where the HTML parser would parse 2 directives as a single directive because it would not reject whitespace in Vue directives. This would cause the formatter to erroneously merge the 2 directives into one, resulting in broken code.

    - <Component v-else:property="123" />
+ <Component v-else :property="123" />

  • #8088 0eb08e8 Thanks @db295! - Fixed #7876: The noUnusedImports rule now ignores imports that are used by @linkcode and @linkplain (previously supported @link and @see).

    The following code will no longer be a false positive:

    import type { a } from "a"

/**
 * {@linkcode a}
 */
function func() {}

  • #8119 8d64655 Thanks @ematipico! - Improved the detection of the rule noUnnecessaryConditions. Now the rule isn't triggered for variables that are mutated inside a module.

    This logic deviates from the original rule, hence noUnnecessaryConditions is now marked as "inspired".

    In the following example, hey starts as false, but then it's assigned to a string. The rule isn't triggered inside the if check.

    let hey = false;

function test() {
  hey = "string";
}

if (hey) {
}

  • #8149 e0a02bf Thanks @Netail! - Fixed #8144: Improve noSyncScripts, ignore script tags with type="module" as these are always non-blocking.

  • #8182 e9f068e Thanks @hirokiokada77! - Fixed #7877: Range suppressions now handle suppressed categories properly.

    Valid:

    // biome-ignore-start lint: explanation
const foo = 1;
// biome-ignore-end lint: explanation

  • #8111 bf1a836 Thanks @ryan-m-walker! - Added support for parsing and formatting the CSS if function.

    Example

    .basic-style {
  color: if(style(--scheme: dark): #eeeeee; else: #000000;);
}

  • #8173 7fc07c1 Thanks @ematipico! - Fixed #8138 by reverting an internal refactor that caused a regression to the rule noUnusedPrivateClassMembers.

  • #8119 8d64655 Thanks @ematipico! - Improved the type inference engine, by resolving types for variables that are assigned to multiple values.

  • #8158 fb1458b Thanks @dyc3! - Added the useVueValidVText lint rule to enforce valid v-text directives. The rule reports when v-text has an argument, has modifiers, or is missing a value.

    Invalid:

    <div v-text />
<!-- missing value -->
<div v-text:aaa="foo" />
<!-- has argument -->
<div v-text.bbb="foo" />
<!-- has modifier -->

  • #8158 fb1458b Thanks @dyc3! - Fixed useVueValidVHtml so that it will now flag empty strings, e.g. v-html=""

  • #7078 bb7a15c Thanks @emilyinure! - Fixed #6675: Now only flags noAccumulatingSpread on Object.assign when a new object is being allocated on each iteration. Before, all cases using Object.assign with reduce parameters were warned despite not making new allocations.

    The following code will no longer be a false positive:

    foo.reduce((acc, bar) => Object.assign(acc, bar), {});

    The following cases which do make new allocations will continue to warn:

    foo.reduce((acc, bar) => Object.assign({}, acc, bar), {});

  • #8175 0c8349e Thanks @ryan-m-walker! - Fixed CSS formatting of dimension units to use correct casing for Q, Hz and kHz.

    Before:

    .cssUnits {
  a: 1Q;
  b: 1Hz;
  c: 1kHz;
}

    After:

    .cssUnits {
  a: 1Q;
  b: 1Hz;
  c: 1kHz;
}
What's Changed
New Contributors

Full Changelog: https://github.com/biomejs/biome/compare/@biomejs/biome@2.3.6...@biomejs/biome@2.3.7

View originalPermalink
How 2.3.7 went
2.3.6

Biome CLI v2.3.6

Added 5
  • Added the nursery rule useFind to enforce the use of Array.prototype.find() over Array.prototype.filter() followed by [0] when looking for a single result
  • Added the nursery rule useConsistentGraphqlDescriptions requiring all descriptions to follow the same style (either block or inline) inside GraphQL files
  • Added the nursery rule noVueVIfWithVFor to disallow v-for and v-if on the same element
  • Added the nursery rule noForIn to disallow iterating using a for-in loop
  • Added the nursery rule useVueHyphenatedAttributes to encourage using kebab case for attribute names per the Vue style guide
Fixed 5
  • Fixed useValidLang to accept valid BCP 47 language tags with script subtags
  • Fixed noParametersOnlyUsedInRecursion to correctly detect recursion by comparing function bindings instead of just names
  • Fixed noNestedTernary to correctly detect nested ternary expressions even when they are wrapped in parentheses
  • Fixed useReadonlyClassProperties code fix when checkAllProperties is enabled to no longer insert a newline after readonly and the class property
  • Fixed useReactFunctionComponents to no longer report class components that implement componentDidCatch using class expressions

From Biome

2.3.6
Patch Changes

  • #8100 82b9a8e Thanks @Netail! - Added the nursery rule useFind. Enforce the use of Array.prototype.find() over Array.prototype.filter() followed by [0] when looking for a single result.

    Invalid:

    [1, 2, 3].filter((x) => x > 1)[0];

[1, 2, 3].filter((x) => x > 1).at(0);

  • #8118 dbc7021 Thanks @hirokiokada77! - Fixed #8117: useValidLang now accepts valid BCP 47 language tags with script subtags.

    Valid:

    <html lang="zh-Hans-CN"></html>

  • #7672 f1d5725 Thanks @Netail! - Added the nursery rule useConsistentGraphqlDescriptions, requiring all descriptions to follow the same style (either block or inline) inside GraphQL files.

    Invalid:

    enum EnumValue {
  "this is a description"
  DEFAULT
}

    Valid:

    enum EnumValue {
  """
  this is a description
  """
  DEFAULT
}

  • #8026 f102661 Thanks @matanshavit! - Fixed #8004: noParametersOnlyUsedInRecursion now correctly detects recursion by comparing function bindings instead of just names.

    Previously, the rule incorrectly flagged parameters when a method had the same name as an outer function but called the outer function (not itself):

    function notRecursive(arg) {
  return arg;
}

const obj = {
  notRecursive(arg) {
    return notRecursive(arg); // This calls the outer function, not the method itself
  },
};

    Biome now properly distinguishes between these cases and will not report false positives.

  • #8097 5fc5416 Thanks @dyc3! - Added the nursery rule noVueVIfWithVFor. This rule disallows v-for and v-if on the same element.

    <!-- Invalid -->
<div v-for="item in items" v-if="item.isActive">
  {{ item.name }}
</div>

  • #8085 7983940 Thanks @Netail! - Added the nursery rule noForIn. Disallow iterating using a for-in loop.

    Invalid:

    for (const i in array) {
  console.log(i, array[i]);
}

  • #8086 2b41e82 Thanks @matanshavit! - Fixed #8045: The noNestedTernary rule now correctly detects nested ternary expressions even when they are wrapped in parentheses (e.g. foo ? (bar ? 1 : 2) : 3).

    Previously, the rule would not flag nested ternaries like foo ? (bar ? 1 : 2) : 3 because the parentheses prevented detection. The rule now looks through parentheses to identify nested conditionals.

    Previously not detected (now flagged):

    const result = foo ? (bar ? 1 : 2) : 3;

    Still valid (non-nested with parentheses):

    const result = foo ? bar : baz;

  • #8075 e403868 Thanks @YTomm! - Fixed #7948: The useReadonlyClassProperties code fix when checkAllProperties is enabled will no longer insert a newline after readonly and the class property.

  • #8102 47d940e Thanks @lucasweng! - Fixed #8027. useReactFunctionComponents no longer reports class components that implement componentDidCatch using class expressions.

    The rule now correctly recognizes error boundaries defined as class expressions:

    const ErrorBoundary = class extends Component {
  componentDidCatch(error, info) {}

  render() {
    return this.props.children;
  }
};

  • #8097 5fc5416 Thanks @dyc3! - Added the nursery rule useVueHyphenatedAttributes, which encourages using kebab case for attribute names, per the Vue style guide's recommendations.

    <!-- Invalid -->
<MyComponent myProp="value" />

<!-- Valid -->
<MyComponent my-prop="value" />

  • #8108 0f0a658 Thanks @Netail! - Added the nursery rule noSyncScripts. Prevent the usage of synchronous scripts.

    Invalid:

    <script src="https://third-party-script.js" />

    Valid:

    <script src="https://third-party-script.js" async />
<script src="https://third-party-script.js" defer />

  • #8098 1fdcaf0 Thanks @Jayllyz! - Added documentation URLs to rule descriptions in the JSON schema.

  • #8097 5fc5416 Thanks @dyc3! - Fixed an issue with the HTML parser where it would treat Vue directives with dynamic arguments as static arguments instead.

  • #7684 f4433b3 Thanks @vladimir-ivanov! - Changed noUnusedPrivateClassMembers to align more fully with meaningful reads.

    This rule now distinguishes more carefully between writes and reads of private class members.

    • A meaningful read is any access that affects program behavior.
    • For example, this.#x += 1 both reads and writes #x, so it counts as usage.
    • Pure writes without a read (e.g. this.#x = 1 with no getter) are no longer treated as usage.

    This change ensures that private members are only considered “used” when they are actually read in a way that influences execution.

    Invalid examples (previously valid)

    class UsedMember {
  set #x(value) {
    doSomething(value);
  }

  foo() {
    // This assignment does not actually read #x, because there is no getter.
    // Previously, this was considered a usage, but now it’s correctly flagged.
    this.#x = 1;
  }
}

    Valid example (Previously invalid)

    class Foo {
  #usedOnlyInWriteStatement = 5;

  method() {
    // This counts as a meaningful read because we both read and write the value.
    this.#usedOnlyInWriteStatement += 42;
  }
}

  • #7684 f4433b3 Thanks @vladimir-ivanov! - Improved detection of used private class members

    The analysis for private class members has been improved: now the tool only considers a private member “used” if it is actually referenced in the code.

    • Previously, some private members might have been reported as used even if they weren’t actually accessed.
    • With this change, only members that are truly read or called in the code are counted as used.
    • Members that are never accessed will now be correctly reported as unused.

    This makes reports about unused private members more accurate and helps you clean up truly unused code.

    Example (previously valid)

    type YesNo = "yes" | "no";

export class SampleYesNo {
  private yes: () => void;
  private no: () => void;
  private dontKnow: () => void; // <- will now report as unused

  on(action: YesNo): void {
    this[action]();
  }
}

  • #7681 b406db6 Thanks @kedevked! - Added the new lint rule, useSpread, ported from the ESLint rule prefer-spread.

    This rule enforces the use of the spread syntax (...) over Function.prototype.apply() when calling variadic functions, as spread syntax is generally more concise and idiomatic in modern JavaScript (ES2015+).

    The rule provides a safe fix.

    Invalid
    Math.max.apply(Math, args);
foo.apply(undefined, args);
obj.method.apply(obj, args);
    Valid
    Math.max(...args);
foo(...args);
obj.method(...args);

// Allowed: cases where the `this` binding is intentionally changed
foo.apply(otherObj, args);

  • #7287 aa55c8d Thanks @ToBinio! - Fixed #7205: The noDuplicateTestHooks rule now treats chained describe variants (e.g., describe.each/for/todo) as proper describe scopes, eliminating false positives.

    The following code will no longer be a false positive:

    describe("foo", () => {
  describe.for([])("baz", () => {
    beforeEach(() => {});
  });

  describe.todo("qux", () => {
    beforeEach(() => {});
  });

  describe.todo.each([])("baz", () => {
    beforeEach(() => {});
  });
});

  • #8013 0c0edd4 Thanks @Jayllyz! - Added the GraphQL nursery rule useUniqueGraphqlOperationName. This rule ensures that all GraphQL operations within a document have unique names.

    Invalid:

    query user {
  user {
    id
  }
}

query user {
  user {
    id
    email
  }
}

    Valid:

    query user {
  user {
    id
  }
}

query userWithEmail {
  user {
    id
    email
  }
}

  • #8084 c2983f9 Thanks @dyc3! - Fixed #8080: The HTML parser, when parsing Vue, can now properly handle Vue directives with no argument, modifiers, or initializer (e.g. v-else). It will no longer treat subsequent valid attributes as bogus.

    <p v-else class="flex">World</p>
<!-- Fixed: class now gets parsed as it's own attribute -->

  • #8104 041196b Thanks @Conaclos! - Fixed noInvalidUseBeforeDeclaration. The rule no longer reports a use of an ambient variable before its declarations. The rule also completely ignores TypeScript declaration files. The following code is no longer reported as invalid:

    CONSTANT;
declare const CONSTANT: number;

  • #8060 ba7b076 Thanks @dyc3! - Added the nursery rule useVueValidVBind, which enforces the validity of v-bind directives in Vue files.

    Invalid v-bind usages include:

    <Foo v-bind />
<!-- Missing argument -->
<Foo v-bind:foo />
<!-- Missing value -->
<Foo v-bind:foo.bar="baz" />
<!-- Invalid modifier -->

  • #8113 fb8e3e7 Thanks @Conaclos! - Fixed noInvalidUseBeforeDeclaration. The rule now reports invalid use of classes, enums, and TypeScript's import-equals before their declarations.

    The following code is now reported as invalid:

    new C();
class C {}

  • #8077 0170dcb Thanks @dyc3! - Added the rule useVueValidVElseIf to enforce valid v-else-if directives in Vue templates. This rule reports invalid v-else-if directives with missing conditional expressions or when not preceded by a v-if or v-else-if directive.

  • #8077 0170dcb Thanks @dyc3! - Added the rule useVueValidVElse to enforce valid v-else directives in Vue templates. This rule reports v-else directives that are not preceded by a v-if or v-else-if directive.

  • #8077 0170dcb Thanks @dyc3! - Added the rule useVueValidVHtml to enforce valid usage of the v-html directive in Vue templates. This rule reports v-html directives with missing expressions, unexpected arguments, or unexpected modifiers.

  • #8077 0170dcb Thanks @dyc3! - Added the rule useVueValidVIf to enforce valid v-if directives in Vue templates. It disallows arguments and modifiers, and ensures a value is provided.

  • #8077 0170dcb Thanks @dyc3! - Added the rule useVueValidVOn to enforce valid v-on directives in Vue templates. This rule reports invalid v-on / shorthand @ directives with missing event names, invalid modifiers, or missing handler expressions.

What's Changed
New Contributors

Full Changelog: https://github.com/biomejs/biome/compare/@biomejs/biome@2.3.5...@biomejs/biome@2.3.6

View originalPermalink
How 2.3.6 went
2.3.5

Biome CLI v2.3.5

Added 6
  • Support Svelte syntax `{@html}` with parsing and formatting capability
  • Support Svelte syntax `{@render}` with parsing and formatting capability
  • Support Svelte syntax `{@attach}` with parsing and formatting capability
  • Support Svelte syntax `{#key}` with parsing and formatting capability
  • Support Svelte syntax `{@const}` with parsing and formatting capability
  • Nursery rule `useArraySortCompare` to require Array#sort and Array#toSorted calls to always provide a compareFunction
Changed 5
  • CSS Parser with `tailwindDirectives` enabled now accepts at rules like `@media` and `@supports` in `@custom-variant` shorthand syntax
  • Biome keeps a blank line after the frontmatter section in Astro files
  • HTML parser now able to parse Vue directives for inspecting `<template>` section
  • Updated documentation and diagnostic for `lint/complexity/noBannedTypes` rule with more detailed description and error message
  • Corrected rule source references for better detection of rules in eslint configurations by `biome migrate eslint`
Fixed 2
  • Biome Language Server no longer enables project file watcher when no project rules are enabled
  • Support for advanced SVG props

From Biome

2.3.5
Patch Changes

  • #8023 96f3e77 Thanks @ematipico! - Added support Svelte syntax {@html}. Biome now is able to parse and format the Svelte syntax {@html}:

    -{@html   'div'}
+{@html 'div'}

    The contents of the expressions inside the {@html <expression>} aren't formatted yet.

  • #8058 5f68bcc Thanks @ematipico! - Fixed a bug where the Biome Language Server would enable its project file watcher even when no project rules were enabled.

    Now the watching of nested configuration files and nested ignore files is delegated to the editor, if their LSP spec supports it.

  • #8023 96f3e77 Thanks @ematipico! - Added support Svelte syntax {@render}. Biome now is able to parse and format the Svelte syntax {@render}:

    -{@render   sum(1, 2)   }
+{@render sum(1, 2)}

    The contents of the expressions inside the {@render <expression>} aren't formatted yet.

  • #8006 f0612a5 Thanks @Bertie690! - Updated documentation and diagnostic for lint/complexity/noBannedTypes. The rule should have a more detailed description and diagnostic error message.

  • #8039 da70d8b Thanks @PFiS1737! - Biome now keeps a blank line after the frontmatter section in Astro files.

  • #8042 b7efa6f Thanks @dyc3! - The CSS Parser, with tailwindDirectives enabled, will now accept at rules like @media and @supports in @custom-variant shorthand syntax.

  • #8064 3ff9d45 Thanks @dibashthapa! - Fixed #7967: Fixed the issue with support for advanced SVG props

  • #8023 96f3e77 Thanks @ematipico! - Added support Svelte syntax {@attach}. Biome now is able to parse and format the Svelte syntax {@attach}:

    -<div {@attach    myAttachment   }>...</div>
+<div {@attach myAttachment}>...</div>

    The contents of the expressions inside the {@attach <expression>} aren't formatted yet.

  • #8001 6e8a50e Thanks @ematipico! - Added support Svelte syntax {#key}. Biome now is able to parse and format the Svelte syntax {#key}:

    -{#key   expression} <div></div> {/key}
+{#key expression}
+  <div></div>
+{/key}

    The contents of the expressions inside the {#key <expression>} aren't formatted yet.

  • #8023 96f3e77 Thanks @ematipico! - Added support Svelte syntax {@const}. Biome now is able to parse and format the Svelte syntax {@const}:

    -{@const   name = value}
+{@const name = value}

    The contents of the expressions inside the {@const <expression>} aren't formatted yet.

  • #8044 8f77d4a Thanks @Netail! - Corrected rule source references. biome migrate eslint should do a bit better detecting rules in your eslint configurations.

  • #8065 1a2d1af Thanks @Netail! - Added the nursery rule useArraySortCompare. Require Array#sort and Array#toSorted calls to always provide a compareFunction.

    Invalid:

    const array = [];
array.sort();

    Valid:

    const array = [];
array.sort((a, b) => a - b);

  • #7673 a3a713d Thanks @dyc3! - The HTML parser is now able to parse vue directives. This enables us to write/port Vue lint rules that require inspecting the <template> section. However, this more complex parsing may result in parsing errors where there was none before. For those of you that have opted in to the experimental support (aka experimentalFullSupportEnabled), we greatly appreciate your help testing this out, and your bug reports.

  • #8031 fa6798a Thanks @ematipico! - Added support for the Svelte syntax {#if}{/if}. The Biome HTML parser is now able to parse and format the {#if}{/if} blocks:

    <!-- if / else-if / else -->
{#if porridge.temperature > 100}
-<p>too hot!</p>
+  <p>too hot!</p>
{:else if 80 > porridge.temperature}
-<p>too cold!</p>
+  <p>too cold!</p>
{:else if 100 > porridge.temperature}
-<p>too too cold!</p>
+  <p>too too cold!</p>
{:else}
-<p>just right!</p>
+  <p>just right!</p>
{/if}

  • #8041 beeb7bb Thanks @dyc3! - The CSS parser, with tailwindDirectives enabled, will now accept lists of selectors in @custom-variant shorthand syntax.

    @custom-variant cell (th:has(&), td:has(&));

  • #8028 c09e45c Thanks @fmajestic! - The GitLab reporter now outputs format errors.

  • #8037 78011b1 Thanks @PFiS1737! - indentScriptAndStyle no longer indents the frontmatter in Astro files.

  • #8009 6374b1f Thanks @tmcw! - Fixed an edge case in the useArrowFunction rule.

    The rule no longer emits diagnostics for or offers to fix functions that reference the arguments object, because that object is undefined for arrow functions.

    Valid example:

    // Valid: this function cannot be transformed into an arrow function because
// arguments is not defined for arrow functions.
const getFirstArg = function () {
  return arguments[0];
};
What's Changed
New Contributors

Full Changelog: https://github.com/biomejs/biome/compare/@biomejs/biome@2.3.4...@biomejs/biome@2.3.5

View originalPermalink
How 2.3.5 went
2.3.4

Biome CLI v2.3.4

Added 2
  • Added support for the Svelte syntax {@debug}
  • Added the nursery rule noContinue to disallow the usage of the continue statement
Changed 1
  • Refactored formatter to use strict Token element for better performance with optimizations for static, ASCII-only text
Fixed 4
  • Fixed a regression in Astro frontmatter parsing where comments inside quoted strings were incorrectly detected as actual comments
  • Rules' options are now properly merged with the inherited options from a shared configuration
  • Fixed detection and parsing of lang='tsx' and lang='jsx' languages inside .vue files when .experimentalFullSupportEnabled is enabled
  • Fixed CSS parser with tailwindDirectives enabled to parse @source inline(...)

From Biome

2.3.4
Patch Changes

  • #7989 4855c4a Thanks @alissonlauffer! - Fixed a regression in Astro frontmatter parsing where comments inside quoted strings were incorrectly detected as actual comments. This caused the parser to prematurely terminate frontmatter parsing when encountering strings like const test = "//";. For example, the following Astro frontmatter now parses correctly:

    ---
const test = "// not a real comment";
---

  • #7968 0b28f5f Thanks @denbezrukov! - Refactored formatter to use strict Token element for better performance. The new Token variant is optimized for static, ASCII-only text (keywords, operators, punctuation) with the following constraints:

    • ASCII only (no Unicode characters)
    • No newlines (\n, \r)
    • No tab characters (\t)

    This enables faster printing and fitting logic by using bulk string operations (push_str, len()) instead of character-by-character iteration with Unicode width calculations.

  • #7941 19b8280 Thanks @Conaclos! - Fixed #7943. Rules' options are now properly merged with the inherited options from a shared configuration.

    This means that you can now override a specific option from a rule without resetting the other options to their default.

    Given the following shared configuration:

    {
  "linter": {
    "rules": {
      "style": {
        "useNamingConvention": {
          "level": "on",
          "options": {
            "strictCase": false,
            "conventions": [
              {
                "selector": { "kind": "variable", "scope": "global" },
                "formats": ["CONSTANT_CASE"]
              }
            ]
          }
        }
      }
    }
  }
}

    And the user configuration that extends this shared configuration:

    {
  "extends": ["shared.json"],
  "linter": {
    "rules": {
      "style": {
        "useNamingConvention": {
          "level": "on",
          "options": { "strictCase": true }
        }
      }
    }
  }
}

    The obtained merged configuration is now as follows:

    {
  "extends": ["shared.json"],
  "linter": {
    "rules": {
      "style": {
        "useNamingConvention": {
          "level": "on",
          "options": {
            "strictCase": true,
            "conventions": [
              {
                "selector": { "kind": "variable", "scope": "global" },
                "formats": ["CONSTANT_CASE"]
              }
            ]
          }
        }
      }
    }
  }
}

  • #7969 425963d Thanks @ematipico! - Added support for the Svelte syntax {@debug}. The Biome HTML parser is now able to parse and format the blocks:

    -{@debug     foo,bar,    something}
+{@debug foo, bar, something}

  • #7986 3256f82 Thanks @lisiur! - Fixed #7981. Now Biome correctly detects and parses lang='tsx' and lang='jsx' languages when used inside in .vue files, when .experimentalFullSupportEnabled is enabled.

  • #7921 547c2da Thanks @dyc3! - Fixed #7854: The CSS parser, with tailwindDirectives enabled, will now parse @source inline("underline");.

  • #7856 c9e20c3 Thanks @Netail! - Added the nursery rule noContinue. Disallowing the usage of the continue statement, structured control flow statements such as if should be used instead.

    Invalid:

    let sum = 0,
  i;

for (i = 0; i < 10; i++) {
  if (i >= 5) {
    continue;
  }

  sum += i;
}

    Valid:

    let sum = 0,
  i;

for (i = 0; i < 10; i++) {
  if (i < 5) {
    sum += i;
  }
}
What's Changed
New Contributors

Full Changelog: https://github.com/biomejs/biome/compare/@biomejs/biome@2.3.3...@biomejs/biome@2.3.4

View originalPermalink
How 2.3.4 went
2.3.3

Biome CLI v2.3.3

Added 4
  • Added the rule noParametersOnlyUsedInRecursion that detects function parameters exclusively used in recursive calls
  • Added the new rule no-unknown-property from ESLint
  • YAML parser now parses document end token
  • Tailwind parser now parses negative candidates
Fixed 5
  • The Biome parser now correctly parses Astro frontmatter even when a triple fence is inside quotes
  • The HTML parser now correctly handles Unicode BOM (Byte Order Mark) characters at the beginning of HTML files
  • Biome now preserves component tag name casing in Svelte, Astro, and Vue files
  • The CSS parser with tailwindDirectives enabled now correctly handles @slot
  • The Biome Language Server no longer returns an internal error when the formatter is disabled in the configuration

From Biome

2.3.3
Patch Changes

  • #7907 57bd662 Thanks @ematipico! - Fixed #7839. Now the Biome parser correctly parses the Astro frontmatter even when a triple fence is inside quotes.

  • #7934 a35c496 Thanks @alissonlauffer! - Fixed #7919: The HTML parser now correctly handles Unicode BOM (Byte Order Mark) characters at the beginning of HTML files, ensuring proper parsing and tokenization.

  • #7869 c80361d Thanks @matanshavit! - Fixed #7864: Biome now preserves component tag name casing in Svelte, Astro, and Vue files.

  • #7926 69cecec Thanks @matanshavit! - Added the rule noParametersOnlyUsedInRecursion.

    This rule detects function parameters that are exclusively used in recursive calls and can be removed to simplify the function signature since they are effectively unused.

    function factorial(n, acc) {
  if (n === 0) return 1;
  return factorial(n - 1, acc); // acc is only used here
}

    Fixes #6484.

  • #7774 2509b91 Thanks @dibashthapa! - Fixed #7657: Added the new rule no-unknown-property from ESLint

  • #7918 7165d06 Thanks @dyc3! - Fixed #7913: The CSS parser, with tailwindDirectives enabled, will now correctly handle @slot.

  • #7959 ffae203 Thanks @siketyan! - Fixed the Biome Language Server so it no longer returns an internal error when the formatter is disabled in the configuration.

What's Changed
New Contributors

Full Changelog: https://github.com/biomejs/biome/compare/@biomejs/biome@2.3.2...@biomejs/biome@2.3.3

View originalPermalink
How 2.3.3 went
2.3.2

Biome CLI v2.3.2

Added 1
  • Add the nursery rule noIncrementDecrement, which disallows the usage of the unary operators ++ and --
Changed 1
  • Update Boa to v0.21.0
Fixed 4
  • Fix parsing of text expressions that contained nested curly brackets, which was breaking parsing in Astro and Svelte files
  • Fix noUselessStringConcat rule to no longer emit false positives for multi-line strings with leading + operators
  • Fix Biome Language Server panic when opening HTML-ish files with experimental full support enabled
  • Fix Grit plugin's code snippet matcher to properly match snippets with only one child

From Biome

2.3.2
Patch Changes

  • #7859 c600618 Thanks @Netail! - Added the nursery rule noIncrementDecrement, disallows the usage of the unary operators ++ and --.

  • #7901 0d17b05 Thanks @ematipico! - Fixed #7837, where Biome couldn't properly parse text expressions that contained nested curly brackets. This was breaking parsing in Astro and Svelte files.

  • #7874 e617d36 Thanks @Bertie690! - Fixed #7230: noUselessStringConcat no longer emits false positives for multi-line strings with leading + operators.

    Previously, the rule did not check for leading newlines on the + operator, emitting false positives if one occurred at the start of a line.
    Notably, formatting with operatorLinebreak="before" would move the + operators to the start of lines automatically, resulting in spurious errors whenever a multi-line string was used.

    Now, the rule correctly detects and ignores multi-line concatenations with leading operators as well, working regardless of the setting of operatorLinebreak.

    Example

    // The following code used to error if the `+` operators were at the start of lines (as opposed to the end).
// Now, the rule correctly recognizes this as a stylistic concatenation and ignores it.
const reallyLongStringThatShouldNotError =
  "Lorem ipsum dolor sit amet consectetur adipiscing elit." +
  "Quisque faucibus ex sapien vitae pellentesque sem placerat." +
  "In id cursus mi pretium tellus duis convallis." +
  "Tempus leo eu aenean sed diam urna tempor. Pulvinar vivamus fringilla";

  • #7786 33ffcd5 Thanks @daivinhtran! - Fixed #7601: Properly match Grit plugin's code snippet with only one child.

  • #7901 0d17b05 Thanks @ematipico! - Fixed #7837, where Biome Language Server panicked when opening HTML-ish files when the experimental full support is enabled.

What's Changed

Full Changelog: https://github.com/biomejs/biome/compare/@biomejs/biome@2.3.1...@biomejs/biome@2.3.2

View originalPermalink
How 2.3.2 went
2.3.1

Biome CLI v2.3.1

Fixed 8
  • The `ci` command now recognizes the new `--css-parse-*` arguments
  • The LSP method `workspace/didChangeWorkspaceFolders` now performs incremental updates instead of replacing the entire folder list
  • The CSS parser with `tailwindDirectives` enabled correctly parses `--*: initial;`
  • The HTML parser now accepts Svelte attribute shorthand syntax in `.svelte` files
  • The CSS parser with `tailwindDirectives` enabled now accepts `@plugin` options
  • The CSS parser with `tailwindDirectives` enabled correctly parses tailwind's source exclude syntax `@source not "foo.css";`
  • Biome now parses `<script>` tags as TypeScript when analysing `.astro` files
  • The HTML parser error message for disabled text expressions now correctly references the `html.parser.interpolation` option instead of the non-existent `html.parser.textExpression` option

From Biome

2.3.1
Patch Changes

  • #7840 72afdfa Thanks @ematipico! - Fixed #7838, which caused the new --css-parse-* arguments not being recognised by the ci command.

  • #7789 d5b416e Thanks @fronterior! - Fixed the LSP method workspace/didChangeWorkspaceFolders to perform incremental updates instead of replacing the entire folder list.

  • #7852 bd254c7 Thanks @dyc3! - Fixed #7843: The CSS parser, when tailwindDirectives is enabled, correctly parses --*: initial;.

  • #7872 0fe13fe Thanks @dyc3! - Fixed #7861: The HTML parser will now accept Svelte attribute shorthand syntax in .svelte files.

  • #7866 7b2600b Thanks @dyc3! - Fixed #7860: The css parser, with tailwindDirectives enabled, will now accept @plugin options.

  • #7853 fe90c78 Thanks @dyc3! - Fixed #7848: The css parser with tailwindDirectives enabled will now correctly parse tailwind's source exclude syntax: @source not "foo.css";

  • #7878 c9f7fe5 Thanks @ematipico! - Fixed #7857: Biome now parses <script> tags as TypeScript when analysing .astro files.

  • #7867 b42b718 Thanks @smorimoto! - Fixed incorrect option name in HTML parser error message.

    The error message for disabled text expressions incorrectly referred to the html.parser.textExpression option, which does not exist. Updated it to reference the correct html.parser.interpolation option.

What's Changed
New Contributors

Full Changelog: https://github.com/biomejs/biome/compare/@biomejs/biome@2.3.0...@biomejs/biome@2.3.1

View originalPermalink
How 2.3.1 went
2.3.0

Biome CLI v2.3.0

Added 5
  • Biome's resolver now supports `baseUrl` if specified in `tsconfig.json`
  • Added `ignore` option to `noUnknownAtRules` rule to prevent diagnostics for unknown at-rules matching provided patterns
  • Added `--css-parse-css-modules` CLI flag to control whether CSS Modules syntax is enabled
  • Added `--css-parse-tailwind-directives` CLI flag to control whether Tailwind CSS 4.0 directives and functions are enabled
  • Implemented the `indentScriptAndStyle` option for Vue and Svelte files to indent content within `<script>` and `<style>` tags
Changed 3
  • Enhanced the `init` command to detect and automatically configure `.gitignore` or `.ignore` files and exclude known generated folders like `dist/`
  • Rules in a domain are no longer enabled automatically by installed dependencies unless the rule is recommended
  • Updated formatting of `.svelte` and `.vue` files so indentation of JavaScript blocks matches Prettier's
Deprecated 1
  • Deprecated the option `files.experimentalScannerIgnores` in favour of force-ignore syntax in `files.includes`

From Biome

2.3.0
Minor Changes

  • #7263 a3e3369 Thanks @arendjr! - Biome's resolver now supports baseUrl if specified in tsconfig.json.

    Example

    Given the following file structure:

    tsconfig.json

    {
  "compilerOptions": {
    "baseUrl": "./src"
  }
}

    src/foo.ts

    export function foo() {}

    In this scenario, import { foo } from "foo"; should work regardless of the location of the file containing the import statement.

    Fixes #6432.

  • #7745 6fcbc07 Thanks @dyc3! - Added ignore option to noUnknownAtRules. If an unknown at-rule matches any of the items provided in ignore, a diagnostic won't be emitted.

  • #7753 63cb7ff Thanks @ematipico! - Enhanced the init command. The init command now checks if the existing project contains known ignore files and known generated folders.

    If Biome finds .gitignore or .ignore files, it will add the following configuration to biome.json:

    {
+  "vcs": {
+    "enabled": true,
+    "clientKind": "git",
+    "useIgnoreFile": true
+  }
}

    If Biome finds a dist/ folder, it will exclude it automatically using the double-exclude syntax:

    {
+  "files": {
+    "includes": ["**", "!!**/dist"]
+  }
}

  • #7548 85d3a3a Thanks @siketyan! - The rules in a domain are no longer enabled automatically by the installed dependencies unless the rule is recommended.

  • #7723 d3aac63 Thanks @ematipico! - Added --css-parse-css-modules CLI flag to control whether CSS Modules syntax is enabled.

    You can now enable or disable CSS Modules parsing directly from the command line:

    biome check --css-parse-css-modules=true file.module.css
biome format --css-parse-css-modules=true file.module.css
biome lint --css-parse-css-modules=true file.module.css
biome ci --css-parse-css-modules=true file.module.css

  • #7723 d3aac63 Thanks @ematipico! - Added --css-parse-tailwind-directives CLI flag to control whether Tailwind CSS 4.0 directives and functions are enabled.

    You can now enable or disable Tailwind CSS 4.0 directive parsing directly from the command line:

    biome check --css-parse-tailwind-directives=true file.css
biome format --css-parse-tailwind-directives=true file.css
biome lint --css-parse-tailwind-directives=true file.css
biome ci --css-parse-tailwind-directives=true file.css

  • #7330 272632f Thanks @ematipico! - Updated the formatting of .svelte and .vue files. Now the indentation of the JavaScript blocks matches Prettier's:

    <script>
- import Component from "./Component"
+   import Component from "./Component"
</script>

  • #7333 de0d2d6 Thanks @dyc3! - Implemented the indentScriptAndStyle option for vue and svelte files, with the default set to false to match Prettier's vueIndentScriptAndStyle option. When enabled, this option indents the content within <script> and <style> tags to align with the surrounding HTML structure.

    It can be enabled with this configuration:

    {
  "html": {
    "formatter": {
      "indentScriptAndStyle": true
    }
  }
}

    Which will format this code to:

    <script>
import Component from "./Component.vue";
</script>

  • #7359 ebbddc4 Thanks @arendjr! - Deprecated the option files.experimentalScannerIgnores in favour of force-ignore syntax in files.includes.

    files.includes supports ignoring files by prefixing globs with an exclamation mark (!). With this change, it also supports force-ignoring globs by prefixing them with a double exclamation mark (!!).

    The effect of force-ignoring is that the scanner will not index files matching the glob, even in project mode, even if those files are imported by other files, and even if they are files that receive special treatment by Biome, such as nested biome.json files.

    Example

    Let's take the following configuration:

    {
  "files": {
    "includes": [
      "**",
      "!**/generated",
      "!!**/dist",
      "fixtures/example/dist/*.js"
    ]
  },
  "linter": {
    "domains": {
      "project": "all"
    }
  }
}

    This configuration achieves the following:

    • Because the project domain is enabled, all supported files in the project are indexed and processed by the linter, except:
    • Files inside a generated folder are not processed by the linter, but they will get indexed if a file outside a generated folder imports them.
    • Files inside a dist folder are never indexed nor processed, not even if they are imported for any purpose, except:
    • When the dist folder is inside fixtures/example/, its .js files do get both indexed and processed.

    In general, we now recommend using the force-ignore syntax for any folders that contain output files, such as build/ and dist/. For such folders, it is highly unlikely that indexing has any useful benefits. For folders containing generated files, you may wish to use the regular ignore syntax so that type information can still be extracted from the files.

    experimentalScannerIgnores will continue to work for now, but you'll see a deprecation warning if you still use it.

    Run the biome migrate --write command to automatically update the configuration file.

  • #7698 3b6f5e3 Thanks @ematipico! - Added a new reporter named rdjson. This reporter prints diagnostics following the RDJSON format:

    The following command:

    biome check --reporter=rdjson

    Will emit diagnostics in the following format:

    {
  "source": {
    "name": "Biome",
    "url": "https://biomejs.dev"
  },
  "diagnostics": [
    {
      "code": {
        "url": "https://biomejs.dev/linter/rules/no-unused-imports",
        "value": "lint/correctness/noUnusedImports"
      },
      "location": {
        "path": "index.ts",
        "range": {
          "end": {
            "column": 11,
            "line": 0
          },
          "start": {
            "column": 7,
            "line": 0
          }
        }
      },
      "message": "This import is unused."
    },
    {
      "code": {
        "url": "https://biomejs.dev/linter/rules/no-unused-imports",
        "value": "lint/correctness/noUnusedImports"
      },
      "location": {
        "path": "index.ts",
        "range": {
          "end": {
            "column": 10,
            "line": 1
          },
          "start": {
            "column": 9,
            "line": 1
          }
        }
      },
      "message": "Several of these imports are unused."
    }
  ]
}

  • #7719 188a767 Thanks @cadunass! - The formatWithErrors option can now be set via CLI using the --format-with-errors flag.

    This flag was previously only available in the configuration file. It allows formatting to proceed on files with syntax errors, which is useful during development when you want to auto-format code while fixing syntax issues.

    Example
    biome format --format-with-errors=true --write file.js

  • #7723 d3aac63 Thanks @ematipico! - Added --json-parse-allow-comments CLI flag to control whether comments are allowed in JSON files.

    You can now enable or disable comment parsing in JSON files directly from the command line:

    biome check --json-parse-allow-comments=true file.json
biome format --json-parse-allow-comments=true file.json
biome lint --json-parse-allow-comments=true file.json
biome ci --json-parse-allow-comments=true file.json

  • #7723 d3aac63 Thanks @ematipico! - Added --json-parse-allow-trailing-commas CLI flag to control whether trailing commas are allowed in JSON files.

    You can now enable or disable trailing comma parsing in JSON files directly from the command line:

    biome check --json-parse-allow-trailing-commas=true file.json
biome format --json-parse-allow-trailing-commas=true file.json
biome lint --json-parse-allow-trailing-commas=true file.json
biome ci --json-parse-allow-trailing-commas=true file.json

  • #7758 cea002f Thanks @ematipico! - Promoted new lint rules:

    • Promoted noNonNullAssertedOptionalChain to the suspicious group
    • Promoted useReactFunctionComponents to the style group
    • Promoted useImageSize to the correctness group
    • Promoted useConsistentTypeDefinitions to the style group
    • Promoted useQwikClasslist to the correctness group
    • Promoted noSecrets to the security group

    Removed the lint rule useAnchorHref, because its use case is covered by useValidAnchor.

  • #6356 296627d Thanks @wrick17! - Added the new checkstyle reporter. When --reporter=checkstyle is passed to the CLI, Biome will emit diagnostics for Checkstyle format:

    <?xml version="1.0" encoding="utf-8"?>
<checkstyle version="4.3">
  <file name="index.ts">
    <error line="1" column="8" severity="warning" message="This import is unused." source="lint/correctness/noUnusedImports" />
    <error line="2" column="10" severity="warning" message="Several of these imports are unused." source="lint/correctness/noUnusedImports" />
    <error line="8" column="5" severity="warning" message="This variable f is unused." source="lint/correctness/noUnusedVariables" />
    <error line="9" column="7" severity="warning" message="This variable f is unused." source="lint/correctness/noUnusedVariables" />
    <error line="1" column="1" severity="error" message="The imports and exports are not sorted." source="assist/source/organizeImports" />
    <error line="4" column="3" severity="error" message="Using == may be unsafe if you are relying on type coercion." source="lint/suspicious/noDoubleEquals" />
    <error line="6" column="1" severity="error" message="This is an unexpected use of the debugger statement." source="lint/suspicious/noDebugger" />
    <error line="8" column="5" severity="error" message="This variable implicitly has the any type." source="lint/suspicious/noImplicitAnyLet" />
    <error line="9" column="7" severity="error" message="This variable implicitly has the any type." source="lint/suspicious/noImplicitAnyLet" />
    <error line="2" column="10" severity="error" message="Shouldn&apos;t redeclare &apos;z&apos;. Consider to delete it or rename it." source="lint/suspicious/noRedeclare" />
    <error line="9" column="7" severity="error" message="Shouldn&apos;t redeclare &apos;f&apos;. Consider to delete it or rename it." source="lint/suspicious/noRedeclare" />
    <error line="0" column="0" severity="error" message="Formatter would have printed the following content:" source="format" />
  </file>
  <file name="main.ts">
    <error line="1" column="8" severity="warning" message="This import is unused." source="lint/correctness/noUnusedImports" />
    <error line="2" column="10" severity="warning" message="Several of these imports are unused." source="lint/correctness/noUnusedImports" />
    <error line="8" column="5" severity="warning" message="This variable f is unused." source="lint/correctness/noUnusedVariables" />
    <error line="9" column="7" severity="warning" message="This variable f is unused." source="lint/correctness/noUnusedVariables" />
    <error line="1" column="1" severity="error" message="The imports and exports are not sorted." source="assist/source/organizeImports" />
    <error line="4" column="3" severity="error" message="Using == may be unsafe if you are relying on type coercion." source="lint/suspicious/noDoubleEquals" />
    <error line="6" column="1" severity="error" message="This is an unexpected use of the debugger statement." source="lint/suspicious/noDebugger" />
    <error line="8" column="5" severity="error" message="This variable implicitly has the any type." source="lint/suspicious/noImplicitAnyLet" />
    <error line="9" column="7" severity="error" message="This variable implicitly has the any type." source="lint/suspicious/noImplicitAnyLet" />
    <error line="2" column="10" severity="error" message="Shouldn&apos;t redeclare &apos;z&apos;. Consider to delete it or rename it." source="lint/suspicious/noRedeclare" />
    <error line="9" column="7" severity="error" message="Shouldn&apos;t redeclare &apos;f&apos;. Consider to delete it or rename it." source="lint/suspicious/noRedeclare" />
    <error line="0" column="0" severity="error" message="Formatter would have printed the following content:" source="format" />
  </file>
</checkstyle>

  • #7488 b13e524 Thanks @kpapa05! - Added "@rbxts/react" as an alias for "react" for handling the reactClassic jsxRuntime.

  • #7536 0bccd34 Thanks @TheAlexLichter! - Added .oxlintrc.json to well-known files.

  • #7548 85d3a3a Thanks @siketyan! - The following rules are now a part of the react domain, and they won't be enabled automatically unless you enabled the domain, or Biome detects react as a dependency of your closest package.json:

  • #7667 480909a Thanks @ematipico! - Added the ability to show severity Information diagnostics in reporter outputs.

    If one or more rules are triggered, and they are configured to emit an Information diagnostic, now they're counted in the final output:

    Checked 1 file in <TIME>. No fixes applied.
Found 1 info.

  • #7702 28e8860 Thanks @ematipico! - Added linting and assist support for .html files, with addition of two new configurations:

    • html.linter.enabled
    • html.assist.enabled

    The HTML linter, in this release, only contains the rule noHeaderScope. More rules will be released in the upcoming releases.

  • #7164 f66b0c5 Thanks @dyc3! - Added a new CSS parser option tailwindDirectives. Enabling this option will allow all of Tailwind v4's syntax additions to be parsed and formatted by Biome.

    You can enable this by setting css.parser.tailwindDirectives to true in your Biome configuration.

    {
  "css": {
    "parser": {
      "tailwindDirectives": true
    }
  }
}

  • #7669 6ed4d16 Thanks @barklund! - React 19.2 support is now supported in Biome:

  • #7702 28e8860 Thanks @ematipico! - Added experimental full support for HTML, Vue, Svelte and Astro files. In this release, the HTML parser has been enhanced, and it's now able to parse .vue, .svelte and .astro files.

    This means that now Biome is able to lint and format the JavaScript (TypeScript), HTML and CSS code that is contained in these files.

    Now that the main architecture is stable and working, in the upcoming patches and minors we will also fix possible inaccuracies and edge cases coming from existing lint rules, such as noUnusedVariables inside <script> blocks or frontmatter.

    The support is considered experimental because there might be cases that aren't fine-parsed yet, hence causing possible inaccuracies when it comes to formatting and linting.

  • #7599 09445c8 Thanks @anaisbetts! - #### lineEnding has a new option auto

    The option lineEnding now has a variant called auto to match the operating system's expected line-ending style: on Windows, this will be CRLF (\r\n), and on macOS / Linux, this will be LF (\n).

    This allows for cross-platform projects that use Biome not to have to force one option or the other, which aligns better with Git's default behavior on these platforms.

    Example usage:

    {
  "formatter": {
    "lineEnding": "auto"
  }
}

    biome format --line-ending auto

  • #7392 e4feb8e Thanks @ematipico! - Added new capabilities to the CLI arguments --skip and --only, available to the biome lint command.

    --skip and --only can now accept domain names; when provided, Biome will run or skip all the rules that belong to a certain domain.

    For example, the following command will only run the rules that belong to the next domain:

    biome lint --only=next

    Another example, the following command will skip the rules that belong to the project domain:

    biome lint --skip=project

  • #7702 28e8860 Thanks @ematipico! - Added a new option called html.interpolation. This option enables the parsing of text expressions (or interpolation) in HTML files.

    The following file.html will be correctly formatted:

    <!-- file.html -->
<div>
  Hello {{ name }}!
  <p>Your balance is: {{ account.balance }}</p>
  <button>{{ isLoading ? "Loading..." : "Submit" }}</button>
</div>

    To note that html.interpolation only parses text expressions that are delimited by double curly braces ({{ }}). The content of expressions is parsed as normal text.

Patch Changes

  • #7712 fcc9b42 Thanks @minht11! - Added new rule useVueDefineMacrosOrder which allows enforcing specific order for Vue compiler macros.

    In this example, the rule will suggest moving defineProps before defineEmits:

    <script lang="ts" setup>
const emit = defineEmits(["update"]);
const props = defineProps<{ name: string }>();
</script>

  • #7698 3b6f5e3 Thanks @ematipico! - Fixed an issue where the JUnit reporter returned a zero-based location. Now the location returned is one-based.

  • #7819 ef45056 Thanks @ematipico! - Fixed #7788. Removes some error logging that were emitted when loading possible configuration files.

  • #7593 e51dd55 Thanks @arendjr! - Fixed an issue with the files.maxSize setting. Previously the setting would always be looked up in the root settings, even in monorepos where a closer biome.json is available. It now correctly uses the nearest configuration.

  • #7825 ad55b35 Thanks @Conaclos! - Fixed #7798. useNamingConvention no longer panics when it encounters a name that consists of a single dollar sign $ that doesn't match a custom convention.

  • #7764 93be2ab Thanks @gaauwe! - Fixed #6589: Biome now properly loads extension settings before loading the configuration file when opening a text document in the LSP server.

What's Changed
New Contributors

Full Changelog: https://github.com/biomejs/biome/compare/@biomejs/biome@2.2.7...@biomejs/biome@2.3.0

View originalPermalink
How 2.3.0 went
2.2.7

Biome CLI v2.2.7

Added 1
  • Add the nursery rule noEmptySource, disallowing meaningless js, css, json & graphql files to prevent codebase clutter
Changed 2
  • Increase the maximum line limit for noExcessiveLinesPerFunction from 255 to 65,535 to better support large JSX/front-end components
  • Improve the diagnostic message of the rule noDuplicateTestHooks
Fixed 3
  • Fix noRedundantUseStrict to keep leading trivia
  • Detect infinite loops caused by conflicting rule fixes
  • Unload plugin cache when project closes
Security 2
  • Update dependency happy-dom to v20
  • Update dependency vite to v7.1.11

From Biome

2.2.7
Patch Changes
What's Changed
New Contributors

Full Changelog: https://github.com/biomejs/biome/compare/@biomejs/biome@2.2.6...@biomejs/biome@2.2.7

View originalPermalink
How 2.2.7 went
2.2.6

Biome CLI v2.2.6

Added 3
  • Add the useQwikMethodUsage lint rule for the Qwik domain to validate Qwik hook usage
  • Add the useQwikValidLexicalScope rule to the Qwik domain to check that variables and functions are declared in the correct place
  • Add the useDeprecatedDate rule which makes a deprecation date required for the GraphQL @deprecated directive
Fixed 6
  • Fix NoUnknownPseudoClass rule to no longer report local pseudo-classes when CSS Modules are used
  • Fix useImportExtensions rule to no longer emit diagnostics on valid import paths that end with a query or hash
  • Fix useExhaustiveDependencies rule to correctly add an object dependency when its method is called within the closure
  • Fix noUselessEscapeInString rule to no longer report ${ escape in template literals
  • Add support for parsing the CSS :state() pseudo-class
  • Fix useMaxParams rule to highlight parameter lists instead of entire function bodies

From Biome

2.2.6
Patch Changes

  • #7071 a8e7301 Thanks @ptkagori! - Added the useQwikMethodUsage lint rule for the Qwik domain.

    This rule validates Qwik hook usage. Identifiers matching useXxx must be called only within serialisable reactive contexts (for example, inside component$, route loaders/actions, or within other Qwik hooks), preventing common Qwik antipatterns.

    Invalid:

    // Top-level hook call is invalid.
const state = useStore({ count: 0 });

function helper() {
  // Calling a hook in a non-reactive function is invalid.
  const loc = useLocation();
}

    Valid:

    component$(() => {
  const state = useStore({ count: 0 }); // OK inside component$.
  return <div>{state.count}</div>;
});

const handler = $(() => {
  const loc = useLocation(); // OK inside a $-wrapped closure.
  console.log(loc.params);
});

  • #7685 52071f5 Thanks @denbezrukov! - Fixed #6981: The NoUnknownPseudoClass rule no longer reports local pseudo-classes when CSS Modules are used.

  • #7640 899f7b2 Thanks @arendjr! - Fixed #7638: useImportExtensions no longer emits diagnostics on valid import paths that end with a query or hash.

    Example
    // This no longer warns if `index.css` exists:
import style from "../theme/index.css?inline";

  • #7071 a8e7301 Thanks @ptkagori! - Added the useQwikValidLexicalScope rule to the Qwik domain.

    This rule helps you avoid common bugs in Qwik components by checking that your variables and functions are declared in the correct place.

    Invalid:

    // Invalid: state defined outside the component's lexical scope.
let state = useStore({ count: 0 });
const Component = component$(() => {
  return (
    <button onClick$={() => state.count++}>Invalid: {state.count}</button>
  );
});

    Valid:

    // Valid: state initialised within the component's lexical scope and captured by the event.
const Component = component$(() => {
  const state = useStore({ count: 0 });
  return <button onClick$={() => state.count++}>Valid: {state.count}</button>;
});

  • #7620 5beb1ee Thanks @Netail! - Added the rule useDeprecatedDate, which makes a deprecation date required for the graphql @deprecated directive.

    Invalid
    query {
  member @deprecated(reason: "Use `members` instead") {
    id
  }
}
    Valid
    query {
  member
    @deprecated(reason: "Use `members` instead", deletionDate: "2099-12-25") {
    id
  }
}

  • #7709 d6da4d5 Thanks @siketyan! - Fixed #7704: The useExhaustiveDependencies rule now correctly adds an object dependency when its method is called within the closure.

    For example:

    function Component(props) {
  useEffect(() => {
    props.foo();
  }, []);
}

    will now be fixed to:

    function Component(props) {
  useEffect(() => {
    props.foo();
  }, [props]);
}

  • #7624 309ae41 Thanks @lucasweng! - Fixed #7595: noUselessEscapeInString no longer reports $\{ escape in template literals.

  • #7665 29e4229 Thanks @ryan-m-walker! - Fixed #7619: Added support for parsing the CSS :state() pseudo-class.

    custom-selector:state(checked) {
}

  • #7608 41df59b Thanks @ritoban23! - Fixed #7604: the useMaxParams rule now highlights parameter lists instead of entire function bodies. This provides more precise error highlighting. Previously, the entire function was highlighted; now only the parameter list is highlighted, such as (a, b, c, d, e, f, g, h).

  • #7643 459a6ac Thanks @daivinhtran! - Fixed #7580: Include plugin in summary report

What's Changed
New Contributors

Full Changelog: https://github.com/biomejs/biome/compare/@biomejs/biome@2.2.5...@biomejs/biome@2.2.6

View originalPermalink
How 2.2.6 went
2.2.5

Biome CLI v2.2.5

Added 3
  • Add new lint rule noReactForwardRef to detect usages of forwardRef that is deprecated in React 19
  • Add new nursery rule noDeprecatedImports to flag imports of deprecated symbols
  • Add style and requireForObjectLiteral options to useConsistentArrowReturn rule
Fixed 3
  • useImportExtensions rule now works correctly with aliased paths
  • noUselessFragments rule now aligns with ESLint by not reporting fragments containing only text
  • useExhaustiveDependencies rule now correctly adds dependencies captured in shorthand object members

From Biome

2.2.5
Patch Changes

  • #7597 5c3d542 Thanks @arendjr! - Fixed #6432: useImportExtensions now works correctly with aliased paths.

  • #7269 f18dac1 Thanks @CDGardner! - Fixed #6648, where Biome's noUselessFragments contained inconsistencies with ESLint for fragments only containing text.

    Previously, Biome would report that fragments with only text were unnecessary under the noUselessFragments rule. Further analysis of ESLint's behavior towards these cases revealed that text-only fragments (<>A</a>, <React.Fragment>B</React.Fragment>, <RenamedFragment>B</RenamedFragment>) would not have noUselessFragments emitted for them.

    On the Biome side, instances such as these would emit noUselessFragments, and applying the suggested fix would turn the text content into a proper JS string.

    // Ended up as: - const t = "Text"
const t = <>Text</>

// Ended up as: - const e = t ? "Option A" : "Option B"
const e = t ? <>Option A</> : <>Option B</>

/* Ended up as:
  function someFunc() {
    return "Content desired to be a multi-line block of text."
  }
*/
function someFunc() {
  return <>
    Content desired to be a multi-line
    block of text.
  <>
}

    The proposed update was to align Biome's reaction to this rule with ESLint's; the aforementioned examples will now be supported from Biome's perspective, thus valid use of fragments.

    // These instances are now valid and won't be called out by noUselessFragments.

const t = <>Text</>
const e = t ? <>Option A</> : <>Option B</>

function someFunc() {
  return <>
    Content desired to be a multi-line
    block of text.
  <>
}

  • #7498 002cded Thanks @siketyan! - Fixed #6893: The useExhaustiveDependencies rule now correctly adds a dependency that is captured in a shorthand object member. For example:

    useEffect(() => {
  console.log({ firstId, secondId });
}, []);

    is now correctly fixed to:

    useEffect(() => {
  console.log({ firstId, secondId });
}, [firstId, secondId]);

  • #7509 1b61631 Thanks @siketyan! - Added a new lint rule noReactForwardRef, which detects usages of forwardRef that is no longer needed and deprecated in React 19.

    For example:

    export const Component = forwardRef(function Component(props, ref) {
  return <div ref={ref} />;
});

    will be fixed to:

    export const Component = function Component({ ref, ...props }) {
  return <div ref={ref} />;
};

    Note that the rule provides an unsafe fix, which may break the code. Don't forget to review the code after applying the fix.

  • #7520 3f06e19 Thanks @arendjr! - Added new nursery rule noDeprecatedImports to flag imports of deprecated symbols.

    Invalid example
    // foo.js
import { oldUtility } from "./utils.js";

    // utils.js
/**
 * @deprecated
 */
export function oldUtility() {}
    Valid examples
    // foo.js
import { newUtility, oldUtility } from "./utils.js";

    // utils.js
export function newUtility() {}

// @deprecated (this is not a JSDoc comment)
export function oldUtility() {}

  • #7457 9637f93 Thanks @kedevked! - Added style and requireForObjectLiteral options to the lint rule useConsistentArrowReturn.

    This rule enforces a consistent return style for arrow functions. It can be configured with the following options:

    • style: (default: asNeeded)
      • always: enforces that arrow functions always have a block body.
      • never: enforces that arrow functions never have a block body, when possible.
      • asNeeded: enforces that arrow functions have a block body only when necessary (e.g. for object literals).
    style: "always"

    Invalid:

    const f = () => 1;

    Valid:

    const f = () => {
  return 1;
};
    style: "never"

    Invalid:

    const f = () => {
  return 1;
};

    Valid:

    const f = () => 1;
    style: "asNeeded"

    Invalid:

    const f = () => {
  return 1;
};

    Valid:

    const f = () => 1;
    style: "asNeeded" and requireForObjectLiteral: true

    Valid:

    const f = () => {
  return { a: 1 };
};

  • #7510 527cec2 Thanks @rriski! - Implements #7339. GritQL patterns can now use native Biome AST nodes using their PascalCase names, in addition to the existing TreeSitter-compatible snake_case names.

    engine biome(1.0)
language js(typescript,jsx)

or {
  // TreeSitter-compatible pattern
  if_statement(),

  // Native Biome AST node pattern
  JsIfStatement()
} as $stmt where {
  register_diagnostic(
    span=$stmt,
    message="Found an if statement"
  )
}

  • #7574 47907e7 Thanks @kedevked! - Fixed 7574. The diagnostic message for the rule useSolidForComponent now correctly emphasizes <For /> and provides a working hyperlink to the Solid documentation.

  • #7497 bd70f40 Thanks @siketyan! - Fixed #7320: The useConsistentCurlyBraces rule now correctly detects a string literal including " inside a JSX attribute value.

  • #7522 1af9931 Thanks @Netail! - Added extra references to external rules to improve migration for the following rules: noUselessFragments & noNestedComponentDefinitions

  • #7597 5c3d542 Thanks @arendjr! - Fixed an issue where package.json manifests would not be correctly discovered when evaluating files in the same directory.

  • #7565 38d2098 Thanks @siketyan! - The resolver can now correctly resolve .ts, .tsx, .d.ts, .js files by .js extension if exists, based on the file extension substitution in TypeScript.

    For example, the linter can now detect the floating promise in the following situation, if you have enabled the noFloatingPromises rule.

    foo.ts

    export async function doSomething(): Promise<void> {}

    bar.ts

    import { doSomething } from "./foo.js"; // doesn't exist actually, but it is resolved to `foo.ts`

doSomething(); // floating promise!

  • #7542 cadad2c Thanks @mdevils! - Added the rule noVueDuplicateKeys, which prevents duplicate keys in Vue component definitions.

    This rule prevents the use of duplicate keys across different Vue component options such as props, data, computed, methods, and setup. Even if keys don't conflict in the script tag, they may cause issues in the template since Vue allows direct access to these keys.

    Invalid examples
    <script>
export default {
  props: ["foo"],
  data() {
    return {
      foo: "bar",
    };
  },
};
</script>

    <script>
export default {
  data() {
    return {
      message: "hello",
    };
  },
  methods: {
    message() {
      console.log("duplicate key");
    },
  },
};
</script>

    <script>
export default {
  computed: {
    count() {
      return this.value * 2;
    },
  },
  methods: {
    count() {
      this.value++;
    },
  },
};
</script>
    Valid examples
    <script>
export default {
  props: ["foo"],
  data() {
    return {
      bar: "baz",
    };
  },
  methods: {
    handleClick() {
      console.log("unique key");
    },
  },
};
</script>

    <script>
export default {
  computed: {
    displayMessage() {
      return this.message.toUpperCase();
    },
  },
  methods: {
    clearMessage() {
      this.message = "";
    },
  },
};
</script>

  • #7546 a683acc Thanks @siketyan! - Internal data for Unicode strings have been updated to Unicode 17.0.

  • #7497 bd70f40 Thanks @siketyan! - Fixed #7256: The useConsistentCurlyBraces rule now correctly ignores a string literal with braces that contains only whitespaces. Previously, literals that contains single whitespace were only allowed.

  • #7565 38d2098 Thanks @siketyan! - The useImportExtensions rule now correctly detects imports with an invalid extension. For example, importing .ts file with .js extension is flagged by default. If you are using TypeScript with neither the allowImportingTsExtensions option nor the rewriteRelativeImportExtensions option, it's recommended to turn on the forceJsExtensions option of the rule.

  • #7581 8653921 Thanks @lucasweng! - Fixed #7470: solved a false positive for noDuplicateProperties. Previously, declarations in @container and @starting-style at-rules were incorrectly flagged as duplicates of identical declarations at the root selector.

    For example, the linter no longer flags the display declaration in @container or the opacity declaration in @starting-style.

    a {
  display: block;
  @container (min-width: 600px) {
    display: none;
  }
}

[popover]:popover-open {
  opacity: 1;
  @starting-style {
    opacity: 0;
  }
}

  • #7529 fea905f Thanks @qraqras! - Fixed #7517: the useOptionalChain rule no longer suggests changes for typeof checks on global objects.

    // ok
typeof window !== "undefined" && window.location;

  • #7476 c015765 Thanks @ematipico! - Fixed a bug where the suppression action for noPositiveTabindex didn't place the suppression comment in the correct position.

  • #7511 a0039fd Thanks @arendjr! - Added nursery rule noUnusedExpressions to flag expressions used as a statement that is neither an assignment nor a function call.

    Invalid examples
    f; // intended to call `f()` instead

    function foo() {
  0; // intended to `return 0` instead
}
    Valid examples
    f();

    function foo() {
  return 0;
}

  • #7564 40e515f Thanks @turbocrime! - Fixed #6617: improved useIterableCallbackReturn to correctly handle arrow functions with a single-expression void body.

    Now the following code doesn't trigger the rule anymore:

    [].forEach(() => void null);
What's Changed
New Contributors

Full Changelog: https://github.com/biomejs/biome/compare/@biomejs/biome@2.2.4...@biomejs/biome@2.2.5

View originalPermalink
How 2.2.5 went
2.2.4

Biome CLI v2.2.4

Added 2
  • Added the new nursery lint rule noJsxLiterals, which disallows the use of string literals inside JSX
  • Added the new nursery rule noDuplicateDependencies, which verifies that no dependencies are duplicated between bundledDependencies, bundleDependencies, dependencies, devDependencies, overrides, optionalDependencies, and peerDependencies sections
Changed 2
  • Greatly improved performance of noImportCycles by eliminating allocations
  • Improved performance of noPrivateImports by eliminating allocations
Fixed 7
  • Aliases specified in package.json's imports section now support having multiple targets as part of an array
  • The GritQL $... spread metavariable now correctly matches members in object literals, aligning its behavior with arrays and function calls
  • Type inference now recognises index signatures and their accesses when they are being indexed as a string
  • The useOptionalChain rule now recognizes optional chaining using typeof
  • noUnusedPrivateClassMembers no longer reports TypeScript private members as unused if the rule encounters a computed access on this
  • The useHookAtTopLevel rule no longer reports excessive diagnostics for nested hook calls
  • The Biome Language Server no longer has a regression where opening an editor with a file already open wouldn't load the project settings correctly

From Biome

2.2.4
Patch Changes

  • #7453 aa8cea3 Thanks @arendjr! - Fixed #7242: Aliases specified in package.json's imports section now support having multiple targets as part of an array.

  • #7454 ac17183 Thanks @arendjr! - Greatly improved performance of noImportCycles by eliminating allocations.

    In one repository, the total runtime of Biome with only noImportCycles enabled went from ~23s down to ~4s.

  • #7447 7139aad Thanks @rriski! - Fixes #7446. The GritQL $... spread metavariable now correctly matches members in object literals, aligning its behavior with arrays and function calls.

  • #6710 98cf9af Thanks @arendjr! - Fixed #4723: Type inference now recognises index signatures and their accesses when they are being indexed as a string.

    Example
    type BagOfPromises = {
  // This is an index signature definition. It declares that instances of type
  // `BagOfPromises` can be indexed using arbitrary strings.
  [property: string]: Promise<void>;
};

let bag: BagOfPromises = {};
// Because `bag.iAmAPromise` is equivalent to `bag["iAmAPromise"]`, this is
// considered an access to the string index, and a Promise is expected.
bag.iAmAPromise;

  • #7415 d042f18 Thanks @qraqras! - Fixed #7212, now the useOptionalChain rule recognizes optional chaining using typeof (e.g., typeof foo !== 'undefined' && foo.bar).

  • #7419 576baf4 Thanks @Conaclos! - Fixed #7323. noUnusedPrivateClassMembers no longer reports as unused TypeScript private members if the rule encounters a computed access on this.

    In the following example, member as previously reported as unused. It is no longer reported.

    class TsBioo {
  private member: number;

  set_with_name(name: string, value: number) {
    this[name] = value;
  }
}

  • 351bccd Thanks @ematipico! - Added the new nursery lint rule noJsxLiterals, which disallows the use of string literals inside JSX.

    The rule catches these cases:

    <>
  <div>test</div> {/* test is invalid */}
  <>test</>
  <div>
    {/* this string is invalid */}
    asdjfl test foo
  </div>
</>

  • #7406 b906112 Thanks @mdevils! - Fixed an issue (#6393) where the useHookAtTopLevel rule reported excessive diagnostics for nested hook calls.

    The rule now reports only the offending top-level call site, not sub-hooks of composite hooks.

    // Before: reported twice (useFoo and useBar).
function useFoo() {
  return useBar();
}
function Component() {
  if (cond) useFoo();
}
// After: reported once at the call to useFoo().

  • #7461 ea585a9 Thanks @arendjr! - Improved performance of noPrivateImports by eliminating allocations.

    In one repository, the total runtime of Biome with only noPrivateImports enabled went from ~3.2s down to ~1.4s.

  • 351bccd Thanks @ematipico! - Fixed #7411. The Biome Language Server had a regression where opening an editor with a file already open wouldn't load the project settings correctly.

  • #7142 53ff5ae Thanks @Netail! - Added the new nursery rule noDuplicateDependencies, which verifies that no dependencies are duplicated between the bundledDependencies, bundleDependencies, dependencies, devDependencies, overrides, optionalDependencies, and peerDependencies sections.

    For example, the following snippets will trigger the rule:

    {
  "dependencies": {
    "foo": ""
  },
  "devDependencies": {
    "foo": ""
  }
}

    {
  "dependencies": {
    "foo": ""
  },
  "optionalDependencies": {
    "foo": ""
  }
}

    {
  "dependencies": {
    "foo": ""
  },
  "peerDependencies": {
    "foo": ""
  }
}

  • 351bccd Thanks @ematipico! - Fixed #3824. Now the option CLI --color is correctly applied to logging too.

View originalPermalink
How 2.2.4 went
2.2.3

Biome CLI v2.2.3

Added 3
  • Added the new lint rule useConsistentArrowReturn which enforces a consistent return style for arrow functions
  • Support dynamic import defer and import source syntax
  • Range suppressions are now supported for Grit plugins
Changed 1
  • Reduced the severity of certain diagnostics emitted when Biome deserializes the configuration files to Information level
Fixed 8
  • The linter now allows the navigation property for view-transition in CSS
  • Files that are explicitly passed as CLI arguments are now correctly ignored if they reside in an ignored folder
  • The rule noDescendingSpecificity now correctly calculates the specificity of selectors when they are included inside a media query
  • The useOptionalChain rule now recognizes optional chaining using Yoda expressions
  • The useImportType rule now inlines import type into import { type } when the style option is set to inlineType
  • The characters ・ (KATAKANA MIDDLE DOT, U+30FB) and ･ (HALFWIDTH KATAKANA MIDDLE DOT, U+FF65) are no longer considered as valid characters in identifiers
  • Fixed a bug where the Biome Language Server didn't correctly compute the diagnostics of a monorepo setting
  • The useReadonlyClassProperties rule now correctly skips JavaScript files

From Biome

2.2.3
Patch Changes

  • #7353 4d2b719 Thanks @JeetuSuthar! - Fixed #7340: The linter now allows the navigation property for view-transition in CSS.

    Previously, the linter incorrectly flagged navigation: auto as an unknown property. This fix adds navigation to the list of known CSS properties, following the CSS View Transitions spec.

  • #7275 560de1b Thanks @arendjr! - Fixed #7268: Files that are explicitly passed as CLI arguments are now correctly ignored if they reside in an ignored folder.

  • #7358 963a246 Thanks @ematipico! - Fixed #7085, now the rule noDescendingSpecificity correctly calculates the specificity of selectors when they are included inside a media query.

  • #7387 923674d Thanks @qraqras! - Fixed #7381, now the useOptionalChain rule recognizes optional chaining using Yoda expressions (e.g., undefined !== foo && foo.bar).

  • #7316 f9636d5 Thanks @Conaclos! - Fixed #7289. The rule useImportType now inlines import type into import { type } when the style option is set to inlineType.

    Example:

    import type { T } from "mod";
// becomes
import { type T } from "mod";

  • #7350 bb4d407 Thanks @siketyan! - Fixed #7261: two characters ・ (KATAKANA MIDDLE DOT, U+30FB) and ･ (HALFWIDTH KATAKANA MIDDLE DOT, U+FF65) are no longer considered as valid characters in identifiers. Property keys containing these character(s) are now preserved as string literals.

  • #7377 811f47b Thanks @ematipico! - Fixed a bug where the Biome Language Server didn't correctly compute the diagnostics of a monorepo setting, caused by an incorrect handling of the project status.

  • #7245 fad34b9 Thanks @kedevked! - Added the new lint rule useConsistentArrowReturn.

    This rule enforces a consistent return style for arrow functions.

    Invalid
    const f = () => {
  return 1;
};

    This rule is a port of ESLint's arrow-body-style rule.

  • #7370 e8032dd Thanks @fireairforce! - Support dynamic import defer and import source. The syntax looks like:

    import.source("foo");
import.source("x", { with: { attr: "val" } });
import.defer("foo");
import.defer("x", { with: { attr: "val" } });

  • #7369 b1f8cbd Thanks @siketyan! - Range suppressions are now supported for Grit plugins.

    For JavaScript, you can suppress a plugin as follows:

    // biome-ignore-start lint/plugin/preferObjectSpread: reason
Object.assign({ foo: "bar" }, baz);
// biome-ignore-end lint/plugin/preferObjectSpread: reason

    For CSS, you can suppress a plugin as follows:

    body {
  /* biome-ignore-start lint/plugin/useLowercaseColors: reason */
  color: #fff;
  /* biome-ignore-end lint/plugin/useLowercaseColors: reason */
}

  • #7384 099507e Thanks @ematipico! - Reduced the severity of certain diagnostics emitted when Biome deserializes the configuration files. Now these diagnostics are emitted as Information severity, which means that they won't interfere when running commands with --error-on-warnings

  • #7302 2af2380 Thanks @unvalley! - Fixed #7301: useReadonlyClassProperties now correctly skips JavaScript files.

  • #7288 94d85f8 Thanks @ThiefMaster! - Fixed #7286. Files are now formatted with JSX behavior when javascript.parser.jsxEverywhere is explicitly set.

    Previously, this flag was only used for parsing, but not for formatting, which resulted in incorrect formatting of conditional expressions when JSX syntax is used in .js files.

  • #7311 62154b9 Thanks @qraqras! - Added the new nursery rule noUselessCatchBinding. This rule disallows unnecessary catch bindings.

    try {
    // Do something
- } catch (unused) {}
+ } catch {}

  • #7349 45c1dfe Thanks @ematipico! - Fixed #4298. Biome now correctly formats CSS declarations when it contains one single value:

    .bar {
-  --123456789012345678901234567890: var(--1234567890123456789012345678901234567);
+  --123456789012345678901234567890: var(
+    --1234567890123456789012345678901234567
+  );
}

  • #7295 7638e84 Thanks @ematipico! - Fixed #7130. Removed the emission of a false-positive diagnostic. Biome no longer emits the following diagnostic:

    lib/main.ts:1:5 suppressions/unused ━━━━━━━━━━━━━━━━━━━━━━━━━

  ⚠ Suppression comment has no effect because the tool is not enabled.

  > 1 │ /** biome-ignore-all assist/source/organizeImports: For the lib root file, we don't want to organize exports */
      │     ^^^^^^^^^^^^^^^^

  • #7377 811f47b Thanks @ematipico! - Fixed #7371 where the Biome Language Server didn't correctly recompute the diagnostics when updating a nested configuration file.

  • #7348 ac27fc5 Thanks @ematipico! - Fixed #7079. Now the rule useSemanticElements doesn't trigger components and custom elements.

  • #7389 ab06a7e Thanks @Conaclos! - Fixed #7344. useNamingConvention no longer reports interfaces defined in global declarations.

    Interfaces declared in global declarations augment existing interfaces. Thus, they must be ignored.

    In the following example, useNamingConvention reported HTMLElement. It is now ignored.

    export {};
declare global {
  interface HTMLElement {
    foo(): void;
  }
}

  • #7315 4a2bd2f Thanks @vladimir-ivanov! - Fixed #7310: useReadonlyClassProperties correctly handles nested assignments, avoiding false positives when a class property is assigned within another assignment expression.

    Example of code that previously triggered a false positive but is now correctly ignored:

    class test {
  private thing: number = 0; // incorrectly flagged

  public incrementThing(): void {
    const temp = { x: 0 };
    temp.x = this.thing++;
  }
}
What's Changed
New Contributors

Full Changelog: https://github.com/biomejs/biome/compare/@biomejs/biome@2.2.2...@biomejs/biome@v2.2.3

View originalPermalink
How 2.2.3 went
2.2.2

Biome CLI v2.2.2

Added 1
  • JSX node kinds are now supported in GritQL AST nodes
Fixed 12
  • Fixed an issue where Biome got stuck when analyzing some files by adding guards in case the number of types grows too much, and emitting a diagnostic if that happens
  • Fixed an issue where the function scanProject wouldn't work as expected
  • Fixed Biome Language Server to show unsafe fixes when requesting quick fixes in LSP editors
  • Fixed an issue with analysing types of static member expressions involving unions that referenced nested unions
  • Fixed an overcorrection in useImportExtensions when importing explicit index files to preserve them instead of rewriting to nested index paths
  • Fixed an issue with inferring types for rest parameters that caused incorrect types and performance regressions

From Biome

2.2.2
Patch Changes

  • #7266 b270bb5 Thanks @ematipico! - Fixed an issue where Biome got stuck when analyzing some files. This is usually caused by a bug in the inference engine. Now Biome has some guards in place in case the number of types grows too much, and if that happens, a diagnostic is emitted and the inference is halted.

  • #7281 6436180 Thanks @ematipico! - Fixed an issue where the function scanProject wouldn't work as expected.

  • #7285 1511d0c Thanks @rriski! - Partially fixed #6782: JSX node kinds are now supported in GritQL AST nodes.

  • #7249 dff85c0 Thanks @ematipico! - Fixed #748, where Biome Language Server didn't show the unsafe fixes when requesting the quick fixes. Now all LSP editors will show also opt-in, unsafe fixes.

  • #7266 b270bb5 Thanks @ematipico! - Fixed #7020: Resolved an issue with analysing types of static member expressions involving unions. If the object type was a union that referenced nested unions, it would trigger an infinite loop as it tried to keep expanding nested unions, and the set of types would grow indefinitely.

  • #7209 679b70e Thanks @patrickshipe! - Resolved an overcorrection in useImportExtensions when importing explicit index files.

    Imports that explicitly reference an index file are now preserved and no longer rewritten to nested index paths.

    Example
    // Before
-      import "./sub/index";
+      import "./sub/index/index.js";

// After
-      import "./sub/index";
+      import "./sub/index.js";

  • #7270 953f9c6 Thanks @arendjr! - Fixed #6172: Resolved an issue with inferring types for rest parameters. This issue caused rest-parameter types to be incorrect, and in some cases caused extreme performance regressions in files that contained many methods with rest-parameter definitions.

  • #7234 b7aa111 Thanks @JeetuSuthar! - Fixed #7233: The useIndexOf rule now correctly suggests using indexOf() instead of findIndex().

    The diagnostic message was incorrectly recommending Array#findIndex() over Array#indexOf(), when it should recommend the opposite for simple equality checks.

  • #7283 0b07f45 Thanks @ematipico! - Fixed #7236. Now Biome correctly migrates JSONC configuration files when they are passed using --config-path.

  • #7239 1d643d8 Thanks @minht11! - Fixed an issue where Svelte globals ($state and so on) were not properly recognized inside .svelte.test.ts/js and .svelte.spec.ts/js files.

  • #7264 62fdbc8 Thanks @ematipico! - Fixed a regression where when using --log-kind-pretty wasn't working anymore as expected.

  • #7244 660031b Thanks @JeetuSuthar! - Fixed #7225: The noExtraBooleanCast rule now preserves parentheses when removing Boolean calls inside negations.

    // Before
!Boolean(b0 && b1);
// After
!(b0 && b1); // instead of !b0 && b1

  • #7298 46a8e93 Thanks @unvalley! - Fixed #6695: useNamingConvention now correctly reports TypeScript parameter properties with modifiers.

    Previously, constructor parameter properties with modifiers like private or readonly were not checked against naming conventions. These properties are now treated consistently with regular class properties.

What's Changed
New Contributors

Full Changelog: https://github.com/biomejs/biome/compare/@biomejs/biome@2.2.0...@biomejs/biome@2.2.2

View originalPermalink
How 2.2.2 went
2.2.0

Biome CLI v2.2.0

Added 5
  • The `noRestrictedImports` rule now supports a `patterns` option that allows gitignore-style patterns for flexible import restrictions, including `importNamePattern` to restrict specific import names using regular expressions and `invertImportNamePattern` to reverse the logic
  • The `assist/source/useSortedKeys`, `assist/source/useSortedAttributes`, and `assist/source/organizeImports` actions now support customizable sort order options with `natural` and `lexicographic` values
  • Added the `useBiomeIgnoreFolder` rule to detect and promote correct folder ignore patterns in `files.includes` configuration
  • Added support for `.graphqls` files for GraphQL formatting and linting
  • Added `javascript.formatter.operatorLinebreak` option to configure whether long lines should be broken before or after binary operators
Fixed 1
  • Fixed handling of `files.includes` glob patterns so that folders are properly ignored without requiring the `/**` suffix

From Biome

2.2.0
Minor Changes

  • #5506 1f8755b Thanks @sakai-ast! - The noRestrictedImports rule has been enhanced with a new patterns option. This option allows for more flexible and powerful import restrictions using gitignore-style patterns.

    You can now define patterns to restrict entire groups of modules. For example, you can disallow imports from any path under import-foo/ except for import-foo/baz.

    {
  "options": {
    "patterns": [
      {
        "group": ["import-foo/*", "!import-foo/baz"],
        "message": "import-foo is deprecated, except for modules in import-foo/baz."
      }
    ]
  }
}

    Invalid examples

    import foo from "import-foo/foo";
import bar from "import-foo/bar";

    Valid examples

    import baz from "import-foo/baz";

    Additionally, the patterns option introduces importNamePattern to restrict specific import names using regular expressions. The following example restricts the import names that match x , y or z letters from modules under import-foo/.

    {
  "options": {
    "patterns": [
      {
        "group": ["import-foo/*"],
        "importNamePattern": "[xyz]"
      }
    ]
  }
}

    Invalid examples

    import { x } from "import-foo/foo";

    Valid examples

    import { foo } from "import-foo/foo";

    Furthermore, you can use the invertImportNamePattern boolean option to reverse this logic. When set to true, only the import names that match the importNamePattern will be allowed. The following configuration only allows the import names that match x , y or z letters from modules under import-foo/.

    {
  "options": {
    "patterns": [
      {
        "group": ["import-foo/*"],
        "importNamePattern": "[xyz]",
        "invertImportNamePattern": true
      }
    ]
  }
}

    Invalid examples

    import { foo } from "import-foo/foo";

    Valid examples

    import { x } from "import-foo/foo";

  • #6506 90c5d6b Thanks @nazarhussain! - Allow customization of the sort order for different sorting actions. These actions now support a sort option:

    For each of these options, the supported values are the same:

    1. natural. Compares two strings using a natural ASCII order. Uppercase letters come first (e.g. A < a < B < b) and number are compared in a human way (e.g. 9 < 10). This is the default value.
    2. lexicographic. Strings are ordered lexicographically by their byte values. This orders Unicode code points based on their positions in the code charts. This is not necessarily the same as “alphabetical” order, which varies by language and locale.

  • #7159 df3afdf Thanks @ematipico! - Added the new rule useBiomeIgnoreFolder. Since v2.2, Biome correctly prevents the indexing and crawling of folders.

    However, the correct pattern has changed. This rule attempts to detect incorrect usage, and promote the new pattern:

    // biome.json
{
  "files": {
    "includes": [
-      "!dist/**",
-      "!**/fixtures/**",
+      "!dist",
+      "!**/fixtures",
    ]
  }
}

  • #6989 85b1128 Thanks @arendjr! - Fixed minor inconsistencies in how files.includes was being handled.

    Previously, Biome sometimes failed to properly ignore the contents of a folder if you didn't specify the /** at the end of a glob pattern. This was unfortunate, because it meant we still had to traverse the folder and then apply the glob to every entry inside it.

    This is no longer an issue and we now recommend to ignore folders without using the /** suffix.

  • #7118 a78e878 Thanks @avshalomt2! - Added support for .graphqls files. Biome can now format and lint GraphQL files that have the extension .graphqls

  • #6159 f02a296 Thanks @bavalpey! - Added a new option to Biome's JavaScript formatter, javascript.formatter.operatorLinebreak, to configure whether long lines should be broken before or after binary operators.

    For example, the following configuration:

    {
  formatter: {
    javascript: {
      operatorLinebreak: "before", // defaults to "after"
    },
  },
}

    Will cause this JavaScript file:

    const VERY_LONG_CONDITION_1234123412341234123412341234 = false;

if (
  VERY_LONG_CONDITION_1234123412341234123412341234 &&
  VERY_LONG_CONDITION_1234123412341234123412341234 &&
  VERY_LONG_CONDITION_1234123412341234123412341234 &&
  VERY_LONG_CONDITION_1234123412341234123412341234
) {
  console.log("DONE");
}

    to be formatted like this:

    const VERY_LONG_CONDITION_1234123412341234123412341234 = false;
if (
  VERY_LONG_CONDITION_1234123412341234123412341234 &&
  VERY_LONG_CONDITION_1234123412341234123412341234 &&
  VERY_LONG_CONDITION_1234123412341234123412341234 &&
  VERY_LONG_CONDITION_1234123412341234123412341234
) {
  console.log("DONE");
}

  • #7137 a653a0f Thanks @ematipico! - Promoted multiple lint rules from nursery to stable groups and renamed several rules for consistency.

    Promoted rules

    The following rules have been promoted from nursery to stable groups:

    CSS
    GraphQL
    JavaScript/TypeScript
    Renamed rules

    The following rules have been renamed during promotion. The migration tool will automatically update your configuration:

    Configuration files using the old rule names will need to be updated. Use the migration tool to automatically update your configuration:

    biome migrate --write

  • #7159 df3afdf Thanks @ematipico! - Added the new rule noBiomeFirstException. This rule prevents the incorrect usage of patterns inside files.includes.

    This rule catches if the first element of the array contains !. This mistake will cause Biome to analyze no files:

    // biome.json
{
  files: {
    includes: ["!dist/**"], // this is an error
  },
}

  • #6923 0589f08 Thanks @ptkagori! - Added Qwik Domain to Biome

    This release introduces Qwik domain support in Biome, enabling Qwik developers to use Biome as a linter and formatter for their projects.

  • #6989 85b1128 Thanks @arendjr! - Fixed #6965: Implemented smarter scanner for project rules.

    Previously, if project rules were enabled, Biome's scanner would scan all dependencies regardless of whether they were used by/reachable from source files or not. While this worked for a first version, it was far from optimal.

    The new scanner first scans everything listed under the files.includes setting, and then descends into the dependencies that were discovered there, including transitive dependencies. This has three main advantages:

    • Dependencies that are not reachable from your source files don't get indexed.
    • Dependencies that have multiple type definitions, such as those with separate definitions for CommonJS and ESM imports, only have the relevant definitions indexed.
    • If vcs.useIgnoreFile is enabled, .gitignore gets respected as well. Assuming you have folders such as build/ or dist/ configured there, those will be automatically ignored by the scanner.

    The change in the scanner also has a more nuanced impact: Previously, if you used files.includes to ignore a file in an included folder, the scanner would still index this file. Now the file is fully ignored, unless you import it.

    As a user you should notice better scanner performance (if you have project rules enabled), and hopefully you need to worry less about configuring files.experimentalScannerIgnores. Eventually our goal is still to deprecate that setting, so if you're using it today, we encourage you to see which ignores are still necessary there, and whether you can achieve the same effect by ignoring paths using files.includes instead.

    None of these changes affect the scanner if no project rules are enabled.

  • #6731 d6a05b5 Thanks @ematipico! - The --reporter=summary has been greatly enhanced. It now shows the list of files that contains violations, the files shown are clickable and can be opened from the editor.

    Below an example of the new version:

    reporter/parse ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  i The following files have parsing errors.

  - index.css

reporter/format ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  i The following files needs to be formatted.

  - index.css
  - index.ts
  - main.ts

reporter/violations ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  i Some lint rules or assist actions reported some violations.

  Rule Name                                        Diagnostics

  lint/correctness/noUnknownFunction               14 (2 error(s), 12 warning(s), 0 info(s))
  lint/suspicious/noImplicitAnyLet                 16 (12 error(s), 4 warning(s), 0 info(s))
  lint/suspicious/noDoubleEquals                   8 (8 error(s), 0 warning(s), 0 info(s))
  assist/source/organizeImports                    2 (2 error(s), 0 warning(s), 0 info(s))
  lint/suspicious/noRedeclare                      12 (12 error(s), 0 warning(s), 0 info(s))
  lint/suspicious/noDebugger                       8 (8 error(s), 0 warning(s), 0 info(s))

  • #6896 527db7f Thanks @ematipico! - Added new functions to the @biomejs/wasm-* packages:

    • fileExists: returns whether the input file exists in the workspace.
    • isPathIgnored: returns whether the input path is ignored.
    • updateModuleGraph: updates the internal module graph of the input path.
    • getModuleGraph: it returns a serialized version of the internal module graph.
    • scanProject: scans the files and directories in the project to build the internal module graph.

  • #6398 d1a315d Thanks @josh-! - Added support for tracking stable results in user-provided React hooks that return objects to useExhaustiveDependencies to compliment existing support for array return values. For example:

    // biome.json
{
  // rule options
  useExhaustiveDependencies: {
    level: "error",
    options: {
      hooks: [
        {
          name: "useCustomHook",
          stableResult: ["setMyState"],
        },
      ],
    },
  },
}

    This will allow the following to be validated:

    const { myState, setMyState } = useCustomHook();
const toggleMyState = useCallback(() => {
  setMyState(!myState);
}, [myState]); // Only `myState` needs to be specified here.

  • #7201 2afaa49 Thanks @Conaclos! - Implemented #7174. useConst no longer reports variables that are read before being written.

    Previously, useConst reported uninitialised variables that were read in an inner function before being written, as shown in the following example:

    let v;
function f() {
  return v;
}
v = 0;

    This can produce false positives in the case where f is called before v has been written, as in the following code:

    let v;
function f() {
  return v;
}
console.log(f()); // print `undefined`
v = 0;

    Although this is an expected behavior of the original implementation, we consider it problematic since the rule’s fix is marked as safe. To avoid false positives like this, the rule now ignores the previous examples. However, this has the disadvantage of resulting in false negatives, such as not reporting the first example.

Patch Changes

  • #7156 137d111 Thanks @ematipico! - Fixed #7152. Now the rule noDuplicateFontNames correctly detects font names with spaces e.g. Liberation Mono. The diagnostic of the rule now points to the first instances of the repeated font.

    The following example doesn't trigger the rule anymore:

    c {
  font-family:
    SF Mono,
    Liberation Mono,
    sans-serif;
}
d {
  font:
    1em SF Mono,
    Liberation Mono,
    sans-serif;
}

  • #6907 7331bb9 Thanks @ematipico! - Added a new experimental option that allows parsing of .html files that contain interpolation syntax.

    // biome.json
{
  html: {
    // This is the new, experimental option.
    parser: {
      interpolation: true,
    },
  },
}

    <h1>{{ $title }}</h1>

  • #7124 3f436b8 Thanks @Jayllyz! - Added the rule useMaxParams.

    This rule enforces a maximum number of parameters for functions to improve code readability and maintainability. Functions with many parameters are difficult to read, understand, and maintain because they require memorizing parameter order and types.

    // Invalid - too many parameters (default max: 4)
function processData(
  name,
  age,
  email,
  phone,
  address,
  city,
  country,
  zipCode,
) {
  // ...
}

// Valid - within parameter limit
function processData(userData) {
  const { name, age, email, phone, address, city, country, zipCode } =
    userData;
  // ...
}

function calculateSum(a, b, c) {
  return a + b + c;
}

  • #7161 1a14a59 Thanks @ematipico! - Fixed #7160. Now Biome correctly computes ignored files when using formatter.includes, linter.includes and assist.includes inside nested configurations that use "extends": "//".

  • #7081 a081bbe Thanks @Jayllyz! - Added the rule noNextAsyncClientComponent.

    This rule prevents the use of async functions for client components in Next.js applications. Client components marked with "use client" directive should not be async as this can cause hydration mismatches, break component rendering lifecycle, and lead to unexpected behavior with React's concurrent features.

    "use client";

// Invalid - async client component
export default async function MyComponent() {
  return <div>Hello</div>;
}

// Valid - synchronous client component
export default function MyComponent() {
  return <div>Hello</div>;
}

  • #7171 5241690 Thanks @siketyan! - Fixed #7162: The noUndeclaredDependencies rule now considers a type-only import as a dev dependency.

    For example, the following code is no longer reported:

    package.json:

    {
  "devDependencies": {
    "type-fest": "*"
  }
}

    foo.ts:

    import type { SetRequired } from "type-fest";

    Note that you still need to declare the package in the devDependencies section in package.json.

What's Changed
New Contributors

Full Changelog: https://github.com/biomejs/biome/compare/@biomejs/biome@2.1.4...@biomejs/biome@2.2.0

View originalPermalink
How 2.2.0 went
2.1.4

Biome CLI v2.1.4

Added 5
  • Added the noQwikUseVisibleTask rule to Qwik to warn about the use of useVisibleTask$() functions
  • Added the noUnnecessaryConditions nursery rule to detect conditions that don't change during program life cycle
  • Added the useImageSize rule to enforce width and height attributes on img elements for performance reasons
  • Added the useAnchorHref rule to enforce the presence of an href attribute on a elements in JSX
  • Added the noNonNullAssertedOptionalChain rule to prevent non-null assertions immediately after optional chaining expressions
Changed 1
  • Removed option, combobox, listbox roles from useSemanticElements suggestions
Fixed 4
  • Imported symbols using aliases are now correctly recognised
  • Private members are no longer marked as unused when their values are used in assignment expressions, increment expressions, etc.
  • Inference of return types no longer mistakenly picks up return types of nested functions
  • noUnusedPrivateClassMembers now handles members declared as part of constructor arguments

From Biome

2.1.4
Patch Changes

  • #7121 b9642ab Thanks @arendjr! - Fixed #7111: Imported symbols using aliases are now correctly recognised.

  • #7103 80515ec Thanks @omasakun! - Fixed #6933 and #6994.

    When the values of private member assignment expressions, increment expressions, etc. are used, those private members are no longer marked as unused.

  • #6887 0cc38f5 Thanks @ptkagori! - Added the noQwikUseVisibleTask rule to Qwik.

    This rule is intended for use in Qwik applications to warn about the use of useVisibleTask$() functions which require careful consideration before use.

    Invalid:

    useVisibleTask$(() => {
  console.log("Component is visible");
});

    Valid:

    useTask$(() => {
  console.log("Task executed");
});

  • #7084 50ca155 Thanks @ematipico! - Added the new nursery rule noUnnecessararyConditions, which detects whenever some conditions don't change during the life cycle of the program, and truthy or false, hence deemed redundant.

    For example, the following snippets will trigger the rule:

    // Always truthy literal conditions
if (true) {
  console.log("always runs");
}

    // Unnecessary condition on constrained string type
function foo(arg: "bar" | "baz") {
  if (arg) {
    // This check is unnecessary
  }
}

  • #6887 0cc38f5 Thanks @ptkagori! - Added the useImageSize rule to Biome.

    The useImageSize rule enforces the use of width and height attributes on <img> elements for performance reasons. This rule is intended to prevent layout shifts and improve Core Web Vitals by ensuring images have explicit dimensions.

    Invalid:

    <img src="/image.png" />
<img src="https://example.com/image.png" />
<img src="/image.png" width="200" />
<img src="/image.png" height="200" />

    Valid:

    <img width="200" height="600" src="/static/images/portrait-01.webp" />
<img width="100" height="100" src="https://example.com/image.png" />

  • #6887 0cc38f5 Thanks @ptkagori! - Added the useAnchorHref rule to Biome.

    The useAnchorHref rule enforces the presence of an href attribute on <a> elements in JSX. This rule is intended to ensure that anchor elements are always valid and accessible.

    Invalid:

    <a>Link</a>

    <a target="_blank">External</a>

    Valid:

    <a href="/home">Home</a>

    <a href="https://example.com" target="_blank">
  External
</a>

  • #7100 29fcb05 Thanks @Jayllyz! - Added the rule noNonNullAssertedOptionalChain.

    This rule prevents the use of non-null assertions (!) immediately after optional chaining expressions (?.). Optional chaining is designed to safely handle nullable values by returning undefined when the chain encounters null or undefined. Using a non-null assertion defeats this purpose and can lead to runtime errors.

    // Invalid - non-null assertion after optional chaining
obj?.prop!;
obj?.method()!;
obj?.[key]!;
obj?.prop!;

// Valid - proper optional chaining usage
obj?.prop;
obj?.method();
obj?.prop ?? defaultValue;
obj!.prop?.method();

  • #7129 9f4538a Thanks @drwpow! - Removed option, combobox, listbox roles from useSemanticElements suggestions

  • #7106 236deaa Thanks @arendjr! - Fixed #6985: Inference of return types no longer mistakenly picks up return types of nested functions.

  • #7102 d3118c6 Thanks @omasakun! - Fixed #7101: noUnusedPrivateClassMembers now handles members declared as part of constructor arguments:

    1. If a class member defined in a constructor argument is only used within the constructor, it removes the private modifier and makes it a plain method argument.
    2. If it is not used at all, it will prefix it with an underscore, similar to noUnusedFunctionParameter.

  • #7104 5395297 Thanks @harxki! - Reverting to prevent regressions around ref handling

  • #7143 1a6933a Thanks @siketyan! - Fixed #6799: The noImportCycles rule now ignores type-only imports if the new ignoreTypes option is enabled (enabled by default).

    [!WARNING] Breaking Change: The noImportCycles rule no longer detects import cycles that include one or more type-only imports by default. To keep the old behaviour, you can turn off the ignoreTypes option explicitly:

    {
  "linter": {
    "rules": {
      "nursery": {
        "noImportCycles": {
          "options": {
            "ignoreTypes": false
          }
        }
      }
    }
  }
}

  • #7099 6cc84cb Thanks @arendjr! - Fixed #7062: Biome now correctly considers extended configs when determining the mode for the scanner.

  • #6887 0cc38f5 Thanks @ptkagori! - Added the useQwikClasslist rule to Biome.

    This rule is intended for use in Qwik applications to encourage the use of the built-in class prop (which accepts a string, object, or array) instead of the classnames utility library.

    Invalid:

    <div class={classnames({ active: true, disabled: false })} />

    Valid:

    <div classlist={{ active: true, disabled: false }} />

  • #7019 57c15e6 Thanks @fireairforce! - Added support in the JS parser for import source(a stage3 proposal). The syntax looks like:

    import source foo from "<specifier>";

  • #7053 655049e Thanks @jakeleventhal! - Added the useConsistentTypeDefinitions rule.

    This rule enforces consistent usage of either interface or type for object type definitions in TypeScript.

    The rule accepts an option to specify the preferred style:

    • interface (default): Prefer using interface for object type definitions
    • type: Prefer using type for object type definitions

    Examples:

    // With default option (interface)
// ❌ Invalid
type Point = { x: number; y: number };

// ✅ Valid
interface Point {
  x: number;
  y: number;
}

// With option { style: "type" }
// ❌ Invalid
interface Point {
  x: number;
  y: number;
}

// ✅ Valid
type Point = { x: number; y: number };

    The rule will automatically fix simple cases where conversion is straightforward.

What's Changed
New Contributors

Full Changelog: https://github.com/biomejs/biome/compare/@biomejs/biome@2.1.3...@biomejs/biome@2.1.4

View originalPermalink
How 2.1.4 went
2.1.3

Biome CLI v2.1.3

Added 2
  • Added the rule noVueReservedKeys, which prevents the use of reserved Vue keys such as those starting with $ (like $el, $data, $props) and keys starting with _ in data properties
  • Added a new JSON rule called noQuickfixBiome, which disallows the use of code action quickfix.biome inside code editor settings
Changed 2
  • Added @eslint-react/no-nested-component-definitions as a rule source for noNestedComponentDefinitions so it will be picked up by biome migrate --eslint
  • Added support for parsing the :active-view-transition-type() pseudo-class in CSS
Fixed 10
  • Fixed noMagicNumbers rule to ignore type casts and assertions when evaluating numbers
  • Fixed website link for the useComponentExportOnlyModules linter rule to point to the correct URL
  • Fixed @vitest/eslint-plugin source url
  • Fixed ESLint migration for the rule prefer-for from eslint-plugin-solid to Biome's useForComponent
  • Fixed noUnusedVariables and noUnusedFunctionParameters rules no longer causing an infinite loop when the suggested name is not applicable
  • Fixed the documentation URL for lint/correctness/noUnknownPseudoClass

From Biome

2.1.3
Patch Changes

  • #7057 634a667 Thanks @mdevils! - Added the rule noVueReservedKeys, which prevents the use of reserved Vue keys.

    It prevents the use of Vue reserved keys such as those starting with # @biomejs/biome (like $el, $data, $props) and keys starting with _` in data properties, which can cause conflicts and unexpected behavior in Vue components.

    Invalid example
    <script>
export default {
  data: {
    $el: "",
    _foo: "bar",
  },
};
</script>

    <script>
export default {
  computed: {
    $data() {
      return this.someData;
    },
  },
};
</script>
    Valid examples
    <script>
export default {
  data() {
    return {
      message: "Hello Vue!",
      count: 0,
    };
  },
};
</script>

    <script>
export default {
  computed: {
    displayMessage() {
      return this.message;
    },
  },
};
</script>

  • #6941 734d708 Thanks @JamBalaya56562! - Added @eslint-react/no-nested-component-definitions as a rule source for noNestedComponentDefinitions. Now it will get picked up by biome migrate --eslint.

  • #6463 0a16d54 Thanks @JamBalaya56562! - Fixed a website link for the useComponentExportOnlyModules linter rule to point to the correct URL.

  • #6944 e53f2fe Thanks @sterliakov! - Fixed #6910: Biome now ignores type casts and assertions when evaluating numbers for noMagicNumbers rule.

  • #6991 476cd55 Thanks @denbezrukov! - Fixed #6973: Add support for parsing the :active-view-transition-type() pseudo-class

    :active-view-transition-type(first second) {
}

  • #6992 0b1e194 Thanks @ematipico! - Added a new JSON rule called noQuickfixBiome, which disallow the use of code action quickfix.biome inside code editor settings.

  • #6943 249306d Thanks @JamBalaya56562! - Fixed @vitest/eslint-plugin source url.

  • #6947 4c7ed0f Thanks @JamBalaya56562! - Fixed ESLint migration for the rule prefer-for from eslint-plugin-solid to Biome's useForComponent.

  • #6976 72ebadc Thanks @siketyan! - Fixed #6692: The rules noUnusedVariables and noUnusedFunctionParameters no longer cause an infinite loop when the suggested name is not applicable (e.g. the suggested name is already declared in the scope).

  • #6990 333f5d0 Thanks @rvanlaarhoven! - Fixed the documentation URL for lint/correctness/noUnknownPseudoClass

  • #7000 4021165 Thanks @harxki! - Fixed #6795: noUnassignedVariables now correctly recognizes variables used in JSX ref attributes.

  • #7044 b091ddf Thanks @ematipico! - Fixed #6622, now the rule useSemanticElements works for JSX self-closing elements too.

  • #7014 c4864e8 Thanks @siketyan! - Fixed #6516: The biome migrate command no longer break the member list with trailing comments.

  • #6979 29cb6da Thanks @unvalley! - Fixed #6767: useSortedClasses now correctly removes leading and trailing whitespace in className.

    Previously, trailing spaces in className were not fully removed.

    // Think we have this code:
<div className="text-sm font-bold            " />

// Before: applied fix, but a trailing space was preserved
<div className="font-bold text-sm " />

// After: applied fix, trailing spaces removed
<div className="font-bold text-sm" />

  • #7055 ee4828d Thanks @dyc3! - Added the nursery rule useReactFunctionComponents. This rule enforces the preference to use function components instead of class components.

    Valid:

    function Foo() {
  return <div>Hello, world!</div>;
}

    Invalid:

    class Foo extends React.Component {
  render() {
    return <div>Hello, world!</div>;
  }
}

  • #6924 2d21be9 Thanks @ematipico! - Fixed #113, where the Biome Language Server didn't correctly update the diagnostics when the configuration file is modified in the editor. Now the diagnostics are correctly updated every time the configuration file is modified and saved.

  • #6931 e6b2380 Thanks @arendjr! - Fixed #6915: useHookAtTopLevel no longer hangs when rules call themselves recursively.

  • #7012 01c0ab4 Thanks @siketyan! - Fixed #5837: Invalid suppression comments such as biome-ignore-all-start or biome-ignore-all-end no longer causes a panic.

  • #6949 48462f8 Thanks @fireairforce! - Support parse import defer(which is a stage3 proposal). The syntax look like this:

    import defer * as foo from "<specifier>";

  • #6938 5feb5a6 Thanks @vladimir-ivanov! - Fixed #6919 and #6920: useReadonlyClassProperties now does checks for mutations in async class methods.

    Example:

    class Counter3 {
  private counter: number;
  async count() {
    this.counter = 1;
    const counterString = `${this.counter++}`;
  }
}

  • #6942 cfda528 Thanks @sterliakov! - Fixed #6939. Biome now understands this binding in classes outside of methods.

What's Changed
New Contributors

Full Changelog: https://github.com/biomejs/biome/compare/@biomejs/biome@2.1.2...@biomejs/biome@2.1.3

View originalPermalink
How 2.1.3 went
2.1.2

Biome CLI v2.1.2

Changed 4
  • Refactored CSS declaration access to remove one level of indirection
  • Improved performance of noImportCycles by approximately 30%
  • Optimized how function arguments are stored in type inference, improving performance by approximately 10% on RedisCommander.d.ts and 2% on @next/font type definitions
  • Biome now considers whether the linter is enabled when determining how the project should be scanned
Fixed 10
  • Handle multiple semicolons correctly in CSS blocks
  • Biome now recognizes that ~/.config/zed/settings.json and ~/.config/Code/User/settings.json allow comments by default
  • File Watcher no longer incorrectly watches and stores ignored files, preventing memory leaks from dynamically created files
  • Language Server now correctly ignores specific files when vcs.useIgnoreFile is set to true
  • Fixed false positive in useImportExtensions when importing a .js file with a matching .d.ts file
  • Fixed incorrect string quotes when applying fixes to classes strings, resulting in invalid code

From Biome

2.1.2
Patch Changes

  • #6865 b35bf64 Thanks @denbezrukov! - Fix #6485: Handle multiple semicolons correctly in blocks (#6485)

    div {
  box-sizing: border-box;
  color: red;
}

  • #6798 3579ffa Thanks @dyc3! - Fixed #6762, Biome now knows that ~/.config/zed/settings.json and ~/.config/Code/User/settings.json allows comments by default.

  • #6839 4cd62d8 Thanks @ematipico! - Fixed #6838, where the Biome File Watcher incorrectly watched and stored ignored files, causing possible memory leaks when those files were dynamically created (e.g. built files).

  • #6879 0059cd9 Thanks @denbezrukov! - Refactor: remove one level of indirection for CSS declarations with semicolon Previously, accessing a declaration from a list required an extra step:

    item
.as_any_css_declaration_with_semicolon()
.as_css_declaration_with_semicolon()

    Now, it can be done directly with:

    item.as_css_declaration_with_semicolon()

  • #6839 4cd62d8 Thanks @ematipico! - Fixed a bug where the Biome Language Server didn't correctly ignore specific files when vcs.useIgnoreFile is set to true.

  • #6884 5ff50f8 Thanks @arendjr! - Improved the performance of noImportCycles by ~30%.

  • #6903 241dd9e Thanks @arendjr! - Fixed #6829: Fixed a false positive reported by useImportExtensions when importing a .js file that had a matching .d.ts file in the same folder.

  • #6846 446112e Thanks @darricheng! - Fixed an issue where biome was using the wrong string quotes when the classes string has quotes, resulting in invalid code after applying the fix.

  • #6823 eebc48e Thanks @arendjr! - Improved #6172: Optimised the way function arguments are stored in Biome's type inference. This led to about 10% performance improvement in RedisCommander.d.ts and about 2% on @next/font type definitions.

  • #6878 3402976 Thanks @ematipico! - Fixed a bug where the Biome Language Server would apply an unsafe fix when using the code action quickfix.biome.

    Now Biome no longer applies an unsafe code fix when using the code action quickfix.biome.

  • #6794 4d5fc0e Thanks @vladimir-ivanov! - Fixed #6719: The noInvalidUseBeforeDeclaration rule covers additional use cases.

    Examples:

    type Bar = { [BAR]: true };
const BAR = "bar";

    interface Bar {
  child: { grandChild: { [BAR]: typeof BAR; enumFoo: EnumFoo } };
}
const BAR = "bar";
enum EnumFoo {
  BAR = "bar",
}

  • #6863 531e97e Thanks @dyc3! - Biome now considers whether the linter is enabled when figuring out how the project should be scanned. Resolves #6815.

  • #6832 bdbc2b1 Thanks @togami2864! - Fixed #6165: Fixed false negative in noUnusedPrivateClassMembers rule when checking member usage in classes

  • #6839 4cd62d8 Thanks @ematipico! - Fixed a bug where the root ignore file wasn't correctly loaded during the scanning phase, causing false positives and incorrect expectations among users.

    Now, when using vcs.useIgnoreFile, the the globs specified in the ignore file from the project root will have the same semantics as the files.includes setting of the root configuration.

    Refer to the relative web page to understand how they work.

  • #6898 5beb024 Thanks @arendjr! - Fixed #6891: Improved type inference for array indices.

    Example:

    const numbers: number[];
numbers[42]; // This now infers to `number | undefined`.

  • #6809 8192451 Thanks @arendjr! - Fixed #6796: Fixed a false positive that happened in noFloatingPromises when calling functions that were declared as part of for ... of syntax inside async functions.

    Instead, the variables declared inside for ... of loops are now correctly inferred if the expression being iterated evaluates to an Array (support for other iterables will follow later).

    Invalid example

    const txStatements: Array<(tx) => Promise<any>> = [];

db.transaction((tx: any) => {
  for (const stmt of txStatements) {
    // We correctly flag this resolves to a `Promise`:
    stmt(tx);
  }
});

    Valid example

    async function valid(db) {
  const txStatements: Array<(tx: any) => void> = [(tx) => tx.insert().run()];

  db.transaction((tx: any) => {
    for (const stmt of txStatements) {
      // We don't flag a false positive here anymore:
      stmt(tx);
    }
  });
}

  • #6757 13a0818 Thanks @mdevils! - Added the rule noVueReservedProps, resolves #6309.

    It prevents the use of reserved Vue prop names such as key and ref which can cause conflicts and unexpected behavior in Vue components.

    Invalid example
    import { defineComponent } from "vue";

export default defineComponent({
  props: ["ref", "key", "foo"],
});

    <script setup>
defineProps({
  ref: String,
  key: String,
  foo: String,
});
</script>
    Valid examples
    import { defineComponent } from "vue";

export default defineComponent({
  props: ["foo"],
});

    <script setup>
defineProps({ foo: String });
</script>

  • #6840 1a57b51 Thanks @denbezrukov! - Allow multiple identifiers in ::part() pseudo-element selector.

    ::part(first second) {
}

  • #6845 4fd44ec Thanks @arendjr! - Fixed #6510: The scanner no longer shows diagnostics on inaccessible files unless --verbose is used.

  • #6844 b7e2d4d Thanks @sterliakov! - Fixed #6837: Fixed regression with multiple consecutive line suppression comments using instances (like // biome-ignore lint/correctness/useExhaustiveDependencies(depName): reason).

  • #6818 5f3f5a6 Thanks @siketyan! - Fixed an issue where textDocument/codeAction in the LSP could respond with outdated text edits after the workspace watcher observed outdated changes to the file.

  • #6804 3e6ab16 Thanks @arendjr! - noFloatingPromises will no longer suggest to add await keyword inside synchronous callbacks nested inside async functions.

  • #6901 c9e969a Thanks @arendjr! - Fixed #6777: Fixed type inference handling of this to avoid infinite recursion.

    Thanks to @sterliakov for the thorough investigation!

  • #6855 d1581c7 Thanks @vladimir-ivanov! - Fixed #6775: useReadonlyClassProperties now also captures mutations inside function arguments.

    Example:

    class Counter {
  private counter: number;
  count() {
    console.log(this.counter++);
    const counterString = `${this.counter++}`;
  }
}

  • #6839 4cd62d8 Thanks @ematipico! - Fixed a bug where Biome didn't throw any error when vcs.useIgnoreFile is set to true, and there wasn't any ignore file read. Now Biome correctly throws an error if no ignore files are found.

  • #6911 6d68074 Thanks @arendjr! - Fixed #6838: Reduce resource consumption in the Biome Language Server by using non-recursive filesystem watchers instead of recursive ones.

    Watchers are responsible for notifying Biome of changes to files in the filesystem. We used to set up a single recursive watcher, but that meant that Biome would receive filesystem notifications for all files in your project, even for ignored folders such as build/ or dist/ folders.

    With this patch, we set up non-recursive watchers only for the folders that are relevant to a project.

    Related to this, we also solved an issue where incoming notifications were incorrectly filtered, causing ignored files to be processed and stored in our module graph anyway.

What's Changed
New Contributors

Full Changelog: https://github.com/biomejs/biome/compare/@biomejs/js-api@2.0.3...@biomejs/biome@2.1.2

View originalPermalink
How 2.1.2 went
2.1.1

Biome CLI v2.1.1

Fixed 2
  • Fixed the FileFeaturesResult interface in the WASM API that was defined as a mapped object but the actual value was a Map object
  • Fixed a false positive for noFocusedTests rule that was triggered by calling any function with the name fit on any object

From Biome

2.1.1
Patch Changes

  • #6781 9bbd34f Thanks @siketyan! - Fixed the FileFeaturesResult interface in the WASM API was defined as a mapped object but the actual value was a Map object.

  • #6761 cf3c2ce Thanks @dyc3! - Fixed #6759, a false positive for noFocusedTests that was triggered by calling any function with the name fit on any object.

    The following code will now pass the noFocusedTests rule:

    import foo from "foo";
foo.fit();
What's Changed

Full Changelog: https://github.com/biomejs/biome/compare/@biomejs/js-api@2.0.1...@biomejs/biome@2.1.1

View originalPermalink
How 2.1.1 went
2.1.0

Biome CLI v2.1.0

Added 6
  • The rule noFloatingPromises can now detect floating arrays of Promises
  • Type inference now handles the sequence operator (,) and post- and pre-update operators (++)
  • Added the nursery rule noMisusedPromises to signal Promises in places where conditionals or iterables are expected
  • Added the ignoreRestSiblings option to the noUnusedFunctionParameters rule
  • nx.json and project.json have been added to the list of well-known files
  • Added # @biomejs/biome symbol to organizeImports :ALIAS: group
Fixed 4
  • .gitignore files are now picked up even when running Biome from a nested directory or when the ignore file itself is ignored through files.includes
  • biome migrate no longer enables style rules that were recommended in v1
  • Implemented a more targeted version of the scanner that excludes directories not relevant to provided file paths
  • Biome now supports // biome-ignore-all file-level suppressions in files that start with a shebang (#!)

From Biome

2.1.0
Minor Changes

  • #6512 0c0bf82 Thanks @arendjr! - The rule noFloatingPromises can now detect floating arrays of Promises.

    Invalid examples

    // This gets flagged because the Promises are not handled.
[1, 2, 3].map(async (x) => x + 1);

    Valid examples

    await Promise.all([1, 2, 3].map(async (x) => x + 1));

  • #6637 6918085 Thanks @arendjr! - Type inference is now able to handle the sequence operator (,), as well as post- and pre-update operators: ++.

    Example

    let x = 5;

// We now infer that `x++` resolves to a number, while the expression as a whole
// becomes a Promise:
x++, new Promise((resolve) => resolve("comma"));

  • #6752 c9eaca4 Thanks @arendjr! - Fixed #6646: .gitignore files are now picked up even when running Biome from a nested directory, or when the ignore file itself is ignored through files.includes.

  • #6746 90aeead Thanks @arendjr! - biome migrate no longer enables style rules that were recommended in v1, because that would be undesirable for users upgrading from 2.0.

    Users who are upgrading from Biome 1.x are therefore advised to first upgrade to Biome 2.0, and run the migration, before continuing to Biome 2.1 or later.

  • #6583 d415a3f Thanks @arendjr! - Added the nursery rule noMisusedPromises.

    It signals Promises in places where conditionals or iterables are expected.

    Invalid examples

    const promise = Promise.resolve("value");

// Using a `Promise` as conditional is always truthy:
if (promise) {
  /* ... */
}

// Spreading a `Promise` has no effect:
console.log({ foo: 42, ...promise });

// This does not `await` the `Promise`s from the callbacks,
// so it does not behave as you may expect:
[1, 2, 3].forEach(async (value) => {
  await fetch(`/${value}`);
});

    Valid examples

    const promise = Promise.resolve("value");

if (await promise) {
  /* ... */
}

console.log({ foo: 42, ...(await promise) });

  • #6405 cd4a9bb Thanks @vladimir-ivanov! - Added the ignoreRestSiblings option to the noUnusedFunctionParameters rule.

    This option is used to ignore unused function parameters that are siblings of the rest parameter.

    The default is false, which means that unused function parameters that are siblings of the rest parameter will be reported.

    Example

    {
  "rules": {
    "noUnusedFunctionParameters": ["error", { "ignoreRestSiblings": true }]
  }
}

  • #6614 0840021 Thanks @arendjr! - We have implemented a more targeted version of the scanner, which ensures that if you provide file paths to handle on the CLI, the scanner will exclude directories that are not relevant to those paths.

    Note that for many commands, such as biome check and biome format, the file paths to handle are implicitly set to the current working directory if you do not provide any path explicitly. The targeted scanner also works with such implicit paths, which means that if you run Biome from a subfolder, other folders that are part of the project are automatically exempted.

    Use cases where you invoke Biome from the root of the project without providing a path, as well as those where project rules are enabled, are not expected to see performance benefits from this.

    Implemented #6234, and fixed #6483 and #6563.

  • #6488 c5ee385 Thanks @ianzone! - nx.json and project.json have been added to the list of well-known files.

  • #6720 52e36ae Thanks @minht11! - Added # @biomejs/biome symbol to [organizeImports](https://biomejs.dev/assist/actions/organize-imports) :ALIAS:` group.

    import { action } from '$lib' will be treated as alias import.

Patch Changes

  • #6712 2649ac6 Thanks @sterliakov! - Fixed #6595: Biome now supports // biome-ignore-all file-level suppressions in files that start with a shebang (#!).

  • #6758 28dc49e Thanks @arendjr! - Fixed #6573: Grit plugins can now match bare imports.

    Example

    The following snippet:

    `import $source`

    will now match:

    import "main.css";

  • #6550 b424f46 Thanks @arendjr! - Type inference is now able to handle logical expressions: &&, ||, and ??.

    Examples

    // We can now infer that because `true` is truthy, the entire expression
// evaluates to a `Promise`.
true && Promise.reject("logical operator bypass");

// And we know that this doesn't:
false && Promise.reject("logical operator bypass");

// Truthiness, falsiness, and non-nullishness can all be determined on more
// complex expressions as well. So the following also works:
type Nullish = null | undefined;

type Params = {
  booleanOption: boolean | Nullish;
  falsyOption: false | Nullish;
};

function foo({ booleanOption, falsyOption }: Params) {
  // This may be a Promise:
  booleanOption ?? Promise.reject("logical operator bypass");

  // But this never is:
  falsyOption && Promise.reject("logical operator bypass");
}

  • #6413 4aa0e50 Thanks @wojtekmaj! - Improved error message in useDateNow rule.

  • #6673 341e062 Thanks @dyc3! - Fixed a case where the HTML formatter would mangle embedded language tags if whitespaceSensitivity was set to strict

  • #6642 a991229 Thanks @unvalley! - Fixed #4494: The noSecrets rule now correctly uses the entropyThreshold option to detect secret like strings.

  • #6520 0c43545 Thanks @arendjr! - Type inference is now able to handle ternary conditions in type aliases.

    Note that we don't attempt to evaluate the condition itself. The resulting type is simply a union of both conditional outcomes.

    Example

    type MaybeResult<T> = T extends Function ? Promise<string> : undefined;

// We can now detect this function _might_ return a `Promise`:
function doStuff<T>(input: T): MaybeResult<T> {
  /* ... */
}

  • #6711 1937691 Thanks @sterliakov! - Fixed #6654: Fixed range highlighting of <explanation> placeholder in inline suppression block comments.

  • #6756 d12b26f Thanks @dyc3! - Fixed #6669: Added an exception to noUnusedImports to allow type augmentation imports.

    import type {} from "@mui/lab/themeAugmentation";

  • #6643 df15ad6 Thanks @skewb1k! - Fixed #4994: LSP server registered some capabilities even when the client did not support dynamic registration.

  • #6599 5e611fa Thanks @vladimir-ivanov! - Fixed #6380: The noFocusedTests rule now correctly displays the function name in the diagnostic message when a test is focused.

    Every instance of a focused test function (like fdescribe, fit, ftest and only) had the word 'only' hardcoded. This has been updated to use the actual function name, so the message is now more accurate and specific.

    Example for fdescribe:

      i The 'fdescribe' method is often used for debugging or during implementation.

  i Consider removing 'f' prefix from 'fdescribe' to ensure all tests are executed.

  • #6671 0c9ab43 Thanks @vladimir-ivanov! - Fixed #6634: The useReadonlyClassProperties rule now correctly flags mutations in class getters and in arrow functions within class properties.

    Examples:

    class GetterWithMutationValue {
  #value: string;

  get value() {
    if (!this.#value) {
      this.#value = "defaultValue";
    }

    return this.#value;
  }
}

    class ClassPropertyArrowFunctionWithMutation {
  private bar: string | null = null;

  readonly action = () => {
    this.bar = "init";
  };
}

  • #6682 ca04cea Thanks @ematipico! - Fixed #6668: Biome Assist is now enabled by default for CSS files.

  • #6525 66b089c Thanks @arendjr! - Type inference can now infer the return types of functions and methods without annotations.

    Examples

    const sneakyObject = {
  doSomething() {
    return Promise.resolve("This is a floating promise!");
  },
};

// We can now detect that `doSomething()` returns a `Promise`.
sneakyObject.doSomething();

  • #6531 c06df79 Thanks @arendjr! - Biome's type inference now detects the type of properties with getters.

    Examples

    const sneakyObject2 = {
  get something() {
    return new Promise((_, reject) => reject("This is a floating promise!"));
  },
};
// We now detect this is a Promise:
sneakyObject2.something;

  • #6587 a330fcc Thanks @Conaclos! - organizeImports is now able to sort named specifiers and import attributes with bogus nodes.

  • #6618 6174869 Thanks @Shinyaigeek! - Fixed #6610: JSON import attributes are now correctly detected when they contain extra whitespace.

  • #6753 fce5d2c Thanks @dyc3! - Improved the error messages when Biome is provided incompatible arguments on the CLI.

  • #6587 a330fcc Thanks @Conaclos! - Fixed #6491: The action of useSortedKeys removed comments or wrongly transferred them to distinct nodes.

  • #6696 92964a7 Thanks @unvalley! - Fixed #6633: The noImplicitCoercion rule no longer reports diagnostics for 1 / value expressions.

    1 / value; // no error

  • #6683 43d871e Thanks @ematipico! - Fixed #6537: Biome no longer removes the trailing comma from JSON files when formatter.json.trailingCommas is explicitly set to "all".

  • #6693 bfdce0b Thanks @dyc3! - Fixed #6691: The HTML parser will now consider . to be a valid character for tag names.

  • #6716 ead03d1 Thanks @siketyan! - The Biome LSP server no longer responds with an error for a textDocument/codeActions request when Biome doesn't support a feature for the file (e.g. Code actions aren't supported in GritQL files).

  • #6679 7bf9a60 Thanks @marko-hologram! - Fixed #6638: JavaScript formatter overrides options now correctly override expand option. JSON formatter overrides options now correctly override bracketSpacing and expand options.

  • #6717 7f5b541 Thanks @siketyan! - Fixed #6688: the noUselessFragments no longer reports <Fragment /> elements that includes HTML character entities.

  • #6600 853e1b5 Thanks @daivinhtran! - Fixed #4677: The noUnusedImports rule won't produce diagnostics for types used in comments of static members anymore.

  • #6662 3afc804 Thanks @arendjr! - If a nested configuration file is ignored by the root configuration, it will now actually be ignored.

    Biome has an exception in place for configuration files so they cannot be ignored, because the configuration files are vital to Biome itself. But this exception was incorrectly applied to nested configurations as well. Now only the root configuration is exempt from being ignored.

  • #6596 c0718ca Thanks @ematipico! - Fixed #6566: Biome no longer errors when using the option --files-ignore-unknown=true in stdin mode.

    Biome has also become less strict when using --stdin-file-path in stdin mode. It will no longer error if the file path doesn't contain an extension, but instead it will return the original content.

  • #6562 153eda7 Thanks @vladimir-ivanov! - Added the nursery rule noMagicNumbers. The rule detects and reports the use of "magic numbers" — numeric literals that are used directly in code without being assigned to a named constant.

    Example

    let total = price * 1.23; // Magic number for tax rate will highlight 1.23 as magic number

  • #6663 af78d6d Thanks @ematipico! - Fixed #6656: Biome now correctly formats HTML void elements such as <meta> when they contain a self-closing slash.

    - <meta foo="bar" />
+ <meta foo="bar">

  • #6732 31e4396 Thanks @vladimir-ivanov! - Resolved #6281: Improved performance of handling package.json files in the scanner.

  • #6625 19cb475 Thanks @arendjr! - Fixed #6616: Fixed an issue with extending configurations that contained an explicit root field while the configuration in the project did not.

  • #6650 19aab18 Thanks @sterliakov! - Fixed #6621: Improved handling of multiple adjacent line suppressions. Biome now handles such suppressions separately, tracking whether each one is used.

  • #6700 cdd6e17 Thanks @denbezrukov! - Fixed #6680: Biome incorrectly formatted container-style queries by inserting misplaced spaces.

    - @container style (--responsive: true) {}
+ @container style(--responsive: true) {}

  • #6709 ecf3954 Thanks @dyc3! - Fixed #6038: Fixed a false positive in noShadow where a function parameter in a type definition was erroneously flagged as a violation.

  • #6593 a4acbb7 Thanks @arendjr! - Type inference is now able to handle ternary conditions in expressions.

    Examples

    const condition = Math.random() > -1; // Always true, but dynamic to linter

// We now detect that this may return a `Promise`.
condition ? Promise.reject("ternary bypass") : null;

// On the other hand, we know the following is never a `Promise`:
const alwaysFalsy = 0;
alwaysFalsy ? Promise.reject("ternary bypass") : null;

  • #6428 4b501d3 Thanks @siketyan! - Added MemoryFileSystem to the WASM API.

    You can now insert a file from your JS code:

    import { MemoryFileSystem, Workspace } from "@biomejs/wasm-web";

const fs = new MemoryFileSystem();
const workspace = Workspace.withFileSystem(fs);

fs.insert("/index.js", new TextEncoder().encode("let foo = 1;"));
fs.remove("/index.js");

  • #6594 626d4a1 Thanks @ematipico! - Fixed #6528: Biome didn't return the correct output when applying source.fixAll.biome inside Astro/Vue/Svelte files that contained safe fixed.

What's Changed
New Contributors

Full Changelog: https://github.com/biomejs/biome/compare/@biomejs/biome@2.0.6...@biomejs/biome@2.1.0

View originalPermalink
How 2.1.0 went
2.0.6

Biome CLI v2.0.6

Added 1
  • Added the nursery rule `noExcessiveLinesPerFunction` to restrict a maximum number of lines of code in a function body.
Changed 1
  • When using the `extends` field to extend a configuration from an NPM package, Biome now accepts the condition names `biome` and `default` for exporting the configuration in `package.json`.
Fixed 11
  • Fixed a bug where Biome didn't provide all the available code actions when requested by the editor.
  • The `organizeImports` assist action no longer duplicates a comment at the start of the file when `:BLANK_LINE:` precedes the first import group.
  • Biome Language Server now adheres to the `settings.requireConfiguration` option when pulling diagnostics and code actions.
  • The `useSortedKeys` rule no longer panics in edge cases where object spreads are involved.
  • Fixed nursery rules that belonged to a domain being incorrectly enabled.
  • The `noUnusedImports` rule no longer produces diagnostics for types used in JSDoc comments of exports.

From Biome

2.0.6
Patch Changes

  • #6557 fd68458 Thanks @ematipico! - Fixed a bug where Biome didn't provide all the available code actions when requested by the editor.

  • #6511 72623fa Thanks @Conaclos! - Fixed #6492. The organizeImports assist action no longer duplicates a comment at the start of the file when :BLANK_LINE: precedes the first import group.

  • #6557 fd68458 Thanks @ematipico! - Fixed #6287 where Biome Language Server didn't adhere to the settings.requireConfiguration option when pulling diagnostics and code actions. Note that for this configuration be correctly applied, your editor must support dynamic registration capabilities.

  • #6551 0b63b1d Thanks @Conaclos! - Fixed #6536. useSortedKeys no longer panics in some edge cases where object spreads are involved.

  • #6503 9a8fe0f Thanks @ematipico! - Fixed #6482 where nursery rules that belonged to a domain were incorrectly enabled.

  • #6565 e85761c Thanks @daivinhtran! - Fixed #4677: Now the noUnusedImports rule won't produce diagnostics for types used in JSDoc comment of exports.

  • #6166 b8cbd83 Thanks @mehm8128! - Added the nursery rule noExcessiveLinesPerFunction. This rule restrict a maximum number of lines of code in a function body.

    The following code is now reported as invalid when the limit of maximum lines is set to 2:

    function foo() {
  const x = 0;
  const y = 1;
  const z = 2;
}

    The following code is now reported as valid when the limit of maximum lines is set to 3:

    const bar = () => {
  const x = 0;
  const z = 2;
};

  • #6553 5f42630 Thanks @denbezrukov! - Fixed #6547. Now the Biome CSS parser correctly parses @starting-style when it's used inside other at-rules. The following example doesn't raise an error anymore:

    @layer my-demo-layer {
  @starting-style {
    div.showing {
      background-color: red;
    }
  }
}

  • #6458 05402e3 Thanks @ematipico! - Fixed an issue where the rule useSemanticElements used the incorrect range when positioning suppression comments.

  • #6560 6d8a6b9 Thanks @siketyan! - Fixed #6559: the error message on detected a large file was outdated and referred a removed configuration option files.ignore.

  • #6458 05402e3 Thanks @ematipico! - Fixed #6384. The rule useAltText now emits a diagnostic with a correct range, so suppression comments can work correctly.

  • #6518 7a56288 Thanks @wojtekmaj! - Fixed #6508, where the rule noUselessFragments incorrectly flagged Fragments containing HTML entities as unnecessary.

  • #6517 c5217cf Thanks @arendjr! - Fixed #6515. When using the extends field to extend a configuration from an NPM package, we now accept the condition names "biome" and "default" for exporting the configuration in the package.json.

    This means that where previously your package.json had to contain an export declaration similar to this:

    {
  "exports": {
    ".": "./biome.json"
  }
}

    You may now use one of these as well:

    {
  "exports": {
    ".": {
      "biome": "./biome.json"
    }
  }
}

    Or:

    {
  "exports": {
    ".": {
      "default": "./biome.json"
    }
  }
}

  • #6219 a3a3715 Thanks @huangtiandi1999! - Added new nursery rule noUnassignedVariables, which disallows let or var variables that are read but never assigned.

    The following code is now reported as invalid:

    let x;
if (x) {
  console.log(1);
}

    The following code is now reported as valid:

    let x = 1;
if (x) {
  console.log(1);
}

  • #6395 f62e748 Thanks @mdevils! - Added the new nursery rule noImplicitCoercion, which disallows shorthand type conversions in favor of explicit type conversion functions.

    Example (Invalid): Boolean conversion using double negation:

    !!foo;
!!(foo + bar);

    Example (Invalid): Number conversion using unary operators:

    +foo;
-(-foo);
foo - 0;
foo * 1;
foo / 1;

    Example (Invalid): String conversion using concatenation:

    "" + foo;
foo + "";
`` + foo;
foo += "";

    Example (Invalid): Index checking using bitwise NOT:

    ~foo.indexOf(1);
~foo.bar.indexOf(2);

    Example (Valid): Using explicit type conversion functions:

    Boolean(foo);
Number(foo);
String(foo);
foo.indexOf(1) !== -1;

  • #6544 f28b075 Thanks @daivinhtran! - Fixed #6536. Now the rule noUselessFragments produces diagnostics for a top-level useless fragment that is in a return statement.

  • #6320 5705f1a Thanks @mdevils! - Added the new nursery rule useUnifiedTypeSignature, which disallows overload signatures that can be unified into a single signature.

    Overload signatures that can be merged into a single signature are redundant and should be avoided. This rule helps simplify function signatures by combining overloads by making parameters optional and/or using type unions.

    Example (Invalid): Overload signatures that can be unified:

    function f(a: number): void;
function f(a: string): void;

    interface I {
  a(): void;
  a(x: number): void;
}

    Example (Valid): Unified signatures:

    function f(a: number | string): void {}

    interface I {
  a(x?: number): void;
}

    Example (Valid): Different return types cannot be merged:

    interface I {
  f(): void;
  f(x: number): number;
}

  • #6545 2782175 Thanks @ematipico! - Fixed #6529, where the Biome Language Server would emit an error when the user would open a file that isn't part of its workspace (node_modules or external files). Now the language server doesn't emit any errors and it exits gracefully.

  • #6524 a27b825 Thanks @vladimir-ivanov! - Fixed #6500: The useReadonlyClassProperties rule now correctly marks class properties as readonly when they are assigned in a constructor, setter or method, even if the assignment occurs inside an if or else block.

    The following code is now correctly detected by the rule:

    class Price {
  #price: string;

  @Input()
  set some(value: string | number) {
    if (
      value === undefined ||
      value === null ||
      value === "undefined" ||
      value === "null" ||
      Number.isNaN(value)
    ) {
      this.#price = "";
    } else {
      this.#price = "" + value;
    }
  }
}

  • #6355 e128ea9 Thanks @anthonyshew! - Added a new nursery rule noAlert that disallows the use of alert, confirm and prompt.

    The following code is deemed incorrect:

    alert("here!");

  • #6548 37e9799 Thanks @ematipico! - Fixed #6459, where the Biome LSP was not taking into account the correct settings when applying source.fixAll.biome code action.

What's Changed
New Contributors

Full Changelog: https://github.com/biomejs/biome/compare/@biomejs/biome@2.0.5...@biomejs/biome@2.0.6

View originalPermalink
How 2.0.6 went
2.0.5

Biome CLI v2.0.5

Fixed 4
  • Fixed stdin mode regression where a temporary new file would be created instead of using the file path provided via --std-file-path, and now applies the configuration that matches it
  • Fixed useNamingConvention rule to check the string case of objects' property shorthand
  • Fixed formatter inconsistent formatting of CSS values separated by commas
  • Fixed grit pattern matching for different kinds of import statements so that import $imports from "foo" matches default imports, named imports, and multiple named imports

From Biome

2.0.5
Patch Changes

  • #6461 38862e6 Thanks @ematipico! - Fixed #6419, a regression where stdin mode would create a temporary new file instead of using the one provided by the user. This was an intended regression.

    Now Biome will use the file path passed via --std-file-path, and apply the configuration that matches it.

  • #6480 050047f Thanks @Conaclos! - Fixed #6371. useNamingConvention now checks the string case of objects' property shorthand.

  • #6477 b98379d Thanks @ematipico! - Fixed an issue where Biome formatter didn't format consistently CSS value separated by commas.

    .font-heading {
- font-feature-settings: var(--heading-salt), var(--heading-ss06),
-   var(--heading-ss11), var(--heading-cv09), var(--heading-liga),
-   var(--heading-calt);

+  font-feature-settings:
+    var(--heading-salt), var(--heading-ss06), var(--heading-ss11),
+    var(--heading-cv09), var(--heading-liga), var(--heading-calt);
}

  • #6248 ec7126c Thanks @fireairforce! - Fixed grit pattern matching for different kinds of import statements.

    The grit pattern import $imports from "foo" will match the following code:

    import bar from "foo";
import { bar } from "foo";
import { bar, baz } from "foo";
What's Changed

Full Changelog: https://github.com/biomejs/biome/compare/@biomejs/biome@2.0.4...@biomejs/biome@2.0.5

View originalPermalink
How 2.0.5 went

2.0.4

Added 1
  • Add new lint rule useReadonlyClassProperties
Fixed 1
  • Fixed an issue where the binary wasn't correctly mapped

From Biome

Patch Changes
What's Changed

Full Changelog: https://github.com/biomejs/biome/compare/@biomejs/biome@2.0.1...@biomejs/biome@v2.0.4

View originalPermalink
How 2.0.4 went

2.0.1

Fixed 9
  • The rule noUselessFragments no longer reports a fragment that contains whitespaces which aren't trimmed by the runtime
  • The pseudo classes and elements :open, ::details-content, ::prefix, ::search-text, and ::suffix are no longer reported by noUnknownPseudoClass or noUnknownPseudoElement rules
  • Boolean values are now correctly merged when using the extends functionality in configuration
  • Fixed an issue where Biome would throw an error for the language tags nb and nn
  • The rule noSelfCompare now correctly compares two function calls with different arguments
  • useExhaustiveDependencies no longer adds duplicated dependencies into the list
Removed 1
  • Removed the experimental rename feature from Biome LSP

From Biome

[!WARNING] Biome v2.0.1 and v2.0.2 are currently broken, please use v2.0.0 in the meantime. See #6435 for details.

Patch Changes

  • #6425 00e97ad Thanks @siketyan! - Fixed #6391: the rule noUselessFragments no longer reports a fragment that contains whitespaces which aren't trimmed by the runtime.

  • #6417 dd88565 Thanks @ematipico! - Fixed #6360: The following pseudo classes and elements are no longer reported by noUnknownPseudoClass or noUnknownPseudoElement rules.

    • :open
    • ::details-content
    • ::prefix
    • ::search-text
    • ::suffix

  • #6417 dd88565 Thanks @ematipico! - Fixed #6357, where the boolean values weren't correctly merged when using the extends functionality. Now Biome correctly merges the values.

  • #6417 dd88565 Thanks @ematipico! - Fixed #6341: Fixed an issue where Biome would throw an error for the language tags nb and nn.

  • #6385 94142dd Thanks @siketyan! - Fixed #6377: The rule noSelfCompare now correctly compares two function calls with different arguments.

  • #6417 dd88565 Thanks @ematipico! - Fixed #6278: useExhaustiveDependencies no longer adds duplicated dependencies into the list.

  • #6417 dd88565 Thanks @ematipico! - Fix #6396, where vi.useFakeTimers() and vi.useRealTimers() incorrectly triggered React Hooks-related rules

  • #6417 dd88565 Thanks @ematipico! - Fixed a bug where Biome didn't correctly discover nested configuration files when using the lint command and the linter is disabled in the root configuration.

  • #6422 594ec50 Thanks @ematipico! - Removed the experimental rename feature from Biome LSP, which caused some issues inside existing editors such as Zed.

  • #6388 c6942d2 Thanks @siketyan! - Fixed #6375: the formatter no longer inserts an extra empty line before a semicolon when it has leading comments.

View originalPermalink
How 2.0.1 went
2.0.0

Biome CLI v2.0.0

Added 2
  • Biome now raises a warning diagnostic for suppression comments that have <explanation> as reason
  • The noRestrictedGlobals lint rule now supports customizing message for each global name
Changed 4
  • Biome now resolves globs and paths from the configuration instead of from the working directory
  • Downgrade code fixes to unsafe for noFlatMapIdentity and noUnusedImports rules
  • Remove support for dynamically built regular expressions from noControlCharactersInRegex and noMisleadingCharacterClass lint rules
  • The includes field uses a different glob pattern format and allows negated patterns with ! prefix
Removed 2
  • Remove the --config-path argument from the biome lsp-proxy and biome start commands
  • Remove include and ignore fields in favor of the new includes field in configuration

From Biome

Major Changes

  • Biome now resolves globs and paths from the configuration. Before, paths and globs were resolved from the working directory.

  • Biome now raises a warning diagnostic for suppression comments that have <explanation> as reason.

    <explanation> is provided as a placeholder when applying the suppression code fix from LSP editors.

  • Removed the --config-path argument from the biome lsp-proxy and biome start commands.

    The option was overriding the configuration path for all workspaces opened in the Biome daemon, which led to a configuration mismatch problem when multiple projects are opened in some editors or IDEs.

    If you are using one of our official plugins for IDEs or editors, it is recommended to update it to the latest version of the plugin, or you will get unexpected behavior.

    If you are a developer of a plugin, please update your plugin to use the workspace/configuration response instead of using the --config-path argument. Biome's LSP will resolve a configuration in the workspace automatically, so it is recommended to keep it empty unless you are using a custom configuration path.

  • Downgraded some code fixes to unsafe which were previously safe.

    The following rules have now a unsafe fix:

    If you want to keep applying these fixes automatically, configure the rule fix as safe:

    {
  "linter": {
    "rules": {
      "correctness": {
        "noFlatMapIdentity": {
          "level": "error",
          "fix": "safe"
        },
        "noUnusedImports": {
          "level": "error",
          "fix": "safe"
        }
      }
    }
  }
}

  • Previously the lint rules noControlCharactersInRegex and noMisleadingCharacterClass checked both regular expression literals like /regex/ and dynamically built regular expressions like new RegExp("regex").

    Checking dynamically built regular expressions has many limitations, edge cases, and complexities. In addition, other rules that lint regular expressions don't check dynamically built regular expressions.

    Rather than add support for other rules and have half-baked checking, we decided to remove support for dynamically built regular expressions.

    Now the lint rules noControlCharactersInRegex and noMisleadingCharacterClass only check literals of regular expressions.

  • The lint rule noRestrictedGlobals now supports customizing message for each global name.

    For example, the following configuration:

    {
  "options": {
    "deniedGlobals": {
      "$": "jQuery is not allowed. Use native DOM manipulation instead."
    }
  }
}

    emits a diagnostic:

    index.js:1:13 lint/style/noRestrictedGlobals ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  ⚠ Do not use the global variable $.

  > 1 │ console.log($)
      │             ^
    2 │

  ℹ jQuery is not allowed. Use native DOM manipulation instead.

    Breaking Change: The option deniedGlobals is now a record instead of an array. Run biome migrate to migrate the configuration automatically.

  • Removed include and ignore fields in favor of the new field includes.

    The Biome configuration file allows users to specify which files should be processed using glob patterns. Prior to Biome 2.0, this was done using the include and ignore fields. In Biome 2.0, include and ignore are removed and replaced by includes. You can run biome migrate to convert include and ignore into includes automatically.

    includes uses a different glob pattern format that fixes many issues and many other limitations that Biome users reported.

    includes accepts an array of glob patterns. A glob pattern starting with a ! is a negated pattern also called exception. This replaces ignore patterns and allows users to create chains of include and ignore patterns. Thus, it is now possible to include again a file previously ignored. This was not possible with include and ignore, because ignore has priority over include.

    The semantics of * and **/* have changed too. Before, with include and ignore, the glob * was interpreted as **/*. Now, with includes, the globs * and **/* are interpreted differently. The first pattern matches all files that are inside a folder. The second pattern recursively matches all files and sub-folders inside a folder.

    Let's take an example. Given the following file hierarchy of a project...

    ├── biome.json
├── src
│   ├── file.js
│   ├── file.ts
│   ├── out.gen.js
│   ├── file.test.js
│   └── test
│       └── special.test.js
└── test ...

    ...we want:

    1. Ignore all files ending with .test.js, except special.test.ts.
    2. Ignore all files of the test directory. The test directory is located at the root of the project.
    3. Execute the linter on files in the src directory, that don't end with .gen.js. The src directory is located at the root of the project.
    4. Enable the noDefaultExport lint rule on files ending with .ts.

    Prior to Biome 2.0, the configuration might look like:

    {
  "files": {
    "ignore": ["*.test.js", "test"]
  },
  "linter": {
    "include": ["src/**"],
    "ignore": ["*.gen.js"],
    "enabled": true
  },
  "overrides": [
    {
      "include": ["*.ts"],
      "linter": { "rules": { "style": { "noDefaultExport": "on" } } }
    }
  ]
}

    Unfortunately, the configuration doesn't quite fit what we want:

    1. There is no way to ignore files and unignore one of them. Thus, we ignore all files ending with .test.js, including special.test.ts.
    2. The configuration ignores all directories named test, including src/test.
    3. The linter is executed on all files of all directories named src

    All these issues and limitations are fixed with includes. Here the migrated configuration:

    {
  "files": {
    "includes": ["**", "!**/*.test.js", "**/special.test.ts", "!test"]
  },
  "linter": {
    "includes": ["src/**", "!**/*.gen.js"],
    "enabled": true
  },
  "overrides": [
    {
      "includes": ["**/*.ts"],
      "linter": { "rules": { "style": { "noDefaultExport": "on" } } }
    }
  ]
}
    1. All files named special.test.ts are unignored because the pattern appear after the pattern that ignore files ending with .test.js.
    2. Only the test directory at the project's root is ignored because the pattern doesn't start with **/.
    3. The linter is executed on the src directory at the project's root only.

    Because includes pattern have a different pattern format than include and ignore we made some adjustments:

    • We added the pattern ** in files.includes to ensure that all files are included before ignoring some of them.
    • We added the prefix **/ for patterns that must match at any level of the file hierarchy.

  • noUndeclaredVariables no longer reports TypeScript types.

    In TypeScript projects, developers often use global declaration files to declare global types. Biome is currently unable to detect these global types. This creates many false positives for noUndeclaredVariables.

    TypeScript is better suited to perform this kind of check. As proof of this, TypeScript ESLint doesn't provide any rule that extends the no-undef ESLint rule.

    This is why Biome 1.9 introduced a new option checkTypes which, when it is set to false, ignores undeclared type references. The option was set to true by default.

    This option is now set to false by default. To get the previous behavior, you have to set checkTypes to true:

    {
  "linter": {
    "rules": {
      "correctness": {
        "noUndeclaredVariables": {
          "level": "on",
          "options": { "checkTypes": true }
        }
      }
    }
  }
}

  • The rule noUnusedVariables no longer reports unused function parameters. Use noUnusedFunctionParameters.

  • Fixed #5564. noTypeOnlyImportAttributes now ignores files ending with the extension .ts when the type field of package.json is set to commonjs.

  • The Biome formatter no longer adds a trailing comma in .json files, even when json.formatter.trailingCommas is set to true.

  • Prettier 3.4 introduced a change in their normalization process of string literals: it no longer unescapes useless escape sequences. Biome now matches the new behavior of Prettier when formatting code. This affects the JSON and JavaScript formatters.

  • Reduced accepted values for formatter options:

    • The option --quote-style doesn't accept Single and Double anymore.
    • The option --quote-properties doesn't accept AsNeeded and Preserve anymore.
    • The option --semicolons doesn't accept AsNeeded and Always anymore.
    • The option --arrow-parenthesis doesn't accept AsNeeded and Always anymore.
    • The option --trailing-commas doesn't accept ES5, All and None anymore.
    • The option --attribute-position doesn't accept Single and Multiline anymore.

  • Removed the option enumMemberCase from the lint rule useNamingConvention.

    enumMemberCase is an option that allows to customize the enforced case for TypeScript's enum members. The option was introduced prior to the conventions option that allows to do the same thing.

    The following configuration...

    {
  "linter": {
    "rules": {
      "style": {
        "useNamingConvention": {
          "level": "on",
          "options": {
            "enumMemberCase": "PascalCase"
          }
        }
      }
    }
  }
}

    ...must be rewritten as:

    {
  "linter": {
    "rules": {
      "style": {
        "useNamingConvention": {
          "level": "on",
          "options": {
            "conventions": [
              {
                "selector": { "kind": "enumMember" },
                "formats": ["PascalCase"]
              }
            ]
          }
        }
      }
    }
  }
}

    Run biome migrate --write to turn enumMemberCase into conventions automatically.

  • Removed support for BIOME_LOG_DIR.

    The environment variable BIOME_LOG_DIR isn't supported anymore.

    Use BIOME_LOG_PATH instead.

  • Remove deprecated rules.

    The following deprecated rules have been deleted:

    • noInvalidNewBuiltin
    • noNewSymbol
    • useShorthandArrayType
    • useSingleCaseStatement
    • noConsoleLog

    Run the command biome migrate --write to update the configuration.

  • Removed the deprecated indentSize option.

    The deprecated option indentSize, and its relative CLI options, has been removed:

    • Configuration file: formatter.indentSize
    • Configuration file: javascript.formatter.indentSize
    • Configuration file: json.formatter.indentSize
    • CLI option --indent-size
    • CLI option --javascript-formatter-indent-size
    • CLI option --json-formatter-indent-size

    Use indentWidth and its relative CLI options instead.

  • Removed ROME_BINARY. Use BIOME_BINARY instead.

  • Removed support for legacy suppressions.

    Biome used to support "legacy suppressions" that looked like this:

    // biome-ignore lint(complexity/useWhile): reason

    This format is no longer supported.

  • Removed support for max_line_length from .editorconfig, as it isn't part of the official spec anymore.

  • Removed support for rome-ignore suppression comments.

    Use biome-ignore suppression comments instead.

  • Removed support for rome.json.

    Use biome.json or biome.jsonc instead.

  • Removed the option all from the linter.

    The options linter.rules.all and linter.rules.<group>.all has been removed.

    The number of rules in Biome have increased in scope and use cases, and sometimes some of them can conflict with each other.

    The option was useful at the beginning, but now it's deemed harmful, because it can unexpected behaviours in users projects.

    To automatically remove it, run the following command:

    biome migrate --write

  • Removed the option trailingComma from the configuration and the CLI. Use the option trailingCommas instead:

    {
  "javascript": {
    "formatter": {
-      "trailingComma": "es5"
+      "trailingCommas": "es5"
    }
  }
}

    -biome format --trailing-comma=es5
+biome format --trailing-commas=es5

  • Removed --apply and --apply-unsafe.

    The CLI options --apply and --apply-unasfe aren't accepted anymore. Use --write and --write --unafe instead:

    -biome check --apply-unsafe
+biome check --write --unsafe

    -biome check --apply
+biome check --write

  • Removed support for assert syntax.

    Biome now longer supports the assert syntax, use the new with syntax instead

    -import {test} from "foo.json" assert { for: "for" }
-export * from "mod" assert { type: "json" }
+import {test} from "foo.json" with { for: "for" }
+export * from "mod" with { type: "json" }

  • Fixed #5495: The rule noBlankTarget has been updated to accept the rel="noopener" in addition to rel="noreferrer". In addition, an option has been added that allows rel="noreferrer" to be disabled.

    The rule has been moved from the a11y group to the security group.

  • The rule useImportRestrictions has been renamed to noPrivateImports, and its functionality has been significantly upgraded.

    Previously, the rule would assume that any direct imports from modules inside other directories should be forbidden due to their package private visibility.

    The updated rule allows configuring the default visibility of exports, and recognises JSDoc comments to override this visibility. The default visibility is now **public**, but can be set to **package**, or even **private**. Refer to the documentation of the rule to understand how to leverage the JSDoc comments.

    noPrivateImports is now recommended by default.

  • The Biome daemon now reuses its workspace across connections. This allows multiple clients to reuse the same documents and other cached data that we extract from them.

    This primarily affects our IDE extensions: If you open multiple IDEs/windows for the same project, they'll connect to the same daemon and reuse each other's workspace.

    The Biome CLI is unaffected unless you opt in with the --use-server argument.

  • Biome no longer treats too large files as errors.

    Previously, files that exceed the configured size limit would throw an error, and the CLI would exit with an error code.

    Now, the CLI ignores the file, emits an information diagnostic and doesn't exit with an error code.

  • Change the group of some rules, promote nursery rules and update the recommended rule set.

    The following rules have been moved to a new group:

    New rules are incubated in the nursery group. Once stable, we promote them to a stable group. Use the biome migrate command to automatically migrate nursery rules that have been promoted.

    The following CSS rules have been promoted:

    The following GraphQL rules have been promoted:

    The following JavaScript rules have been promoted:

    Moreover, the following JavaScript rules are now recommended:

    And the following style rules are no longer recommended:

  • Update the default severity level of lint rules.

    Every diagnostic emitted by Biome has a severity level set to error, warn, or info. Previously, all recommended lint rules had a default severity level set to error. All other lint rules had a default severity level set to warn.

    We have adjusted the default severity level of every rule, whether recommended or not, to better communicate the severity that a diagnostic highlights.

    • Rules that report hard errors, likely erroneous code, dangerous code, or accessibility issues now have a default severity level of error.
    • Rules that report possibly erroneous codes, or code that could be cleaner if rewritten in another way now have a default severity level of warn.
    • Rules that reports stylistic suggestions now have a default severity level of info.

    You can use the CLI option --diagnostic-level=error to display only errors, or --diagnostic-level=warning to display both errors and warnings. By default, all diagnostics are shown. You can also use the CLI option --error-on-warnings to make the command fail when warnings are emitted.

  • Reworked some recommended rules recommended to be less pedantic and blocking. This is a breaking change if your project relied on those rules to block the CI in case of violations; if that's the case, you should raise their severity level to error.

    Some rules aren't recommended anymore, and some others return a different severity.

    The following rules return a warning diagnostic:

    • noDelete
    • noForEach
    • noSuspiciousSemicolonInJsx
    • noThisInStatic
    • noUnusedLabels

    The following rules return an information diagnostic:

    • noUselessCatch
    • noUselessConstructor
    • noUselessEmptyExport
    • noUselessFragments
    • noUselessLabel
    • noUselessLoneBlockStatements
    • noUselessSwitchCase
    • noUselessTernary
    • noUselessThisAlias
    • noUselessTypeConstraint
    • noFlatMapIdentity

    The following rules aren't recommended anymore:

    • noDelete
    • noForEach

    The rule noRenderReturnValue and useExhaustiveDependencies are only recommended when the react domain is enabled.

  • Renamed the global option --skip-errors to --skip-parse-errors.

  • Remove the code action quickfix.suppressRule.

    The code action quickfix.suppressRule was removed in favour of two new code actions:

    • quickfix.suppressRule.inline.biome: a code action that adds a suppression comment for each violation.
    • quickfix.suppressRule.topLevel.biome: a code action that adds a suppression comment at the top of the file which suppresses a rule for the whole file.

    Given the following code

    let foo = "one";
debugger;

    The code action quickfix.suppressRule.inline.biome will result in the following code:

    // biome-ignore lint/style/useConst: <explanation>
let foo = "one";
// biome-ignore lint/suspicious/noDebugger: <explanation>
debugger;

    The code action quickfix.suppressRule.topLevel.biome, instead, will result in the following code:

    /** biome-ignore lint/suspicious/noDebugger: <explanation> */
/** biome-ignore lint/style/useConst: <explanation> */

let foo = "one";
debugger;

  • Changed default formatting of package.json.

    When Biome encounters a file called package.json, by default it will format the file with all objects and arrays expanded.

    - { "name": "project", "dependencies": { "foo": "latest" } }
+ {
+  "projectName": "project",
+  "dependencies": {
+    "foo": "^1.0.0"
+  }
+ }

  • The organizeImports is now part of Biome Assist.

  • The rule noVar now belongs to the suspicious group

  • The rule useWhile now belongs to the complexity group.

  • The rule useImportExtensions has been updated to suggest actual file extensions instead of guesses based on hueristics.

    As part of this, the suggestedExtensions option has been removed. A simpler, new option called forceJsExtensions has been introduced for those who use tsc's "module": "node16" setting.

    The rule also no longer reports diagnostics to add an extension when the path doesn't exist at all, with or without extension.

  • Fixed #4545: useNamingConvention now correctly ignores declarations inside TypeScript's external modules.

    The following interface name is no longer reported by the rule:

    declare module "myExternalModule" {
  export interface my_INTERFACE {}
}

  • The rule useAltText no longer checks the element's attributes containing object spread.

    The following code doesn't trigger the rule anymore:

    <img src="test.png" alt={alt} {...restProps}></img>

  • The rule useNamingConvention no longer accepts non-ASCII characters by default.

    Prior to Biome 2.0, non-ASCII names were accepted by default. They are now rejected.

    For example, the following code is now reported as invalid by the useNamingConvention rule.

    let johnCafé;

    If you want to allow non ASCII filenames and non-ASCII identifiers, you need to set the requireAscii options in your Biome configuration file to false:

    {
    "linter": {
        "rules": {
            "style": {
                "useFilenamingConvention": {
                    "level": "on",
                    "options": {
                        "requireAscii": false
                    }
                }
                "useFilenamingConvention": {
                    "level": "on",
                    "options": {
                        "requireAscii": false
                    }
                }
            }
        }
    }
}

  • Renamed the rule noUnnecessaryContinue to noUselessContinue. Run the command biome migrate to update your configuration.

  • Renamed the rule noMultipleSpacesInRegularExpressionLiterals to noAdjacentSpacesInRegex. Run the command biome migrate to update your configuration.

Minor Changes

  • An option called allowNoReferrer has been added to the noBlankTarget rule.

    By default, noBlankTarget accepts both rel="noopener" and rel="noreferrer" with links that have target="_blank". This is because the latter implies the former, so either one is sufficient to mitigate the security risk.

    However, allowing rel="noreferrer" may still be undesirable, because it can break tracking, which may be an undesirable side-effect. As such, you can set allowNoReferrer: false to only accept rel="noopener".

  • Added new option javascript.parser.jsxEverywhere. This new option allows to control whether Biome should expect JSX syntax in .js/.mjs/.cjs files.

    When jsxEverywhere is set to false, having JSX syntax like <div></div> inside .js/.mjs/.cjs files will result in a parsing error.

    Despite the name of the option, JSX is never supported inside .ts files. This is because TypeScript generics syntax may conflict with JSX in such files.

    This option defaults to true.

  • Add a new JS assist rule - useSortedKeys which enforces ordering of a JS object properties. This rule will consider spread/calculated keys e.g [k]: 1 as non-sortable. Instead, whenever it encounters a non-sortable key, it will sort all the previous sortable keys up until the nearest non-sortable key, if one exist. This prevents breaking the override of certain keys using spread keys.

    Source: https://perfectionist.dev/rules/sort-objects

    // Base
// from
const obj = {
  b: 1,
  a: 1,
  ...g,
  ba: 2,
  ab: 1,
  set aab(v) {
    this._aab = v;
  },
  [getProp()]: 2,
  aba: 2,
  abc: 3,
  abb: 3,
  get aaa() {
    return "";
  },
};
// to
const obj = {
  a: 1,
  b: 1,
  ...g,
  set aab(v) {
    this._aab = v;
  },
  ab: 1,
  ba: 2,
  [getProp()]: 2,
  get aaa() {
    return "";
  },
  aba: 2,
  abb: 3,
  abc: 3,
};

  • Added the new rule noFloatingPromises.

  • Added the new rule noImportCycles.

  • Added the new rule noTsIgnore.

  • Added the new rule noUnwantedPolyfillio.

  • Added a format option expand for Javascript and JSON formatters. The option allows to enforce the formatting of arrays and objects on multiple lines, regardless of their length. It has three options:

    When set to auto (default), objects are expanded if the first property has a leading newline. Arrays are collapsed when they fit to a single line. For example, both styles below are considered as already formatted:

    const obj = {
  foo: "bar",
};

    const obj = { foo: "bar" };

    When set to always, objects and arrays are always expanded.

    When set to never, objects and arrays are never expanded when they fit in a single line. It is equivalent to Prettier's Object Wrap option with collapse.

  • The nursery rule noUnresolvedImports has been added.

    Importing a non-existing export is an error at runtime or build time. With this rule, Biome can detect such incorrect imports and report errors for them.

    Note that if you use TypeScript, you probably don't want to use this rule, since TypeScript already performs such checks for you.

  • The rule noFocusedTests can now detect the usage of focused tests inside loops.

    // invalid
describe.only.each([["a"], ["b"]])("%s", (a) => {});
it.only.each([["a"], ["b"]])("%s", (a) => {});
test.only.each([["a"], ["b"]])("%s", (a) => {});

// valid
describe.each([["a"], ["b"]])("%s", (a) => {});
it.each([["a"], ["b"]])("%s", (a) => {});
test.each([["a"], ["b"]])("%s", (a) => {});

  • Linter groups now accept new options to enable/disable all rules that belong to a group, and control the severity of the rules that belong to those groups.

    For example, you can downgrade the severity of rules that belong to "style" to emit "info" diagnostics:

    {
  "linter": {
    "rules": {
      "style": "info"
    }
  }
}

    You can also enable all rules that belong to a group using the default severity of the rule using the "on" option:

    {
  "linter": {
    "rules": {
      "complexity": "on"
    }
  }
}

  • Biome assist is a new feature of the Biome analyzer. The assist is meant to provide actions. Actions differ from linter rules in that they aren't meant to signal errors.

    The assist will provide code actions that users can opt into via configuration or via IDEs/editors, using the Language Server Protocol.

    The assist is enabled by default. However, you can turn if off via configuration:

    {
  "assist": {
    "enabled": false
  }
}

    You can turn on the actions that you want to use in your configuration. For example, you can enable the useSortedKeys action like this:

    {
  "assist": {
    "actions": {
      "source": {
        "useSortedKeys": "on"
      }
    }
  }
}

    Alternatively, IDE/editor users can decide which action to apply on save directly from the editor settings, as long as the assist is enabled.

    For example, in VS Code you can apply the useSortedKeys action when saving a file by adding the following snippet in settings.json:

    {
  "editor.codeActionsOnSave": {
    "source.biome.useSortedKeys": "explicit"
  }
}

    In Zed, you can achieve the same by adding the following snippet in ~/.config/zed/settings.json:

    {
  "code_actions_on_format": {
    "source.biome.useSortedKeys": true
  }
}

  • Biome migrate eslint outputs a better overriding behavior.

    A Biome rule can have multiple ESLint equivalent rules. For example, useLiteralKeys has two ESLint equivalent rules: dot-notation and @typescript-eslint/dot-notation.

    Previously, Biome wouldn't always enable a Biome rule even if one of its equivalent rules was enabled. Now Biome uses the higher severity level of all the equivalent ESLint rules to set the severity level of the Biome rule.

    The following ESLint configuration...

    {
  "rules": {
    "@typescript-eslint/dot-notation": "error",
    "dot-notation": "off"
  }
}

    ...is now migrated to...

    {
  "linter": {
    "rules": {
      "complexity": {
        "useLiteralKeys": "error"
      }
    }
  }
}

    ...because error is higher than off.

  • Add useSymbolDescription.

  • Enhanced the command migrate eslint. Now the command shows which ESLint rules were migrated, and which rules aren't supported yet.

    ./eslint.config.js migrate ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  ℹ 42% (3/7) of the rules have been migrated.

  ℹ Migrated rules:

  - getter-return
  - prefer-const
  - @typescript-eslint/require-await

  ℹ Rules that can be migrated to an inspired rule using --include-inspired:

  - @typescript-eslint/parameter-properties

  ℹ Rules that can be migrated to a nursery rule using --include-nursery:

  - @typescript-eslint/switch-exhaustiveness-check

  ℹ Stylistic rules that the formatter may support (manual migration required):

  - semi

  ℹ Unsupported rules:

  - block-scoped-var

configuration ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  ℹ Migration results:

  - ./biome.json: configuration successfully migrated.

  • Suppression of syntax rules

    Added support for suppressing syntax rules. Syntax rules are particular rules meant to complement the parser, hence they can't be configured.

    Biome now allows to suppress those rules. This can, for example, be useful in case the rule is affected by a bug. However, this is more an escape hatch, so if a syntax rule requires a suppression, please file an issue.

    Example:

    // biome-ignore syntax/correctness/noTypeOnlyImportAttributes: bug
import type { MyType } from "my-esm-pkg" with { "resolution-mode": "import" };

    Biome now requires all biome-ignore-start suppressions to have an equivalent biome-ignore-end comment.

  • Add a new lint rule noConstantBinaryExpression. This rule is inspired from ESLint's no-constant-binary-expression rule.

  • The CLI options --only and --skip now accept rule and action names without prefixing the group name.

    Previously --only=noDebugger was rejected. You had to add the group name: --only=suspicious/noDebugger.

  • Fixed #3574: noUnusedImports now reports empty named imports and suggests their removal.

    The rule now suggests the removal of empty named imports such as:

    - import {} from "mod";

  • Added the new rule useAdjacentGetterSetter, which enforces getters and setters for the same property to be adjacent in class and object definitions.

    Example (Invalid): Name getter and setter are not adjacent:

    class User {
  get name() {
    return this._name;
  }
  constructor() {}
  set name(value) {
    this._name = value;
  }
}

    **Example (Invalid): Getter should go before the setter.

    const user = {
  set name(value) {
    this._name = value;
  },
  get name() {
    return this._name;
  },
};

    Example (Valid): Name getter and setter are adjacent:

    class User {
  get name() {
    return this._name;
  }
  set name(value) {
    this._name = value;
  }
  get age() {
    return this._age;
  }
  set age(age) {
    this._age = age;
  }
}

  • Added new rule useConsistentResponse which suggests to use static Response.json() and Response.redirect() methods instead of new Response when possible.

    Example:

    new Response(JSON.stringify({ value: 1 }));
Response.json({ value: 1 });

  • Biome users can now configure code actions from linter rules as well as assist actions directly in the settings of their IDE/editor.

    For example, let's consider the lint rule noSwitchDeclarations, which has an unsafe fix. Previously, if you wanted to use this rule, you were "forced" to enable it via configuration, and if you wanted to apply its fix when you saved a file, you were forced to mark the fix as safe:

    {
  "linter": {
    "rules": {
      "correctness": {
        "noSwitchDeclarations": {
          "level": "error",
          "fix": "safe"
        }
      }
    }
  }
}

    Now, you can benefit from the code action without making the fix safe for the entire project. IDEs and editors that are LSP compatible allow to list a series of "filters" or code actions that can be applied on save. In the case of VS Code, you will need to add the following snippet in the settings.json:

    {
  "editor.codeActionsOnSave": {
    "quickfix.biome.correctness.noSwitchDeclarations": "explicit"
  }
}

    Upon save, Biome will inform the editor the apply the code action of the rule noSwitchDeclarations.

  • Fixed #3401: noUnusedImports now keeps comments separated from the import with a blank line.

    For example:

      // Orphan comment

- // Header comment
- import {} from "mod";

  • Added a new propertyAssignment option to the noParameterAssign rule. This option allows to configure whether property assignments on function parameters are permitted. By default, propertyAssignment is set to allow. Setting it to deny enforces stricter immutability by disallowing property mutations on function parameters.

  • The formatter option bracketSpacing is now also supported in JSON files.

  • useValidTypeof now accepts comparisons with variables.

    Previously, the rule required to compare a typeof expression against another typeof expression or a valid string literal. We now accept more cases, notably comparison against a variable:

    if (typeof foo === bar) {
  // ...
}

  • Added the new rule noNestedComponentDefinitions, which disallows nested component definitions in React components.

    This rule is useful for preventing potential performance issues and improving code readability by ensuring that components are defined at the top level.

    Example (Invalid):

    function ParentComponent() {
  function ChildComponent() {
    return <div>Hello</div>;
  }
  return <ChildComponent />;
}

    Example (Valid):

    function ChildComponent() {
  return <div>Hello</div>;
}
function ParentComponent() {
  return <ChildComponent />;
}

  • Added the new rule noDestructuredProps, which disallow the use of destructured props in Solid projects.

  • You can now enable lint rules using the default severity suggested by Biome using the new variant "on", when enabling a rule.

    For example, the default severity of the rule style.noVar is error, so you would use "on", and then linting a code that uses var, will result in an error:

    {
  "linter": {
    "recommended": false,
    "rules": {
      "style": {
        "noVar": "on"
      }
    }
  }
}

    // main.js
var name = "tobias";

    The command biome lint main.js will result in an error due to the default severity assigned to noVar.

    Refer to the documentation page of each rule to know their suggested diagnostic severity, or use the command biome explain <RULE_NAME>:

    biome explain noVar

  • Biome VCS integration now supports nested ignore files.

    For git, if a .gitignore is found in a nested folder root/packages/foo/, and it contains the pattern dist/, only files and directories inside root/packages/foo/dist are matched.

  • Added the rule useUniqueElementIds. This rule disallows the use of static IDs in React components. It encourages to generate unique IDs for accessibility purposes using useId.

    The following code is now reported as invalid:

    function App() {
  return <div id="static-id" />;
}

    The following code is now reported as valid:

    import { useId } from "react";
function App() {
  const id = useId();
  return <div id={id} />;
}

  • Added the new JavaScript rule useConsistentObjectDefinition rule. The rule enforces a consistent style for the definition of objects:

    By default, the rule enforces a shorthand style:

    const validShorthand = {
  // Property shorthand
  foo,

  // Method shorthand
  method() {
    return "method";
  },
};

    Alternatively, the rule can be configured to enforce an explicit style:

    const invalidExplicit = {
  // Basic property shorthand violations
  foo: foo,

  // Method shorthand violations
  method: function () {
    return "method";
  },
};

  • Introduced more advanced logging capabilities:

    Every Biome CLI command can now be passed a --log-file=<path> argument, which will write all log messages for that invocation to the given path instead of stdout.

    In addition, the --log-level parameter now also accepts a tracing value. When --log-level=tracing is used, Biome also prints timing information from tracing spans to the log.

    Combined with Biome's ability to print logs in JSON format, and the jq command line utility, this allows you to perform advanced analysis on Biome's internal performance.

    For example, if you want to figure out which paths take the longest when building the module graph, you can use the following commands:

    biome lint --log-level=tracing --log-kind=json --log-file=tracing.json
cat tracing.json | jq '. | select(.span.name == "update_module_graph") | { path: .span.path, time_busy: .["time.busy"], time_idle: .["time.idle"] }' > filtered.json

    Now you will have a file called filtered.json with all the relevant timings, together with the paths used during the invocations.

  • Added options to suspicious/noConfusingLabels to allow specific labels.

  • Fixed #4549: noUnknownProperty now accepts more known CSS properties.

    - ['anchor-default', 'anchor-scroll', 'inset-area', 'position-animation', 'position-fallback', 'position-fallback-bounds', 'position-try-options']
+ ['anchor-scope', 'interpolate-size', 'line-fit-edge', 'masonry', 'masonry-auto-tracks', 'masonry-direction', 'masonry-fill', 'masonry-flow', 'masonry-slack', 'masonry-template-areas', 'masonry-template-tracks', 'position-anchor', 'position-area', 'position-try-fallbacks', 'position-visibility', 'scroll-start-target', 'text-box', 'view-transition-class', 'view-transition-group']

    This change replaces deprecated properties, improving CSS validation.

  • LSP clients can now override the configuration path for each workspace, by responding to workspace/configuration requests.

  • Added the new CSS rule noImportantStyles, which prevents the use of !important inside CSS declarations.

  • Biome now emits a warning diagnostic if the configuration contains an out-of-sync schema URL.

  • Introduced a new configuration setting files.experimentalScannerIgnores.

    This setting may be used to configure a set of file and folder names that should be unconditionally ignored by Biome's scanner.

    Biome maintains an internal list of default ignore entries, which is based on user feedback and which may change in any release. This setting allows overriding this internal list completely.

    This is considered an advanced feature that users should not need to tweak themselves, but they can as a last resort. This setting can only be configured in root configurations, and is ignored in nested configs.

    Entries must be file or folder names. Specific paths and globs are not supported.

    Examples where this may be useful:

    {
  "files": {
    "experimentalScannerIgnores": [
      // You almost certainly don't want to scan your `.git` folder, which
      // is why it's already ignored by default:
      ".git",

      // But the scanner does scan `node_modules` by default. If you
      // *really* don't want this, you can ignore it like this:
      "node_modules",

      // But it's probably better to ignore a specific dependency.
      // For instance, one that happens to be particularly slow to scan:
      "RedisCommander.d.ts",
    ],
  },
}

    Please be aware that rules relying on the module graph or type inference information may be negatively affected if dependencies of your project aren't (fully) scanned.

  • Added the new rule useSingleJsDocAsterisk which enforces JSDoc comment lines to start with a single asterisk.

    // Invalid
/**
 ** Description
 */

// Valid
/**
 * Description
 */

  • The CLI flag --javascript-attribute-position was renamed to --javascript-formatter-attribute-position for consistency.

  • Introduced the domains linter feature. The Biome linter now has a new way to opt-in rules, with a concept called domains.

    Domains can be seen as concepts shared by different rules.

    You can enable and disable multiple rules that belong to a domain. When you assign "all", Biome will enable all the rules, when you assign "none", Biome will disable the rules, when you assign "recommended", Biome will enable all rules of the domain that are recommended.

    // biome.jsonc
{
  linter: {
    domains: {
      test: "all", // all rules that belong to this domain are enabled
      react: "recommended", // only the recommended rules from this domain are enabled
      solid: "none", // rules related to Solid are disabled
    },
  },
}

    New domains introduced:

    • test: it will enable rules:
      • noExportsInTest
      • noExcessiveNestedTestSuites
      • noDuplicateTestHooks
      • noFocusedTests And it will inject the following globals:
      • after
      • afterAll
      • afterEach
      • before
      • beforeEach
      • beforeAll
      • describe
      • it
      • expect
      • test
    • next: it will enable rules for Next.js projects:
      • useExhaustiveDependencies
      • useHookAtTopLevel
      • noImgElement
      • noHeadImportInDocument
      • noHeadImportInDocument
    • react: it will enable rules for React projects:
      • useExhaustiveDependencies
      • useHookAtTopLevel
    • solid: it will enable rules for Solid projects:
      • noReactSpecificProps

    For more information regarding how Biome enables rules via domains, please refer to the documentation page of each rule.

  • Biome now prints diagnostics sorted by their severity. The order is the following:

    1. information
    2. warning
    3. error

    This means that error diagnostics are printed last, so users can see them first.

  • Added the new rule useIterableCallbackReturn, which enforces consistent return values in iterable callbacks.

    The following methods require a return value in their callback:

    • every
    • filter
    • find
    • findIndex
    • findLast
    • findLastIndex
    • flatMap
    • map
    • reduce
    • reduceRight
    • some
    • sort
    • toSorted — from (when called on Array)

    The rule disallows a return value inside the callback of the method forEach.

    Examples:

    [].map(() => {
  // Missing return value
});

    [].forEach(() => {
  return 1; // Disallowed
});

  • Added the new rule noReactPropAssign, based on the react-hooks rule react-hooks/react-compiler

    The following code is now reported as invalid:

    function Foo(props) {
  props.bar = `Hello ${props.bar}`;
  return <div>{props.bar}</div>;
}

    The following code is now reported as valid:

    function Foo({ bar }) {
  bar = `Hello ${bar}`;
  return <div>{bar}</div>;
}

  • Added new rule noBitwiseOperators, which disallows bitwise operators.

  • The Biome analyzer now supports a new top-level suppression. These suppression have to be placed at the top of the file, and they must be followed by two newlines (\n\n\).

    The analyzer rules specified inside the block comment will be suppressed for the whole file.

    In the example, we suppress the rules lint/style/useConst and lint/suspicious/noDebugger for the whole file:

    // main.js
/**
 * biome-ignore-all lint/style/useConst: i like let
 * biome-ignore-all lint/suspicious/noDebugger: needed now
 */

let path = "/path";
let _tmp = undefined;
debugger;

    In this other example, we suppress lint/suspicious/noEmptyBlock for a whole CSS file:

    /**
/* biome-ignore-all lint/suspicious/noEmptyBlock: it's fine to have empty blocks
*/

a {
}
span {
}

    A new diagnostic is emitted if biome-ignore-all suppression isn't placed at the top of the file:

    file.js:3:1 suppressions/incorrect ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  ! Top level suppressions can only be used at the beginning of the file.

    2 │ let foo = 2;
  > 3 │ /**
      │ ^^^
  > 4 │ * biome-ignore-all lint/style/useConst: reason
  > 5 │ */
      │ ^^
    6 │ let bar = 33;

  i Rename this to biome-ignore

    2 │ let foo = 2;
    3 │ /**
  > 4 │ * biome-ignore-all lint/style/useConst: reason
      │   ^^^^^^^^^^^^^^^^
    5 │ */
    6 │ let bar = 33;

  • Added the new rule useNumericSeparators, which encourages the use of numeric separators to improve readability.

  • useImportExtensions now checks imports with sub extensions.

    - import 'styles.css'
+ import 'styles.css.ts'

  • It's possible to override the option files.maxSize. This option is helpful if you need to process specific files that exceed the default maxSize:

    {
	"overrides": [{
		"includes": ["dist/**"]
		"files": {
			"maxSize": 20000
		}
	}]
}

  • Added the new CLI option called --threads to the ci command. It allows to control the numbers of threads that can be used when using the Biome CLI.

    It's possible to use the environment variable BIOME_THREADS as an alternatives.

    This feature is useful when running the CLI in environments that have limited resources, for example CI/CD.

    biome ci --threads=1
BIOME_THREADS=1 biome ci

  • Added the new rule useObjectSpread, which prefers object spread syntax over Object.assign() when constructing new objects.

    Example (Invalid): Using Object.assign with an empty object:

    Object.assign({}, foo);
Object.assign({}, { foo: "bar" });

    Example (Invalid): Using Object.assign with object literal as first argument:

    Object.assign({ foo: "bar" }, baz);
Object.assign({}, baz, { foo: "bar" });

    Example (Valid): Using object spread syntax:

    ({ ...foo });
({ ...baz, foo: "bar" });

    Example (Valid): Modifying existing objects is allowed:

    Object.assign(foo, { bar: baz });
Object.assign(foo, bar, baz);

  • Added an option to the lint command called --suppress. The new option suppresses a violation instead of applying a rule fix. The option accepts a string that is used as reason of the suppression comment.

    When running the following command, it will add the suppression comment:

    biome lint --write --suppress="Migration to Biome"

    debugger;
foo == bar;

    + // biome-ignore lint/suspicious/noDebugger: Migration to Biome
debugger;
+ // biome-ignore lint/suspicious/noDoubleEquals: Migration to Biome
foo == bar;

  • Add an ignoreRestSiblings option into noUnusedVariables.

    When this option is set to false, the rule will not ignore variables that created using the rest pattern:

    {
  "linter": {
    "rules": {
      "correctness": {
        "noUnusedVariables": {
          "level": "error",
          "options": {
            "ignoreRestSiblings": false
          }
        }
      }
    }
  }
}

    const { lorem, ...test } = bar; // the variable "test" will trigger the rule
console.log(lorem);

  • Upgraded some unsafe fixes to safe fixes.

    The following rules have now a safe fix:

  • Added support for monorepos. The feature will work out of the box for the majority of the users. If your project has nested configuration files, use the command biome migrate from the root of the project.

    Monorepo support in Biome is done in a single way. Create a biome.json at the root of the project. This configuration file is now called the root configuration. Then, each nested configuration file must specify the new field "root": false.

    We also introduced a new microsyntax for extending a nested configuration from the root configuration, which is "extends": "//". This new syntax means “this config extends from the root config”. When using this microsyntax, you may omit the "root": false field as it is implied.

    Note that nested configs are not required to extend from the root config, and you can still have independent nested configs, as well as nested configs that extend from other files. In those cases, "root": false must be specified explicitly.

  • Added support for formatting .html files. The formatting is considered experimental, and it's only opt-in via configuration:

    {
  "html": {
    "formatter": {
      "enabled": true
    }
  }
}

    Biome formatter attempts to format as Prettier, however some default options might differ.

    An option html.formatter.selfCloseVoidElements allows to control whether the trailing / of void elements should be printed.

    By default, Biome formatter will remove the /:

    - <input />
+ <input>

    If you come from Prettier and you want to keep the same formatting behaviour, you should set the option to "always":

    {
  "html": {
    "formatter": {
      "selfCloseVoidElements": "always"
    }
  }
}

    - <input>
+ <input />

    Use to the command biome migrate prettier to apply this change automatically.

  • Added an unsafe fix to the rule useExhaustiveDependencies.

    For example, this violation will provide the following code fix:

    import { useEffect } from "react";

function MyComponent() {
  let a = 1;
  useEffect(() => {}, [a]);
}

      × This hook specifies more dependencies than necessary: a

    3 │ function MyComponent() {
    4 │   let a = 1;
  > 5 │   useEffect(() => {}, [a]);
      │   ^^^^^^^^^
    6 │ }
    7 │

  i This dependency can be removed from the list.

    3 │ function MyComponent() {
    4 │   let a = 1;
  > 5 │   useEffect(() => {}, [a]);
      │                        ^
    6 │ }
    7 │

  i Unsafe fix: Remove the extra dependencies from the list.

    5 │ ··useEffect(()·=>·{},·[a]);
      │                        -

  • The rule useExhaustiveDependencies now reports a diagnostic when the dependency list is not an array literal.

  • Added the new rule useIndexOf, based on the unicorn rule prefer-array-index-of

  • Added a new rule useExhaustiveSwitchCases, which detects any missing cases for switch statements. Currently, it supports only literal union types.

    For example:

    type Day =
  | "Monday"
  | "Tuesday"
  | "Wednesday"
  | "Thursday"
  | "Friday"
  | "Saturday"
  | "Sunday";

const day: Day = "Monday";
let result = 0;

switch (day) {
  case "Monday": {
    result = 1;
    break;
  }
}

    The switch statement is missing other cases than 'Monday', which will cause a runtime error. To fix this issue, add missing cases or a default case to the statement.

  • Fixed #4416: The rules useExportType and useImportType now ignore TypeScript declaration files.

  • Added the new rule useForComponent.

    This rule enforces usage of Solid's <For /> component for mapping an array to JSX elements.

  • Added new lint rule noShadow, a port of eslint's no-shadow.

    This rule disallows variable declarations from shadowing variables declared in an outer scope. For example:

    const foo = 1;

function bar() {
  const foo = 2; // This variable shadows the outer foo
}

  • Add style option for the useImportType rule.

    The rule now allows enforcing an import style for importing types. See the rule documentation for more details.

  • Added the new rule useJsonImportAttribute to enforce the use of import attributes for JSON modules.

    This rule ensures that all imports of .json files include the with { type: "json" } assertion, which is required to inform the JavaScript runtime that the imported file should be parsed as JSON.

    - import jsonData from './data.json';
+ import jsonData from './data.json' with { type: "json" };

    - import jsonData from './data.json' with { someOtherAttribute: "value" };
+ import jsonData from './data.json' with { type: "json", someOtherAttribute: "value" };

    This rule is based on the proposal in issue #6043.

  • useLiteralKeys now handles numeric keys and is declared as being the same rule as the ESLint no-useless-computed-key rule.

  • useNamingConmvention now ignores unused variables prefixed with an underscore _.

    This avoids conflicts with the unsafe fix of noUnusedVariables. The following code is now accepted because the variable is unused and prefixed with an underscore.

    const _Unknown_Style = 0;

  • The package now requires v2 of the WebAssembly packages. The internal APIs of Workspace are now camelCase.

  • The rule useArrayLiterals now provides a code fix.

    - const xs = new Array();
+ const xs = [];

    The code fix is currently marked as unsafe. We plan to make it safe in a future release of Biome.

  • The command migrate is now able to migrate nested configuration files.

  • Added the new rule noRestrictedElements, which prevents use of the specified HTML elements and components.

  • Added the new lint rule noAwaitInLoop.

Patch Changes

  • Fix #5001, where the CSS formatter removes whitespace from selector preceded by a comment

  • Fixed noUnusedVariables rule to suggest unsafe fix for unused function declarations.

  • Fixed a false positive of noUselessEscapeInRegex where \k was reported as useless in non-Unicode regular expressions.

  • Fixed an issue where the ordering of the diagnostics wasn't predictable.

  • Fixed a bug where the environment variable BIOME_CONFIG_PATH wasn't correctly picked up.

  • Biome logs a warning in case a folder contains biome.json and biome.jsonc, and it will use biome.json by default.

  • noUndeclaredVariables is now able to bind read of value to a type-only import in ambient contexts (#4526).

    In the following code, A is now correctly bound to the type-only import. Previously, A was reported as an undeclared variable.

    import type { A } from "mod";

declare class B extends A {}

  • Fix #4317, setter parameter can contain a trailing comma, the following example will now parsed correctly:

    export class DummyClass {
  set input(value: string) {}
}

  • Fix #4575, don't wrap selector indentation after css comments.

  • Fix #4258, where fixed css parse error with @-moz-document url-prefix().

  • Fixed #4391: Some files from the .vscode directory are no longer incorrectly parsed as JSON.

  • The biome format command now correctly handles the --skip-errors option, allowing it to skip files with syntax errors and continue formatting the remaining valid files. When this option is used, skipped syntax errors are reported as information, since the user is already aware of them.

  • biome migrate eslint now correctly resolves the scoped package named eslint-config.

  • Fixed #3836: The CSS parser will now correctly parse the following:

    .foo {
  color: red;
}

  • Fixed a bug where the related diagnostics attached to the main diagnostics didn't have a correct message.

  • Fixed noAccumulatingSpread not reporting calls to Object.assign. The following code will now be reported:

    let a = [{ a: 1 }, { b: 2 }];
a.reduce((acc, val) => Object.assign(acc, val), []);

  • The summary reporter doesn't take --max-diagnostics into account anymore.

  • Fixed #4553: noUselessFragments will now correctly fix JSX attributes:

    <Suspense
  fallback={
    <>
      <span>Loading...</span>
    </>
  }
>
  {children}
</Suspense>

    becomes:

    <Suspense fallback={<span>Loading...</span>}>{children}</Suspense>

  • Fixed #4528: biome migrate eslint now correctly handles shared ESLint configuration that don't follow the ESLint naming convention.

    ESLint recommends that a package that exports a shared configuration be prefixed with eslint-config- or simply named eslint-config. This is only a recommendation. Packages that export shared configurations can have arbitrary names. Biome is now able to load any package.

  • Fixed #4993: useAwait now correctly warn on functions with decorator with callback argument.

  • Fixed #4756: noDuplicateProperties now throws lint errors properly when we use @supports.

  • Fixed #5981, where noUnknownPseudoClass didn't take :global into consideration when cssModules is enabled.

  • Fixed #2406: Biome longer expands properties of object type annotations in the only function parameter to align with Prettier.

  • Fixed #4740: biome migrate eslint now correctly handles ESLint configuration with null values in file lists.

  • Fixed #4202: Align with Prettier in formatting test functions.

  • Fixed #342: The JavaScript parser now properly handles unterminated string literals, such as:

    function Comp() {
  return (
      <a rel="

  • Fixed a bug where syntax rules didn't provide an automatic way to suppress the rule. Now the LSP will show supression actions if a syntax rule is violated.

  • Fixed a CSS parser error: @-moz-document url-prefix(https://example.com) and @-moz-document domain(example.com) are now valid.

  • Fixed #4967: The fix for useArrowFunction no longer breaks function bodies starting with {.

  • Fixed #5998. The rule noUnknownPseudoElement now correctly cheks names of pseudo-element functions.

  • Fixed #5024: Added useJsxKeyInIterable rule to React domain.

  • Fixed #5410. Biome now correctly parse an .editorconfig that includes character classes in glob patterns.

  • Fixed #2260: The LSP server now returns correct text edits for the specified range in textDocument/rangeFormatting and textDocument/onTypeFormatting requests.

  • noUnusedVariables no longer reports top-level variables in a global declaration file as unused.

  • Type exports now support renaming types to default.

    The following code is now parsed successfully:

    export { type A as default } from "./b.ts";

  • Added proper support for arrow functions in the lint rule https://biomejs.dev/linter/rules/use-explicit-type/

  • The rule useNamingConvention no longer suggests renaming top-level variables in a global declaration file.

  • Improved context in error messages when migrating Prettier configurations

  • Allowed single spaces in useConsistentCurlyBraces rule.

  • Fixed #4413: The GraphQL formatter no longer adds a new line at the start of block comments on Windows.

  • Fixed #5407. Now the noUnusedImports code fix correctly keeps top-level comments that were attached to lone imports.

  • Fixed #3859: the --skip-parse-errors option is now applied to commands: lint, check, and ci.

  • The rage command now prints the configuration path relative to the working directory, if applicable.

  • Fixed #5606: We now correctly handle .mjs extensions in Node.js packages with "type": "commonjs".

  • Fixed #1597: useExhaustiveDependencies no longer gets confused about the stability of dependencies by parentheses or type assertions.

  • Fixed #4751 by checking fragments inside JSXElement and conditional expressions.

    For example, the following two cases will now be reported:

    <section>
  <>
    <div />
    <div />
  </>
</section>

    showFullName ? <>{fullName}</> : <>{firstName}</>;

  • The rule noFallthroughSwitchCase no longer panics on some incomplete code snippets.

  • Fixed #5007: Resolved false positives in noMissingVarFunction for container-name.

  • Fixed #4841: Shebang and top leading comments in .cjs files are now handled correctly

    Example: shebang only (keep it as is)

    #!/usr/bin/env node

    Example: comments only (keep it as is)

    // comment

    Example: with shebang

    - #!/usr/bin/env node"use strict";
+ #!/usr/bin/env node
+ "use strict";
let some_variable = "some value";

    Example: with comment

    - // comment
- "use strict"; // comment
+ "use strict";
+ // comment
let some_variable = "some value";

    Example: with shebang and comment

    - #!/usr/bin/env node"use strict";
- // comment
+ #!/usr/bin/env node
+ "use strict";
+ // comment
let some_variable = "some value";

  • Fixes useExhaustiveDependencies missing dependencies being defined after the hook itself failure.

    Example:

    import { useState, useEffect } from "react";

function MyComponent() {
  useEffect(() => {
    console.log(a);
  }, []);

  let a = 1;
}

  • Fixed #4714: Suppression comments no longer fail on functions that themselves contain suppression comments.

    This now works correctly:

    // biome-ignore lint/complexity/useArrowFunction: this suppression now works
const foo0 = function (bar: string) {
  // biome-ignore lint/style/noParameterAssign: even if there are other suppressions inside
  bar = "baz";
};

  • Add @vitest/eslint-plugin to list of Biome rule sources

  • Fixed useHookAtTopLevel rule to properly detect React components wrapped in memo and forwardRef, and correctly handle property accessors in control flow analysis.

    The rule now correctly identifies hooks in components like:

    const TestMemo = memo(
  forwardRef((props, ref) => {
    useEffect(() => {
      const [test, setTest] = useState(1); // now properly flagged
    }, []);
    return <div ref={ref}>test</div>;
  }),
);

    And properly handles property accessors:

    function ReactComponent() {
  const testObj = {
    get print() {
      return "hello"; // no longer considered component return
    },
  };
  const callback = useCallback(() => {}, []);
  return <></>;
}

  • noMisleadingCharacterClass no longer panics on malformed escape sequences that end with a multi-byte character (#4587).

  • Fixed the flag --bracket-spacing that was duplicated between the global configuration and the language-specific override for JavaScript.

  • Fixed #4715: The useJsxKeyInIterable rule now reports missing keys inside switch and if statements.

    const data = [
  { value: "a", type: "string" },
  { value: 9, type: "number" },
  { value: "c", type: "string" },
];

const MyComponent = () => {
  return (
    <>
      {/* if statements */}
      {data.map((x) => {
        if (x.type === "string") {
          return <div>{x.value}</div>; // no key, emits diagnostic
        } else {
          return <div>{x.value}</div>; // no key, emits diagnostic
        }
      })}

      {/* switch statements */}
      {data.map((x) => {
        switch (x.type) {
          case "string":
            return <div>{x.value}</div>; // no key, emits diagnostic
          case "number":
            return <div>{x.value}</div>; // no key, emits diagnostic
          default:
            return <div key={x.value}>{x.value}</div>;
        }
      })}
    </>
  );
};

  • Fixed #4121: The CSS formatter no longer indents a selector when it has leading comments.

  • Fixed an issue where react lint rules could panic Biome when some incorrect code was analyzed.

  • Fixed #4982: the JavaScript parser now throws a syntax error for the following code:

    type T = import;
type U = typeof import;

  • Fixed a bug with the --verbose CLI flag. Now the printed paths are relative to the working directory.

  • Fixed noNoninteractiveElementToInteractiveRole mistakenly flagging <li role="treeitem">,

  • Fixed #4622: Our JavaScript parser can now gracefully handle situations where we detect the parser to have stalled.

    This means we don't fail with an assertion anymore, but invalid code can trigger a regular diagnostic in such cases.

  • Fixed #342: The JavaScript parser now correctly handles invalid object member names, such as:

    ({
  params: { [paramName: string]: number } = {}
})

  • Fixed #6211: previously the import organizer emitted broken code when it merged an import at the start of the file with another import and placed the merged result after a third import.

    The following code is now correctly organized:

    - import { B } from "bc";
- import { C } from "bc";
  import { A } from "a";
+ import { B, C } from "bc";

  • Fixed #4334: The formatter no longer inserts trailing a comma inside dynamic import expressions.

  • Fixed #5629: useHookAtTopLevel no longer report false-positives where the hook is at the top-level in a class method.

  • Fixed #5900: biome migrate eslint now support a nested files property in ESLint flat configs.

  • Fixed #3895: noUnusedImports no longer reports used values imported as types in an external module.

  • Fixed a case where the code fix for noUselessFragments would remove more than just the fragment.

  • Fixed #5919. Now Biome correctly loads the configuration passed via --config-path when its path starts with ./ e.g. --confi-path=./project/biome.json

  • Fixed #5031: CSS formatting has been improved for numbers:

    .class {
-	padding: .5em;
-	marding: 1.0;
+	padding: 0.5em;
+	marding: 1;
}

  • Fixed #5989 where large octal escape sequences led to an overflow.

  • Implement improved error handling for the supports at rule

  • Fix #5053, now the rule correctly handles console.log inside arrow function expressions.

  • Fix #6105: css lint rules useSortedProperties should skip unknown properties.

  • Fixed #3229: Made formatting of compound selectors more consistent.

  • Fixed a bug where passing --max-diagnostics=0 would return a zero code even when errors were emitted.

  • Fixed a bug where Biome didn't report any error when --stdin-file-path didn't have any extension. Now Biome returns an error if --stdin-file-path doesn't have an extension.

  • Fixed #5601: The useSortedClasses rule now properly preserves the original JSX quote style when sorting utility classes, preventing syntax errors.

  • The fix for useSelfClosingElements was marked as safe and the error message was improved.

  • Fixed overrides that include language-specific settings from having an effect for some languages

  • Fixed #6144: noUnusedImports reported incorrectly imports that were used as the type of parameters with the same name. In the following code, the import name was reported as unused.

    import name from "mod";
function f(name: name.Readable): void {}

  • The lint rules useNamingConvention and useFilenamingConvention now accept character escapes at the start of a regex group.

    Both these rules provide options that allow matching names against a regular expression. Previously, an escaped character at the start of a regex group reported an error. They are now accepted.

    For example, the following configuration is now valid doesn't emit an error anymore.

    {
  "linter": {
    "rules": {
      "style": {
        "useNamingConvention": {
          "level": "on",
          "options": {
            "conventions": [
              {
                "selector": {
                  "kind": "let"
                },
                "match": "(\\n.*)"
              }
            ]
          }
        }
      }
    }
  }
}

  • Fixed #5617: noDuplicateObjectKeys now transfers the leading comments of the removed member.

  • Fixed #5409: noParameterAssign now reports reassigned parameter of unparenthesized arrow functions.

    The following code is now reported as invalid.

    const f = (param) => {
  param = {}; // Reassigning a function parameter is confusing.
};

  • Fixed #4875: Relative file paths are now clickable in the Jetbrains IDE terminal.

  • Fixed #4719: bracketSameLine now performs as expected when a comment is placed before the last JSX attribute.

  • Fixed #4564: Biome no longer panics when a multi-byte character is found in a unicode escape sequence.

  • Fixed #4950: Resolved a false positive of character class range operators in regular expressions.

  • Fixed handling of top-level variables by useExplicitType rule (#5932). Biome now allows all variables with explicit annotations, as well as variables with trivial RHS. Biome no longer emits duplicated errors when an untyped function is assigned to an untyped variable.

  • Fixed #4947: The useTemplate lint rule now ignores concatenated literals folded to multiple lines.

  • Fixed #4568: Broken import statements no longer can cause a panic in useExhaustiveDependencies.

  • Fixed #6042: noUselessEscapeInString now reports useless escapes after skipping ${ in template literals.

  • Fixed #6229 where the fix of noUnusedImports emitted an invalid syntax. Now the following case emits a code fix that is syntactically correct:

    import Used, { NotUsed } from "foo";

Used();

  • Fix #5682: Object patterns with a nested assignment pattern no longer break properties.

    For example, the following code:

    const { foo: { bar } = { bar: false } } = props;

    is used to be formatted into:

    const { foo: { bar } = { bar: false } } = props;

    , while Prettier does not expand properties in this case.

  • Fixed #5620, noConsole rule now correctly handles indirect console.log calls and references.

  • When pulling code actions from the LSP, now the first choice suggested by the client will be the safe fix.

  • Fixed #6022, now the rule noDuplicateProperties does't trigger properties defined inside the @keyframes at rule

  • Enhanced the error message of the diagnostics emitted when Biome can't parse a suppression comment.

  • Fixed link to the docs inside CLI markup

  • Fixed a bug where a suppression comment with an empty explanation was valid.

    Now a suppression comment // biome-ignore lint: will raise a warning diagnostic.

  • Fixed #4026: Comments in grid-template are no longer moved by the formatter.

  • Fixed #3394: Resolved a false positive in useSortedClasses.

  • Fixed #342 and #4562: Biome no longer crashes when a declare statement is followed by an unexpected token.

  • Fixed false positive in the rule noUnknownFunction where the tech function was incorrectly flagged as an unknown function.

  • Fixed #4511: noLabelWithoutControl now detects <button> tags as input.

  • Fixed #6039: noUselessEscapeInString no longer reports \${ escape in template literals.

  • Fixed #5985, which caused the import organizer to fail the merging of a default import with a named import. The following code is now correctly organized:

    - import moment from 'moment';
- import { Moment } from 'moment';
+ import moment, { Moment } from 'moment';

  • Fixed an issue where the explain command didn't the diagnostic category when a rule was explained.

  • Improved the diagnostic of the rule noUnusedVariables. The rule message now provides the name of the unused binding.

  • Added RegExpStringIterator to the analyzer globals.

  • Fixed #4208: noUselessFragments now handles JsxAttributeInitializerClause, ensuring that fragments inside expressions like <A b=<></> /> are preserved.

  • Fixed #4533: noUnknownPseudoClass no longer reports pseudo classes after a webkit scrollbar pseudo element.

    The following code will no longer report a diagnostic:

    ::-webkit-scrollbar-thumb:hover {
}

  • Updates the useJsxKeyInIterable rule to more closely match the behavior of the ESLint plugin (e.g. mark the whole fragment as incorrect when no key is present). This also adds the option to check shorthand fragments (<></>)

  • Renamed the rule noDuplicatedFields to noDuplicateFields. Run the command biome migrate to update your configuration.

  • Fixed an issue where ignored files were incorrectly tracked by the Daemon.

  • Fixed #5116: noUnknownPseudoElement now supports ::slotted.

  • Fixed #5979: biome search now correctly skips files that don't match the pattern's target language.

  • Fixed #4323: Fixed the case where useSemanticElement accidentally showed recommendations for role="searchbox" instead of role="search".

  • Support setting indent_size to tab in .editorconfig, the following config will not cause error:

    root = true
[*]
indent_size = tab

  • Fixed #4565: noControlCharactersInRegex no longer panics when it encounters an unterminated unicode escape sequence.

  • Fixed #5770, Biome's configuration file is now respected by the migrate command during migration

  • Fixed an issue where the lexer didn't report errors for unterminated regex or string literals, such as the following cases:

    "string
'str
/\\217483

  • The useKeyWithClickEvents rule has been improved with better support for ARIA roles.

    Key improvements:

    1. Accessibility checks:

    Now the rule correctly handles the following cases:

    • If an element is hidden from screen readers
    • If an element has the presentation role
    • If an element is interactive
    // No errors
<div aria-hidden="true" onClick={() => {}} /> // hidden from screen reader
<div role="presentation" onClick={() => {}} /> // presentation role
<button onClick={() => {}} /> // interactive role

    This change ensures the rule is more accurate and helpful.

    1. Checks spread syntax:

    Spread syntax used to be ignored, but has been changed to be pointed out for more stringent checking.

    // Errors
<div {...props} onClick={() => {}} />
// No errors
<div {...props} onClick={() => {}} onKeyDown={foo} />;
    1. Refactor:

    Now the rule uses the aria roles to determine if an element is interactive.

    The changes shown here are meant to be closer to the original jsx-eslint's click-events-have-key-events rule.

  • Fixed #6029: A new line before the semicolon in the previous statement is now kept after formatting.

    For example, the following code:

    const foo = 3;

[1, 2, 3].map((x) => x * 2);

    when javascript.formatter.semicolons is always, it becomes:

    const foo = 3;

[1, 2, 3].map((x) => x * 2);

    when javascript.formatter.semicolons is asNeeded, the original code is considered as already formatted.

  • useArrayLiterals now reports all expressions using the Array constructors.

    Previously, the rule reported only use of the Array constructor in expressions statements.

    // This was reported
new Array();
// This was not reported
const xs = new Array();

  • Improved error handling for the container at-rule.

  • Fixed #4665: the LSP previously identified .cjs files as ESM files, making rules like noRedundantUseStrict reports incorrectly valid "use strict" directives.

  • Fixed #5382: useExportType no longer reports an identifier that bound by both a variable and a type.

  • Fixed #5826: useNumericSeparators no longer reports single-digit 0.

  • Fixed #5307, where CSS value lists were wrapped in a way that did not preserve semantic structure.

    Biome now ensures that CSS value lists follow a more readable format, aligning with Prettier's behavior.

    Before:

    * {
  box-shadow:
    0 0 0 1px #fff,
    0 0 0 3.2px rgba(89, 89, 235, 0.25),
    0 0 0 3.2px rgba(89, 89, 235, 0.25),
    0 0 0 3.2px red,
    0 0 0 3.2px rgba(89, 89, 235, 0.25);
}

    After:

    * {
  box-shadow:
    0 0 0 1px #fff,
    0 0 0 3.2px rgba(89, 89, 235, 0.25),
    0 0 0 3.2px rgba(89, 89, 235, 0.25),
    0 0 0 3.2px red,
    0 0 0 3.2px rgba(89, 89, 235, 0.25);
}

  • tsconfig.*.json files will now be treated the same as tsconfig.json files.

  • The summary reporter now prints the files processed and the files fixed when passing the --verbose flag.

  • Fixed #5693: useRegexLiterals now correctly handle useless escaped character in string literals.

  • useRegexLiterals now suggests a correct fix when the pattern contains an escaped anti-slash \/.

    Previously the rule suggested the following fix that led to a syntax error:

    - new RegExp("\/");
+ /\\//

    The rule now suggests a correct fix:

    - new RegExp("\/");
+ /\//

    Fixed #5487.

  • Fixed useConsistentCurlyBraces breaks react/no-unescaped-entities rule

    Added a check for forbidden characters: >, ", ' and }. If any of these characters are detected, curly braces will be preserved.

    Example:

    function MyComponent() {
  return <Foo>Jupiter {">"} Venus</Foo>;
}

  • The rule useNamingConvention now suggests a rename that preserves uppercase if possible.

    For instance, Biome suggested renaming HTMLWrapper as htmlWrapper:

    - import HTMLWrapper from "HTMLWrapper.tsx";
+ import htmlWrapper from "HTMLWrapper.tsx";

  function component() {
-   return <HTMLWrapper> </HTMLWrapper>;
+   return <htmlWrapper> </HTMLWrapper>;
  }

    Since both PascalCase and CamelCase are accepted, Biome now suggests renaming HTMLWrapper as HtmlWrapper:

    - import HTMLWrapper from "HTMLWrapper.tsx";
+ import HtmlWrapper from "HTMLWrapper.tsx";

  function component() {
-   return <HTMLWrapper> </HTMLWrapper>;
+   return <HtmlWrapper> </HTMLWrapper>;
  }

  • Fix a parsing error when a JsxElementName is JsxMemberExpression, and a JsLogicalExpreesion before it without a semicolon.

    The following case will now not throw error:

    import React from "react";

let b = 0;

function A() {
  const a = b > 0 && b < 1;

  return <React.Fragment>{a}</React.Fragment>;
}

  • Fixed Biome being unable to parse insert_final_newline = unset in EditorConfig files.

  • Fixed #4530: useArrowFunction now preserves directives.

    Previously the rule removed the directives when a function expression was turned into an arrow function. The rule now correctly keeps the directives.

    - const withDirective = function () {
+ const withDirective = () => {
    "use server";
    return 0;
  }

  • Fixed #4855: useSortedClasses now suggests code fixes that match the JSX quote style of the formatter.

View originalPermalink
How 2.0.0 went
2.0.0-beta.6Pre-release

CLI v2.0.0-beta.6

Added 13
  • Implement useUniqueElementIds rule
  • Implement useConsistentResponse rule
  • Implement useIndexOf rule
  • Implement useObjectSpread rule
  • Add plugins to override config
  • Add monorepo support
Changed 4
  • Move noArguments and noCommaOperator to complexity
  • Change default syntax from explicit to shorthand for useConsistentObjectDefinition
  • Scan project based on ScanKind in LSP
  • Handle numeric keys in useLiteralKeys
Fixed 3
  • Fix recommended and domains
  • Do not ignore required files
  • Process root ignore first

From Biome

What's Changed
Other changes
New Contributors

Full Changelog: https://github.com/biomejs/biome/compare/@biomejs/biome@2.0.0-beta.5...@biomejs/biome@2.0.0-beta.6

View originalPermalink
How 2.0.0-beta.6 went
2.0.0-beta.5Pre-release

CLI v2.0.0-beta.5

Added 6
  • Support rule without group in `--only` and `--skip` flags
  • Added maxSize option to files configuration
  • YAML parser now handles implicit block mapping
  • Implemented useAdjacentGetterSetter rule
  • YAML parser allows omitting value in explicit mapping
  • Implemented noNestedComponentDefinitions rule
Changed 3
  • useConst rule is now recommended
  • Some unsafe fixes upgraded to safe fixes
  • noUselessContinue rule moved to complexity category
Fixed 10
  • Fixed paths are relative in the reporter
  • noDuplicateProperties rule no longer tracks @keyframes
  • Core only triggers on ServiceDataNotification per scan
  • Analyzer fixed plugin diagnostic suppression and resolved double diagnostics
  • noUselessEscapeInString rule avoids false positive for ${} escape in template literals
  • LSP scopes workspace/configuration request to workspace folder

From Biome

What's Changed
Other changes
New Contributors

Full Changelog: https://github.com/biomejs/biome/compare/@biomejs/js-api@v0.8.0-beta.2...@biomejs/biome@2.0.0-beta.5

View originalPermalink
How 2.0.0-beta.5 went
2.0.0-beta.4Pre-release

CLI v2.0.0-beta.4

Added 1
  • Migrate nested configuration files
Changed 3
  • Handle already migrated rules in migrate
  • Don't unpromote useNamingConvention in migrate
  • Improve error handling for the supports at rule in CSS parser
Fixed 7
  • Add a missing space between words in diagnostic for useDateNow
  • Avoid overflow in noUselessBackrefInRegex
  • Merge default and named imports in organizeImports
  • Take CSS modules into consideration in lint
  • Correct type for enforce-assist in ci
  • noUnknownPseudoElement selector check
  • Compare only the formatted range on range formatting in LSP

From Biome

What's Changed
Other changes

Full Changelog: https://github.com/biomejs/biome/compare/@biomejs/biome@2.0.0-beta.3...@biomejs/biome@2.0.0-beta.4

View originalPermalink
How 2.0.0-beta.4 went
2.0.0-beta.3Pre-release

CLI v2.0.0-beta.3

Added 13
  • Expose `getTypeInfo` in WebAssembly API
  • Implement `noShadow` rule for JavaScript
  • Add semantic model debug printer to workspace
  • Implement full project-level type inference
  • Add `noUselessBackrefInRegex` linting rule
  • Handle additional cases from typescript-eslint in `noShadow` rule
Fixed 9
  • Fix downgrading of project references
  • Ignore node_modules during traversal
  • Do not scan node_modules when using the light scanner
  • Fix panic error in package_json analyzer
  • Avoid false positive on single-digit 0 in useNumericSeparators
  • Mark whole fragment as incorrect if without key in JSX

From Biome

What's Changed
Other changes
New Contributors

Full Changelog: https://github.com/biomejs/biome/compare/@biomejs/biome@2.0.0-beta.2...@biomejs/biome@2.0.0-beta.3

View originalPermalink
How 2.0.0-beta.3 went
2.0.0-beta.2Pre-release

CLI v2.0.0-beta.2

Added 5
  • Update and move noBlankTarget rule
  • Make useNamingConvention ignore unused var prefixed with underscore
  • Implement noUnresolvedImports rule
  • Add data structures for type info
  • Add CSS rule noImportantStyles
Changed 2
  • Make useImportExtensions check imports with sub extensions
  • Improve useKeyWithClickEvents rule
Fixed 20
  • Keep comments in noUnusedImports
  • Better check in noDestructuredProps when inside a function
  • Push noVar member inside existing list during migration
  • Report non array literal deps list in useExhaustiveDependencies
  • Suppression for assist actions
  • Improve error messages when parsing Prettier configuration during migration

From Biome

What's Changed
Other changes
New Contributors

Full Changelog: https://github.com/biomejs/biome/compare/@biomejs/js-api@v0.8.0-beta.1...@biomejs/biome@2.0.0-beta.2

View originalPermalink
How 2.0.0-beta.2 went
2.0.0-betaPre-release

CLI v2.0.0-beta

Added 11
  • Add dedicated crate for globs
  • Add rule noTsIgnore to the linter
  • Add codegen crate utility
  • Implement noLowerCaseEnum rule
  • Implement range suppressions in analyzer
  • Add NoUnknownAtRule to the linter
Changed 6
  • Use papaya instead of DashMap for workspace documents
  • Stricter validation for globs
  • Remove the all option
  • Get rule severity from metadata severity
  • Add Workspace scanner
  • Treat tsconfig.*.json files as well known and allow comments and trailing comments by default
Fixed 2
  • Don't use organize imports implicitly in analyzer
  • Update Rust crates
Removed 1
  • Drop slotmap and simplify locking

From Biome

Read our blog post announcement.

What's Changed
Other changes
New Contributors

Full Changelog: https://github.com/biomejs/biome/compare/cli/v1.9.5-nightly.81fdedb...@biomejs/biome@2.0.0-beta

View originalPermalink
How 2.0.0-beta went

More in Developer Tools

View all
flutter

Flutter makes it easy and fast to build beautiful apps for mobile and beyond

flutter
DeepSeek Harness

DeepSeek Harness: Everything is a Plugin.

DeepSeek
tmux

A terminal multiplexer: many terminals in one screen, detachable and persistent.

tmux
markitdown

Python tool for converting files and office documents to Markdown.

microsoft
Claude Code

Anthropic's agentic coding tool for the terminal, IDE and web.

Anthropic
Godot Engine

The free, open-source 2D and 3D game engine.

Godot Foundation

Discussion

If you publish Biome, you can claim this product by proving you administer its repository.