Skip to content

build(deps-dev): bump all (major) #1601

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
wants to merge 1 commit into
base: live
Choose a base branch
from
Open

build(deps-dev): bump all (major) #1601

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 23, 2025 •
edited
Loading

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@biomejs/biome (source) 1.9.4 -> 2.0.6 age adoption passing confidence
stylelint-config-recess-order 6.1.0 -> 7.1.0 age adoption passing confidence
stylelint-config-standard-scss 14.0.0 -> 15.0.1 age adoption passing confidence

Release Notes

biomejs/biome (@​biomejs/biome)

v2.0.6

Compare Source

Patch Changes

  • #​6557 fd68458 Thanks @​ematipico! - Fixed a bug where Biome didn't provide all the available code actions when requested by the editor.

  • #​6511 72623fa Thanks @​Conaclos! - Fixed #​6492. The
    organizeImports assist action no longer duplicates a comment at the start of
    the file when :BLANK_LINE: precedes the first import group.

  • #​6557 fd68458 Thanks @​ematipico! - Fixed #​6287 where Biome Language Server didn't adhere to the settings.requireConfiguration option when pulling diagnostics and code actions.
    Note that for this configuration be correctly applied, your editor must support dynamic registration capabilities.

  • #​6551 0b63b1d Thanks @​Conaclos! - Fixed #​6536. useSortedKeys no longer panics in some edge cases where object spreads are involved.

  • #​6503 9a8fe0f Thanks @​ematipico! - Fixed #​6482 where nursery rules that belonged to a domain were incorrectly enabled.

  • #​6565 e85761c Thanks @​daivinhtran! - Fixed #​4677: Now the noUnusedImports rule won't produce diagnostics for types used in JSDoc comment of exports.

  • #​6166 b8cbd83 Thanks @​mehm8128! - Added the nursery rule noExcessiveLinesPerFunction.
    This rule restrict a maximum number of lines of code in a function body.

    The following code is now reported as invalid when the limit of maximum lines is set to 2:

    function foo() {
  const x = 0;
  const y = 1;
  const z = 2;
}

    The following code is now reported as valid when the limit of maximum lines is set to 3:

    const bar = () => {
  const x = 0;
  const z = 2;
};

  • #​6553 5f42630 Thanks @​denbezrukov! - Fixed #​6547. Now the Biome CSS parser correctly parses @starting-style when it's used inside other at-rules. The following example doesn't raise an error anymore:

    @​layer my-demo-layer {
  @​starting-style {
    div.showing {
      background-color: red;
    }
  }
}

  • #​6458 05402e3 Thanks @​ematipico! - Fixed an issue where the rule useSemanticElements used the incorrect range when positioning suppression comments.

  • #​6560 6d8a6b9 Thanks @​siketyan! - Fixed #​6559: the error message on detected a large file was outdated and referred a removed configuration option files.ignore.

  • #​6458 05402e3 Thanks @​ematipico! - Fixed #​6384. The rule useAltText now emits a diagnostic with a correct range, so suppression comments can work correctly.

  • #​6518 7a56288 Thanks @​wojtekmaj! - Fixed #​6508, where the rule noUselessFragments incorrectly flagged Fragments containing HTML entities as unnecessary.

  • #​6517 c5217cf Thanks @​arendjr! - Fixed #​6515. When using the
    extends field to extend a configuration from an NPM package, we now accept the
    condition names "biome" and "default" for exporting the configuration in
    the package.json.

    This means that where previously your package.json had to contain an export
    declaration similar to this:

    {
  "exports": {
    ".": "./biome.json"
  }
}

    You may now use one of these as well:

    {
  "exports": {
    ".": {
      "biome": "./biome.json"
    }
  }
}

    Or:

    {
  "exports": {
    ".": {
      "default": "./biome.json"
    }
  }
}

  • #​6219 a3a3715 Thanks @​huangtiandi1999! - Added new nursery rule noUnassignedVariables, which disallows let or var variables that are read but never assigned.

    The following code is now reported as invalid:

    let x;
