All versions since 2.3.13

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:
```
1
<div @keydown.arrow-down="handler"></div>
2
<div @keydown.a="handler"></div>
3
<div @keydown.b="handler"></div>
4
<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.

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:
```
1
// Now correctly suggests `props.value` instead of `props.value[day]`
2
useMemo(() => {
3
  return WeekdayValues.filter((day) => props.value[day]);
4
}, [props.value]);
```
When calling methods on objects, only the object is suggested as a dependency:
```
1
// Now correctly suggests `props.data` instead of `props.data.forEach`
2
useMemo(() => {
3
  props.data.forEach((item) => console.log(item));
4
}, [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:
```
1
type A<B, C extends D> = // Some comment
2
undefined;
3
type A<B, C extends D> =
4
    // Some comment
5
    undefined;
```
#8916 ea4bd04 Thanks @ryan-m-walker! - Fixed #4013, where comments in member chains caused unnecessary line breaks.
```
1
// Before
2
aFunction.b().c.d();
3

4
// After
5
aFunction.b().c.d();
```

#8945 fa66fe3 Thanks @fireairforce! - Fixed #8354: Don’t remove quotes when type memeber is new.

1
// Input:
2
type X = {
3
  "new"(): string;
4
  "foo"(): string;
5
};
6

7
// Format Output:
8
type X = {
9
  "new()": string;
10
  foo(): string;
11
};

#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.

1
type Props = { msg: string };
2

3
// Arrow function without parentheses around `props`
4
const Component: React.FC<Props> = (props) => {
5
  const { msg } = props;
6
  // Previously, this incorrectly reported `msg` as unnecessary
7
  useEffect(() => console.log(msg), [msg]);
8
};

#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):
```
1
interface Foo {
2
  method(a: string): void;
3
}
```
Invalid code with style set to "method":
```
1
type Bar = {
2
  prop: (a: string) => void;
3
}
```
#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.).

1
let renderCount = 0;
2

3
export const MyComponent = () => {
4
  // `count` is now correctly recognized as a required dependency
5
  // because `renderCount++` can produce different values between renders
6
  const count = renderCount++;
7

8
  useEffect(() => {
9
    console.log(count);
10
  }, [count]); // no longer reports `count` as unnecessary
11
};

#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:
```
1
type Mutation {
2
  SetMessage(message: String): String
3
}
```
#8922 871b45e Thanks @siketyan! - Fixed #8829: Revamped the noGlobalDirnameFilename rule to catch many false negatives that have not been reported.

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.
```
1
// Invalid: nested promise that can be flattened
2
doThing().then(function () {
3
  return doOtherThing().then(console.log);
4
});
5

6
// Valid: flat promise chain
7
doThing()
8
  .then(() => doOtherThing())
9
  .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.
```
1
// Invalid: return at end of function is redundant
2
function foo() {
3
  doSomething();
4
  return;
5
}
```
#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.

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:

1
{
2
  "linter": {
3
    "rules": {
4
      "correctness": {
5
        "useHookAtTopLevel": {
6
          "options": {
7
            "ignore": ["useDebounce", "useCustomUtility"]
8
          }
9
        }
10
      }
11
    }
12
  }
13
}

#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:
Terminal window
```
1
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:
Terminal window
```
1
biome ci --reporter=rdjson --reporter-file=/etc/tmp/report.json
2
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:
Terminal window
```
1
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:
```
1
language json
2

3
pair(key = $k, value = $v)
```
Match objects with specific structure:
```
1
language json
2

3
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:
```
1
<iframe></iframe> <iframe title=""></iframe>
```
Valid:
```
1
<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.
```
1
interface MixedMembers {
2
  z: string;
3
  a: number;
4
  (): void;
5
  y: boolean;
6
}
```
Valid example (after using the assist).
```
1
interface MixedMembers {
2
  a: number;
3
  y: boolean;
4
  z: string;
5
  (): void;
6
}
```
#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:
Terminal window
```
1
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
```
1
{
2
  compilerOptions: {
3
    jsx: "react",
4
    jsxFactory: "h",
5
    jsxFragmentFactory: "Fragment",
6
  },
7
}
```
Component.jsx
```
1
import { h, Fragment } from "preact";
2

3
function App() {
4
  return <div>Hello</div>;
5
}
```
#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:
```
1
<html></html>
2
<html lang></html>
3
<html lang=""></html>
```
Valid:
```
1
<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:

1
import gql from "graphql-tag";
2

3
const PeopleCountQuery = gql`
4
  query PeopleCount {
5
    allPeople {
6
      totalCount
7
    }
8
  }
9
`;

1
import { graphql } from "./graphql";
2

3
const PeopleCountQuery = graphql(`
4
  query PeopleCount {
5
    allPeople {
6
      totalCount
7
    }
8
  }
9
`);

This feature is experimental and must be enabled explicitly in the configuration:

1
{
2
  "javascript": {
3
    "experimentalEmbeddedSnippetsEnabled": true
4
  }
5
}

#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:

1
{
2
  "linter": {
3
    "rules": {
4
      "source": {
5
        "useSortedKeys": {
6
          "options": {
7
            "groupByNesting": true
8
          }
9
        }
10
      }
11
    }
12
  }
13
}

With this option, the following unsorted object:

1
const object = {
2
  name: "Sample",
3
  details: {
4
    description: "nested",
5
  },
6
  id: 123,
7
};

Will be sorted as:

1
const object = {
2
  id: 123,
3
  name: "Sample",
4
  details: {
5
    description: "nested",
6
  },
7
};

#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:
```
1
// Invalid: hooks cannot be called at the module level.
2
useHook();
```
```
1
// Invalid: hooks must be called from another hook or component.
2
function notAHook() {
3
  useHook();
4
}
```
Valid:
```
1
// Valid: hooks may be called from function expressions, such as in tests.
2
test("my hook", () => {
3
  renderHook(() => useHook());
4

5
  renderHook(function () {
6
    return useHook();
7
  });
8
});
```
#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.
```
1
// Before
2
<div class="flex p-4 flex" />;
3

4
// After
5
<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:
```
1
{
2
  "css": {
3
    "parser": {
4
      "cssModules": true
5
    }
6
  }
7
}
```
#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.
```
1
// biome-ignore-all format: generated
2

3
const a = [];
4

5
const a = [];
6

7
const a = [];
```
#8255 da85e3c Thanks @ryan-m-walker! - Added support for the typed attr function. Addresses issue #6183.

Example
```
1
.btn {
2
  width: attr(data-size type(<length> | <percentage>), 0px);
3
}
```

#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:

1
<input type="submit" accesskey="s" value="Submit" />
2
<a href="https://webaim.org/" accesskey="w">WebAIM.org</a>
3
<button accesskey="n">Next</button>

Valid:

1
<input type="submit" value="Submit" />
2
<a href="https://webaim.org/">WebAIM.org</a>
3
<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
```
1
{
2
  lsp: {
3
    biome: {
4
      settings: {
5
        inline_config: {
6
          formatter: {
7
            indentStyle: "space",
8
            indentWidth: 4,
9
          },
10
        },
11
      },
12
    },
13
  },
14
}
```
#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:
```
1
function cook(scoops: IceCreamScoop[]): void;
2
function cook(cakeType: string): void;
```
Valid code with ignoreDifferentJsDoc set to true:
```
1
/** Does objs have "cow" inside it? */
2
function hasCow(objs: string[]): boolean;
3
/** @deprecated - convert to array */
4
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:

1
import styled from "styled-components";
2

3
const Foo = styled.div`
4
  display: flex;
5
  color: red;
6
`;

1
import styled from "@emotion/styled";
2

3
const Foo = styled(Box)`
4
  display: flex;
5
  color: red;
6
`;

1
import { css } from "@emotion/react";
2

3
const style = css`
4
  display: flex;
5
  color: red;
6
`;

However, snippets with interpolations are not supported yet. For example, the following snippet isn’t formatted:

1
import styled from "@emotion/styled";
2

3
const Foo = styled.div<{ color: string }>`
4
  display: flex;
5
  color: ${(props) => props.color};
6
`;

This feature is experimental and must be enabled explicitly in the configuration:

1
{
2
  "javascript": {
3
    "experimentalEmbeddedSnippetsEnabled": true
4
  }
5
}

#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:
```
1
{
2
  "options": {
3
    "extensionMappings": {
4
      "ts": "js"
5
    }
6
  }
7
}
```
#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:
Terminal window
```
1
biome check --only=suspicious/noDebugger src/**/*.js
2
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:
```
1
{
2
  "formatter": {
3
    "trailingNewline": false
4
  },
5
  "javascript": {
6
    "formatter": {
7
      "trailingNewline": true
8
    }
9
  }
10
}
```
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.
```
1
@function --transparent(--color <color>, --alpha <number>: 0.5) returns
2
  <color> {
3
  result: oklch(from var(--color) l c h / var(--alpha));
4
}
```
#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:

1
<button>Do something</button>
2
<button type="incorrectType">Do something</button>
3
<button type>Do something</button>
4
<button type />

Valid:

1
<button type="button">Do something</button>
2
<button type="reset">Do something</button>
3
<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:
Terminal window
```
1
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.
```
1
export const Route = createFileRoute('/')({
2
  component: HomeComponent,
3
})
4

5
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.
```
1
<div>a<div>b</div> c</div>
2
<div>
3
  a
4
  <div>b</div>
5
  c
6
</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:
```
1
{
2
  "overrides": [
3
    {
4
      "includes": ["**/*.svelte", "**/*.astro", "**/*.vue"],
5
      "linter": {
6
        "rules": {
7
          "style": {
8
            "useConst": "off",
9
            "useImportType": "off"
10
          },
11
          "correctness": {
12
            "noUnusedVariables": "off",
13
            "noUnusedImports": "off"
14
          }
15
        }
16
      }
17
    }
18
  ]
19
}
```
#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.

2.4.1

Patch Changes

#9092 6edd600 Thanks @ematipico! - Fixed #9052. This PR reverts changes introduced by https://github.com/biomejs/biome/pull/8519, which caused unwanted changes on how paths are resolved.
#9091 3bf674d Thanks @ematipico! - Fixed #9090, where SCSS files were incorrectly processed by Biome. This was a regressions caused by the latest developments for supporting SCSS out of the box.
#9100 66931a8 Thanks @siketyan! - Fixed #9081: The noUnknownPseudoElement rule no longer reports false positives for any known pseudo elements in CSS modules. This was a regression introduced in v2.4.0.
#9102 d01b903 Thanks @ematipico! - Fixed #9095, where Biome didn’t print anything in stdin mode. This was a regression caused by a recent, internal refactor.

2.4.2

Patch Changes

#9103 fc9850c Thanks @dyc3! - Fixed #9098: useImportType no longer incorrectly flags imports used in Svelte control flow blocks ({#if}, {#each}, {#await}, {#key}) as type-only imports.
#9106 f4b7296 Thanks @dyc3! - Updated rule source metadata for rules from html-eslint.

#8960 4a5ff40 Thanks @abossenbroek! - Added the nursery rule noConditionalExpect. This rule disallows conditional expect() calls inside tests, which can lead to tests that silently pass when assertions never run.

1
// Invalid - conditional expect may not run
2
test("conditional", async ({ page }) => {
3
  if (someCondition) {
4
    await expect(page).toHaveTitle("Title");
5
  }
6
});
7

8
// Valid - unconditional expect
9
test("unconditional", async ({ page }) => {
10
  await expect(page).toHaveTitle("Title");
11
});

#8960 4a5ff40 Thanks @abossenbroek! - Added the nursery rule noPlaywrightElementHandle. Prefers locators to element handles.
```
1
const el = await page.$(".btn");
```
#8960 4a5ff40 Thanks @abossenbroek! - Added the nursery rule noPlaywrightEval. Disallows page.$eval() and page.$$eval() methods.
```
1
await page.$eval(".btn", (el) => el.textContent);
```
#8960 4a5ff40 Thanks @abossenbroek! - Added the nursery rule noPlaywrightForceOption. Disallows the force option on user interactions.
```
1
await locator.click({ force: true });
```
#8960 4a5ff40 Thanks @abossenbroek! - Added the nursery rule noPlaywrightMissingAwait. Enforces awaiting async Playwright APIs.
```
1
const el = page.locator(".btn");
2
el.click(); // Missing await
```
#8960 4a5ff40 Thanks @abossenbroek! - Added the nursery rule noPlaywrightNetworkidle. Disallows deprecated networkidle wait option.
```
1
await page.goto(url, { waitUntil: "networkidle" });
```
#8960 4a5ff40 Thanks @abossenbroek! - Added the nursery rule noPlaywrightPagePause. Disallows page.pause() debugging calls in committed code.
```
1
await page.pause();
```
#8960 4a5ff40 Thanks @abossenbroek! - Added the nursery rule noPlaywrightUselessAwait. Disallows unnecessary await on synchronous Playwright methods.
```
1
// Incorrect - locator() is synchronous
2
const loc = await page.locator(".btn");
```
#8960 4a5ff40 Thanks @abossenbroek! - Added the nursery rule noPlaywrightWaitForNavigation. Prefers modern navigation APIs over deprecated waitForNavigation().
```
1
await page.waitForNavigation();
```
#8960 4a5ff40 Thanks @abossenbroek! - Added the nursery rule noPlaywrightWaitForSelector. Prefers locators over deprecated waitForSelector().
```
1
await page.waitForSelector(".btn");
```
#8960 4a5ff40 Thanks @abossenbroek! - Added the nursery rule noPlaywrightWaitForTimeout. Disallows hard-coded timeouts with waitForTimeout().
```
1
await page.waitForTimeout(5000);
```
#8960 4a5ff40 Thanks @abossenbroek! - Enhanced noSkippedTests to detect Playwright patterns (.fixme, test.describe, test.step, bracket notation, bare calls). Consolidated noPlaywrightSkippedTest into this rule.
#9101 0c0fb6f Thanks @siketyan! - Fixed #9080: The noUnusedVariables rule no longer reports a top-level Props interface or type alias as unused in Astro files.

#8960 4a5ff40 Thanks @abossenbroek! - Added the nursery rule useExpect. This rule ensures that test functions contain at least one expect() assertion.

1
// Invalid - test without assertion
2
test("no assertion", async ({ page }) => {
3
  await page.goto("/");
4
});
5

6
// Valid - test with assertion
7
test("has assertion", async ({ page }) => {
8
  await expect(page).toHaveTitle("Title");
9
});

#8960 4a5ff40 Thanks @abossenbroek! - Added the nursery rule usePlaywrightValidDescribeCallback. Validates that describe callback signatures are not async.
```
1
test.describe("suite", async () => {});
```

2.4.3 Latest

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.

All versions since 2.3.13

2.3.13

Patch Changes

2.3.14

Patch Changes

Examples

2.3.15

Patch Changes

2.4.0

Minor Changes

Combine two reporters in CI

Save reporter output to a file

`--watcher-kind`

`--watcher-polling-interval`

Example

Correctness

Suspicious

Complexity

Style

Examples

Patch Changes

`--log-file`

`--log-prefix-name`

`--log-path`

`--log-level`

`--log-kind`

Reduce dumping of LSP logs

2.4.1

Patch Changes

2.4.2

Patch Changes

2.4.3 Latest

Patch Changes