Skip to content

Releases: biomejs/biome

Biome CLI v2.3.3

03 Nov 09:56
@github-actions github-actions
@biomejs/[email protected]
fd282fc
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Choose a tag to compare

View all tags
Biome CLI v2.3.3 Latest
Latest

2.3.3

Patch Changes

  • #7907 57bd662 Thanks @ematipico! - Fixed #7839. Now the Biome parser correctly parses the Astro frontmatter even when a triple fence is inside quotes.

  • #7934 a35c496 Thanks @alissonlauffer! - Fixed #7919: The HTML parser now correctly handles Unicode BOM (Byte Order Mark) characters at the beginning of HTML files, ensuring proper parsing and tokenization.

  • #7869 c80361d Thanks @matanshavit! - Fixed #7864: Biome now preserves component tag name casing in Svelte, Astro, and Vue files.

  • #7926 69cecec Thanks @matanshavit! - Added the rule noParametersOnlyUsedInRecursion.

    This rule detects function parameters that are exclusively used in recursive calls and can be removed to simplify the function signature since they are effectively unused.

    function factorial(n, acc) {
  if (n === 0) return 1;
  return factorial(n - 1, acc); // acc is only used here
}

    Fixes #6484.

  • #7774 2509b91 Thanks @dibashthapa! - Fixed #7657: Added the new rule no-unknown-property from ESLint

  • #7918 7165d06 Thanks @dyc3! - Fixed #7913: The CSS parser, with tailwindDirectives enabled, will now correctly handle @slot.

  • #7959 ffae203 Thanks @siketyan! - Fixed the Biome Language Server so it no longer returns an internal error when the formatter is disabled in the configuration.

What's Changed

  • fix(html): parse frontmatter inside quotes by @ematipico in #7907
  • fix(parse/css): add @slot tailwind at rule by @dyc3 in #7918
  • fix(formatter): preserve component tag casing in Svelte/Astro/Vue files by @matanshavit in #7869
  • feat(lint): new rule: no parameters only used in recursion by @matanshavit in #7926
  • fix(html): correctly handle BOM in HTML-ish languages by @alissonlauffer in #7934
  • feat(yaml_parser): parse document end token by @l0ngvh in #7936
  • feat(parse/tailwind): parse negative candidates, other misc cleanup/refactors by @dyc3 in #7937
  • feat(lint): implement no-unknown-property from eslint react by @dibashthapa in #7774
  • chore: update Rust to v1.91.0 by @Gumichocopengin8 in #7947
  • chore(deps): update github-actions by @renovate[bot] in #7952
  • chore(deps): update dependency @types/node to v22.19.0 by @renovate[bot] in #7953
  • chore(deps): update rust crate ignore to 0.4.25 by @renovate[bot] in #7954
  • chore(deps): update dependency eslint to v9.39.0 - autoclosed by @renovate[bot] in #7955
  • fix(console): escape backquotes in MDX context by @siketyan in #7956
  • fix(lsp): do not return error if the formatter is disabled by @siketyan in #7959
  • ci: release by @github-actions[bot] in #7916

New Contributors

Full Changelog: https://github.com/biomejs/biome/compare/@biomejs/[email protected]...@biomejs/[email protected]

Contributors

ematipico, dyc3, and 7 other contributors
Assets 10
Loading

Biome CLI v2.3.2

28 Oct 18:49
@github-actions github-actions
@biomejs/[email protected]
6d95a67
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Choose a tag to compare

View all tags
Biome CLI v2.3.2

2.3.2

Patch Changes

  • #7859 c600618 Thanks @Netail! - Added the nursery rule noIncrementDecrement, disallows the usage of the unary operators ++ and --.

  • #7901 0d17b05 Thanks @ematipico! - Fixed #7837, where Biome couldn't properly parse text expressions that contained nested curly brackets. This was breaking parsing in Astro and Svelte files.

  • #7874 e617d36 Thanks @Bertie690! - Fixed #7230: noUselessStringConcat no longer emits false positives for multi-line strings with leading + operators.

    Previously, the rule did not check for leading newlines on the + operator, emitting false positives if one occurred at the start of a line.
    Notably, formatting with operatorLinebreak="before" would move the + operators to the start of lines automatically, resulting in spurious errors whenever a multi-line string was used.

    Now, the rule correctly detects and ignores multi-line concatenations with leading operators as well, working regardless of the setting of operatorLinebreak.

    Example

    // The following code used to error if the `+` operators were at the start of lines (as opposed to the end).
// Now, the rule correctly recognizes this as a stylistic concatenation and ignores it.
const reallyLongStringThatShouldNotError =
  "Lorem ipsum dolor sit amet consectetur adipiscing elit." +
  "Quisque faucibus ex sapien vitae pellentesque sem placerat." +
  "In id cursus mi pretium tellus duis convallis." +
  "Tempus leo eu aenean sed diam urna tempor. Pulvinar vivamus fringilla";

  • #7786 33ffcd5 Thanks @daivinhtran! - Fixed #7601: Properly match Grit plugin's code snippet with only one child.

  • #7901 0d17b05 Thanks @ematipico! - Fixed #7837, where Biome Language Server panicked when opening HTML-ish files when the experimental full support is enabled.