if (x) {
  console.log(1);
}

    The following code is now reported as valid:

    let x = 1;
if (x) {
  console.log(1);
}

  • #​6395 f62e748 Thanks @​mdevils! - Added the new nursery rule noImplicitCoercion, which disallows shorthand type conversions in favor of explicit type conversion functions.

    Example (Invalid): Boolean conversion using double negation:

    !!foo;
!!(foo + bar);

    Example (Invalid): Number conversion using unary operators:

    +foo;
-(-foo);
foo - 0;
foo * 1;
foo / 1;

    Example (Invalid): String conversion using concatenation:

    "" + foo;
foo + "";
`` + foo;
foo += "";

    Example (Invalid): Index checking using bitwise NOT:

    ~foo.indexOf(1);
~foo.bar.indexOf(2);

    Example (Valid): Using explicit type conversion functions:

    Boolean(foo);
Number(foo);
String(foo);
foo.indexOf(1) !== -1;

  • #​6544 f28b075 Thanks @​daivinhtran! - Fixed #​6536. Now the rule noUselessFragments produces diagnostics for a top-level useless fragment that is in a return statement.

  • #​6320 5705f1a Thanks @​mdevils! - Added the new nursery rule useUnifiedTypeSignature, which disallows overload signatures that can be unified into a single signature.

    Overload signatures that can be merged into a single signature are redundant and should be avoided. This rule helps simplify function signatures by combining overloads by making parameters optional and/or using type unions.

    Example (Invalid): Overload signatures that can be unified:

    function f(a: number): void;
function f(a: string): void;
    interface I {
  a(): void;
  a(x: number): void;
}

    Example (Valid): Unified signatures:

    function f(a: number | string): void {}
    interface I {
  a(x?: number): void;
}

    Example (Valid): Different return types cannot be merged:

    interface I {
  f(): void;
  f(x: number): number;
}

  • #​6545 2782175 Thanks @​ematipico! - Fixed #​6529, where the Biome Language Server would emit an error when the user would open a file that isn't part of its workspace (node_modules or external files).
    Now the language server doesn't emit any errors and it exits gracefully.

  • #​6524 a27b825 Thanks @​vladimir-ivanov! - Fixed #​6500: The useReadonlyClassProperties rule now correctly marks class properties as readonly when they are assigned in a constructor, setter or method,
    even if the assignment occurs inside an if or else block.

    The following code is now correctly detected by the rule:

    class Price {
  #price: string;

  @​Input()
  set some(value: string | number) {
    if (
      value === undefined ||
      value === null ||
      value === "undefined" ||
      value === "null" ||
      Number.isNaN(value)
    ) {
      this.#price = "";
    } else {
      this.#price = "" + value;
    }
  }
}

  • #​6355 e128ea9 Thanks @​anthonyshew! - Added a new nursery rule noAlert that disallows the use of alert, confirm and prompt.

    The following code is deemed incorrect:

    alert("here!");

  • #​6548 37e9799 Thanks @​ematipico! - Fixed #​6459, where the Biome LSP was not taking into account the correct settings when applying source.fixAll.biome code action.

v2.0.5

Compare Source

Patch Changes

  • #​6461 38862e6 Thanks @​ematipico! - Fixed #​6419, a regression where stdin mode would create a temporary new file instead of using the one provided by the user. This was an intended regression.

    Now Biome will use the file path passed via --std-file-path, and apply the configuration that matches it.

  • #​6480 050047f Thanks @​Conaclos! - Fixed #​6371.
    useNamingConvention now checks the string case of objects' property shorthand.

  • #​6477 b98379d Thanks @​ematipico! - Fixed an issue where Biome formatter didn't format consistently CSS value separated by commas.

    .font-heading {
- font-feature-settings: var(--heading-salt), var(--heading-ss06),
-   var(--heading-ss11), var(--heading-cv09), var(--heading-liga),
-   var(--heading-calt);

+  font-feature-settings:
+    var(--heading-salt), var(--heading-ss06), var(--heading-ss11),
+    var(--heading-cv09), var(--heading-liga), var(--heading-calt);
}

  • #​6248 ec7126c Thanks @​fireairforce! - Fixed grit pattern matching for different kinds of import statements.

    The grit pattern import $imports from "foo" will match the following code:

    import bar from "foo";
