Skip to content

Releases: biomejs/biome

CLI v1.9.4

17 Oct 17:49
fa93a14
Compare
Choose a tag to compare

Analyzer

Bug fixes

  • Improved the message for unused suppression comments. Contributed by @dyc3

  • Fix #4228, where the rule a11y/noInteractiveElementToNoninteractiveRole incorrectly reports a role for non-interactive elements. Contributed by @eryue0220

  • noSuspiciousSemicolonInJsx now catches suspicious semicolons in React fragments. Contributed by @vasucp1207

CLI

Enhancements

  • The --summary reporter now reports parsing diagnostics too. Contributed by @ematipico

  • Improved performance of GritQL queries by roughly 25-30%. Contributed by @arendjr

Configuration

Bug fixes

  • Fix an issue where the JSON schema marked lint rules options as mandatory. Contributed by @ematipico

Formatter

Bug fixes

  • Fix #4121. Respect line width when printing multiline strings. Contributed by @ah-yu

Linter

New features

Bug Fixes

  • Biome no longer crashes when it encounters a string that contains a multibyte character (#4181).

    This fixes a regression introduced in Biome 1.9.3
    The regression affected the following linter rules:

    • nursery/useSortedClasses
    • nursery/useTrimStartEnd
    • style/useTemplate
    • suspicious/noMisleadingCharacterClass

    Contributed by @Conaclos

  • Fix #4190, where the rule noMissingVarFunction wrongly reported a variable as missing when used inside a var() function that was a newline. Contributed by @ematipico

  • Fix #4041. Now the rule useSortedClasses won't be triggered if className is composed only by inlined variables. Contributed by @ematipico

  • useImportType and useExportType now report useless inline type qualifiers (#4178).

    The following fix is now proposed:

    - import type { type A, B } from "";
    + import type { A, B } from "";
    
    - export type { type C, D };
    + export type { C, D };

    Contributed by @Conaclos

  • useExportType now reports ungrouped export from.

    The following fix is now proposed:

    - export { type A, type B } from "";
    + export type { A, B } from "";

    Contributed by @Conaclos

  • noVoidTypeReturn now accepts void expressions in return position (#4173).

    The following code is now accepted:

    function f(): void {
      return void 0;
    }

    Contributed by @Conaclos

  • noUselessFragments now correctly handles fragments containing HTML escapes (e.g.  ) inside expression escapes { ... } (#4059).

    The following code is no longer reported:

    function Component() {
      return (
        <div key={index}>{line || <>&nbsp;</>}</div>
      )
    }

    Contributed by @fireairforce

  • noUnusedFunctionParameters and noUnusedVariables no longer reports a parameter as unused when another parameter has a constructor type with the same parameter name (#4227).

    In the following code, the name parameter is no longer reported as unused.

    export class Foo {
      bar(name: string, _class: new (name: string) => any) {
        return name
      }
    }

    Contributed by @Conaclos

  • noUndeclaredDependencies now accepts dependency names with dots. Contributed by @Conaclos

  • useFilenamingConvention now correctly handles renamed exports (#4254).

    The rule allows the filename to be named as one of the exports of the module.
    For instance, the file containing the following export can be named Button.

    class Button {}
    export { Button }

    The rule now correctly handles the renaming of an export.
    For example, the file containing the following export can only be named Button.
    Previously the rule expected the file to be named A.

    class A {}
    export { A as Button }

    Contributed by @Conaclos

  • useConsistentMemberAccessibility now ignores private class members such as #property (#4276). Contributed by @Conaclos

  • noUnknownFunction correctly handles calc-size function (#4212).

    The following code calc-size is no longer reported as unknown:

    .a { height: calc-size(0px); }

    Contributed by @fireairforce

  • useNamingConvention now allows configuring conventions for readonly index signatures. Contributed by @sepruko

  • noDuplicateCustomProperties now correctly handles custom properties and ignores non-custom properties.
    Previously, the rule incorrectly reported duplicates for all properties, including non-custom ones. Contributed by @togami2864

Parser

Bug Fixes

  • The CSS parser now accepts more emoji in identifiers (#3627).

    Browsers accept more emoji than the standard allows.
    Biome now accepts these additional emojis.

    The following code is now correctly parsed:

    p {
      ---color: red;
      color: var(--✨-color);
    }

    Contributed by @Conaclos

  • Add support for parsing typescript's resolution-mode in Import Types(#2115)

    export type Fs = typeof import('fs', { with: { 'resolution-mode': 'import' } });
    export type TypeFromRequire =
      import("pkg", { with: { "resolution-mode": "require" } }).TypeFromRequire;
    export type TypeFromImport =
      import("pkg", { with: { "resolution-mode": "import" } }).TypeFromImport;

    Contributed by @fireairforce

What's Changed

Other changes

Read more

JavaScript APIs v0.7.1

01 Oct 16:17
2670095
Compare
Choose a tag to compare

CLI

New features

  • GritQL queries that match functions or methods will now match async functions or methods as well.

    If this is not what you want, you can capture the async keyword (or its absence) in a metavariable and assert its emptiness:

    $async function foo() {} where $async <: .
    

    Contributed by @arendjr

Bug fixes

  • Fix #4077: Grit queries no longer need to match the statement's trailing semicolon. Contributed by @arendjr

  • Fix #4102. Now the CLI command lint doesn't exit with an error code when using --write/--fix. Contributed by @ematipico

Configuration

Bug fixes

  • Fix #4125, where noLabelWithoutControl options where incorrectly marked as mandatory. Contributed by @ematipico

Editors

  • Fix a case where CSS files weren't correctly linted using the default configuration. Contributed by @ematipico

Formatter

Bug fixes

  • Fix #3924 where GraphQL formatter panics in block comments with empty line. Contributed by @vohoanglong0107

  • Fix a case where raw values inside url() functions weren't properly trimmed.

    .value {
    -  background: url(
    -   whitespace-around-string
    -  );
    + background: url(whitespace-around-string);
    }

    Contributed by @ematipico

  • Fixed #4076, where a media query wasn't correctly formatted:

    .class {
    -  @media (1024px <= width <=1280px) {
    +  @media (1024px <= width <= 1280px) {
       color: red;
       }
    }

    Contributed by @blaze-d83

JavaScript API

Bug fixes

  • Fix #3881, by updating the APIs to use the latest WASM changes. Contributed by @ematipico

Linter

New features

Bug fixes

Parser

Bug fixes

  • Forbid undefined as type name for typescript parser. Contributed by @fireairforce

What's Changed

Other changes

Full Changelog: cli/v1.9.3...js-api/v0.7.1

CLI v1.9.3

01 Oct 13:54
d503451
Compare
Choose a tag to compare

CLI

New features

  • GritQL queries that match functions or methods will now match async functions or methods as well.

    If this is not what you want, you can capture the async keyword (or its absence) in a metavariable and assert its emptiness:

    $async function foo() {} where $async <: .
    

    Contributed by @arendjr

Bug fixes

  • Fix #4077: Grit queries no longer need to match the statement's trailing semicolon. Contributed by @arendjr

  • Fix #4102. Now the CLI command lint doesn't exit with an error code when using --write/--fix. Contributed by @ematipico

Configuration

Bug fixes

  • Fix #4125, where noLabelWithoutControl options where incorrectly marked as mandatory. Contributed by @ematipico

Editors

  • Fix a case where CSS files weren't correctly linted using the default configuration. Contributed by @ematipico

Formatter

Bug fixes

  • Fix #3924 where GraphQL formatter panics in block comments with empty line. Contributed by @vohoanglong0107

  • Fix a case where raw values inside url() functions weren't properly trimmed.

    .value {
    -  background: url(
    -   whitespace-around-string
    -  );
    + background: url(whitespace-around-string);
    }

    Contributed by @ematipico

  • Fixed #4076, where a media query wasn't correctly formatted:

    .class {
    -  @media (1024px <= width <=1280px) {
    +  @media (1024px <= width <= 1280px) {
       color: red;
       }
    }

    Contributed by @blaze-d83

JavaScript API

Bug fixes

  • Fix #3881, by updating the APIs to use the latest WASM changes. Contributed by @ematipico

Linter

New features

Bug fixes

Parser

Bug fixes

  • Forbid undefined as type name for typescript parser. Contributed by @fireairforce

What's Changed

Other changes

  • fix(bench): typo in .prettierignore by @Jayllyz in #4134
  • feat(formatter): implement formatting for GritQL root node by @arendjr in #4128
  • feat(useExhaustiveDependencies): add option to disable errors for unecessary dependencies by @simon-paris in #4135
  • perf(linter): remove unneeded memory allocation for str by @togami2864 in #4142
  • fix: add missing word by @lanker in #4150

New Contributors

Full Changelog: cli/v1.9.3-nightly.75b4387...cli/v1.9.3

CLI v1.9.3-nightly.75b4387

27 Sep 11:11
97e86f5
Compare
Choose a tag to compare
Pre-release

Analyzer

CLI

New features

  • GritQL queries that match functions or methods will now match async functions or methods as well.

    If this is not what you want, you can capture the async keyword (or its absence) in a metavariable and assert its emptiness:

    $async function foo() {} where $async <: .
    

    Contributed by @arendjr

Bug fixes

  • Fix #4077: Grit queries no longer need to match the statement's trailing semicolon. Contributed by @arendjr

Configuration

Editors

Formatter

Bug fixes

  • Fix #3924 where GraphQL formatter panics in block comments with empty line. Contributed by @vohoanglong0107

JavaScript API

Linter

New features

Bug fixes

  • noMisleadingCharacterClass no longer reports issues outside of character classes.

    The following code is no longer reported:

    /[a-z]👍/;

    Contributed by @Conaclos

  • noUndeclaredDependencies no longer reports Node.js builtin modules as undeclared dependencies.

    The rule no longer reports the following code:

    import * as fs from "fs";

    Contributed by @Conaclos

  • noUselessEscapeInRegex no longer panics on regexes that start with an empty character class. Contributed by @Conaclos

  • noUselessStringConcat no longer panics when it encounters malformed code. Contributed by @Conaclos

  • noUnusedFunctionParameters no longer reports unused parameters inside an object pattern with a rest parameter.

    In the following code, the rule no longer reports a as unused.

    function f({ a, ...rest }) {
      return rest;
    }

    This matches the behavior of noUnusedVariables.

    Contributed by @Conaclos

  • useButtonType no longer reports dynamically created button with a valid type (#4072).

    The following code is no longer reported:

    React.createElement("button", { type: "button" }, "foo")

    Contributed by @Conaclos

  • useSemanticElements now ignores elements with the img role (#3994).

    MDN recommends using role="img" for grouping images or creating an image from other elements.
    The following code is no longer reported:

    <div role="img" aria-label="That cat is so cute">
      <p>&#x1F408; &#x1F602;</p>
    </div>

    Contributed by @Conaclos

  • useSemanticElements now ignores alert and alertdialog roles (#3858). Contributed by @Conaclos

  • noUselessFragments don't create invaild JSX code when Fragments children contains JSX Expression and in a LogicalExpression. Contributed by @fireairforce

Parser

Bug fixes

  • Forbid undefined as type name for typescript parser. Contributed by @fireairforce

What's Changed

Other changes

  • test(format/html): reenable snapshot tests by @dyc3 in #3979
  • refactor(lint): set version field for new rules by @Conaclos in #3995
  • docs: improve documentation of rule by @ematipico in #3999
  • feat(linter): implement noOctalEscape by @fireairforce in #3986
  • feat(grit): implement GritQL log() function by @arendjr in #4003
  • fix(html/parser): support root element list by @suxin2017 in #3985
  • feat(html/formatter): self close tag add slash char by @suxin2017 in #3984
  • chore(readme): use polar shield by @ematipico in #4000
  • feat: add additional FeatureKind entries for debug features by @dyc3 in #3892
  • feat(formatter/html): add line break at the end of files by @dyc3 in #4010
  • fix(parser/html): fix incorrect parsing when text starts with a quote by @dyc3 in #4011
  • chore(cli): replace PanicInfo -> PanicHookInfo by @minht11 in #4015
  • chore: enforce usage of to_ascii_lowercase_cow by @minht11 in #4014
  • chore: fix udeps failure by @dyc3 in #4016
  • feat(linter): implement useExplicitFunctionReturnType by @kaykdm in #3990
  • fix(parser/html): allow multi line attribute values by @dyc3 in #4018
  • feat(lsp): noExcessiveCognitiveComplexity diagnostic shows levels by @chrisgrieser in #4028
  • feat(html): implement debug features for html by @dyc3 in #4019
  • fix(parser/html): add param to void elements list by @dyc3 in #4020
  • feat(html): resolve format options by @dyc3 in #4017
  • test(format/grit): add tests for grit formatter by @branberry in #3937
  • perf(grit): use to_ascii_lowercase_cow by @dyc3 in #4053
  • perf(linter): performance improvement for css semantic model by @togami2864 in #4044
  • refactor(aria_metadata): generate ARIA metadata from specification by @Conaclos in #4055
  • refactor(parser/html): refactor comments to be nodes in the tree by @dyc3 in #4056
  • feat(markdown/parser): support thematic break block parser by @suxin2017 in #3982
  • feat(linter): implement no-nested-ternary by @kaykdm in #4067
  • fix(format/html): keep at most 1 empty line between elements by @dyc3 in #4057
  • fix(schema): make optional the options JSON schema field by @Conaclos in #4080
  • feat(grit): implement disregarded snippet nodes by @arendjr in #4084
  • chore: to_lowercase -> to_lowercase_cow by @minht11 in #4030
  • docs: fix isNan to isNaN by @Omochice in #4106

New Contributors

Full Changelog: cli/v1.9.2...cli/v1.9.3-nightly.75b4387

CLI v1.9.2

19 Sep 13:16
5f2287e
Compare
Choose a tag to compare

CLI

New features

Bug fixes

  • Fix #3917, where the fixed files were incorrectly computed. Contributed by @ematipico
  • Fixed an issue that caused GritQL contains queries to report false positives when the matched
    node appeared inside a sibling node. Contributed by @arendjr

Editors

Bug fixes

  • Fix #3923. Now the .editorconfig is correctly parsed by the LSP, and the options are correctly applied to files when formatting is triggered.
    Plus, the Biome LSP now watches for any change to the .editorconfig, and updates the formatting settings.

  • Reduced the number of log files generated by the LSP server. Now the maximum number of logs saved on disk is seven. Contributed by @ematipico

  • Fix the code actions capabilities available in the LSP Biome server. Before, the LSP was using the default capabilities, which resulted in pulling code actions even when they were disabled by the editor.

    This means that the code actions are pulled by the client only when the editor enables quickfix.biome, source.organizeImports.biome and source.fixAll.biome.

    Now, if you enable organizeImports.enabled: true in the biome.json, and then you configure your editor with the following code action source.organizeImports.biome: false, the editor won't sort the imports.

    Contributed by @ematipico

Linter

New features

Bug fixes

Parser

Bug fixes

  • useStrictMode now reports Script files with some directives, but without the use strict directive. Contributed by @Conaclos

  • The CSS parser now accepts the characters U+FFDCF and U+FFFD in identifiers. Contributed by @Conaclos

What's Changed

Other changes

  • chore: update biome version of rules by @nhedger in #3901
  • chore(ci): add gh token for setup-rust by @Jayllyz in #3902
  • fix(deps): update rust crates by @renovate in #3910
  • chore(deps): update rust crate serde_json to 1.0.128 by @renovate in #3909
  • feat(format/grit): grit formatter initial configuration by @branberry in #3885
  • docs(readme): add zh-tw readme translation by @jacklee814 in #3894
  • chore(deps): update dependency eslint to v9.10.0 by @renovate in #3913
  • chore(deps): update rust crate tokio to 1.40.0 by @renovate in #3918
  • chore(deps): update rust docker tag to v1.81.0 by @renovate in #3919
  • fix: re-implement #3856 to improve correctness by @anthonyshew in #3865
  • chore(deps): update rust crate insta to 1.40.0 by @renovate in #3916
  • chore(deps): update rust crate dashmap to 6.1.0 by @renovate in #3915
  • chore(deps): update dependency @typescript-eslint/eslint-plugin to v8.5.0 by @renovate in #3912
  • chore(deps): update @biomejs packages by @renovate in #3911
  • chore(deps): update rust crate serde to 1.0.210 by @renovate in #3906
  • chore(deps): update rust crate anyhow to 1.0.89 by @renovate in #3905
  • fix(parser/html): fix whitespace being lexed as html literal by @dyc3 in #3908
  • fix(config): handle unset and off values in editorconfig files by @dyc3 in #3907
  • fix: preserve other children in useConsistentCurlyBraces by @suzak in #3925
  • test: fix outdated snapshot tests by @ematipico in #3953
  • feat(format/html): port JsxChildList formatting to HtmlElementList by @dyc3 in #3782
  • chore(deps): update dependency vite to v5.4.6 [security] by @renovate in #3963
  • fix(parser/html): check void element names case insensitively by @dyc3 in #3959
  • fix(format/html): keep single quotes if string contains a double quote by @dyc3 in #3960
  • fix(format/html): fix doctype formatting by @dyc3 in #3961
  • feat(markdown): support markdown grammar code generation by @suxin2017 in #3775
  • feat(parser/html): lex and parse unquoted attribute values by @dyc3 in #3951
  • feat(parser/html): parse doctype declarations by @dyc3 in #3962
  • feat(parser/html): handle script and style tags by @dyc3 in #3970
  • build: upgrade to Rust 1.81 by @Conaclos in #3972
  • feat(html): add experimental-html feature flag to enable html file handler by @dyc3 in #3967
  • feat(grit): support for Grit pattern, predicate and function definitions by @arendjr in #3983
  • feat(grit): implement Grit built-ins by @arendjr in #3987
  • fix(grit): fix node walking by @arendjr in #3988

New Contributors

Full Changelog: cli/v1.9.1...cli/v1.9.2

CLI v1.9.1

15 Sep 17:06
9bf1e4c
Compare
Choose a tag to compare

Analyzer

CLI

Bug fixes

  • useEditorConfig now loads the editorconfig when running biome ci #3864. Contributed by @dyc3

  • Revert #3731 to fix broken quick fixes and code actions. Contributed by @nhedger

Linter

New Features

Bug fixes

What's Changed

Other changes

New Contributors

Full Changelog: cli/v1.9.1-nightly.12688b6...cli/v1.9.1

CLI v1.9.1-nightly.12688b6

13 Sep 22:07
12688b6
Compare
Choose a tag to compare
Pre-release

Analyzer

CLI

Bug fixes

  • useEditorConfig now loads the editorconfig when running biome ci #3864. Contributed by @dyc3

Configuration

Editors

Formatter

JavaScript APIs

Linter

Bug fixes

Parser

What's Changed

Other changes

New Contributors

Full Changelog: cli/v1.9.0...cli/v1.9.1-nightly.12688b6

CLI v1.9.0

12 Sep 13:36
b260d5b
Compare
Choose a tag to compare

Analyzer

CLI

New features

  • Add --graphql-linter-enabled option, to control whether the linter should be enabled or not for GraphQL files. Contributed by @ematipico

  • New EXPERIMENTAL search command. The search command allows you to search a Biome project using GritQL syntax.

    GritQL is a powerful language that lets you do structural searches on your codebase. This means that trivia such as whitespace or even the type of strings quotes used will be ignored in your search query. It also has many features for querying the structure of your code, making it much more elegant for searching code than regular expressions.

    While we believe this command may already be useful to users in some situations (especially when integrated in the IDE extensions!), we also had an ulterior motive for adding this command: We intend to utilize GritQL for our plugin efforts, and by allowing our users to try it out in a first iteration, we hope to gain insight in the type of queries you want to do, as well as the bugs we need to focus on.

    For now, the search command is explicitly marked as EXPERIMENTAL, since many bugs remain. Keep this in mind when you try it out, and please let us know your issues!

    Note: GritQL escapes code snippets using backticks, but most shells interpret backticks as command invocations. To avoid this, it's best to put single quotes around your Grit queries.

    biome search '`console.log($message)`' # find all `console.log` invocations

    Contributed by @arendjr and @BackupMiles

  • The option --max-diagnostics now accept a none value, which lifts the limit of diagnostics shown. Contributed by @ematipico

    • Add a new reporter --reporter=gitlab, that emits diagnostics for using the GitLab Code Quality report.

      [
        {
          "description": "Use === instead of ==. == is only allowed when comparing against `null`",
          "check_name": "lint/suspicious/noDoubleEquals",
          "fingerprint": "6143155163249580709",
          "severity": "critical",
          "location": {
            "path": "main.ts",
            "lines": {
              "begin": 4
            }
          }
        }
      ]

      Contributed by @NiclasvanEyk

  • Add new options to the lsp-proxy and start commands:

    • --log-path: a directory where to store the daemon logs. The commands also accepts the environment variable BIOME_LOG_PATH.
    • --log-prefix-name: a prefix that's added to the file name of the logs. It defaults to server.log. The commands also accepts the environment variable BIOME_LOG_PREFIX_NAME.

    @contributed by @ematipico

Enhancements

  • When a --reporter is provided, and it's different from the default one, the value provided by via --max-diagnostics is ignored and the limit is lifted. Contributed by @ematipico

  • biome init now generates a new config file with more options set.
    This change intends to improve discoverability of the options and to set the more commonly used options to their default values.
    Contributed by @Conaclos

  • The --verbose flag now reports the list of files that were evaluated, and the list of files that were fixed.
    The evaluated files are the those files that can be handled by Biome, files that are ignored, don't have an extension or have an extension that Biome can't evaluate are excluded by this list.
    The fixed files are those files that were handled by Biome and changed. Files that stays the same after the process are excluded from this list.

     VERBOSE  ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
    
      ℹ Files processed:
    
      - biome/biome.json
      - biome/packages/@biomejs/cli-win32-arm64/package.json
      - biome/packages/tailwindcss-config-analyzer/package.json
    
     VERBOSE  ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
    
      ℹ Files fixed:
    
      - biome/biome/packages/tailwindcss-config-analyzer/src/generate-tailwind-preset.ts

    Contributed by @ematipico

  • Allow passing nursery to the --only and --skip filters.

    The --only option allows you to run a given rule or rule group.
    The --skip option allows you to skip the execution of a given group or a given rule.

    Previously, it was not possible to pass nursery.
    This restriction is now removed, as it may make sense to skip the nursery rules that a project has enabled.

    Contributed by @Conaclos

  • The CLI now returns an error code when calling a command in stdin mode, and the contents of the files aren't fixed. For example, the following example will result in an error code of 1 because the lint command triggers some lint rules:

    echo "let x = 1" | biome lint --stdin-file-path=stdin.js

    Contributed by @ematipico

Bug fixes

  • biome lint --write now takes --only and --skip into account (#3470). Contributed by @Conaclos

  • Fix #3368, now the reporter github tracks the diagnostics that belong to formatting and organize imports. Contributed by @ematipico

  • Fix #3545, display a warning, 'Avoid using unnecessary Fragment,' when a Fragment contains only one child element that is placed on a new line. Contributed by @satojin219

  • Migrating from Prettier or ESLint no longer overwrite the overrides field from the configuration (#3544). Contributed by @Conaclos

  • Fix JSX expressions for noAriaHiddenOnFocusable (#3708). Contributed by @anthonyshew

  • Fix edge case for <canvas> elements that use role="img" (#3728). Contributed by @anthonyshew

  • Fix #3633, where diagnostics where incorrectly printed if the code has errors. Contributed by @ematipico

  • Allow aria-label on heading to prevent useHeadingContent diagnostic (#3767). Contributed by @anthonyshew

  • Fix edge case #3791 for rule noFocusedTests being used with non-string-like expressions (#3793). Contributed by @h-a-n-a

  • Fix optional ARIA properties for role="separator" in useAriaPropsForRole (#3856). Contributed by @anthonyshew

Configuration

  • Add support for loading configuration from .editorconfig files (#1724).

    Configuration supplied in .editorconfig will be overridden by the configuration in biome.json. Support is disabled by default and can be enabled by adding the following to your formatter configuration in biome.json:

    {
      "formatter": {
        "useEditorconfig": true
      }
    }

    Contributed by @dyc3

  • overrides from an extended configuration is now merged with the overrides of the extension.

    Given the following shared configuration biome.shared.json:

    {
      "overrides": [
        {
          "include": ["**/*.json"],
          // ...
        }
      ]
    }

    and the following configuration:

    {
      "extends": ["./biome.shared.json"],
      "overrides": [
        {
          "include": ["**/*.ts"],
          // ...
        }
      ]
    }

    Previously, the overrides from biome.shared.json was overwritten.
    It is now merged and results in the following configuration:

    {
      "extends": ["./biome.shared.json"],
      "overrides": [
        {
          "include": ["**/*.json"],
          // ...
        },
        {
          "include": ["**/*.ts"],
          // ...
        }
      ]
    }

    Contributed by @Conaclos

Editors

  • Fix #3577, where the update of the configuration file was resulting in the creation of a new internal project. Contributed by @ematipico

  • Fix #3696, where biome.jsonc was incorrectly parsed with incorrect options. Contributed by @ematipico

Formatter

  • The CSS formatter is enabled by default. Which means that you don't need to opt-in anymore using the configuration file biome.json:

    {
    -  "css": {
    -    "formatter": {
    -      "enabled": true
    -    }
    -  }
    }

    Contributed by @ematipico

  • Add parentheses for nullcoalescing in ternaries.

    This change aligns on Prettier 3.3.3.
    This adds clarity to operator precedence.

    - foo ? bar ?? foo : baz;
    + foo ? (bar ?? foo) : baz;

    Contributed by @Conaclos

  • Keep the parentheses around infer ... extends declarations in type unions and type intersections (#3419). Contributed by @Conaclos

  • Keep parentheses around a yield expression inside a type assertion.

    Previously, Biome removed parentheses around some expressions that require them inside a type assertion.
    For example, in the following code, Biome now preserves the parentheses.

    function* f() {
      return <T>(yield 0);
    }

    Contributed by @Conaclos

  • Remove parentheses around expressions that don't need them inside a decorator.

    Biome now matches Pr...

Read more

CLI v1.8.4-nightly.7aaf0ce

06 Sep 09:13
7aaf0ce
Compare
Choose a tag to compare
Pre-release

Analyzer

New features

Enhancements

CLI

New features

  • Add --graphql-linter-enabled option, to control whether the linter should be enabled or not for GraphQL files. Contributed by @ematipico

  • New EXPERIMENTAL search command. The search command allows you to search a Biome project using GritQL syntax.

    GritQL is a powerful language that lets you do structural searches on your codebase. This means that trivia such as whitespace or even the type of strings quotes used will be ignored in your search query. It also has many features for querying the structure of your code, making it much more elegant for searching code than regular expressions.

    While we believe this command may already be useful to users in some situations (especially when integrated in the IDE extensions!), we also had an ulterior motive for adding this command: We intend to utilize GritQL for our plugin efforts, and by allowing our users to try it out in a first iteration, we hope to gain insight in the type of queries you want to do, as well as the bugs we need to focus on.

    For now, the search command is explicitly marked as EXPERIMENTAL, since many bugs remain. Keep this in mind when you try it out, and please let us know your issues!

    Note: GritQL escapes code snippets using backticks, but most shells interpret backticks as command invocations. To avoid this, it's best to put single quotes around your Grit queries.

    biome search '`console.log($message)`' # find all `console.log` invocations

    Contributed by @arendjr and @BackupMiles

  • The option --max-diagnostics now accept a none value, which lifts the limit of diagnostics shown. Contributed by @ematipico

    • Add a new reporter --reporter=gitlab, that emits diagnostics for using the GitLab Code Quality report.

      [
        {
          "description": "Use === instead of ==. == is only allowed when comparing against `null`",
          "check_name": "lint/suspicious/noDoubleEquals",
          "fingerprint": "6143155163249580709",
          "severity": "critical",
          "location": {
            "path": "main.ts",
            "lines": {
              "begin": 4
            }
          }
        }
      ]

      Contributed by @NiclasvanEyk

  • Add new options to the lsp-proxy and start commands:

    • --log-path: a directory where to store the daemon logs. The commands also accepts the environment variable BIOME_LOG_PATH.
    • --log-prefix-name: a prefix that's added to the file name of the logs. It defaults to server.log. The commands also accepts the environment variable BIOME_LOG_PREFIX_NAME.

    @contributed by @ematipico

Enhancements

  • When a --reporter is provided, and it's different from the default one, the value provided by via --max-diagnostics is ignored and the limit is lifted. Contributed by @ematipico

  • biome init now generates a new config file with more options set.
    This change intends to improve discoverability of the options and to set the more commonly used options to their default values.
    Contributed by @Conaclos

  • The --verbose flag now reports the list of files that were evaluated, and the list of files that were fixed.
    The evaluated files are the those files that can be handled by Biome, files that are ignored, don't have an extension or have an extension that Biome can't evaluate are excluded by this list.
    The fixed files are those files that were handled by Biome and changed. Files that stays the same after the process are excluded from this list.

     VERBOSE  ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
    
      ℹ Files processed:
    
      - biome/biome.json
      - biome/packages/@biomejs/cli-win32-arm64/package.json
      - biome/packages/tailwindcss-config-analyzer/package.json
    
     VERBOSE  ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
    
      ℹ Files fixed:
    
      - biome/biome/packages/tailwindcss-config-analyzer/src/generate-tailwind-preset.ts

    Contributed by @ematipico

  • Allow passing nursery to the --only and --skip filters.

    The --only option allows you to run a given rule or rule group.
    The --skip option allows you to skip the execution of a given group or a given rule.

    Previously, it was not possible to pass nursery.
    This restriction is now removed, as it may make sense to skip the nursery rules that a project has enabled.

    Contributed by @Conaclos

  • The CLI now returns an error code when calling a command in stdin mode, and the contents of the files aren't fixed. For example, the following example will result in an error code of 1 because the lint command triggers some lint rules:

    echo "let x = 1" | biome lint --stdin-file-path=stdin.js

    Contributed by @ematipico

Bug fixes

  • biome lint --write now takes --only and --skip into account (#3470). Contributed by @Conaclos

  • Fix #3368, now the reporter github tracks the diagnostics that belong to formatting and organize imports. Contributed by @ematipico

  • Fix #3545, display a warning, 'Avoid using unnecessary Fragment,' when a Fragment contains only one child element that is placed on a new line. Contributed by @satojin219

  • Migrating from Prettier or ESLint no longer overwrite the overrides field from the configuration (#3544). Contributed by @Conaclos

  • Fix JSX expressions for noAriaHiddenOnFocusable (#3708). Contributed by @anthonyshew

  • Fix edge case for <canvas> elements that use role="img" (#3728). Contributed by @anthonyshew

  • Fix #3633, where diagnostics where incorrectly printed if the code has errors. Contributed by @ematipico

  • Allow aria-label on heading to prevent useHeadingContent diagnostic (#3767). Contributed by @anthonyshew

  • Fix edge case #3791 for rule noFocusedTests being used with non-string-like expressions (#3793). Contributed by @h-a-n-a

Configuration

  • Add support for loading configuration from .editorconfig files (#1724).

    Configuration supplied in .editorconfig will be overridden by the configuration in biome.json. Support is disabled by default and can be enabled by adding the following to your formatter configuration in biome.json:

    {
      "formatter": {
        "useEditorconfig": true
      }
    }

    Contributed by @dyc3

  • overrides from an extended configuration is now merged with the overrides of the extension.

    Given the following shared configuration biome.shared.json:

    {
      "overrides": [
        {
          "include": ["**/*.json"],
          // ...
        }
      ]
    }

    and the following configuration:

    {
      "extends": ["./biome.shared.json"],
      "overrides": [
        {
          "include": ["**/*.ts"],
          // ...
        }
      ]
    }

    Previously, the overrides from biome.shared.json was overwritten.
    It is now merged and results in the following configuration:

    {
      "extends": ["./biome.shared.json"],
      "overrides": [
        {
          "include": ["**/*.json"],
          // ...
        },
        {
          "include": ["**/*.ts"],
          // ...
        }
      ]
    }

    Contributed by @Conaclos

Editors

Bug fixes

  • Fix #3577, where the update of the configuration file was resulting in the creation of a new internal project. Contributed by @ematipico
  • Fix #3696, where biome.jsonc was incorrectly parsed with incorrect options. Contributed by @ematipico

Formatter

Enhancements

  • Add parentheses for nullcoalescing in ternaries.

    This change aligns on Prettier 3.3.3.
    This adds clarity to operator precedence.

    - foo ? bar ?? foo : baz;
    + foo ? (bar ?? foo) : baz;

    Contributed by @Conaclos

  • The CSS formatter is enabled by default. Which means that you don't need to opt-in anymore using the configuration file biome.json:

    {
    -  "css": {
    -    "formatter": {
    -      "enabled": true
    -    }
    -  }
    }

    Contributed by @ematipico

Bug fixes

  • Keep the parentheses around infer ... extends declarations in type unions and type intersections (#3419). Contributed by @Conaclos

  • Keep parentheses around a yield expression inside a type assertion.

    Previously, Biome removed parentheses around some expressions that require them inside a type assertion.
    For example, in the following code, Biome now preserves the parentheses.

    function* f() {
      return <T>(yield 0);
    }

    Contributed by @Conaclos

  • Remove parentheses around expressions ...

Read more

CLI v1.8.4-nightly.bd1d0c6

04 Aug 10:20
bd1d0c6
Compare
Choose a tag to compare
Pre-release

Analyzer

Enhancements

CLI

New features

  • Add --graphql-linter-enabled option, to control whether the linter should be enabled or not for GraphQL files. Contributed by @ematipico
  • The option --max-diagnostics now accept a none value, which lifts the limit of diagnostics shown. Contributed by @ematipico

Enhancements

  • When a --reporter is provided, and it's different from the default one, the value provided by via --max-diagnostics is ignored and the limit is lifted. Contributed by @ematipico

  • biome init now generates a new config file with more options set.
    This change intends to improve discoverability of the options and to set the more commonly used options to their default values.
    Contributed by Conaclos

Bug fixes

  • biome lint --write now takes --only and --skip into account (#3470). Contributed by Conaclos

Configuration

  • Add support for loading configuration from .editorconfig files (#1724). Contributed by @dyc3
    Configuration supplied in .editorconfig will be overridden by the configuration in biome.json. Support is disabled by default and can be enabled by adding the following to your formatter configuration in biome.json:
    {
      "formatter": {
        "useEditorconfig": true
      }
    }

Formatter

Enhancements

  • Add parentheses for nullcoalescing in ternaries.

    This change aligns on Prettier 3.3.3.
    This adds clarity to operator precedence.

    - foo ? bar ?? foo : baz;
    + foo ? (bar ?? foo) : baz;

    Contributed by @Conaclos

Bug fixes

  • Keep the parentheses around infer declarations in type unions and type intersections (#3419). Contributed by @Conaclos

  • Keep parentheses around a yield expression inside a type assertion.

    Previously, Biome removed parentheses around some expressions that require them inside a type assertion.
    For example, in the following code, Biome now preserves the parentheses.

    function* f() {
      return <T>(yield 0);
    }

    Contributed by @Conaclos

  • Remove parentheses around expressions that don't need them inside a decorator.

    Biome now matches Prettier in the following cases:

      class {
    -   @(decorator)
    +   @decorator
        method() {}
      },
      class {
    -   @(decorator())
    +   @decorator()
        method() {}
      },
      class {
        @(decorator?.())
        method() {}
      },

    Contributed by @Conaclos

  • Keep parentheses around objects preceded with a @satisfies comment.

    In the following example, parentheses are no longer removed.

    export const PROPS = /** @satisfies {Record<string, string>} */ ({
      prop: 0,
    });

    Contributed by @Conaclos

Linter

New features

Enhancements

  • noInvalidUseBeforeDeclaration now reports direct use of an enum member before its declaration.

    In the following code, A is reported as use before its declaration.

    enum E {
      B = A << 1,
      A = 1,
    }

    Contributed by @Conaclos

  • useFilenamingConvention now supports unicase letters.

    unicase letters have a single case: they are neither uppercase nor lowercase.
    Biome now accepts filenames in unicase.
    For example, the filename 안녕하세요 is now accepted.

    We still reject a name that mixes unicase characters with lowercase or uppercase characters.
    For example, the filename A안녕하세요 is rejected.

    This change also fixes #3353.
    Filenames consisting only of numbers are now accepted.

    Contributed by @Conaclos

  • useFilenamingConvention now supports Next.js/Nuxt/Astro dynamic routes (#3465).

    Next.js, SolidStart, Nuxt, and Astro support dynamic routes such as [...slug].js and [[...slug]].js.

    Biome now recognizes this syntax. slug must contain only alphanumeric characters.

    Contributed by @Conaclos

  • useExportType no longer report empty export (#3535).

    An empty export {} allows you to force TypeScript to consider a file with no imports and exports as an EcmaScript module.
    While export type {} is valid, it is more common to use export {}.
    Users may find it confusing that the linter asks them to convert it to export type {}.
    Also, a bundler should be able to remove export {} as well as export type {}.
    So it is not so useful to report export {}.

    Contributed by @Conaclos

  • noUnusedVariables now checks TypeScript declaration files.

    This allows to report a type that is unused because it isn't exported.
    Global declarations files (declarations files without exports and imports) are still ignored.

    Contributed by @Conaclos

Bug fixes

  • Don't request alt text for elements hidden from assistive technologies (#3316). Contributed by @robintown

  • Fix [#3149] crashes that occurred when applying the noUselessFragments unsafe fixes in certain scenarios. Contributed by @unvalley

  • noExcessiveNestedTestSuites: Fix another edge case where the rule would alert on heavily nested zod schemas. Contributed by @dyc3

  • noExtraNonNullAssertion no longer reports a single non-null assertion enclosed in parentheses (#3352). Contributed by @Conaclos

  • useAdjacentOverloadSignatures no longer reports a #private class member and a public class member that share the same name (#3309).

    The following code is no longer reported:

    class C {
      #f() {}
      g() {}
      f() {}
    }

    Contributed by @Conaclos

  • useNamingConvention now accepts applying custom convention on abstract classes. Contributed by @Conaclos

  • useNamingConvention no longer suggests an empty fix when a name doesn't match strict Pascal case (#3561).

    Previously the following code led useNamingConvention to suggest an empty fix.
    The rule no longer provides a fix for this case.

    type AAb = any

    Contributed by @Conaclos

  • useNamingConvention no longer provides fixes for global TypeScript declaration files.

    Global TypeScript declaration files have no epxorts and no imports.
    All the declared types are available in all files of the project.
    Thus, it is not safe to propose renaming only in the declaration file.

    Contributed by @Conaclos

Parser

Bug fixes

.class {
  && {
    color: red;
  }
}
  • Fix #3410 by correctly parsing break statements containing keywords.
    out: while (true) {
      break out;
    }
    Contributed by @ah-yu

What's Changed

Other changes

  • fix(codegen): create output directory if it doesn't exist by @dyc3 in #3389
  • refactor(codegen): generate most functions on LanguageKind with a macro by @dyc3 in #3380
  • chore(grit): add auto-wrap + integrate with search command by @arendjr in #3288
  • refactor(formatter_test...
Read more