Skip to content
Biome
Docs Enterprise Playground
Blog

Version History
All versions

Version 2.6.2 Latest

Minor Changes

  • #11479 5c60ba8 Thanks @nhedger! - Added a --git flag to biome init. The flag enables Git VCS integration and sets vcs.useIgnoreFile to true in the generated configuration, even when the command runs outside a Git repository.

  • #11742 3a1356d Thanks @Netail! - Added the biome migrate stylelint command. It imports a Stylelint configuration and its ignore settings into your Biome configuration, mapping Stylelint rules to their Biome equivalents. Pass --write to apply the changes, and --include-inspired or --include-nursery to migrate additional rules.

  • #12318 774b5b5 Thanks @Netail! - Added the new assist action useGraphqlSortedDefinitions, which sorts the named definitions of a GraphQL document, such as types, type extensions, directives, fragments, and operations.

    Invalid:

    type User {
      id: ID!
    }
    

    enum Role {
      ADMIN
      USER
    }
    

    directive @auth on FIELD_DEFINITION

  • #6886 3479d15 Thanks @christymcgrory! - biome rage now shows the resolved files.includes and files.ignoreUnknown configuration.

  • #11102 0874b7f Thanks @gameroman! - Added support for useTailwindSortedClasses rule in HTML-ish files.

  • #10711 40de5a0 Thanks @soconnor-seeq! - Adds a new resolutionKind option for object-syntax plugin entries.

    This allows shared Biome configs in monorepos to load local Grit plugins from the package that declares them instead of resolving plugin paths from the consuming project.

    {
      "plugins": [
        { "path": "./grit/no-debugger.grit", "resolutionKind": "config" },
        { "path": "local-plugin.grit", "resolutionKind": "project" },
        { "path": "local-plugin.grit" }
      ]
    }

    Use resolutionKind: "config" to resolve the plugin from the configuration file that declares it. Use resolutionKind: "project" to resolve the plugin from the consuming project. When omitted, resolutionKind defaults to project. This only affects plugin resolution; includes still apply to end-user project files as usual.

  • #11432 4befd08 Thanks @ematipico! - Added biome inspect config to show resolved configuration values and their origins as human-readable diagnostics, including matching overrides.

    Configuration files can also extend other configurations up to ten levels deep. Repeated references to the same resolved file are ignored with an information diagnostic, while resolving multiple versions of one extended package produces an error.

  • #11477 ab05554 Thanks @nhedger! - Added automatic Git VCS integration when running biome init inside a Git repository, including from nested directories and Git worktrees. The generated configuration sets vcs.enabled and vcs.useIgnoreFile to true, with vcs.clientKind set to "git".

  • #11451 1ac4b09 Thanks @ematipico! - #### YAML is now supported

    Added support for formatting YAML files, both .yaml and .yml extensions

  • #11432 4befd08 Thanks @ematipico! - Configuration files can now recursively extend local files and npm package configurations up to ten levels. Every repeated reference participates in the merge, while resolving multiple versions of one extended package produces an error.

  • #11713 ac6a640 Thanks @dyc3! - Added support for Grit range() patterns, addressing #8454. Plugins can filter syntax nodes by optional start_line, start_column, end_line, and end_column bounds.

    For example, this pattern matches function calls contained entirely on line 2.

    range(start_line=2, end_line=2) as $call where {
        $call <: call_expression()
    }

  • #11244 0628b53 Thanks @ematipico! - Added the new CLI option --profile-type-inference to the commands lint and check.

    The profiler is designed to track the execution time of internal queries and operations, group them by file, and sort them from the most expensive to the least expensive.

    Terminal window
    biome lint --profile-type-inference
    profiler ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
    

      i Type inference profile (Biome <version>)
    

      src/index.ts
    

        Requests (top 5 of 12 groups; 28 source records; 46 executions)
          1. Promise classification <- nursery/noFloatingPromises
          ...
    

        Queries (top 8 of 25 groups; 61 source records; 94 executions)
          1. Promises / infer_expression_is_promise
          ...
    

        Whole-module inference (top 1 of 1 group; 1 source record; 1 execution)
          1. Import depth limit
          ...
    

      68 files omitted.
    

      ℹ To show all the information, use the --verbose option. The output might be very verbose, so it's advised to analyze a single file.
    

      $ biome lint --profile-type-inference --verbose ./path/to/file.ts

    Use --verbose to include detailed timings, attribution, breadth, and implementation references for the top source records in each file.

  • #12108 4fcb880 Thanks @ematipico! - Promoted 59 nursery rules to stable groups.

    Correctness

    Promoted the following rules to the correctness group with error severity. All of them are recommended:

    Suspicious

    Promoted the following rules to the suspicious group:

    Security

    Promoted useIframeSandbox to the security group with error severity.

    Performance

    Promoted the recommended rule useDomNodeTextContent to the performance group with warning severity.

    Complexity

    Promoted the following rules to the complexity group:

    Style

    Promoted the following rules to the style group with information severity:

  • #12206 0f984fb Thanks @dyc3! - Added the ignoreUsingDeclarations option to noUnusedVariables. When enabled, the rule no longer reports unused variables declared with using or await using, because these declarations clean up their value automatically even when the code never reads it.

    {
      "linter": {
        "rules": {
          "correctness": {
            "noUnusedVariables": {
              "options": { "ignoreUsingDeclarations": true }
            }
          }
        }
      }
    }

  • #12424 6a41490 Thanks @siketyan! - Removed the javascript.parser.gritMetavariables option. It was intended for internal use only and had no effect on how Biome parses JavaScript and TypeScript files. Biome now reports it as an unknown key and exits with a configuration error, so remove it from your configuration file.

  • #12055 54870c0 Thanks @ff1451! - Added the new assist action useGraphqlSortedVariables, which sorts the variable definitions of GraphQL operations.

    Invalid:

    query GetUser($userId: ID!, $includePosts: Boolean = false, $after: String) {
      user(id: $userId) {
        name
      }
    }

  • #12149 83df808 Thanks @dyc3! - Added the tailwind.stylesheet option, which points Biome at the CSS file that holds your Tailwind CSS configuration. useTailwindSortedClasses reads the @theme, @utility, and @custom-variant rules in that file and in the local files it imports, so your own theme values, utilities, and variants sort correctly.

    biome.json
    {
      "tailwind": { "stylesheet": "./src/app.css" }
    }
    src/app.css
    @import "tailwindcss";
    

    @theme {
      --color-brand: #3b82f6;
    }
    

    @utility content-auto {
      content-visibility: auto;
    }
    

    @custom-variant theme-midnight (&:where([data-theme="midnight"] *));

  • #12206 0f984fb Thanks @dyc3! - Added migration of the ignoreRestSiblings and ignoreUsingDeclarations options of no-unused-vars, @typescript-eslint/no-unused-vars, and unused-imports/no-unused-vars to noUnusedVariables in biome migrate eslint. Options that the ESLint configuration omits are set to ESLint’s defaults, so the migrated rule reports the same variables. For example, "no-unused-vars": "error" now migrates ignoreRestSiblings as false.

  • #11709 32d12cb Thanks @ematipico! - Added the new command biome inspect file, which returns developer information for the given file.

    Terminal window
    biome inspect file path/to/file.ts

    By default, the command returns the CST of the file. The command accepts the following arguments:

    • --ast, which returns the AST of a file.
    • --ir, which returns the formatting IR of a file.
    • --semantic, which returns the semantic model information of a file, if available.

  • #12221 cb571af Thanks @dyc3! - The rule noEmptySource now supports Markdown files. It reports files that contain only blank lines and HTML comments. For example, the following file is now reported:

    <!-- TODO -->

  • #12214 8955b56 Thanks @dyc3! - The rule noEmptySource now supports YAML files. It reports files with no documents and each document that has no content. For example, the second document in the following code is now reported:

    name: foo
    ---

  • #12033 8669e53 Thanks @dyc3! - Added the ignoreElements option to noRedundantRoles. Elements listed in this option are not checked by the rule.

    {
      "linter": {
        "rules": {
          "a11y": {
            "noRedundantRoles": {
              "options": {
                "ignoreElements": ["button"]
              }
            }
          }
        }
      }
    }

  • #12084 04e3750 Thanks @dyc3! - The rule noRestrictedElements now supports HTML, Vue, Svelte, and Astro files. For example, with { "elements": { "marquee": "Use CSS animations instead." } }, the following code is now reported:

    <marquee>Breaking news</marquee>

  • #11408 5a870f2 Thanks @ematipico! - Added support for distributing named Grit rules, rule presets, and configurations through packages that have a manifest file.

    The field plugins is used to export named Grit plugins, and configs is used to export named configurations. Package entries must select a named export: package/rule, package/presets/preset, or package/configs/config. Bare package entries aren’t supported. Rules consumed from another package are exposed under the consuming package’s name, while package authors continue to reference them by their source package inside the manifest. Configurations consumed from another package are also exposed under the consuming package’s name.

    biome-manifest.json
    {
      "$schema": "./node_modules/@biomejs/biome/manifest_schema.json",
      "version": 1,
      "plugins": {
        "rules": [
          "@org/shared-rules/noDeprecatedApi",
          "@org/strict-rules/presets/recommended",
          { "useCompanyLogger": "./rules/useCompanyLogger.grit" }
        ],
        "presets": {
          "recommended": [
            "useCompanyLogger",
            "@org/shared-rules/noDeprecatedApi"
          ]
        }
      },
      "configs": [
        "@org/shared-configs/configs/recommended",
        { "base": "./configs/base.json" }
      ]
    }

    The package must publish the manifest and every referenced file, for example, through the files field in package.json. Plugin authors can expose their manifest through the biome condition with ./biome-manifest.json as its value.

    package.json
    {
      "name": "@org/biome-plugin",
      "exports": {
        "biome": "./biome-manifest.json",
        "default": "./index.js"
      },
      "files": ["biome-manifest.json", "rules", "configs"]
    }

    And then, you can load the rules in your biome.json:

    biome.json
    {
      "plugins": [
        "@org/biome-plugin/useCompanyLogger",
        "@org/biome-plugin/presets/recommended"
      ]
    }

    For more information on how to create a plugin to distribute via npm, check the relative guide.

  • #12264 90f2eaf Thanks @dyc3! - Fixed #11082: glob patterns in the includes option of a plugin are now matched against file paths relative to the directory of the configuration file, the same as files.includes and overrides[].includes.

    Previously, the patterns were matched against the absolute file path, so a pattern such as packages/**/src/** matched no files and the plugin never ran.

    {
      "plugins": [
        { "path": "./my-plugin.grit", "includes": ["packages/**/src/**"] }
      ]
    }

    Patterns that start with **/ keep working. Patterns that contain the absolute path of the project no longer match, and must be rewritten as relative patterns.

  • #11133 1df00de Thanks @dlecan! - Added Android (Termux) support to the npm distribution (#1340). npm install @biomejs/biome now works on Termux through the new @biomejs/cli-android-arm64 and @biomejs/cli-android-x64 packages, which reuse the static musl binaries.

  • #12132 c5fadc4 Thanks @ematipico! - Added SCSS support throughout the toolchain. Biome can now format and lint .scss files, and recognizes .module.scss files as CSS Modules.

  • #10837 754432c Thanks @JamBalaya56562! - Added support for Google Apps Script (.gs) files.

    They are parsed as JavaScript scripts, so ES module import/export statements are reported as errors (Apps Script has no module system). Common Apps Script service globals (e.g. SpreadsheetApp, DriveApp, Logger) are recognized by noUndeclaredVariables and noGlobalAssign, and the list can be extended through the javascript.globals option.

  • #11126 fa63050 Thanks @Punisheroot! - Biome now recognizes files with the .htm extension as HTML.

  • #12291 6c6619e Thanks @dyc3! - Changed the dependency that enables the tailwind domain automatically. The domain is now enabled when package.json declares tailwindcss v4 or later, instead of v3 or later, because we are currently targeting Tailwind v4 support. The domain can always be enabled manually.

  • #11394 de1ad4c Thanks @ematipico! - #### Markdown is now supported

    Added support for linting and formatting Markdown files. The first version of Biome Markdown parser has 100% compatibility against CommonMark.

    Other variants of Markdown, such as GitHub Flavored Markdown (GFM) aren’t currently supported; however, we plan to support them soon.

    Formatter and Linter are automatically enabled by default.

    Markdown parser

    The parser comes with an opt-in option to enable frontmatter parsing. When enabled, the first thematic break --- is considered the opening fence of the frontmatter:

    biome.json
    {
      "markdown": {
        "parser": {
          "frontmatter": true
        }
      }
    }
    ---
    title: Lorem ipsum
    ---

    The parser also comes with an opt-in option called cjkFriendlyEmphasis. When enabled, the parser follows the CommonMark CJK-friendly amendments and recognizes emphasis markers, such as **, placed directly next to Chinese, Japanese, or Korean text. Enable it only when the tool that renders your Markdown supports the same amendments, because the option changes which text Biome formats and lints as emphasis:

    biome.json
    {
      "markdown": {
        "parser": {
          "cjkFriendlyEmphasis": true
        }
      }
    }

    With the option enabled, the following text is parsed as bold, instead of as literal **:

    **このアスタリスクは強調記号として認識されず、そのまま表示されます。**この文のせいで。
    Markdown formatter

    The formatter has great compatibility with Prettier formatting, more than 90% detected by our infrastructure. The formatter ships with a new option called proseWrap, that allows controlling how the Biome formatter should wrap paragraphs.

    For example, when proseWrap is set to always, the formatter will wrap the paragraph to match the configured lineWidth:

    biome.json
    {
      "markdown": {
        "formatter": {
          "lineWidth": 20,
          "proseWrap": "always"
        }
      }
    }
    Very tiny line width, so
    the paragraph is more
    compact.
    Markdown linter

    The linter ships with a few rules inspired by markdownlint. We plan to ship more rules in the upcoming releases.

    Some rules you can start using already:

    Markdown snippets

    Biome recognizes the code inside fenced code blocks, frontmatter, and HTML blocks as embedded languages, and formats it with the formatter of its language and your configuration:

    ```js
    const   value   =   {a:1,b:2}
    const value = { a: 1, b: 2 };
    ```

    HTML blocks are formatted only when the HTML formatter is enabled. A block with a syntax error stays as written, and Biome still formats the rest of the file.

    The option markdown.formatter.formatEmbeds controls this behavior, and it’s enabled by default. Set it to false to keep the code of these blocks as written:

    biome.json
    {
      "markdown": {
        "formatter": {
          "formatEmbeds": false
        }
      }
    }

    The command biome migrate prettier migrates the Prettier option embeddedLanguageFormatting to markdown.formatter.formatEmbeds.

    The option markdown.analyzeEmbeds runs the linter and assist actions on the same blocks, with the rules and actions of their language, and reports their syntax errors. It’s disabled by default, because fenced code blocks usually contain examples or partial code:

    biome.json
    {
      "markdown": {
        "analyzeEmbeds": true
      }
    }

  • #11634 04c3f5d Thanks @ematipico! - Added biome inspect plugins to list resolved rules by plugin and importing preset without loading or executing plugin code. Include globs show which files each import targets, and --path selects a target file. Fixed Markdown linter overrides and their configuration inspection.

  • #12282 a3fa0d6 Thanks @ff1451! - Added the new assist action useGraphqlSortedArguments, which sorts the arguments of GraphQL fields and directives, and the arguments declared by field and directive definitions.

    Invalid:

    query {
      users(orderBy: NAME, first: 10, after: "cursor") {
        name
      }
    }

  • #10631 1077238 Thanks @thibaut-pro! - Added the sortFirst option to the useSortedAttributes action (JSX and HTML). It takes a list of attribute names that are sorted before all other attributes, in the order given, while the remaining attributes keep their usual sort. This is useful to keep attributes such as key first.

    With the following configuration:

    {
      "assist": {
        "actions": {
          "source": {
            "useSortedAttributes": {
              "level": "on",
              "options": { "sortFirst": ["key"] }
            }
          }
        }
      }
    }

    The attributes are reordered so that key comes first:

    // Before
    <div className={styles.investment} key={investment.id} />;
    

    // After
    <div key={investment.id} className={styles.investment} />;

  • #10424 189b7ba Thanks @LinusU! - Added the partitionByNewLine option to the useSortedInterfaceMembers assist. When enabled, members separated by a blank line are kept in their own section and sorted only within that section, preserving the logical groupings the author intentionally introduced with empty lines.