import { bar } from "foo";
import { bar, baz } from "foo";

v2.0.4

Compare Source

Patch Changes

v2.0.3

Patch Changes

  • #​6439 7e4da4e Thanks @​ematipico! - Fixed an issue where the correct rights aren't added to the binary during publishing

  • #​6297 cc4b8c9 Thanks @​vladimir-ivanov! - Added a new lint useReadonlyClassProperties rule.
    This rule is a port of ESLint's prefer-readonly rule.

    Example:

    class Example {
  // All properties below can be marked as readonly
  public constantValue = 42;
  protected initializedInConstructor: string;
  private privateField = true;

  constructor(initializedInConstructor: string) {
    this.initializedInConstructor = initializedInConstructor;
  }
}

v2.0.2

Patch Changes

v2.0.1

Compare Source

Patch Changes

v2.0.0

Compare Source

Major Changes

  • Biome now resolves globs and paths from the configuration. Before, paths and globs were resolved from the working directory.

  • Biome now raises a warning diagnostic for suppression comments that have <explanation> as reason.

    <explanation> is provided as a placeholder when applying the suppression code fix from LSP editors.

  • Removed the --config-path argument from the biome lsp-proxy and biome start commands.

    The option was overriding the configuration path for all workspaces opened in the Biome daemon, which led to a configuration mismatch problem when multiple projects are opened in some editors or IDEs.

    If you are using one of our official plugins for IDEs or editors, it is recommended to update it to the latest version of the plugin, or you will get unexpected behavior.

    If you are a developer of a plugin, please update your plugin to use the workspace/configuration response instead of using the --config-path argument. Biome's LSP will resolve a configuration in the workspace automatically, so it is recommended to keep it empty unless you are using a custom configuration path.

  • Downgraded some code fixes to unsafe which were previously safe.

    The following rules have now a unsafe fix:

    If you want to keep applying these fixes automatically, configure the rule fix as safe:

    {
  "linter": {
    "rules": {
      "correctness": {
        "noFlatMapIdentity": {
          "level": "error",
          "fix": "safe"
        },
        "noUnusedImports": {
          "level": "error",
          "fix": "safe"
        }
      }
    }
  }
}

  • Previously the lint rules noControlCharactersInRegex and noMisleadingCharacterClass checked both regular expression literals like /regex/ and dynamically built regular expressions like new RegExp("regex").

    Checking dynamically built regular expressions has many limitations, edge cases, and complexities.
    In addition, other rules that lint regular expressions don't check dynamically built regular expressions.

    Rather than add support for other rules and have half-baked checking, we decided to remove support for dynamically built regular expressions.

    Now the lint rules noControlCharactersInRegex and noMisleadingCharacterClass only check literals of regular expressions.

  • The lint rule noRestrictedGlobals now supports customizing message for each global name.

    For example, the following configuration:

    {
  "options": {
    "deniedGlobals": {
      "$": "jQuery is not allowed. Use native DOM manipulation instead."
    }
  }
}

    emits a diagnostic:

    index.js:1:13 lint/style/noRestrictedGlobals ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  ⚠ Do not use the global variable $.

  > 1 │ console.log($)
      │             ^
    2 │

  ℹ jQuery is not allowed. Use native DOM manipulation instead.

    Breaking Change: The option deniedGlobals is now a record instead of an array. Run biome migrate to migrate the configuration automatically.

  • Removed include and ignore fields in favor of the new field includes.

    The Biome configuration file allows users to specify which files should be processed using glob patterns.
    Prior to Biome 2.0, this was done using the include and ignore fields.
    In Biome 2.0, include and ignore are removed and replaced by includes.
    You can run biome migrate to convert include and ignore into includes automatically.

    includes uses a different glob pattern format that fixes many issues and many other limitations that Biome users reported.

    includes accepts an array of glob patterns.
    A glob pattern starting with a ! is a negated pattern also called exception.
    This replaces ignore patterns and allows users to create chains of include and ignore patterns.
    Thus, it is now possible to include again a file previously ignored.
    This was not possible with include and ignore, because ignore has priority over include.

    The semantics of * and **/* have changed too.
    Before, with include and ignore, the glob * was interpreted as **/*.
    Now, with includes, the globs * and **/* are interpreted differently.
    The first pattern matches all files that are inside a folder.
    The second pattern recursively matches all files and sub-folders inside a folder.

    Let's take an example.
    Given the following file hierarchy of a project...

    ├── biome.json
├── src
│   ├── file.js
│   ├── file.ts
│   ├── out.gen.js
│   ├── file.test.js
│   └── test
│       └── special.test.js
└── test ...

    ...we want:

    1. Ignore all files ending with .test.js, except special.test.ts.
    2. Ignore all files of the test directory.
      The test directory is located at the root of the project.
    3. Execute the linter on files in the src directory, that don't end with .gen.js.
      The src directory is located at the root of the project.
    4. Enable the noDefaultExport lint rule on files ending with .ts.

    Prior to Biome 2.0, the configuration might look like:

    {
  "files": {
    "ignore": ["*.test.js", "test"]
  },
  "linter": {
    "include": ["src/**"],
    "ignore": ["*.gen.js"],
    "enabled": true
  },
  "overrides": [
    {
      "include": ["*.ts"],
      "linter": { "rules": { "style": { "noDefaultExport": "on" } } }
    }
  ]
}

    Unfortunately, the configuration doesn't quite fit what we want:

    1. There is no way to ignore files and unignore one of them.
      Thus, we ignore all files ending with .test.js, including special.test.ts.
    2. The configuration ignores all directories named test, including src/test.
    3. The linter is executed on all files of all directories named src

    All these issues and limitations are fixed with includes.
    Here the migrated configuration:

    {
  "files": {
    "includes": ["**", "!**/*.test.js", "**/special.test.ts", "!test"]
  },
  "linter": {
    "includes": ["src/**", "!**/*.gen.js"],
    "enabled": true
  },
  "overrides": [
    {
      "includes": ["**/*.ts"],
      "linter": { "rules": { "style": { "noDefaultExport": "on" } } }
    }
  ]
}
    1. All files named special.test.ts are unignored because the pattern appear after the pattern that ignore files ending with .test.js.
    2. Only the test directory at the project's root is ignored because the pattern doesn't start with **/.
    3. The linter is executed on the src directory at the project's root only.

    Because includes pattern have a different pattern format than include and ignore we made some adjustments:

    • We added the pattern ** in files.includes to ensure that all files are included before ignoring some of them.
    • We added the prefix **/ for patterns that must match at any level of the file hierarchy.

  • noUndeclaredVariables no longer reports TypeScript types.

    In TypeScript projects, developers often use global declaration files to declare global types.
    Biome is currently unable to detect these global types.
    This creates many false positives for noUndeclaredVariables.

    TypeScript is better suited to perform this kind of check.
    As proof of this, TypeScript ESLint doesn't provide any rule that extends the no-undef ESLint rule.

    This is why Biome 1.9 introduced a new option checkTypes which, when it is set to false, ignores undeclared type references.
    The option was set to true by default.

    This option is now set to false by default.
    To get the previous behavior, you have to set checkTypes to true:

    {
  "linter": {
    "rules": {
      "correctness": {
        "noUndeclaredVariables": {
          "level": "on",
          "options": { "checkTypes": true }
        }
      }
    }
  }
}

  • The rule noUnusedVariables no longer reports unused function parameters. Use noUnusedFunctionParameters.

  • Fixed #​5564. noTypeOnlyImportAttributes now ignores files ending with the extension .ts when the type field of package.json is set to commonjs.

  • The Biome formatter no longer adds a trailing comma in .json files, even when json.formatter.trailingCommas is set to true.

  • Prettier 3.4 introduced a change in their normalization process of string literals: it no longer unescapes useless escape sequences.
    Biome now matches the new behavior of Prettier when formatting code.
    This affects the JSON and JavaScript formatters.

  • Reduced accepted values for formatter options:

    • The option --quote-style doesn't accept Single and Double anymore.
    • The option --quote-properties doesn't accept AsNeeded and Preserve anymore.
    • The option --semicolons doesn't accept AsNeeded and Always anymore.
    • The option --arrow-parenthesis doesn't accept AsNeeded and Always anymore.
    • The option --trailing-commas doesn't accept ES5, All and None anymore.
    • The option --attribute-position doesn't accept Single and Multiline anymore.

  • Removed the option enumMemberCase from the lint rule useNamingConvention.

    enumMemberCase is an option that allows to customize the enforced case for TypeScript's enum members.
    The option was introduced prior to the conventions option that allows to do the same thing.

    The following configuration...

    {
  "linter": {
    "rules": {
      "style": {
        "useNamingConvention": {
          "level": "on",
          "options": {
            "enumMemberCase": "PascalCase"
          }
        }
      }
    }
  }
}

    ...must be rewritten as:

    {
  "linter": {
    "rules": {
      "style": {
        "useNamingConvention": {
          "level": "on",
          "options": {
            "conventions": [
              {
                "selector": { "kind": "enumMember" },
                "formats": ["PascalCase"]
              }
            ]
          }
        }
      }
    }
  }
}

    Run biome migrate --write to turn enumMemberCase into conventions automatically.

  • Removed support for BIOME_LOG_DIR.

    The environment variable BIOME_LOG_DIR isn't supported anymore.

    Use BIOME_LOG_PATH instead.

  • Remove deprecated rules.

    The following deprecated rules have been deleted:

    • noInvalidNewBuiltin
    • noNewSymbol
    • useShorthandArrayType
    • useSingleCaseStatement
    • noConsoleLog

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

  • Removed the deprecated indentSize option.

    The deprecated option indentSize, and its relative CLI options, has been removed:

    • Configuration file: formatter.indentSize
    • Configuration file: javascript.formatter.indentSize
    • Configuration file: json.formatter.indentSize
    • CLI option --indent-size
    • CLI option --javascript-formatter-indent-size
    • CLI option --json-formatter-indent-size

    Use indentWidth and its relative CLI options instead.

  • Removed ROME_BINARY. Use BIOME_BINARY instead.

  • Removed support for legacy suppressions.

    Biome used to support "legacy suppressions" that looked like this:

    // biome-ignore lint(complexity/useWhile): reason

    This format is no longer supported.

  • Removed support for max_line_length from .editorconfig, as it isn't part of the official spec anymore.

  • Removed support for rome-ignore suppression comments.

    Use biome-ignore suppression comments instead.

  • Removed support for rome.json.

    Use biome.json or biome.jsonc instead.

  • Removed the option all from the linter.

    The options linter.rules.all and linter.rules.<group>.all has been removed.

    The number of rules in Biome have increased in scope and use cases, and sometimes some of them can conflict with each other.

    The option was useful at the beginning, but now it's deemed harmful, because it can unexpected behaviours in users projects.

    To automatically remove it, run the following command:

    biome migrate --write

  • Removed the option trailingComma from the configuration and the CLI. Use the option trailingCommas instead:

    {
  "javascript": {
    "formatter": {
-      "trailingComma": "es5"
+      "trailingCommas": "es5"
    }
  }
}
    -biome format --trailing-comma=es5