What's Changed

  • fix(lint): noUselessStringConcat now correctly detects leading concatenation operators from operatorLinebreak=before by @Bertie690 in #7874
  • chore(deps): update rust crate globset to 0.4.18 by @renovate[bot] in #7883
  • chore(deps): update rust crate ignore to 0.4.24 by @renovate[bot] in #7884
  • chore(deps): update rust crate proc-macro2 to 1.0.103 by @renovate[bot] in #7885
  • chore(deps): update rust crate tikv-jemallocator to 0.6.1 by @renovate[bot] in #7886
  • fix(lint): extend matcher for GritCodeSnippet to cover edge case by @daivinhtran in #7786
  • feat(js): update Boa to v0.21.0 by @Gumichocopengin8 in #7888
  • chore(deps): update dependency eslint to v9.38.0 by @renovate[bot] in #7890
  • chore(deps): update rust crate indexmap to 2.12.0 by @renovate[bot] in #7891
  • chore(deps): update github-actions - autoclosed by @renovate[bot] in #7892
  • chore(deps): update rust crate rayon to 1.11.0 by @renovate[bot] in #7894
  • chore(deps): update rust crate regex to 1.12.2 by @renovate[bot] in #7895
  • chore(deps): update rust crate tokio to 1.48.0 by @renovate[bot] in #7896
  • fix(core): text expression parsing and LSP file opening by @ematipico in #7901
  • feat(lint): implement noIncrementDecrement by @Netail in #7859
  • ci: release by @github-actions[bot] in #7887

Full Changelog: https://github.com/biomejs/biome/compare/@biomejs/[email protected]...@biomejs/[email protected]

Contributors

ematipico, renovate, and 4 other contributors
Loading

Biome CLI v2.3.1

26 Oct 19:51
@github-actions github-actions
@biomejs/[email protected]
be79a6b
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Choose a tag to compare

View all tags
Biome CLI v2.3.1

2.3.1

Patch Changes

  • #7840 72afdfa Thanks @ematipico! - Fixed #7838, which caused the new --css-parse-* arguments not being recognised by the ci command.

  • #7789 d5b416e Thanks @fronterior! - Fixed the LSP method workspace/didChangeWorkspaceFolders to perform incremental updates instead of replacing the entire folder list.

  • #7852 bd254c7 Thanks @dyc3! - Fixed #7843: The CSS parser, when tailwindDirectives is enabled, correctly parses --*: initial;.

  • #7872 0fe13fe Thanks @dyc3! - Fixed #7861: The HTML parser will now accept Svelte attribute shorthand syntax in .svelte files.

  • #7866 7b2600b Thanks @dyc3! - Fixed #7860: The css parser, with tailwindDirectives enabled, will now accept @plugin options.

  • #7853 fe90c78 Thanks @dyc3! - Fixed #7848: The css parser with tailwindDirectives enabled will now correctly parse tailwind's source exclude syntax: @source not "foo.css";

  • #7878 c9f7fe5 Thanks @ematipico! - Fixed #7857: Biome now parses <script> tags as TypeScript when analysing .astro files.

  • #7867 b42b718 Thanks @smorimoto! - Fixed incorrect option name in HTML parser error message.

    The error message for disabled text expressions incorrectly referred
    to the html.parser.textExpression option, which does not exist.
    Updated it to reference the correct html.parser.interpolation option.

What's Changed

  • fix(cli): css parsing arguments for ci command by @ematipico in #7840
  • chore: document rule-group severity relation and update rules_check by @Conaclos in #7827
  • fix(lsp): make update_workspace_folders perform incremental updates per LSP spec by @fronterior in #7789
  • ci(rules-check): add noSecrets exception by @Conaclos in #7862
  • ci: fix clippy failure by @Conaclos in #7863
  • fix(parse/css): fix parsing --*: initial; with tailwindDirectives enabled by @dyc3 in #7852
  • fix(parse/css): fix parsing tailwind source exclude syntax by @dyc3 in #7853
  • fix(core): parse astro script as TS by @ematipico in #7878
  • fix(biome_html_parser): fix incorrect option name in HTML parser error message by @smorimoto in #7867
  • chore: ai docs revamp by @ematipico in #7879
  • fix(parse/css): allow @plugin to accept options by @dyc3 in #7866
  • feat(parse/html): parse svelte shorthand props and spread props by @dyc3 in #7872
  • ci: release by @github-actions[bot] in #7842

New Contributors

Full Changelog: https://github.com/biomejs/biome/compare/@biomejs/[email protected]...@biomejs/[email protected]

Contributors

ematipico, dyc3, and 3 other contributors
Loading

JavaScript APIs v4.0.0

24 Oct 08:39
@github-actions github-actions
@biomejs/[email protected]
53ffa8b
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Choose a tag to compare

View all tags
JavaScript APIs v4.0.0

4.0.0

Patch Changes

What's Changed

New Contributors

Full Changelog: https://github.com/biomejs/biome/compare/@biomejs/[email protected]...@biomejs/[email protected]

Contributors

anaisbetts, arendjr, and 12 other contributors
Loading

Biome CLI v2.3.0

24 Oct 08:41
@github-actions github-actions
@biomejs/[email protected]
53ffa8b
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Choose a tag to compare

View all tags
Biome CLI v2.3.0

2.3.0