Patch Changes

  • #11953 354f74c Thanks @Th3S4mur41! - Enhanced the nursery rule useLogicalProperties to check physical CSS values in addition to physical property names.

    The rule recognizes physical values in frame-sizing, anchor-size(), and anchor(), with direction-aware replacements controlled by the existing direction option.

    For justify-content: left and justify-content: right, the rule reports a diagnostic without an automatic replacement because the correct logical alignment depends on the layout axis.

    This is a second part of the rule covering parts of #9034

  • #12175 3730b32 Thanks @dyc3! - Added the nursery rule noDoubleComparison, which reports two comparisons of the same values that can be combined into one. For example, x === y || x < y can be written as x <= y.

  • #12166 25eb10c Thanks @dyc3! - Added the new nursery rule noNestedSwitch, which disallows switch statements inside other switch statements.

    switch (n) {
      case 0:
        switch (m) {} // reported
    }

  • #12170 872ac9f Thanks @dyc3! - Added the new nursery rule noNestedTemplateLiterals, which disallows template literals written inside other template literals.

    const message = `I have ${color ? `${count} ${color}` : count} apples`;

  • #12111 f72375f Thanks @dyc3! - Added the nursery rule noObjectConstructor, which disallows calling the Object constructor without arguments, such as new Object() or Object(). Biome can replace these calls with the object literal {}.

  • #12254 cb88f07 Thanks @dyc3! - Added the nursery rule noSvelteClassDirective, which reports Svelte’s class: directive. Since Svelte 5.16, the class attribute accepts objects and arrays, and Svelte recommends them over the directive.

    <div class:active={isActive}></div>

  • #12186 30aa7d2 Thanks @dyc3! - Added the new nursery rule noUselessDateGetTime, which reports dates converted with .getTime() before being passed to the Date constructor. Passing the date directly, as in new Date(date), already creates a copy.

    const copy = new Date(date.getTime());

  • #12229 5f8ea6c Thanks @dyc3! - Added the nursery rule noVueLifecycleAfterAwait, which reports Vue lifecycle hooks, such as onMounted(), that are registered after an await in a component’s setup() function. Vue doesn’t run these hooks.

    <script>
    import { onMounted } from "vue";
    

    export default {
      async setup() {
        await fetchUser();
        onMounted(() => {});
      },
    };
    </script>

  • #12077 3dd096f Thanks @dyc3! - Added the nursery rule noVueRootVIf, which disallows v-if on the only root element of a Vue component template.

    <template>
      <div v-if="visible">Content</div>
    </template>

  • #12136 b92638b Thanks @dyc3! - Added the nursery rule noVueShadowNativeEvents, which reports Vue component events named after built-in browser events, such as click or keydown.

    <script setup>
    // Invalid
    const emit = defineEmits(["click"]);
    emit("click");
    </script>

  • #12135 31a29b6 Thanks @dyc3! - Added the nursery rule noVueVHtml, which disallows Vue’s v-html directive. v-html inserts its value into the page as HTML, so text from users can run code on your page (cross-site scripting, or XSS).

    <template>
      <div v-html="content"></div>
    </template>

  • #12134 60329af Thanks @dyc3! - Added the new nursery rule noVueVText, which disallows Vue’s v-text directive in favor of text interpolation.

    For example, the following snippet triggers the rule:

    <div v-text="message"></div>

  • #9817 241b861 Thanks @dyc3! - Added the new nursery rule noZeroFractions, which disallows numeric literals with redundant zero fractions or dangling dots such as 1.0 and 1.. Biome can now simplify these literals to shorter equivalents.

  • #12109 b45d426 Thanks @dyc3! - Added the nursery rule useConsistentJsonFileRead, which enforces a consistent way of reading JSON files before passing them to JSON.parse(). By default, it reports files read as a Buffer; set readAs to "buffer" to report files read as a UTF-8 string instead.

    const packageJson = JSON.parse(await fs.readFile("./package.json"));

  • #12129 b57f874 Thanks @dyc3! - Added the new nursery rule useMatchingFunctionName, which requires a named function expression to have the same name as the variable or property it’s assigned to.

    // The function name `bar` doesn't match the variable name `foo`.
    const foo = function bar() {};

  • #12169 0f1ae53 Thanks @dyc3! - Added the new nursery rule useSimplifiedBooleanReturn, which reports if statements that only return true or false and can be replaced by returning the condition directly.

    function isPositive(value) {
      if (value > 0) {
        return true;
      }
      return false;
    }

  • #11957 b2db9f2 Thanks @dyc3! - Added the nursery rule useSvelteKitResolve, which requires internal links and calls to goto(), pushState(), and replaceState() to use paths built with SvelteKit’s resolve().

    <a href="/about">About</a>

  • #12235 b7c1870 Thanks @dyc3! - Added the nursery rule useSvelteReactiveClasses, which reports Date, Map, Set, URL, and URLSearchParams objects that are modified in Svelte files or exported from Svelte modules. Svelte doesn’t detect changes made inside these built-in objects, so the rule suggests the matching classes from svelte/reactivity.

    <script>
      const tags = new Set();
      function addTag(tag) {
        tags.add(tag);
      }
    </script>

  • #12172 b47674d Thanks @dyc3! - Added the nursery rule useSvelteShorthandDirective, which enforces the shorthand syntax for Svelte bind:, class:, and style: directives. For example, <input bind:value={value} /> is now reported and can be fixed to <input bind:value />.

  • #12137 4aeca96 Thanks @dyc3! - Added the nursery rule useVueMatchingComponentFileName, which requires the name of a Vue component to match its file name. The following component in MyComponent.vue is now reported:

    <script>
    export default {
      name: "MyButton",
    };
    </script>

  • #12075 de453c0 Thanks @tionway! - Fixed #11902: biome migrate --write now successfully migrates empty nested configuration files without introducing an invalid trailing comma.

  • #12149 83df808 Thanks @dyc3! - Switched useTailwindSortedClasses to the Tailwind CSS v4 class order. The rule now checks the attributes and functions set in the top-level tailwind configuration, and its own attributes and functions options were removed. Run biome migrate --write to move them to tailwind.attributes, tailwind.mergeFunctions, and tailwind.variantFunctions.

    The rule is now part of the project domain, so enabling it makes Biome scan your project.

  • #12202 9f1cfde Thanks @dyc3! - Fixed #12184: useImportExtensions no longer misses relative imports with .jsx or .tsx extensions when using extensionMappings or forceJsExtensions. The rule reports these imports when the configured replacement resolves to an existing file.

  • #12081 fd4df34 Thanks @dyc3! - Added the nursery rule useCapitalizedConstructors, a port of ESLint’s new-cap. It reports new expressions whose callee name starts with a lowercase letter, and calls without new whose callee name starts with an uppercase letter.

    const friend = new person();
    const other = Person();

  • #12061 36aa8c3 Thanks @dyc3! - Added the nursery rule noExcessiveStatementsPerFunction, a port of ESLint’s max-statements. It reports functions that contain more statements than the configured max (default: 10).

  • #12053 b91a445 Thanks @dyc3! - Added the nursery rule useVueConsistentEventHyphenation, a port of vue/v-on-event-hyphenation. It enforces a consistent hyphenation style for event names in v-on directives on custom components. By default, hyphenated names are required, so <MyComponent @customEvent="handler" /> is reported.

  • #12327 2266df2 Thanks @dyc3! - Improved the performance of the Biome CLI on projects with many files during cleanup.

  • #12110 cf408d5 Thanks @dyc3! - Added the recommended nursery rule noOctal, which disallows legacy octal literals such as 071 and decimal literals with leading zeros such as 08. Use 0o71 for explicit octal notation.

  • #12066 d13d1ba Thanks @dyc3! - Updated rule source metadata.

  • #12393 c80f28c Thanks @ematipico! - Fixed #12389: the Svelte formatter no longer duplicates binding names when converting redundant bind: initializers to shorthand syntax.

    <input bind:valuevalue>
    <input bind:value>

  • #12325 31a2fb0 Thanks @dyc3! - Improved the performance of the formatter in files with little or no comments.

  • #12223 9f246d7 Thanks @dyc3! - Added the nursery rule noAccidentalBitwiseOperators, which reports the bitwise operators &, |, and |= where the logical operators &&, ||, and ||= were likely intended.

    if (obj & obj.prop) {}
    options = options | {};

  • #12052 1a6fb41 Thanks @dyc3! - Added the nursery rule noVueBooleanDefault, which disallows default values for Boolean props in Vue components. Vue already defaults an absent Boolean prop to false.

    <script setup lang="ts">
    withDefaults(defineProps<{ disabled?: boolean }>(), {
      disabled: true,
    });
    </script>

  • #12177 215288b Thanks @MustafaKemal0146! - Fixed #4517: noConfusingVoidType no longer reports void in union types that contain only void and never, such as void | never.

  • #12461 259a84e Thanks @ematipico! - Fixed GritQL JSON snippets so patterns such as { $key: $value } can now bind metavariables in object keys and values.

  • #12185 08cfbd2 Thanks @dyc3! - Fixed the Tailwind CSS parser splitting dashed utility names. Classes such as drop-shadow!, flex-grow-0, and max-w-screen-lg now keep drop-shadow, flex-grow, and max-w-screen as their utility names.

  • #12444 ef61338 Thanks @ematipico! - Fixed the match count reported by biome search. The summary and the matches field of the JSON reporters now count every match, instead of the number of searched files.

  • #12292 4eadd57 Thanks @ematipico! - Fixed withastro/compiler-rs#199: processing instructions such as <?xml version="1.0" encoding="UTF-8"?> no longer cause parse errors in Astro and Vue files.

  • #12152 7a573de Thanks @dyc3! - Fixed the Tailwind class parser rejecting arbitrary variants whose selector starts with an attribute selector. Classes like [[data-variant=legend]+&]:-mt-1.5 and group-has-[[data-slot=item-description]]/item:self-start now parse correctly.

  • #12155 851d803 Thanks @erenbati! - biomejs/biome#11949: Fixed noSelfAssign to detect self-assignments when equivalent property names use dot and bracket notation, including numeric and string-literal keys.

  • #12112 db7ede6 Thanks @dyc3! - Added the nursery rule noPromiseExecutorReturn, which disallows returning values from the function passed to new Promise(), because new Promise() ignores them.

    new Promise((resolve) => resolve(1));

  • #12404 fcd3d74 Thanks @dyc3! - Fixed #12374: biome migrate eslint now preserves eqeqeq’s null comparison options when configuring noDoubleEquals. Migrating the default ESLint configuration now sets ignoreNull: false, so comparisons such as x == null remain reported.

  • #12426 0fe3d2b Thanks @dyc3! - Improved the performance of linting by computing the range of a syntax node without allocating its edge tokens.

  • #12441 c4199d7 Thanks @dyc3! - Improved the performance of commands that run with --use-server, such as biome check --use-server. The Biome daemon now processes the files of a command on all available CPU cores, instead of at most four files at a time.

  • #12183 c08e3c3 Thanks @dyc3! - Fixed the Tailwind class parser rejecting CSS variable shorthands whose fallback contains parentheses. Classes like bg-(--a,var(--b)), bg-(--a,calc(1px)), and after:bg-(--drawer-bleed-background,var(--color-popover)) now parse correctly, including in variants (max-(--a,var(--b)):flex) and modifiers (bg-red-500/(--a,var(--b))).

  • #12441 c4199d7 Thanks @dyc3! - Fixed biome stop waiting 15 seconds and then failing with “the request to the remote workspace timed out”, even though the Biome daemon had stopped. The command now returns as soon as the daemon shuts down.

  • #12117 ae0cabd Thanks @dyc3! - Fixed noUnreachable, noUnreachableSuper, useGetterReturn, useIterableCallbackReturn and noFallthroughSwitchClause skipping functions that contain an unlabeled break or continue inside a labeled loop or switch.

    For example, noUnreachable now reports afterBreak() here:

    function f(xs) {
      outer: for (const x of xs) {
        break;
        afterBreak();
      }
    }

  • #11093 78c992f Thanks @dyc3! - Fixed CSS formatting for multiline function arguments preceded by comments:

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

  • #12474 e55a750 Thanks @dyc3! - Fixed #12471: a comment above a CSS rule no longer removes the indentation of the rule’s wrapped selector.

    /* comment */
    .sidebar-navigation
      .sidebar-navigation-item-with-a-long-descriptive-class-name {
      color: red;
    }

  • #12180 6ddce62 Thanks @dyc3! - Fixed #12179: the CSS parser now accepts Tailwind @custom-variant names that start with a digit, such as the 2xl breakpoint.

    @custom-variant 2xl (@container page (width >= 96rem));

  • #12440 6636760 Thanks @dyc3! - Fixed #12433: with html.experimentalFullSupportEnabled, the editor now offers code actions for diagnostics inside embedded code, such as expressions and scripts in Astro, Vue, Svelte, and HTML files.

  • #12480 00771b4 Thanks @vidigoat! - Fixed the formatter duplicating comments inside an empty object, array, or class that is spread in JSX. Each formatting pass added another copy of the comment.

    <div
      {
        ...{
          /* comment */
        }/* comment */
        }
      }
    />

  • #11093 78c992f Thanks @dyc3! - 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.

  • #11563 a4e6528 Thanks @santichausis! - Fixed #11419: noAdjacentSpacesInRegex no longer applies its fix inside a regex character class ([...]), where it was changing what the class matches instead of just clarifying the spacing.

    For example, Biome used to “fix” this regex into matching different characters:

    const before = /[\s   ]/;
    // Biome used to rewrite this to /[\s {3}]/, which is a different regex:
    // {3} isn't a quantifier inside a character class, it's three more
    // characters to match — the fixed regex now also matches "1", "2", "{", "}".

    Adjacent spaces outside a character class are still merged into a quantifier as before.

  • #12451 c71fe6a Thanks @dyc3! - Fixed #12445: noTsIgnore no longer reports comments that merely mention @ts-ignore, such as // see the note on @ts-ignore below or JSDoc prose. The rule now follows TypeScript and only reports @ts-ignore at the start of a comment, or at the start of the last line of a block comment. The fix now rewrites only the directive.

  • #12266 33fef85 Thanks @JamBalaya56562! - Fixed #12265: Biome now uses the correct defaults for semi and singleQuote when migrating a Prettier configuration that doesn’t set them. The migrated configuration uses "semicolons": "always" and "quoteStyle": "double", matching Prettier’s defaults.

  • #11093 78c992f Thanks @dyc3! - 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.

  • #12246 b073c2f Thanks @dyc3! - Fixed the parsing of Svelte class: and style: directive names. Modifiers such as |important in style:color|important are now parsed as modifiers instead of being part of the name, and / in <input class:invalid/> now closes the tag.

  • #12246 b073c2f Thanks @dyc3! - Fixed #11215: noUnusedVariables no longer reports variables in Svelte components that are only used through the class: and style: directive shorthands, such as <div class:active> and <div style:color>.

  • #12104 2bb4838 Thanks @dyc3! - Fixed #12098: useImportExtensions now reports relative imports without extensions in Vue, Svelte, and Astro files when html.experimentalFullSupportEnabled is enabled.

  • #12441 c4199d7 Thanks @dyc3! - Fixed commands that run with --use-server reporting cancelled because of pending write for some files instead of checking them. Biome now sends a cancelled request again, so the command reports the same diagnostics as a run without --use-server.

  • #12242 0ec0a46 Thanks @dyc3! - Fixed a false positive in useVueConsistentDefinePropsDeclaration. The rule no longer reports calls such as a.b.c(0) or calls to a locally imported defineProps function. It now only checks calls to Vue’s defineProps macro.

  • #12244 fe217c6 Thanks @dyc3! - Fixed a false positive in noVueDuplicateKeys where variables created from props wrapped in withDefaults() were reported as duplicates of those props. The following code is now valid:

    <script setup lang="ts">
    import { toRefs } from "vue";
    

    const props = withDefaults(defineProps<{ text: string }>(), {});
    const { text } = toRefs(props);
    </script>

  • #12240 e26a76b Thanks @latent-9! - Fixed a false negative in noUnreachable and useGetterReturn: for loops whose test is a truthy literal, such as for (; true ;), are now handled as infinite loops, consistent with while and do...while.

  • #12212 513f7db Thanks @siketyan! - Added support for formatting CSS-in-JS templates with interpolations, such as the ones of styled-components and Emotion, when javascript.experimentalEmbeddedSnippetsEnabled is enabled. The interpolations are formatted as JavaScript, and the text glued to them is kept as is.

    const Button = styled.button`
      color:${ (props)=>props.color };
      width : ${({width})=>width}px;
      color: ${(props) => props.color};
      width: ${({ width }) => width}px;
    `;

  • #12131 05e3036 Thanks @dyc3! - The HTML formatter now formats the JavaScript inside quoted Vue directive values, such as :prop, v-bind, v-if, @event handlers that reference a function, and v-slot. These values and v-for values are written between double quotes, and the strings inside them use single quotes.

    <div :bar="foo   + 1" v-if='isVisible&&ready'></div>
    <li v-for='item in ["a","b"]'></li>
    <div :bar="foo + 1" v-if="isVisible && ready"></div>
    <li v-for="item in ['a', 'b']"></li>

  • #12218 73e169e Thanks @dyc3! - The HTML formatter now formats Vue @event handlers that contain statements. A single expression stays on one line without a semicolon, and multiple statements are written on lines of their own inside the quotes, like Prettier does.

    <button @click="count  +=   1"></button>
    <button @click="save( );close( )"></button>
    <button @click="count += 1"></button>
    <button
      @click="
        save();
        close();
      "
    ></button>

    The parser also accepts handlers that start with a statement, such as @click="if (ok) save()". The formatter adds the ; that Vue needs to compile them as the body of a function:

    <button @click="if (ok) save()"></button>
    <button @click="if (ok) save();"></button>

    Handlers that Vue compiles as the body of a function keep their semicolons with "semicolons": "asNeeded", because Vue compiles a handler without a ; as an expression.

  • #12192 4d056a5 Thanks @dyc3! - Fixed CSS package imports that use the style export condition, such as tw-animate-css. With tailwind.stylesheet configured, useTailwindSortedClasses now reads utilities and theme values from imported packages, including their transitive CSS imports.

  • #12217 8a253f8 Thanks @dyc3! - Updated biome migrate eslint to migrate tailwindcss/enforces-shorthand to useTailwindShorthandClasses when nursery rules are included, and @html-eslint/no-target-blank to noBlankTarget. Corrected the reported reasons for unsupported legacy, deprecated, formatter-covered, and compiler-dependent rules.

  • #12047 4db3f58 Thanks @denbezrukov! - Fixed parsing of bare if identifiers in CSS if() branch values, such as if(style(--enabled: true): if; else: serif).

  • #12401 e295f02 Thanks @dyc3! - Fixed useTailwindShorthandClasses suggesting invalid or behavior-changing shorthands for rotations, dividers, content alignment, and custom width and height tokens. Shorthand fixes now preserve !important with either leading or trailing ! markers.

  • #11854 2917939 Thanks @dyc3! - Added support for mapped types such as { [K in keyof T]: T[K] } to type inference. Type-aware rules now resolve the properties of mapped types, including generic aliases instantiated with concrete type arguments:

    type Optional<T> = { [K in keyof T]?: T[K] };
    declare const config: Optional<{ retries: number }>;
    // `config.retries` is now inferred as `number | undefined`.

    Mapped types that remap keys with an as clause remain unsupported.

  • #12251 7d55c42 Thanks @dyc3! - Fixed #12233: the biome command installed from npm now exits with a non-zero code when the Biome binary is killed by a signal, such as a crash from SIGABRT or SIGSEGV. Previously, it exited with code 0 and reported the run as successful.

  • #12157 a1320b1 Thanks @dyc3! - Renamed the nursery rule useSortedClasses to useTailwindSortedClasses. Run biome migrate --write to update your configuration.

  • #12124 d5ace64 Thanks @levrik! - Biome now parses and formats the generic attribute of Vue <script setup lang="ts"> blocks, such as generic="TData extends RowData". The declared type parameters are no longer reported by noUndeclaredVariables, noUnusedVariables and noUnusedImports also take the parameters into account now.

    <script setup lang="ts" generic="T   extends   Item,U">
    <script setup lang="ts" generic="T extends Item, U">

  • #12350 97c51a8 Thanks @Netail! - Improved the diagnostics of the GraphQL rules noDuplicateArgumentNames, noDuplicateEnumValueNames, noDuplicateFieldDefinitionNames, noDuplicateGraphqlOperationName, noDuplicateInputFieldNames and noDuplicateVariableNames. Each diagnostic now names the duplicated identifier, highlights its first occurrence and points to every repeated occurrence, instead of highlighting the whole parent node or only the repeated occurrences. Names that are duplicated more than once in the same list are reported separately.

  • #12178 8c4469c Thanks @MustafaKemal0146! - Fixed #10212: useConsistentObjectDefinitions no longer reports named function expressions such as { b: function c() {} }, because converting them to methods can change the function’s name or how its name is resolved inside the body.

  • 9361d23 Thanks @florian-lefebvre! - The JavaScript formatter now wraps a sequence expression returned from a return or throw statement in parentheses, matching Prettier.

    return a, b;
    return (a, b);

  • #12362 ac71f2b Thanks @dyc3! - Improved the performance of the linter and assists, most of all when few rules are enabled, for example with --only.

  • #12185 08cfbd2 Thanks @dyc3! - Added the nursery rule noTailwindLegacyUtilities for JavaScript and HTML. It reports Tailwind CSS classes that Tailwind CSS only keeps for backward compatibility, and fixes them to their current names.

    <div className="flex-grow bg-gradient-to-r" />; // use `grow` and `bg-linear-to-r`

  • #11093 78c992f Thanks @dyc3! - 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);

  • #12063 8724a5d Thanks @dyc3! - Fixed #9749: in GritQL plugins and biome search, a contains followed by further conditions now tries every node it matches, instead of failing when the first match doesn’t satisfy the remaining conditions.

  • #12154 79c1643 Thanks @dyc3! - Added the new nursery rule useLowercaseTestTitle, which requires test, test suite, and benchmark titles to start with a lowercase letter.

    // Invalid
    it("Returns the cached value", () => {});

  • #12086 27a34f9 Thanks @dyc3! - biome migrate eslint now preserves the element lists of react/forbid-elements, svelte/no-restricted-html-elements, and vue/no-restricted-html-elements when migrating them to noRestrictedElements. When several of these rules are configured, their lists are merged.

  • #12174 bee1e54 Thanks @dyc3! - Fixed the Tailwind class parser producing an invalid syntax tree for parenthesized and unary expressions inside arbitrary values. Classes like w-[calc(1px+(2px))], w-[calc((100%_-_2rem)/3)], and w-[calc(1px*-(2px))] now parse correctly.

  • #12203 b1e35fa Thanks @dyc3! - Fixed parsing of Tailwind @theme at-rules with more than one option. Biome now accepts any number of options, including prefix(...), such as the @theme default inline reference { ... } rule in Tailwind’s own tailwindcss/index.css.

  • #11888 02e038f Thanks @dfedoryshchev! - Fixed useNamingConvention reporting a declaration nested in a namespace that is itself inside declare global or inside an external module declaration. Both positions are documented as always ignored, and the rule offered a safe fix, so biome check --write renamed the declaration. This follows up #11827.

    export {}
    declare global {
        namespace Outer {
            // no longer reported
            namespace my_NAMESPACE {}
        }
    }

  • #12068 dd96b11 Thanks @GreedyC! - Fixed #12004: noDuplicateFontNames allows font-family: monospace, monospace, which preserves the inherited font size in browsers.

  • #12411 4de5d3d Thanks @latin-1! - Fixed #12410: the useSortedProperties assist now preserves the relative order of Tailwind CSS wildcard resets such as --font-*: initial and other custom properties.

  • #12211 8d0f080 Thanks @Athish2002! - Fixed #11944: noUselessStringConcat safe fix now accurately stringifies numbers according to ECMAScript Number::toString semantics, properly handling scientific notation (such as 1e21 and 0.1e-6), alternate radixes, and separators.

  • #12392 60211cb Thanks @ematipico! - Fixed #12390: rules from the project and types domains that are enabled in an override now run for files matched by that override.

  • #12399 cd735e9 Thanks @dyc3! - Fixed #12373: biome migrate eslint no longer migrates one-var to useSingleVarDeclarator unless --include-inspired is passed.

  • #12141 4efe06d Thanks @dyc3! - Updated biome migrate eslint to recognize more upstream rules covered by existing Biome rules and explain why additional unsupported rules are skipped.

  • #11093 78c992f Thanks @dyc3! - The HTML parser now accepts mixed-case doctype declarations.

  • #12288 39d7595 Thanks @dyc3! - Fixed false positives in noProto for computed identifiers, property names containing quotes, and tagged templates. Expressions such as obj[__proto__] and obj[`"__proto__"`] no longer trigger the rule.

    Fixed missed diagnostics for __proto__ accesses through parentheses, TypeScript wrappers, and comma expressions, such as obj[('__proto__')].

  • #12341 9a44363 Thanks @dyc3! - Improved the performance of noUnusedVariables, noUnusedImports, and the other lint rules that check whether a variable is used in another language of the same file.

  • #11432 4befd08 Thanks @ematipico! - Fixed JavaScript assist overrides and HTML parser, linter, and assist overrides so they are applied to matching files.

  • #12339 8fa3b1a Thanks @dyc3! - Improved the performance of the linter and assists by up to 50% on some files.

  • #12322 b822e49 Thanks @dyc3! - Improved the performance of biome format --write for files without syntax errors. Biome no longer parses the formatted code of these files a second time. JSON files are not affected.

  • #12362 ac71f2b Thanks @dyc3! - Improved the performance of the lint rules that analyze control flow, such as noUnreachable and useGetterReturn.

  • #12361 f447e08 Thanks @dyc3! - Improved the performance of noIrregularWhitespace. The rule now spends much less time in files that contain no irregular whitespace.

  • #12094 4e50a11 Thanks @dyc3! - Added the nursery rule useConsistentBlockLang, which enforces the languages that the top-level blocks of Vue and Svelte components use. The blocks option configures the allowed languages per block, and the rule doesn’t check anything until it’s configured.

    For example, with { "blocks": { "script": { "lang": ["ts"] } } }, the following is reported:

    <script lang="js"></script>

  • #12114 3743a53 Thanks @dyc3! - Added the recommended nursery rule noArgumentsCallerOrCallee, which disallows arguments.caller and arguments.callee. For example, arguments.callee() now produces a diagnostic; refer to the function by name for recursion.

  • #12360 c2cc18d Thanks @dyc3! - Improved the performance of noTsIgnore. The rule now spends much less time in files that contain no @ts-ignore comment.

  • #12092 d7cf132 Thanks @dyc3! - Added the nursery rule noSvelteUselessDerivedBy, which reports $derived.by() calls whose function only returns a single expression, such as $derived.by(() => count * 2), and suggests $derived(count * 2) instead.

  • #12133 2405c76 Thanks @dyc3! - Added the nursery rule useNamedFunction, which requires functions written with the function keyword to have a name. For example, Foo.prototype.bar = function () {}; is now reported.

  • #12116 b52fee2 Thanks @dyc3! - Added the new nursery rule noUnsafeUnaryMinus, which uses type information to report unary - applied to values that aren’t a number or bigint.

    declare const value: string;
    -value;

  • #12072 c35b067 Thanks @dyc3! - Added the nursery rule noSvelteObjectInTextMustaches, which disallows object, array, function, and class literals in Svelte text mustaches, where they are rendered as strings such as [object Object].

    <!-- Invalid: renders "[object Object]" -->
    {{ name }}

  • #12082 914dca7 Thanks @dyc3! - Added the nursery rule noUselessCall, which reports .call() and .apply() calls that can be replaced with a regular function call.

    obj.foo.call(obj, 1, 2);
    foo.apply(null, [1, 2]);

  • #12067 21fb018 Thanks @dyc3! - Added the nursery rule noSvelteInspect, which reports uses of the Svelte $inspect rune, such as $inspect(count) or $inspect.trace(), left over from debugging.

  • #12199 1004290 Thanks @siketyan! - Fixed CSS metavariables in compound selectors, complex selectors, and property names in GritQL plugins and biome search. Patterns such as `$tag:hover { color: red; }`, `$parent .child {}` and `$property: red` now match the intended rules and declarations, whereas they previously failed to parse or matched the wrong nodes.

  • #12093 3c6331f Thanks @dyc3! - Added the nursery rule useUnaryMinus, which reports multiplying or dividing by -1 instead of using the unary minus operator.

    const inverted = value * -1;

  • #12107 81773ad Thanks @dyc3! - Added the nursery rule noUselessAssignment, which reports assignments whose value is never read before the variable is reassigned or stops being used.

    let id = "x1234"; // this value is never read
    id = generateId();
    doSomethingWith(id);

  • #12115 47c3084 Thanks @dyc3! - Improved type inference for template literals. Biome now infers untagged template literals as strings, so type-aware rules such as noUselessTypeConversion now report code like String(`hello ${name}`).

  • #12468 62d69dc Thanks @dyc3! - Improved performance of the biome search command.

  • #12272 84f62f2 Thanks @dyc3! - The noTailwindRawColors diagnostic now lists up to three classes to use instead. Each one sets a color from your Tailwind CSS theme that looks similar to the reported palette color. Set tailwind.stylesheet to the CSS file that holds your theme to get the list. Biome now scans your project when this rule is enabled, so that it can read that stylesheet.

    For example, with --color-danger: oklch(0.58 0.24 27) in the theme, the diagnostic for bg-red-600/50 lists bg-danger/50.

  • #12402 cf6e36c Thanks @dyc3! - Fixed useVueDefineMacrosOrder missing misplaced bare macro calls and reporting the wrong macro for assigned calls. Its unsafe fix now orders all macro statements in one application and preserves their comments and statement boundaries.

  • #12353 505e2b4 Thanks @Netail! - Improved the quality of diagnostics emitted by the following rules:

  • #11093 78c992f Thanks @dyc3! - Fixed a performance regression in type-aware JavaScript lint rules by inferring only requested types and memoizing export resolution.

  • #12280 80a9204 Thanks @dyc3! - Fixed #12278: noUnusedImports now recognizes Svelte imports used only through $store subscriptions in markup or another script block.

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

  • #12394 eca05e8 Thanks @florian-lefebvre! - Fixes a parser error for Astro shorthand attributes that use an expression instead of a bare identifier, such as {object?.something}:

    <div {object?.something}></div>

  • #12171 271d9b2 Thanks @dyc3! - Improved useBetterDomTraversing to offer its fix when the reported expression is followed by a comment, such as element.childNodes[0] /* first */. The fix keeps the comment.

  • #11961 6d419d4 Thanks @dyc3! - Added the nursery rule useTailwindStaticClassStrings to the Tailwind domain. The rule reports class names assembled from fragments, such as className={"text-" + color} in JSX and class="bg-{color}" in Svelte.

  • #11801 81cccb0 Thanks @dyc3! - Added the nursery rule noTailwindRestyledComponents, which reports Tailwind appearance overrides on JSX and HTML components, such as <Button className="rounded-none" />. No appearance categories are allowed by default. Layout utilities without a category, such as w-full and mt-4, are ignored.

  • #12122 d87ecd3 Thanks @dyc3! - Added the nursery rule noProcessExit, which disallows calling process.exit(). For example, process.exit(1); is now reported.

  • #12249 5fa646c Thanks @dyc3! - Fixed #12247: type inference now infers array literals without as const as arrays, as TypeScript does. For example, [1, "a"] is inferred as (string | number)[] instead of a tuple. As a result, useArraySortCompare now reports sort() and toSorted() calls on arrays without a type annotation.

    const numbers = [1, 2, 3, 10, 20, 30];
    numbers.sort();

  • #12434 8cfb294 Thanks @fe-dudu! - Fixed #12187: noIrregularWhitespace no longer reports irregular whitespace inside CSS and SCSS strings. It avoids duplicate diagnostics in nested rules and checks embedded CSS snippets.

  • #12014 915dc9d Thanks @ematipico! - Fixed noDescendingSpecificity computing the wrong specificity for nested selectors, and ignoring nested selectors inside @container and @starting-style blocks. The following code is now reported, because html body & .d resolves to html body .x .y .d, which is more specific than .x .y .d:

    .x {
      .y {
        html body & .d {}
      }
    }
    .x .y .d {}

  • #12392 60211cb Thanks @ematipico! - Fixed #12358: rules from a domain set to none now remain disabled when an override configures another rule in the same group.

  • #12070 6a8fb01 Thanks @dyc3! - Added the nursery rule noSvelteAddEventListener, which reports addEventListener calls in Svelte files and suggests the on function from svelte/events instead.

    <script>
      window.addEventListener("resize", handler);
    </script>

  • #12089 dba2a37 Thanks @ternaus! - Fixed #12088: false positives in noUnknownAttribute for React 19 transition event handlers. onTransitionCancel, onTransitionRun, onTransitionStart, and their capture variants are recognized when the React dependency range allows React 19 or later.

  • #11093 78c992f Thanks @dyc3! - Improved the performance of Biome formatter up to ~7% across the board.

  • #12194 a3944f7 Thanks @dyc3! - Added the allowedCategories and allowedClasses options to the nursery rule noTailwindArbitraryValue. They allow arbitrary values in categories of utilities, such as layout, or in specific classes, such as p-[13px].

    The rule no longer reports arbitrary modifiers, so bg-black/[0.5] and text-sm/[18px] are now valid.

  • #12120 a1197ac Thanks @dyc3! - Added the nursery rule noInvalidThis, which reports this where it is undefined: at the top level of a module, and in functions that aren’t methods or constructors.

    function foo() {
      this.a = 0;
    }

  • #11093 78c992f 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.

  • #12052 1a6fb41 Thanks @dyc3! - Vue rules that check props, such as noVueReservedProps, now detect props declared inside withDefaults(), for example withDefaults(defineProps<{ key?: string }>(), {}).

  • #12292 4eadd57 Thanks @ematipico! - Fixed a parse error in HTML and Svelte files when an attribute named ? came right before the end of a tag. <div a ?> now has the attributes a and ?, as it already did in Astro and Vue files.

  • #12080 6e2ee70 Thanks @dyc3! - Fixed #12079: the formatter no longer puts the parameters of a Svelte {#snippet} block on separate lines when they fit on one line.

    {#snippet children(
      item,
    )}
    {#snippet children(item)}

  • #12346 ab77fa8 Thanks @ematipico! - Fixed errors that the Biome language server sent to the editor with an empty message. For example, when a nested configuration file sets "root": true, the editor logs now show “Found a nested root configuration, but there’s already a root configuration.” instead of an empty line.

  • #12090 79ed984 Thanks @dyc3! - Added the nursery rule noVueRequiredPropWithDefault, which reports Vue props that are marked as required but also have a default value.

    <script setup lang="ts">
    const props = withDefaults(defineProps<{ name: string }>(), {
      name: "World",
    });
    </script>

  • #11967 4c1612b Thanks @dyc3! - Added the nursery rule useBigintLiterals, which enforces bigint literals over BigInt() calls with a literal argument.

    // Invalid
    const bigint = BigInt(1);
    const hex = BigInt("0xFF");
    

    // Valid
    const bigint = 1n;
    const hex = 0xFFn;
    const computed = BigInt(getSomeNumber());

  • #12014 915dc9d Thanks @ematipico! - Fixed noDuplicateSelectors ignoring nested selectors inside @container and @starting-style blocks. The following duplicate is now reported:

    .card {
      @container (min-width: 1px) {
        & > p {}
        & > p {}
      }
    }

  • #12340 edbe9d7 Thanks @maroKanatani! - Fixed #12320: useReactCompiler now analyzes files that contain an exported type alias, interface, or enum declaration, such as export type Props = { id: string };. Previously, the rule silently skipped these files.

Sponsored by

Copyright (c) 2023-present Biome Developers and Contributors.