+biome format --trailing-commas=es5

  • Removed --apply and --apply-unsafe.

    The CLI options --apply and --apply-unasfe aren't accepted anymore. Use --write and --write --unafe instead:

    -biome check --apply-unsafe
+biome check --write --unsafe
    -biome check --apply
+biome check --write

  • Removed support for assert syntax.

    Biome now longer supports the assert syntax, use the new with syntax instead

    -import {test} from "foo.json" assert { for: "for" }
-export * from "mod" assert { type: "json" }
+import {test} from "foo.json" with { for: "for" }
+export * from "mod" with { type: "json" }

  • Fixed #​5495: The rule
    noBlankTarget has been
    updated to accept the rel="noopener" in addition to rel="noreferrer".
    In addition, an option has been added that allows rel="noreferrer" to be
    disabled.

    The rule has been moved from the a11y group to the security group.

  • The rule useImportRestrictions has been renamed to noPrivateImports, and its
    functionality has been significantly upgraded.

    Previously, the rule would assume that any direct imports from modules inside
    other directories should be forbidden due to their package private visibility.

    The updated rule allows configuring the default visibility of exports, and
    recognises JSDoc comments to override this visibility. The default visibility
    is now **public**, but can be set to **package**, or even **private**.
    Refer to the documentation of the rule to understand how to leverage the JSDoc comments.

    noPrivateImports is now recommended by default.

  • The Biome daemon now reuses its workspace across connections. This allows multiple clients to
    reuse the same documents and other cached data that we extract from them.

    This primarily affects our IDE extensions: If you open multiple IDEs/windows for the same project,
    they'll connect to the same daemon and reuse each other's workspace.

    The Biome CLI is unaffected unless you opt in with the --use-server argument.

  • Biome no longer treats too large files as errors.

    Previously, files that exceed the configured size limit would throw an error, and the CLI would exit with an error code.

    Now, the CLI ignores the file, emits an information diagnostic and doesn't exit with an error code.

  • Change the group of some rules, promote nursery rules and update the recommended rule set.

    The following rules have been moved to a new group:

    New rules are incubated in the nursery group.
    Once stable, we promote them to a stable group.
    Use the biome migrate command to automatically migrate nursery rules that have been promoted.

    The following CSS rules have been promoted:

    The following GraphQL rules have been promoted:

    The following JavaScript rules have been promoted:

    Moreover, the following JavaScript rules are now recommended:

    And the following style rules are no longer recommended:

  • Update the default severity level of lint rules.

    Every diagnostic emitted by Biome has a severity level set to error, warn, or info.
    Previously, all recommended lint rules had a default severity level set to error.
    All other lint rules had a default severity level set to warn.

    We have adjusted the default severity level of every rule, whether recommended or not, to better communicate the severity that a diagnostic highlights.

    • Rules that report hard errors, likely erroneous code, dangerous code, or accessibility issues now have a default severity level of error.
    • Rules that report possibly erroneous codes, or code that could be cleaner if rewritten in another way now have a default severity level of warn.
    • Rules that reports stylistic suggestions now have a default severity level of info.

    You can use the CLI option --diagnostic-level=error to display only errors, or --diagnostic-level=warning to display both errors and warnings.
    By default, all diagnostics are shown.
    You can also use the CLI option --error-on-warnings to make the command fail when warnings are emitted.

  • Reworked some recommended rules recommended to be less pedantic and blocking. This is a breaking change if your project relied on those rules to block the CI in case of violations; if that's the case, you should raise their severity level to error.

    Some rules aren't recommended anymore, and some others return a different severity.

    The following rules return a warning diagnostic:

    • noDelete
    • noForEach
    • noSuspiciousSemicolonInJsx
    • noThisInStatic
    • noUnusedLabels

    The following rules return an information diagnostic:

    • noUselessCatch
    • noUselessConstructor
    • noUselessEmptyExport
    • noUselessFragments
    • noUselessLabel
    • noUselessLoneBlockStatements
    • noUselessSwitchCase
    • noUselessTernary
    • noUselessThisAlias
    • noUselessTypeConstraint
    • noFlatMapIdentity

    The following rules aren't recommended anymore:

    • noDelete
    • noForEach

    The rule noRenderReturnValue and useExhaustiveDependencies are only recommended when the react domain is enabled.

  • Renamed the global option --skip-errors to --skip-parse-errors.

  • Remove the code action quickfix.suppressRule.

    The code action quickfix.suppressRule was removed in favour of two new code actions:

    • quickfix.suppressRule.inline.biome: a code action that adds a suppression comment for each violation.
    • quickfix.suppressRule.topLevel.biome: a code action that adds a suppression comment at the top of the file which suppresses a rule for the whole file.

    Given the following code

    let foo = "one";