Minor Changes

  • #7263 a3e3369 Thanks @arendjr! - Biome's resolver now supports baseUrl if specified in tsconfig.json.

    Example

    Given the following file structure:

    tsconfig.json

    {
  "compilerOptions": {
    "baseUrl": "./src"
  }
}

    src/foo.ts

    export function foo() {}

    In this scenario, import { foo } from "foo"; should work regardless of the
    location of the file containing the import statement.

    Fixes #6432.

  • #7745 6fcbc07 Thanks @dyc3! - Added ignore option to noUnknownAtRules. If an unknown at-rule matches any of the items provided in ignore, a diagnostic won't be emitted.

  • #7753 63cb7ff Thanks @ematipico! - Enhanced the init command. The init command now checks if the existing project contains known ignore files and known generated folders.

    If Biome finds .gitignore or .ignore files, it will add the following configuration to biome.json:

    {
+  "vcs": {
+    "enabled": true,
+    "clientKind": "git",
+    "useIgnoreFile": true
+  }
}

    If Biome finds a dist/ folder, it will exclude it automatically using the double-exclude syntax:

    {
+  "files": {
+    "includes": ["**", "!!**/dist"]
+  }
}

  • #7548 85d3a3a Thanks @siketyan! - The rules in a domain are no longer enabled automatically by the installed dependencies unless the rule is recommended.

  • #7723 d3aac63 Thanks @ematipico! - Added --css-parse-css-modules CLI flag to control whether CSS Modules syntax is enabled.

    You can now enable or disable CSS Modules parsing directly from the command line:

    biome check --css-parse-css-modules=true file.module.css
biome format --css-parse-css-modules=true file.module.css
biome lint --css-parse-css-modules=true file.module.css
biome ci --css-parse-css-modules=true file.module.css

  • #7723 d3aac63 Thanks @ematipico! - Added --css-parse-tailwind-directives CLI flag to control whether Tailwind CSS 4.0 directives and functions are enabled.

    You can now enable or disable Tailwind CSS 4.0 directive parsing directly from the command line:

    biome check --css-parse-tailwind-directives=true file.css
biome format --css-parse-tailwind-directives=true file.css
biome lint --css-parse-tailwind-directives=true file.css
biome ci --css-parse-tailwind-directives=true file.css

  • #7330 272632f Thanks @ematipico! - Updated the formatting of .svelte and .vue files. Now the indentation of the JavaScript blocks matches Prettier's:

    <script>
- import Component from "./Component"
+   import Component from "./Component"
</script>

  • #7333 de0d2d6 Thanks @dyc3! - Implemented the indentScriptAndStyle option for vue and svelte files, with the default set to false to match Prettier's vueIndentScriptAndStyle option. When enabled, this option indents the content within <script> and <style> tags to align with the surrounding HTML structure.

    It can be enabled with this configuration:

    {
  "html": {
    "formatter": {
      "indentScriptAndStyle": true
    }
  }
}

    Which will format this code to:

    <script>
import Component from "./Component.vue";
</script>

  • #7359 ebbddc4 Thanks @arendjr! - Deprecated the option files.experimentalScannerIgnores in favour of force-ignore syntax in files.includes.

    files.includes supports ignoring files by prefixing globs with an exclamation mark (!). With this change, it also supports force-ignoring globs by prefixing them with a double exclamation mark (!!).

    The effect of force-ignoring is that the scanner will not index files matching the glob, even in project mode, even if those files are imported by other files, and even if they are files that receive special treatment by Biome, such as nested biome.json files.

    Example

    Let's take the following configuration:

    {
  "files": {
    "includes": [
      "**",
      "!**/generated",
      "!!**/dist",
      "fixtures/example/dist/*.js"
    ]
  },
  "linter": {
    "domains": {
      "project": "all"
    }
  }
}

    This configuration achieves the following:

    • Because the project domain is enabled, all supported files in the project are indexed and processed by the linter, except:
    • Files inside a generated folder are not processed by the linter, but they will get indexed if a file outside a generated folder imports them.
    • Files inside a dist folder are never indexed nor processed, not even if they are imported for any purpose, except:
    • When the dist folder is inside fixtures/example/, its .js files do get both indexed and processed.

    In general, we now recommend using the force-ignore syntax for any folders that contain output files, such as build/ and dist/. For such folders, it is highly unlikely that indexing has any useful benefits. For folders containing generated files, you may wish to use the regular ignore syntax so that type information can still be extracted from the files.

    experimentalScannerIgnores will continue to work for now, but you'll see a deprecation warning if you still use it.

    Run the biome migrate --write command to automatically update the configuration file.

  • #7698 3b6f5e3 Thanks @ematipico! - Added a new reporter named rdjson. This reporter prints diagnostics following the RDJSON format:

    The following command:

    biome check --reporter=rdjson

    Will emit diagnostics in the following format:

    {
  "source": {
    "name": "Biome",
    "url": "https://biomejs.dev"
  },
  "diagnostics": [
    {
      "code": {
        "url": "https://biomejs.dev/linter/rules/no-unused-imports",
        "value": "lint/correctness/noUnusedImports"
      },
      "location": {
        "path": "index.ts",
        "range": {
          "end": {
            "column": 11,
            "line": 0
          },
          "start": {
            "column": 7,
            "line": 0
          }
        }
      },
      "message": "This import is unused."
    },
    {
      "code": {
        "url": "https://biomejs.dev/linter/rules/no-unused-imports",
        "value": "lint/correctness/noUnusedImports"
      },
      "location": {
        "path": "index.ts",
        "range": {
          "end": {
            "column": 10,
            "line": 1
          },
          "start": {
            "column": 9,
            "line": 1
          }
        }
      },
      "message": "Several of these imports are unused."
    }
  ]
}

  • #7719 188a767 Thanks @cadunass! - The formatWithErrors option can now be set via CLI using the --format-with-errors flag.

    This flag was previously only available in the configuration file. It allows formatting to proceed on files with syntax errors, which is useful during development when you want to auto-format code while fixing syntax issues.

    Example

    biome format --format-with-errors=true --write file.js

  • #7723 d3aac63 Thanks @ematipico! - Added --json-parse-allow-comments CLI flag to control whether comments are allowed in JSON files.

    You can now enable or disable comment parsing in JSON files directly from the command line:

    biome check --json-parse-allow-comments=true file.json
biome format --json-parse-allow-comments=true file.json
biome lint --json-parse-allow-comments=true file.json
biome ci --json-parse-allow-comments=true file.json

  • #7723 [d3aac63](d3aa...

Read more

Contributors

anaisbetts, arendjr, and 12 other contributors
Loading

Biome CLI v2.2.7

22 Oct 09:17
@github-actions github-actions
@biomejs/[email protected]
303eec0
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Choose a tag to compare

View all tags
Biome CLI v2.2.7

2.2.7

Patch Changes

What's Changed

  • fix(deps): update dependency happy-dom to v20 [security] by @renovate[bot] in #7729
  • chore(deps): update docker/dockerfile:1 docker digest to b6afd42 by @renovate[bot] in #7735
  • perf: use the PathsMut API to watch/unwatch folders by @siketyan in #7750
  • feat(lint): implement noEmptySource by @Netail in #7715
  • docs: slight useEmptySource improvement by @Netail in #7757
  • fix(noRedundantUseStrict): keeps leading trivia by @bushuai in #5868
  • chore: add some Web Platform Tests testcases by @drwpow in #7135
  • chore: accept snapshots that were failing CI by @dyc3 in #7767
  • fix: detect inifinite loops caused by conflicting rule fixes by @dyc3 in #7732
  • chore(deps): update dependency happy-dom to v20.0.2 [security] by @renovate[bot] in #7768
  • fix(noDuplicateTestHooks): diagnostic message by @ematipico in #7756
  • fix(no_excessive_lines_per_function): expand max_lines Range in NoExcessiveLinesPerFunctionOptions by @MeGaNeKoS in #7714
  • ci: add CI workflow for trusted publishers for crates by @ematipico in #7769
  • chore: improve rule templates by @Netail in #7781
  • fix(workspace): unload plugin cache when project closes by @dyc3 in #7790
  • chore(deps): update rust crate cfg-if to 1.0.4 by @renovate[bot] in #7793
  • chore(deps): update rust crate globset to 0.4.17 by @renovate[bot] in #7794
  • ci: use classic tokens for crate publishing by @ematipico in #7801
  • chore(deps): update github-actions by @renovate[bot] in #7791
  • chore(deps): update dependency vite to v7.1.11 [security] by @renovate[bot] in #7807
  • Revert "fix(lint/useExhaustiveDependencies): correct fix for method calls" by @siketyan in #7810
  • chore(deps): update pnpm to v10.19.0 by @renovate[bot] in #7739
  • chore(deps): update dependency @types/node to v22.18.12 by @renovate[bot] in #7792
  • ci: release by @github-actions[bot] in #7755
  • chore: fix formatting and code of script by @ematipico in #7821
  • test: ignore tests on macos by @ematipico in #7820

New Contributors

Full Changelog: https://github.com/biomejs/biome/compare/@biomejs/[email protected]...@biomejs/[email protected]

Contributors

ematipico, drwpow, and 6 other contributors
Loading

Biome CLI v2.2.6

13 Oct 10:06
@github-actions github-actions
@biomejs/[email protected]
2d77154
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Choose a tag to compare

View all tags
Biome CLI v2.2.6

2.2.6

Patch Changes

  • #7071 a8e7301 Thanks @ptkagori! - Added the useQwikMethodUsage lint rule for the Qwik domain.

    This rule validates Qwik hook usage. Identifiers matching useXxx must be called only within serialisable reactive contexts (for example, inside component$, route loaders/actions, or within other Qwik hooks), preventing common Qwik antipatterns.

    Invalid:

    // Top-level hook call is invalid.
const state = useStore({ count: 0 });

function helper() {
  // Calling a hook in a non-reactive function is invalid.
  const loc = useLocation();
}

    Valid:

    component$(() => {
  const state = useStore({ count: 0 }); // OK inside component$.
  return <div>{state.count}</div>;
});

const handler = $(() => {
  const loc = useLocation(); // OK inside a $-wrapped closure.
  console.log(loc.params);
});

  • #7685 52071f5 Thanks @denbezrukov! - Fixed #6981: The NoUnknownPseudoClass rule no longer reports local pseudo-classes when CSS Modules are used.

  • #7640 899f7b2 Thanks @arendjr! - Fixed #7638: useImportExtensions no longer emits diagnostics on valid import paths that end with a query or hash.

    Example

    // This no longer warns if `index.css` exists:
import style from "../theme/index.css?inline";

  • #7071 a8e7301 Thanks @ptkagori! - Added the useQwikValidLexicalScope rule to the Qwik domain.

    This rule helps you avoid common bugs in Qwik components by checking that your variables and functions are declared in the correct place.

    Invalid:

    // Invalid: state defined outside the component's lexical scope.
let state = useStore({ count: 0 });
const Component = component$(() => {
  return (
    <button onClick$={() => state.count++}>Invalid: {state.count}</button>
  );
});

    Valid:

    // Valid: state initialised within the component's lexical scope and captured by the event.
const Component = component$(() => {
  const state = useStore({ count: 0 });
  return <button onClick$={() => state.count++}>Valid: {state.count}</button>;
});

  • #7620 5beb1ee Thanks @Netail! - Added the rule useDeprecatedDate, which makes a deprecation date required for the graphql @deprecated directive.

    Invalid
    query {
  member @deprecated(reason: "Use `members` instead") {
    id
  }
}
    Valid
    query {
  member
    @deprecated(reason: "Use `members` instead", deletionDate: "2099-12-25") {
    id
  }
}

  • #7709 d6da4d5 Thanks @siketyan! - Fixed #7704: The useExhaustiveDependencies rule now correctly adds an object dependency when its method is called within the closure.

    For example:

    function Component(props) {
  useEffect(() => {
    props.foo();
  }, []);
}

    will now be fixed to:

    function Component(props) {
  useEffect(() => {
    props.foo();
  }, [props]);
}

  • #7624 309ae41 Thanks @lucasweng! - Fixed #7595: noUselessEscapeInString no longer reports $\{ escape in template literals.

  • #7665 29e4229 Thanks @ryan-m-walker! - Fixed #7619: Added support for parsing the CSS :state() pseudo-class.

    custom-selector:state(checked) {
}

  • #7608 41df59b Thanks @ritoban23! - Fixed #7604: the useMaxParams rule now highlights parameter lists instead of entire function bodies. This provides more precise error highlighting. Previously, the entire function was highlighted; now only the parameter list is highlighted, such as (a, b, c, d, e, f, g, h).

  • #7643 459a6ac Thanks @daivinhtran! - Fixed #7580: Include plugin in summary report