debugger;

    The code action quickfix.suppressRule.inline.biome will result in the following code:

    // biome-ignore lint/style/useConst: <explanation>
let foo = "one";
// biome-ignore lint/suspicious/noDebugger: <explanation>
debugger;

    The code action quickfix.suppressRule.topLevel.biome, instead, will result in the following code:

    /** biome-ignore lint/suspicious/noDebugger: <explanation> */
/** biome-ignore lint/style/useConst: <explanation> */

let foo = "one";
debugger;

  • Changed default formatting of package.json.

    When Biome encounters a file called package.json, by default it will format the file with all objects and arrays expanded.

    - { "name": "project", "dependencies": { "foo": "latest" } }
+ {
+  "projectName": "project",
+  "dependencies": {
+    "foo": "^1.0.0"
+  }
+ }

  • The organizeImports is now part of Biome Assist.

  • The rule noVar now belongs to the suspicious group

  • The rule useWhile now belongs to the complexity group.

  • The rule useImportExtensions has been updated to suggest actual file extensions instead of guesses based on hueristics.

    As part of this, the suggestedExtensions option has been removed. A simpler,
    new option called forceJsExtensions has been introduced for those who use
    tsc's "module": "node16" setting.

    The rule also no longer reports diagnostics to add an extension when the path
    doesn't exist at all, with or without extension.

  • Fixed #​4545: useNamingConvention now correctly ignores declarations inside TypeScript's external modules.

    The following interface name is no longer reported by the rule:

    declare module "myExternalModule" {
  export interface my_INTERFACE {}
}

  • The rule useAltText no longer checks the element's attributes containing object spread.

    The following code doesn't trigger the rule anymore:

    <img src="test.png" alt={alt} {...restProps}></img>

  • The rule useNamingConvention no longer accepts non-ASCII characters by default.

    Prior to Biome 2.0, non-ASCII names were accepted by default. They are now rejected.

    For example, the following code is now reported as invalid by the useNamingConvention rule.

    let johnCafé;

    If you want to allow non ASCII filenames and non-ASCII identifiers, you need to set the requireAscii options in your Biome configuration file to false:

    {
    "linter": {
        "rules": {
            "style": {
                "useFilenamingConvention": {
                    "level": "on",
                    "options": {
                        "requireAscii": false
                    }
                }
                "useFilenamingConvention": {
                    "level": "on",
                    "options": {
                        "requireAscii": false
                    }
                }
            }
        }
    }
}

  • Renamed the rule noUnnecessaryContinue to noUselessContinue. Run the command biome migrate to update your configuration.

  • Renamed the rule noMultipleSpacesInRegularExpressionLiterals to noAdjacentSpacesInRegex. Run the command biome migrate to update your configuration.

Minor Changes

  • An option called allowNoReferrer has been added to the
    noBlankTarget rule.

    By default, noBlankTarget accepts both rel="noopener" and rel="noreferrer"
    with links that have target="_blank". This is because the latter implies the
    former, so either one is sufficient to mitigate the security risk.

    However, allowing rel="noreferrer" may still be undesirable, because it can
    break tracking, which may be an undesirable side-effect. As such, you can set
    allowNoReferrer: false to only accept rel="noopener".

  • Added new option javascript.parser.jsxEverywhere. This new option allows to control whether Biome should expect JSX syntax in .js/.mjs/.cjs files.

    When jsxEverywhere is set to false, having JSX syntax like <div></div> inside .js/.mjs/.cjs files will result in a parsing error.

    Despite the name of the option, JSX is never supported inside .ts files. This is because TypeScript generics syntax may conflict with JSX in such files.

    This option defaults to true.

  • Add a new JS assist rule - useSortedKeys which enforces ordering of a JS object properties.
    This rule will consider spread/calculated keys e.g [k]: 1 as non-sortable.
    Instead, whenever it encounters a non-sortable key, it will sort all the
    previous sortable keys up until the nearest non-sortable key, if one exist.
    This prevents breaking the override of certain keys using spread keys.

    Source: https://perfectionist.dev/rules/sort-objects

    // Base