What's Changed

  • chore: add .zed to gitignore by @daivinhtran in #7634
  • fix(lint/noUselessEscapeInString): avoid false positive for ${ escape in template literals by @lucasweng in #7624
  • fix(lint): only highlight function names in useMaxParams rule by @ritoban23 in #7608
  • docs: add Polish translation of Biome README by @SzymCode in #7630
  • fix(linter): useImportExtensions handles queries and hashes by @arendjr in #7640
  • ci: breakdown benchmarks by @ematipico in #7641
  • chore: upgrade to rust 1.90.0 by @ematipico in #7642
  • fix(css_parser): add support for parsing :state() (#7619) by @ryan-m-walker in #7665
  • fix(cli): include plugin rule in summary report by @daivinhtran in #7643
  • feat(qwik): add useQwikMethodUsage & useQwikValidLexicalScope by @ptkagori in #7071
  • fix: replace domains polyfill.io to Cloudflare by @You-saku in #7678
  • feat(biome_graphql_analyze): implement useDeprecatedDate by @Netail in #7620
  • chore(deps): update dependency @types/node to v22.18.8 by @renovate[bot] in #7686
  • chore(deps): update github-actions by @renovate[bot] in #7687
  • chore(deps): update rust crate regex to 1.11.3 by @renovate[bot] in #7689
  • chore(deps): update rust crate quote to 1.0.41 by @renovate[bot] in #7688
  • chore(deps): update dependency eslint to v9.37.0 by @renovate[bot] in #7691
  • chore(deps): update rust crate serde to 1.0.228 by @renovate[bot] in #7690
  • fix(css_analyze): handle CSS Modules pseudo-class 'local' in NoUnknownPseudoClass rule (#6981) by @denbezrukov in #7685
  • chore(deps): update pnpm to v10.18.0 by @renovate[bot] in #7693
  • chore(deps): update taiki-e/install-action action to v2.62.21 by @renovate[bot] in #7692
  • chore(deps): update rust crate camino to 1.2.1 by @renovate[bot] in #7694
  • fix(deps): update rust crates by @renovate[bot] in #7562
  • fix(lint/useExhaustiveDependencies): correct fix for method calls by @siketyan in #7709
  • chore(deps): update dependency @types/node to v22.18.10 by @renovate[bot] in #7738
  • chore(deps): update rust crate libc to 0.2.177 by @renovate[bot] in #7740
  • chore(deps): update rust crate ureq to 3.1.2 - autoclosed by @renovate[bot] in #7741
  • ci: release by @github-actions[bot] in #7637
  • chore(deps): update github-actions by @renovate[bot] in #7736

New Contributors

Full Changelog: https://github.com/biomejs/biome/compare/@biomejs/[email protected]...@biomejs/[email protected]

Contributors

arendjr, ematipico, and 11 other contributors
Loading

Biome CLI v2.2.5

02 Oct 10:15
@github-actions github-actions
@biomejs/[email protected]
521d149
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Choose a tag to compare

View all tags
Biome CLI v2.2.5

2.2.5

Patch Changes

  • #7597 5c3d542 Thanks @arendjr! - Fixed #6432: useImportExtensions now works correctly with aliased paths.

  • #7269 f18dac1 Thanks @CDGardner! - Fixed #6648, where Biome's noUselessFragments contained inconsistencies with ESLint for fragments only containing text.

    Previously, Biome would report that fragments with only text were unnecessary under the noUselessFragments rule. Further analysis of ESLint's behavior towards these cases revealed that text-only fragments (<>A</a>, <React.Fragment>B</React.Fragment>, <RenamedFragment>B</RenamedFragment>) would not have noUselessFragments emitted for them.

    On the Biome side, instances such as these would emit noUselessFragments, and applying the suggested fix would turn the text content into a proper JS string.

    // Ended up as: - const t = "Text"
const t = <>Text</>

// Ended up as: - const e = t ? "Option A" : "Option B"
const e = t ? <>Option A</> : <>Option B</>

/* Ended up as:
  function someFunc() {
    return "Content desired to be a multi-line block of text."
  }
*/
function someFunc() {
  return <>
    Content desired to be a multi-line
    block of text.
  <>
}

    The proposed update was to align Biome's reaction to this rule with ESLint's; the aforementioned examples will now be supported from Biome's perspective, thus valid use of fragments.

    // These instances are now valid and won't be called out by noUselessFragments.

const t = <>Text</>
const e = t ? <>Option A</> : <>Option B</>

function someFunc() {
  return <>
    Content desired to be a multi-line
    block of text.
  <>
}

  • #7498 002cded Thanks @siketyan! - Fixed #6893: The useExhaustiveDependencies rule now correctly adds a dependency that is captured in a shorthand object member. For example:

    useEffect(() => {
  console.log({ firstId, secondId });
}, []);

    is now correctly fixed to:

    useEffect(() => {
  console.log({ firstId, secondId });
}, [firstId, secondId]);

  • #7509 1b61631 Thanks @siketyan! - Added a new lint rule noReactForwardRef, which detects usages of forwardRef that is no longer needed and deprecated in React 19.

    For example:

    export const Component = forwardRef(function Component(props, ref) {
  return <div ref={ref} />;
});

    will be fixed to:

    export const Component = function Component({ ref, ...props }) {
  return <div ref={ref} />;
};

    Note that the rule provides an unsafe fix, which may break the code. Don't forget to review the code after applying the fix.

  • #7520 3f06e19 Thanks @arendjr! - Added new nursery rule noDeprecatedImports to flag imports of deprecated symbols.

    Invalid example

    // foo.js
import { oldUtility } from "./utils.js";
    // utils.js
/**
 * @deprecated
 */
export function oldUtility() {}

    Valid examples

    // foo.js
import { newUtility, oldUtility } from "./utils.js";
    // utils.js
export function newUtility() {}

// @deprecated (this is not a JSDoc comment)
export function oldUtility() {}

  • #7457 9637f93 Thanks @kedevked! - Added style and requireForObjectLiteral options to the lint rule useConsistentArrowReturn.

    This rule enforces a consistent return style for arrow functions. It can be configured with the following options:

    • style: (default: asNeeded)
      • always: enforces that arrow functions always have a block body.
      • never: enforces that arrow functions never have a block body, when possible.
      • asNeeded: enforces that arrow functions have a block body only when necessary (e.g. for object literals).

    style: "always"

    Invalid:

    const f = () => 1;

    Valid:

    const f = () => {
  return 1;
};

    style: "never"

    Invalid:

    const f = () => {
  return 1;
};

    Valid:

    const f = () => 1;

    style: "asNeeded"

    Invalid:

    const f = () => {
  return 1;
};

    Valid:

    const f = () => 1;

    style: "asNeeded" and requireForObjectLiteral: true

    Valid:

    const f = () => {
  return { a: 1 };
};

  • #7510 527cec2 Thanks @rriski! - Implements #7339. GritQL patterns can now use native Biome AST nodes using their PascalCase names, in addition to the existing TreeSitter-compatible snake_case names.

    engine biome(1.0)
language js(typescript,jsx)

or {
  // TreeSitter-compatible pattern
  if_statement(),

  // Native Biome AST node pattern
  JsIfStatement()
} as $stmt where {
  register_diagnostic(
    span=$stmt,
    message="Found an if statement"
  )
}

  • #7574 47907e7 Thanks @kedevked! - Fixed 7574. The diagnostic message for the rule useSolidForComponent now correctly emphasizes <For /> and provides a working hyperlink to the Solid documentation.

  • #7497 bd70f40 Thanks @siketyan! - Fixed #7320: The useConsistentCurlyBraces rule now correctly detects a string literal including " inside a JSX attribute value.

  • #7522 1af9931 Thanks @Netail! - Added extra references to external rules to improve migration for the following rules: noUselessFragments & noNestedComponentDefinitions

  • #7597 5c3d542 Thanks @arendjr! - Fixed an issue where package.json manifests would not be correctly discovered
    when evaluating files in the same directory.

  • #7565 38d2098 Thanks @siketyan! - The resolver can now correctly resolve .ts, .tsx, .d.ts, .js files by .js extension if exists, based on the file extension substitution in TypeScript.

    For example, the linter can now detect the floating promise in the following situation, if you have enabled the noFloatingPromises rule.

    foo.ts

    export async function doSomething(): Promise<void> {}

    bar.ts

    import { doSomething } from "./foo.js"; // doesn't exist actually, but it is resolved to `foo.ts`

doSomething(); // floating promise!

  • #7542 cadad2c Thanks @mdevils! - Added the rule noVueDuplicateKeys, which prevents duplicate keys in Vue component definitions.

    This rule prevents the use of duplicate keys across different Vue component options such as props, data, computed, methods, and setup. Even if keys don't conflict in the script tag, they may cause issues in the template since Vue allows direct access to these keys.

    Invalid examples
    <script>
export default {
  props: ["foo"],
  data() {
    return {
      foo: "bar",
    };
  },
};
</script>
    <script>
export default {
  data() {
    return {
      message: "hello",
    };
  },
  methods: {
    message() {
      console.log("duplicate key");
    },
  },
};
</script>
    <script>
export default {
  computed: {
    count() {
      return this.value * 2;
    },
...
Read more

Contributors

mdevils, arendjr, and 13 other contributors
Loading

Biome CLI v2.2.4

10 Sep 10:25
@github-actions github-actions
@biomejs/[email protected]
5d212c5
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Choose a tag to compare

View all tags
Biome CLI v2.2.4

2.2.4

Patch Changes

  • #7453
    aa8cea3     Thanks @arendjr! - Fixed #7242: Aliases specified in
    package.json's imports section now support having multiple targets as part of an array.

  • #7454
    ac17183     Thanks @arendjr! - Greatly improved performance of
    noImportCycles by eliminating allocations.

    In one repository, the total runtime of Biome with only noImportCycles enabled went from ~23s down to ~4s.

  • #7447
    7139aad     Thanks @rriski! - Fixes #7446. The GritQL
    $... spread metavariable now correctly matches members in object literals, aligning its behavior with arrays and function calls.

  • #6710
    98cf9af     Thanks @arendjr! - Fixed #4723: Type inference now recognises
    index signatures and their accesses when they are being indexed as a string.

    Example

    type BagOfPromises = {
  // This is an index signature definition. It declares that instances of type
  // `BagOfPromises` can be indexed using arbitrary strings.
  [property: string]: Promise<void>;
};

let bag: BagOfPromises = {};
// Because `bag.iAmAPromise` is equivalent to `bag["iAmAPromise"]`, this is
// considered an access to the string index, and a Promise is expected.
bag.iAmAPromise;

  • #7415
    d042f18     Thanks @qraqras! - Fixed #7212, now the
    useOptionalChain     rule recognizes optional chaining using
    typeof (e.g., typeof foo !== 'undefined' && foo.bar).

  • #7419
    576baf4     Thanks @Conaclos! - Fixed #7323.
    noUnusedPrivateClassMembers     no longer reports as unused TypeScript
    private members if the rule encounters a computed access on this.

    In the following example, member as previously reported as unused. It is no longer reported.

    class TsBioo {
  private member: number;

  set_with_name(name: string, value: number) {
    this[name] = value;
  }
}


  • 351bccd     Thanks @ematipico! - Added the new nursery lint rule
    noJsxLiterals, which disallows the use of string literals inside JSX.

    The rule catches these cases:

    <>
  <div>test</div> {/* test is invalid */}
  <>test</>
  <div>
    {/* this string is invalid */}
    asdjfl test foo
  </div>
</>

  • #7406
    b906112     Thanks @mdevils! - Fixed an issue (#6393) where the useHookAtTopLevel rule reported excessive diagnostics for nested hook calls.

    The rule now reports only the offending top-level call site, not sub-hooks of composite hooks.

    // Before: reported twice (useFoo and useBar).
function useFoo() {
  return useBar();
}
function Component() {
  if (cond) useFoo();
}
// After: reported once at the call to useFoo().

  • #7461
    ea585a9     Thanks @arendjr! - Improved performance of
    noPrivateImports by eliminating allocations.

    In one repository, the total runtime of Biome with only noPrivateImports enabled went from ~3.2s down to ~1.4s.


  • 351bccd     Thanks @ematipico! - Fixed #7411. The Biome Language Server had a regression where opening an editor with a file already open wouldn't load the project settings correctly.

  • #7142
    53ff5ae     Thanks @Netail! - Added the new nursery rule
    noDuplicateDependencies    , which verifies that no dependencies are duplicated between the
    bundledDependencies, bundleDependencies, dependencies, devDependencies, overrides,
    optionalDependencies, and peerDependencies sections.

    For example, the following snippets will trigger the rule:

    {
  "dependencies": {
    "foo": ""
  },
  "devDependencies": {
    "foo": ""
  }
}
    {
  "dependencies": {
    "foo": ""
  },
  "optionalDependencies": {
    "foo": ""
  }
}
    {
  "dependencies": {
    "foo": ""
  },
  "peerDependencies": {
    "foo": ""
  }
}


  • 351bccd     Thanks @ematipico! - Fixed #3824. Now the option CLI
    --color is correctly applied to logging too.

Loading

Biome CLI v2.2.3

05 Sep 13:35
@siketyan siketyan
@biomejs/[email protected]
daa4a66
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Choose a tag to compare

View all tags
Biome CLI v2.2.3

2.2.3

Patch Changes

  • #7353 4d2b719 Thanks @JeetuSuthar! - Fixed #7340: The linter now allows the navigation property for view-transition in CSS.

    Previously, the linter incorrectly flagged navigation: auto as an unknown property. This fix adds navigation to the list of known CSS properties, following the CSS View Transitions spec.

  • #7275 560de1b Thanks @arendjr! - Fixed #7268: Files that are explicitly passed as CLI arguments are now correctly ignored if they reside in an ignored folder.

  • #7358 963a246 Thanks @ematipico! - Fixed #7085, now the rule noDescendingSpecificity correctly calculates the specificity of selectors when they are included inside a media query.

  • #7387 923674d Thanks @qraqras! - Fixed #7381, now the useOptionalChain rule recognizes optional chaining using Yoda expressions (e.g., undefined !== foo && foo.bar).

  • #7316 f9636d5 Thanks @Conaclos! - Fixed #7289. The rule useImportType now inlines import type into import { type } when the style option is set to inlineType.

    Example:

    import type { T } from "mod";
// becomes
import { type T } from "mod";

  • #7350 bb4d407 Thanks @siketyan! - Fixed #7261: two characters ・ (KATAKANA MIDDLE DOT, U+30FB) and ･ (HALFWIDTH KATAKANA MIDDLE DOT, U+FF65) are no longer considered as valid characters in identifiers. Property keys containing these character(s) are now preserved as string literals.

  • #7377 811f47b Thanks @ematipico! - Fixed a bug where the Biome Language Server didn't correctly compute the diagnostics of a monorepo setting, caused by an incorrect handling of the project status.

  • #7245 fad34b9 Thanks @kedevked! - Added the new lint rule useConsistentArrowReturn.

    This rule enforces a consistent return style for arrow functions.

    Invalid

    const f = () => {
  return 1;
};

    This rule is a port of ESLint's arrow-body-style rule.

  • #7370 e8032dd Thanks @fireairforce! - Support dynamic import defer and import source. The syntax looks like:

    import.source("foo");
import.source("x", { with: { attr: "val" } });
import.defer("foo");
import.defer("x", { with: { attr: "val" } });

  • #7369 b1f8cbd Thanks @siketyan! - Range suppressions are now supported for Grit plugins.

    For JavaScript, you can suppress a plugin as follows:

    // biome-ignore-start lint/plugin/preferObjectSpread: reason
Object.assign({ foo: "bar" }, baz);
// biome-ignore-end lint/plugin/preferObjectSpread: reason

    For CSS, you can suppress a plugin as follows:

    body {
  /* biome-ignore-start lint/plugin/useLowercaseColors: reason */
  color: #fff;
  /* biome-ignore-end lint/plugin/useLowercaseColors: reason */
}

  • #7384 099507e Thanks @ematipico! - Reduced the severity of certain diagnostics emitted when Biome deserializes the configuration files.
    Now these diagnostics are emitted as Information severity, which means that they won't interfere when running commands with --error-on-warnings

  • #7302 2af2380 Thanks @unvalley! - Fixed #7301: useReadonlyClassProperties now correctly skips JavaScript files.

  • #7288 94d85f8 Thanks @ThiefMaster! - Fixed #7286. Files are now formatted with JSX behavior when javascript.parser.jsxEverywhere is explicitly set.

    Previously, this flag was only used for parsing, but not for formatting, which resulted in incorrect formatting of conditional expressions when JSX syntax is used in .js files.

  • #7311 62154b9 Thanks @qraqras! - Added the new nursery rule noUselessCatchBinding. This rule disallows unnecessary catch bindings.

    try {
    // Do something
- } catch (unused) {}
+ } catch {}

  • #7349 45c1dfe Thanks @ematipico! - Fixed #4298. Biome now correctly formats CSS declarations when it contains one single value:

    .bar {
-  --123456789012345678901234567890: var(--1234567890123456789012345678901234567);
+  --123456789012345678901234567890: var(
+    --1234567890123456789012345678901234567
+  );
}

  • #7295 7638e84 Thanks @ematipico! - Fixed #7130. Removed the emission of a false-positive diagnostic. Biome no longer emits the following diagnostic:

    lib/main.ts:1:5 suppressions/unused ━━━━━━━━━━━━━━━━━━━━━━━━━

  ⚠ Suppression comment has no effect because the tool is not enabled.

  > 1 │ /** biome-ignore-all assist/source/organizeImports: For the lib root file, we don't want to organize exports */
      │     ^^^^^^^^^^^^^^^^

  • #7377 811f47b Thanks @ematipico! - Fixed #7371 where the Biome Language Server didn't correctly recompute the diagnostics when updating a nested configuration file.

  • #7348 ac27fc5 Thanks @ematipico! - Fixed #7079. Now the rule useSemanticElements doesn't trigger components and custom elements.

  • #7389 ab06a7e Thanks @Conaclos! - Fixed #7344. useNamingConvention no longer reports interfaces defined in global declarations.

    Interfaces declared in global declarations augment existing interfaces.
    Thus, they must be ignored.

    In the following example, useNamingConvention reported HTMLElement.
    It is now ignored.

    export {};
declare global {
  interface HTMLElement {
    foo(): void;
  }
}

  • #7315 4a2bd2f Thanks @vladimir-ivanov! - Fixed #7310: useReadonlyClassProperties correctly handles nested assignments, avoiding false posi...

Read more

Contributors

Sjlver, ThiefMaster, and 14 other contributors
Loading