// from
const obj = {
  b: 1,
  a: 1,
  ...g,
  ba: 2,
  ab: 1,
  set aab(v) {
    this._aab = v;
  },
  [getProp()]: 2,
  aba: 2,
  abc: 3,
  abb: 3,
  get aaa() {
    return "";
  },
};
// to
const obj = {
  a: 1,
  b: 1,
  ...g,
  set aab(v) {
    this._aab = v;
  },
  ab: 1,
  ba: 2,
  [getProp()]: 2,
  get aaa() {
    return "";
  },
  aba: 2,
  abb: 3,
  abc: 3,
};

  • Added the new rule noFloatingPromises.

  • Added the new rule noImportCycles.

  • Added the new rule noTsIgnore.

  • Added the new rule noUnwantedPolyfillio.

  • Added a format option expand for Javascript and JSON formatters.
    The option allows to enforce the formatting of arrays and objects on multiple lines, regardless of their length.
    It has three options:

    When set to auto (default), objects are expanded if the first property has a leading newline.
    Arrays are collapsed when they fit to a single line.
    For example, both styles below are considered as already formatted:

    const obj = {
  foo: "bar",
};
    const obj = { foo: "bar" };

    When set to always, objects and arrays are always expanded.

    When set to never, objects and arrays are never expanded when they fit in a single line.
    It is equivalent to Prettier's Object Wrap option with collapse.

  • The nursery rule noUnresolvedImports has been added.

    Importing a non-existing export is an error at runtime or build time. With this
    rule, Biome can detect such incorrect imports and report errors for them.

    Note that if you use TypeScript, you probably don't want to use this rule, since
    TypeScript already performs such checks for you.

  • The rule noFocusedTests can now detect the usage of focused tests inside loops.

    // invalid
describe.only.each([["a"], ["b"]])("%s", (a) => {});
it.only.each([["a"], ["b"]])("%s", (a) => {});
test.only.each([["a"], ["b"]])("%s", (a) => {});

// valid
describe.each([["a"], ["b"]])("%s", (a) => {});
it.each([["a"], ["b"]])("%s", (a) => {});
test.each([["a"], ["b"]])("%s", (a) => {});

  • Linter groups now accept new options to enable/disable all rules that belong to a group, and control the severity
    of the rules that belong to those groups.

    For example, you can downgrade the severity of rules that belong to "style" to emit "info" diagnostics:

    {
  "linter": {
    "rules": {
      "style": "info"
    }
  }
}

    You can also enable all rules that belong to a group using the default severity of the rule using the "on" option:

    {
  "linter": {
    "rules": {
      "complexity": "on"
    }
  }
}

  • Biome assist is a new feature of the Biome analyzer. The

Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, only on Monday ( * 0-3 * * 1 ) (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@netlify Netlify
Copy link

netlify bot commented Jun 23, 2025 •
edited
Loading

❌ Deploy Preview for gh-pages-openinf failed. Why did it fail? →

Name Link
🔨 Latest commit a0d5ae6
🔍 Latest deploy log https://app.netlify.com/projects/gh-pages-openinf/deploys/685e8fc5b4c12b00080ce10c

@renovate renovate bot force-pushed the renovate/major-all branch 2 times, most recently from 7f64c03 to 7d30387 Compare June 23, 2025 16:40
@socket-security Socket Security
Copy link

socket-security bot commented Jun 23, 2025 •
edited
Loading

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security		 Vulnerability Quality Maintenance License
Updated@​biomejs/​biome@​1.9.4 ⏵ 2.0.6100 +710010099 +1100

View full report

@renovate
build(deps-dev): bump all
a0d5ae6 
Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
@renovate renovate bot force-pushed the renovate/major-all branch from 7d30387 to a0d5ae6 Compare June 27, 2025 12:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
build dependencies deps-dev
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants