Yumeo/Glorpcha
1
0
Fork 0
Code Issues 1 Pull requests Projects Releases Packages 1 Wiki Activity Actions

chore(deps): update dependency @biomejs/biome to v2.2.0 - autoclosed #22

Closed
Renovate wants to merge 1 commit from renovate/biomejs-biome-2.x into main
pull from: renovate/biomejs-biome-2.x
merge into: Yumeo:main
Conversation 1 Commits 1 Files changed 1 +1 -1
Renovate commented 2025-08-08 02:00:13 +02:00
Collaborator
Copy link

This PR contains the following updates:

Package Change Age Confidence
@biomejs/biome (source) 2.1.3 -> 2.2.0 age confidence

Release Notes

biomejs/biome (@​biomejs/biome)

v2.2.0

Compare Source

Minor Changes

  • #​5506 1f8755b Thanks @​sakai-ast! - The noRestrictedImports rule has been enhanced with a new patterns option. This option allows for more flexible and powerful import restrictions using gitignore-style patterns.

    You can now define patterns to restrict entire groups of modules. For example, you can disallow imports from any path under import-foo/ except for import-foo/baz.

    {
  "options": {
    "patterns": [
      {
        "group": ["import-foo/*", "!import-foo/baz"],
        "message": "import-foo is deprecated, except for modules in import-foo/baz."
      }
    ]
  }
}

    Invalid examples

    import foo from "import-foo/foo";
import bar from "import-foo/bar";

    Valid examples

    import baz from "import-foo/baz";

    Additionally, the patterns option introduces importNamePattern to restrict specific import names using regular expressions.
    The following example restricts the import names that match x , y or z letters from modules under import-foo/.

    {
  "options": {
    "patterns": [
      {
        "group": ["import-foo/*"],
        "importNamePattern": "[xyz]"
      }
    ]
  }
}

    Invalid examples

    import { x } from "import-foo/foo";

    Valid examples

    import { foo } from "import-foo/foo";

    Furthermore, you can use the invertImportNamePattern boolean option to reverse this logic. When set to true, only the import names that match the importNamePattern will be allowed. The following configuration only allows the import names that match x , y or z letters from modules under import-foo/.

    {
  "options": {
    "patterns": [
      {
        "group": ["import-foo/*"],
        "importNamePattern": "[xyz]",
        "invertImportNamePattern": true
      }
    ]
  }
}

    Invalid examples

    import { foo } from "import-foo/foo";

    Valid examples

    import { x } from "import-foo/foo";

  • #​6506 90c5d6b Thanks @​nazarhussain! - Allow customization of the sort order for different sorting actions. These actions now support a sort option:

    For each of these options, the supported values are the same:

    1. natural. Compares two strings using a natural ASCII order. Uppercase letters come first (e.g. A < a < B < b) and number are compared in a human way (e.g. 9 < 10). This is the default value.
    2. lexicographic. Strings are ordered lexicographically by their byte values. This orders Unicode code points based on their positions in the code charts. This is not necessarily the same as “alphabetical” order, which varies by language and locale.

  • #​7159 df3afdf Thanks @​ematipico! - Added the new rule useBiomeIgnoreFolder. Since v2.2, Biome correctly prevents the indexing and crawling of folders.

    However, the correct pattern has changed. This rule attempts to detect incorrect usage, and promote the new pattern:

    // biome.json
{
  "files": {
    "includes": [
-      "!dist/**",
-      "!**/fixtures/**",
+      "!dist",
+      "!**/fixtures",
    ]
  }
}

  • #​6989 85b1128 Thanks @​arendjr! - Fixed minor inconsistencies in how files.includes was being handled.

    Previously, Biome sometimes failed to properly ignore the contents of a folder if you didn't specify the /** at the end of a glob pattern. This was unfortunate, because it meant we still had to traverse the folder and then apply the glob to every entry inside it.

    This is no longer an issue and we now recommend to ignore folders without using the /** suffix.

  • #​7118 a78e878 Thanks @​avshalomt2! - Added support for .graphqls files. Biome can now format and lint GraphQL files that have the extension .graphqls

  • #​6159 f02a296 Thanks @​bavalpey! - Added a new option to Biome's JavaScript formatter, javascript.formatter.operatorLinebreak, to configure whether long lines should be broken before or after binary operators.

    For example, the following configuration:

    {
  formatter: {
    javascript: {
      operatorLinebreak: "before", // defaults to "after"
    },
  },
}

    Will cause this JavaScript file:

    const VERY_LONG_CONDITION_1234123412341234123412341234 = false;

if (
  VERY_LONG_CONDITION_1234123412341234123412341234 &&
  VERY_LONG_CONDITION_1234123412341234123412341234 &&
  VERY_LONG_CONDITION_1234123412341234123412341234 &&
  VERY_LONG_CONDITION_1234123412341234123412341234
) {
  console.log("DONE");
}

    to be formatted like this:

    const VERY_LONG_CONDITION_1234123412341234123412341234 = false;
if (
  VERY_LONG_CONDITION_1234123412341234123412341234 &&
  VERY_LONG_CONDITION_1234123412341234123412341234 &&
  VERY_LONG_CONDITION_1234123412341234123412341234 &&
  VERY_LONG_CONDITION_1234123412341234123412341234
) {
  console.log("DONE");
}

  • #​7137 a653a0f Thanks @​ematipico! - Promoted multiple lint rules from nursery to stable groups and renamed several rules for consistency.

Promoted rules

The following rules have been promoted from nursery to stable groups:

CSS
GraphQL
JavaScript/TypeScript
Renamed rules

The following rules have been renamed during promotion. The migration tool will automatically update your configuration:

Configuration files using the old rule names will need to be updated. Use the migration tool to automatically update your configuration:

biome migrate --write

  • #​7159 df3afdf Thanks @​ematipico! - Added the new rule noBiomeFirstException. This rule prevents the incorrect usage of patterns inside files.includes.

    This rule catches if the first element of the array contains !. This mistake will cause Biome to analyze no files:

    // biome.json
{
  files: {
    includes: ["!dist/**"], // this is an error
  },
}

  • #​6923 0589f08 Thanks @​ptkagori! - Added Qwik Domain to Biome

    This release introduces Qwik domain support in Biome, enabling Qwik developers to use Biome as a linter and formatter for their projects.

  • #​6989 85b1128 Thanks @​arendjr! - Fixed #​6965: Implemented smarter scanner for project rules.

    Previously, if project rules were enabled, Biome's scanner would scan all dependencies regardless of whether they were used by/reachable from source files or not. While this worked for a first version, it was far from optimal.

    The new scanner first scans everything listed under the files.includes setting, and then descends into the dependencies that were discovered there, including transitive dependencies. This has three main advantages:

    • Dependencies that are not reachable from your source files don't get indexed.
    • Dependencies that have multiple type definitions, such as those with separate definitions for CommonJS and ESM imports, only have the relevant definitions indexed.
    • If vcs.useIgnoreFile is enabled, .gitignore gets respected as well. Assuming you have folders such as build/ or dist/ configured there, those will be automatically ignored by the scanner.

    The change in the scanner also has a more nuanced impact: Previously, if you used files.includes to ignore a file in an included folder, the scanner would still index this file. Now the file is fully ignored, unless you import it.

    As a user you should notice better scanner performance (if you have project rules enabled), and hopefully you need to worry less about configuring files.experimentalScannerIgnores. Eventually our goal is still to deprecate that setting, so if you're using it today, we encourage you to see which ignores are still necessary there, and whether you can achieve the same effect by ignoring paths using files.includes instead.

    None of these changes affect the scanner if no project rules are enabled.

  • #​6731 d6a05b5 Thanks @​ematipico! - The --reporter=summary has been greatly enhanced. It now shows the list of files that contains violations, the files shown are clickable and can be opened from the editor.

    Below an example of the new version:

    reporter/parse ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  i The following files have parsing errors.

  - index.css

reporter/format ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  i The following files needs to be formatted.

  - index.css
  - index.ts
  - main.ts

reporter/violations ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  i Some lint rules or assist actions reported some violations.

  Rule Name                                        Diagnostics

  lint/correctness/noUnknownFunction               14 (2 error(s), 12 warning(s), 0 info(s))
  lint/suspicious/noImplicitAnyLet                 16 (12 error(s), 4 warning(s), 0 info(s))
  lint/suspicious/noDoubleEquals                   8 (8 error(s), 0 warning(s), 0 info(s))
  assist/source/organizeImports                    2 (2 error(s), 0 warning(s), 0 info(s))
  lint/suspicious/noRedeclare                      12 (12 error(s), 0 warning(s), 0 info(s))
  lint/suspicious/noDebugger                       8 (8 error(s), 0 warning(s), 0 info(s))

  • #​6896 527db7f Thanks @​ematipico! - Added new functions to the @biomejs/wasm-* packages:

    • fileExists: returns whether the input file exists in the workspace.
    • isPathIgnored: returns whether the input path is ignored.
    • updateModuleGraph: updates the internal module graph of the input path.
    • getModuleGraph: it returns a serialized version of the internal module graph.
    • scanProject: scans the files and directories in the project to build the internal module graph.

  • #​6398 d1a315d Thanks @​josh-! - Added support for tracking stable results in user-provided React hooks that return objects to useExhaustiveDependencies to compliment existing support for array return values. For example:

    // biome.json
{
  // rule options
  useExhaustiveDependencies: {
    level: "error",
    options: {
      hooks: [
        {
          name: "useCustomHook",
          stableResult: ["setMyState"],
        },
      ],
    },
  },
}

    This will allow the following to be validated:

    const { myState, setMyState } = useCustomHook();
const toggleMyState = useCallback(() => {
  setMyState(!myState);
}, [myState]); // Only `myState` needs to be specified here.

  • #​7201 2afaa49 Thanks @​Conaclos! - Implemented #​7174. useConst no longer reports variables that are read before being written.

    Previously, useConst reported uninitialised variables that were read in an inner function before being written, as shown in the following example:

    let v;
function f() {
  return v;
}
v = 0;

    This can produce false positives in the case where f is called before v has been written, as in the following code:

    let v;
function f() {
  return v;
}
console.log(f()); // print `undefined`
v = 0;

    Although this is an expected behavior of the original implementation, we consider it problematic since the rule’s fix is marked as safe.
    To avoid false positives like this, the rule now ignores the previous examples.
    However, this has the disadvantage of resulting in false negatives, such as not reporting the first example.

Patch Changes

  • #​7156 137d111 Thanks @​ematipico! - Fixed #​7152. Now the rule noDuplicateFontNames correctly detects font names with spaces e.g. Liberation Mono. The diagnostic of the rule now points to the first instances of the repeated font.

    The following example doesn't trigger the rule anymore:

    c {
  font-family:
    SF Mono,
    Liberation Mono,
    sans-serif;
}
d {
  font:
    1em SF Mono,
    Liberation Mono,
    sans-serif;
}

  • #​6907 7331bb9 Thanks @​ematipico! - Added a new experimental option that allows parsing of .html files that contain interpolation syntax.

    // biome.json
{
  html: {
    // This is the new, experimental option.
    parser: {
      interpolation: true,
    },
  },
}

    <h1>{{ $title }}</h1>

  • #​7124 3f436b8 Thanks @​Jayllyz! - Added the rule useMaxParams.

    This rule enforces a maximum number of parameters for functions to improve code readability and maintainability. Functions with many parameters are difficult to read, understand, and maintain because they require memorizing parameter order and types.

    // Invalid - too many parameters (default max: 4)
function processData(
  name,
  age,
  email,
  phone,
  address,
  city,
  country,
  zipCode,
) {
  // ...
}

// Valid - within parameter limit
function processData(userData) {
  const { name, age, email, phone, address, city, country, zipCode } =
    userData;
  // ...
}

function calculateSum(a, b, c) {
  return a + b + c;
}

  • #​7161 1a14a59 Thanks @​ematipico! - Fixed #​7160. Now Biome correctly computes ignored files when using formatter.includes, linter.includes and assist.includes inside nested configurations that use "extends": "//".

  • #​7081 a081bbe Thanks @​Jayllyz! - Added the rule noNextAsyncClientComponent.

    This rule prevents the use of async functions for client components in Next.js applications. Client components marked with "use client" directive should not be async as this can cause hydration mismatches, break component rendering lifecycle, and lead to unexpected behavior with React's concurrent features.

    "use client";

// Invalid - async client component
export default async function MyComponent() {
  return <div>Hello</div>;
}

// Valid - synchronous client component
export default function MyComponent() {
  return <div>Hello</div>;
}

  • #​7171 5241690 Thanks @​siketyan! - Fixed #​7162: The noUndeclaredDependencies rule now considers a type-only import as a dev dependency.

    For example, the following code is no longer reported:

    package.json:

    {
  "devDependencies": {
    "type-fest": "*"
  }
}

    foo.ts:

    import type { SetRequired } from "type-fest";

    Note that you still need to declare the package in the devDependencies section in package.json.

v2.1.4

Compare Source

Patch Changes

  • #​7121 b9642ab Thanks @​arendjr! - Fixed #​7111: Imported symbols using aliases are now correctly recognised.

  • #​7103 80515ec Thanks @​omasakun! - Fixed #​6933 and #​6994.

    When the values of private member assignment expressions, increment expressions, etc. are used, those private members are no longer marked as unused.

  • #​6887 0cc38f5 Thanks @​ptkagori! - Added the noQwikUseVisibleTask rule to Qwik.

    This rule is intended for use in Qwik applications to warn about the use of useVisibleTask$() functions which require careful consideration before use.

    Invalid:

    useVisibleTask$(() => {
  console.log("Component is visible");
});

    Valid:

    useTask$(() => {
  console.log("Task executed");
});

  • #​7084 50ca155 Thanks @​ematipico! - Added the new nursery rule noUnnecessararyConditions, which detects whenever some conditions don't
    change during the life cycle of the program, and truthy or false, hence deemed redundant.

    For example, the following snippets will trigger the rule:

    // Always truthy literal conditions
if (true) {
  console.log("always runs");
}

    // Unnecessary condition on constrained string type
function foo(arg: "bar" | "baz") {
  if (arg) {
    // This check is unnecessary
  }
}

  • #​6887 0cc38f5 Thanks @​ptkagori! - Added the useImageSize rule to Biome.

    The useImageSize rule enforces the use of width and height attributes on <img> elements for performance reasons. This rule is intended to prevent layout shifts and improve Core Web Vitals by ensuring images have explicit dimensions.

    Invalid:

    <img src="/image.png" />
<img src="https://example.com/image.png" />
<img src="/image.png" width="200" />
<img src="/image.png" height="200" />

    Valid:

    <img width="200" height="600" src="/static/images/portrait-01.webp" />
<img width="100" height="100" src="https://example.com/image.png" />

  • #​6887 0cc38f5 Thanks @​ptkagori! - Added the useAnchorHref rule to Biome.

    The useAnchorHref rule enforces the presence of an href attribute on <a> elements in JSX. This rule is intended to ensure that anchor elements are always valid and accessible.

    Invalid:

    <a>Link</a>

    <a target="_blank">External</a>

    Valid:

    <a href="/home">Home</a>

    <a href="https://example.com" target="_blank">
  External
</a>

  • #​7100 29fcb05 Thanks @​Jayllyz! - Added the rule noNonNullAssertedOptionalChain.

    This rule prevents the use of non-null assertions (!) immediately after optional chaining expressions (?.). Optional chaining is designed to safely handle nullable values by returning undefined when the chain encounters null or undefined. Using a non-null assertion defeats this purpose and can lead to runtime errors.

    // Invalid - non-null assertion after optional chaining
obj?.prop!;
obj?.method()!;
obj?.[key]!;
obj?.prop!;

// Valid - proper optional chaining usage
obj?.prop;
obj?.method();
obj?.prop ?? defaultValue;
obj!.prop?.method();

  • #​7129 9f4538a Thanks @​drwpow! - Removed option, combobox, listbox roles from useSemanticElements suggestions

  • #​7106 236deaa Thanks @​arendjr! - Fixed #​6985: Inference of return types no longer mistakenly picks up return types of nested functions.

  • #​7102 d3118c6 Thanks @​omasakun! - Fixed #​7101: noUnusedPrivateClassMembers now handles members declared as part of constructor arguments:

    1. If a class member defined in a constructor argument is only used within the constructor, it removes the private modifier and makes it a plain method argument.
    2. If it is not used at all, it will prefix it with an underscore, similar to noUnusedFunctionParameter.

  • #​7104 5395297 Thanks @​harxki! - Reverting to prevent regressions around ref handling

  • #​7143 1a6933a Thanks @​siketyan! - Fixed #​6799: The noImportCycles rule now ignores type-only imports if the new ignoreTypes option is enabled (enabled by default).

    [!WARNING]
    Breaking Change: The noImportCycles rule no longer detects import cycles that include one or more type-only imports by default.
    To keep the old behaviour, you can turn off the ignoreTypes option explicitly:

    {
  "linter": {
    "rules": {
      "nursery": {
        "noImportCycles": {
          "options": {
            "ignoreTypes": false
          }
        }
      }
    }
  }
}

  • #​7099 6cc84cb Thanks @​arendjr! - Fixed #​7062: Biome now correctly considers extended configs when determining the mode for the scanner.

  • #​6887 0cc38f5 Thanks @​ptkagori! - Added the useQwikClasslist rule to Biome.

    This rule is intended for use in Qwik applications to encourage the use of the built-in class prop (which accepts a string, object, or array) instead of the classnames utility library.

    Invalid:

    <div class={classnames({ active: true, disabled: false })} />

    Valid:

    <div classlist={{ active: true, disabled: false }} />

  • #​7019 57c15e6 Thanks @​fireairforce! - Added support in the JS parser for import source(a stage3 proposal). The syntax looks like:

    import source foo from "<specifier>";

  • #​7053 655049e Thanks @​jakeleventhal! - Added the useConsistentTypeDefinitions rule.

    This rule enforces consistent usage of either interface or type for object type definitions in TypeScript.

    The rule accepts an option to specify the preferred style:

    • interface (default): Prefer using interface for object type definitions
    • type: Prefer using type for object type definitions

    Examples:

    // With default option (interface)
// ❌ Invalid
type Point = { x: number; y: number };

// ✅ Valid
interface Point {
  x: number;
  y: number;
}

// With option { style: "type" }
// ❌ Invalid
interface Point {
  x: number;
  y: number;
}

// ✅ Valid
type Point = { x: number; y: number };

    The rule will automatically fix simple cases where conversion is straightforward.

Configuration

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

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

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

This PR has been generated by Renovate Bot.

This PR contains the following updates: | Package | Change | Age | Confidence | |---|---|---|---| | [@biomejs/biome](https://biomejs.dev) ([source](https://github.com/biomejs/biome/tree/HEAD/packages/@biomejs/biome)) | [`2.1.3` -> `2.2.0`](https://renovatebot.com/diffs/npm/@biomejs%2fbiome/2.1.3/2.2.0) | [![age](https://developer.mend.io/api/mc/badges/age/npm/@biomejs%2fbiome/2.2.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/@biomejs%2fbiome/2.1.3/2.2.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | --- ### Release Notes <details> <summary>biomejs/biome (@&#8203;biomejs/biome)</summary> ### [`v2.2.0`](https://github.com/biomejs/biome/blob/HEAD/packages/@&#8203;biomejs/biome/CHANGELOG.md#220) [Compare Source](https://github.com/biomejs/biome/compare/@biomejs/biome@2.1.4...@biomejs/biome@2.2.0) ##### Minor Changes - [#&#8203;5506](https://github.com/biomejs/biome/pull/5506) [`1f8755b`](https://github.com/biomejs/biome/commit/1f8755bfcbcd913be9fc1961b45b5c7ade8695c3) Thanks [@&#8203;sakai-ast](https://github.com/sakai-ast)! - The `noRestrictedImports` rule has been enhanced with a new `patterns` option. This option allows for more flexible and powerful import restrictions using gitignore-style patterns. You can now define patterns to restrict entire groups of modules. For example, you can disallow imports from any path under `import-foo/` except for `import-foo/baz`. ```json { "options": { "patterns": [ { "group": ["import-foo/*", "!import-foo/baz"], "message": "import-foo is deprecated, except for modules in import-foo/baz." } ] } } ``` **Invalid examples** ```js import foo from "import-foo/foo"; import bar from "import-foo/bar"; ``` **Valid examples** ```js import baz from "import-foo/baz"; ``` Additionally, the `patterns` option introduces `importNamePattern` to restrict specific import names using regular expressions. The following example restricts the import names that match `x` , `y` or `z` letters from modules under `import-foo/`. ```json { "options": { "patterns": [ { "group": ["import-foo/*"], "importNamePattern": "[xyz]" } ] } } ``` **Invalid examples** ```js import { x } from "import-foo/foo"; ``` **Valid examples** ```js import { foo } from "import-foo/foo"; ``` Furthermore, you can use the `invertImportNamePattern` boolean option to reverse this logic. When set to true, only the import names that match the `importNamePattern` will be allowed. The following configuration only allows the import names that match `x` , `y` or `z` letters from modules under `import-foo/`. ```json { "options": { "patterns": [ { "group": ["import-foo/*"], "importNamePattern": "[xyz]", "invertImportNamePattern": true } ] } } ``` **Invalid examples** ```js import { foo } from "import-foo/foo"; ``` **Valid examples** ```js import { x } from "import-foo/foo"; ``` - [#&#8203;6506](https://github.com/biomejs/biome/pull/6506) [`90c5d6b`](https://github.com/biomejs/biome/commit/90c5d6b857f9fb985f919d601872b3650f1e1e5e) Thanks [@&#8203;nazarhussain](https://github.com/nazarhussain)! - Allow customization of the sort order for different sorting actions. These actions now support a sort option: - [`assist/source/useSortedKeys`](https://biomejs.dev/assist/actions/use-sorted-keys/) now has a `sortOrder` option - [`assist/source/useSortedAttributes`](https://biomejs.dev/assist/actions/use-sorted-attributes/) now has a `sortOrder` option - [`assist/source/organizeImports`](https://biomejs.dev/assist/actions/organize-imports/) now has an `identifierOrder` option For each of these options, the supported values are the same: 1. **`natural`**. Compares two strings using a natural ASCII order. Uppercase letters come first (e.g. `A < a < B < b`) and number are compared in a human way (e.g. `9` < `10`). This is the default value. 2. **`lexicographic`**. Strings are ordered lexicographically by their byte values. This orders Unicode code points based on their positions in the code charts. This is not necessarily the same as “alphabetical” order, which varies by language and locale. - [#&#8203;7159](https://github.com/biomejs/biome/pull/7159) [`df3afdf`](https://github.com/biomejs/biome/commit/df3afdf0e29ebb1db6ec4cf6f54ec822c82e38ab) Thanks [@&#8203;ematipico](https://github.com/ematipico)! - Added the new rule `useBiomeIgnoreFolder`. Since v2.2, Biome correctly prevents the indexing and crawling of folders. However, the correct pattern has changed. This rule attempts to detect incorrect usage, and promote the new pattern: ```diff // biome.json { "files": { "includes": [ - "!dist/**", - "!**/fixtures/**", + "!dist", + "!**/fixtures", ] } } ``` - [#&#8203;6989](https://github.com/biomejs/biome/pull/6989) [`85b1128`](https://github.com/biomejs/biome/commit/85b11289efbda3061438dfb52ceb186d2142a646) Thanks [@&#8203;arendjr](https://github.com/arendjr)! - Fixed minor inconsistencies in how `files.includes` was being handled. Previously, Biome sometimes failed to properly ignore the contents of a folder if you didn't specify the `/**` at the end of a glob pattern. This was unfortunate, because it meant we still had to traverse the folder and then apply the glob to every entry inside it. This is no longer an issue and we now recommend to ignore folders without using the `/**` suffix. - [#&#8203;7118](https://github.com/biomejs/biome/pull/7118) [`a78e878`](https://github.com/biomejs/biome/commit/a78e8781411d151cddec9425763df18ccd2e669b) Thanks [@&#8203;avshalomt2](https://github.com/avshalomt2)! - Added support for `.graphqls` files. Biome can now format and lint GraphQL files that have the extension `.graphqls` - [#&#8203;6159](https://github.com/biomejs/biome/pull/6159) [`f02a296`](https://github.com/biomejs/biome/commit/f02a296eae7e3a8dfeddbf1a034e2bb67e8c9c2d) Thanks [@&#8203;bavalpey](https://github.com/bavalpey)! - Added a new option to Biome's JavaScript formatter, `javascript.formatter.operatorLinebreak`, to configure whether long lines should be broken before or after binary operators. For example, the following configuration: ```json5 { formatter: { javascript: { operatorLinebreak: "before", // defaults to "after" }, }, } ``` Will cause this JavaScript file: ```js const VERY_LONG_CONDITION_1234123412341234123412341234 = false; if ( VERY_LONG_CONDITION_1234123412341234123412341234 && VERY_LONG_CONDITION_1234123412341234123412341234 && VERY_LONG_CONDITION_1234123412341234123412341234 && VERY_LONG_CONDITION_1234123412341234123412341234 ) { console.log("DONE"); } ``` to be formatted like this: ```js const VERY_LONG_CONDITION_1234123412341234123412341234 = false; if ( VERY_LONG_CONDITION_1234123412341234123412341234 && VERY_LONG_CONDITION_1234123412341234123412341234 && VERY_LONG_CONDITION_1234123412341234123412341234 && VERY_LONG_CONDITION_1234123412341234123412341234 ) { console.log("DONE"); } ``` - [#&#8203;7137](https://github.com/biomejs/biome/pull/7137) [`a653a0f`](https://github.com/biomejs/biome/commit/a653a0fb3fa8c6777c9d03829cd88adcfc6b6877) Thanks [@&#8203;ematipico](https://github.com/ematipico)! - Promoted multiple lint rules from nursery to stable groups and renamed several rules for consistency. ##### Promoted rules The following rules have been promoted from nursery to stable groups: ##### CSS - Promoted [`noImportantStyles`](https://biomejs.dev/linter/rules/no-important-styles) to the `complexity` group. - Promoted [`noUnknownAtRules`](https://biomejs.dev/linter/rules/no-unknown-at-rules) to the `suspicious` group. ##### GraphQL - Promoted [`useGraphqlNamedOperations`](https://biomejs.dev/linter/rules/use-graphql-named-operations) to the `correctness` group. - Promoted [`useGraphqlNamingConvention`](https://biomejs.dev/linter/rules/use-graphql-naming-convention) to the `style` group. ##### JavaScript/TypeScript - Promoted [`noExcessiveLinesPerFunction`](https://biomejs.dev/linter/rules/no-excessive-lines-per-function) to the `complexity` group. - Promoted [`noImplicitCoercions`](https://biomejs.dev/linter/rules/no-implicit-coercions) to the `complexity` group. - Promoted [`useIndexOf`](https://biomejs.dev/linter/rules/use-index-of) to the `complexity` group. - Promoted [`noGlobalDirnameFilename`](https://biomejs.dev/linter/rules/no-global-dirname-filename) to the `correctness` group. - Promoted [`noNestedComponentDefinitions`](https://biomejs.dev/linter/rules/no-nested-component-definitions) to the `correctness` group. - Promoted [`noProcessGlobal`](https://biomejs.dev/linter/rules/no-process-global) to the `correctness` group. - Promoted [`noReactPropAssignments`](https://biomejs.dev/linter/rules/no-react-prop-assignments) to the `correctness` group. - Promoted [`noRestrictedElements`](https://biomejs.dev/linter/rules/no-restricted-elements) to the `correctness` group. - Promoted [`noSolidDestructuredProps`](https://biomejs.dev/linter/rules/no-solid-destructured-props) to the `correctness` group. - Promoted [`useJsonImportAttributes`](https://biomejs.dev/linter/rules/use-json-import-attributes) to the `correctness` group. - Promoted [`useParseIntRadix`](https://biomejs.dev/linter/rules/use-parse-int-radix) to the `correctness` group. - Promoted [`useSingleJsDocAsterisk`](https://biomejs.dev/linter/rules/use-single-js-doc-asterisk) to the `correctness` group. - Promoted [`useUniqueElementIds`](https://biomejs.dev/linter/rules/use-unique-element-ids) to the `correctness` group. - Promoted [`noAwaitInLoops`](https://biomejs.dev/linter/rules/no-await-in-loops) to the `performance` group. - Promoted [`noUnwantedPolyfillio`](https://biomejs.dev/linter/rules/no-unwanted-polyfillio) to the `performance` group. - Promoted [`useGoogleFontPreconnect`](https://biomejs.dev/linter/rules/use-google-font-preconnect) to the `performance` group. - Promoted [`useSolidForComponent`](https://biomejs.dev/linter/rules/use-solid-for-component) to the `performance` group. - Promoted [`noMagicNumbers`](https://biomejs.dev/linter/rules/no-magic-numbers) to the `style` group. - Promoted [`useConsistentObjectDefinitions`](https://biomejs.dev/linter/rules/use-consistent-object-definitions) to the `style` group. - Promoted [`useExportsLast`](https://biomejs.dev/linter/rules/use-exports-last) to the `style` group. - Promoted [`useGroupedAccessorPairs`](https://biomejs.dev/linter/rules/use-grouped-accessor-pairs) to the `style` group. - Promoted [`useNumericSeparators`](https://biomejs.dev/linter/rules/use-numeric-separators) to the `style` group. - Promoted [`useObjectSpread`](https://biomejs.dev/linter/rules/use-object-spread) to the `style` group. - Promoted [`useReadonlyClassProperties`](https://biomejs.dev/linter/rules/use-readonly-class-properties) to the `style` group. - Promoted [`useSymbolDescription`](https://biomejs.dev/linter/rules/use-symbol-description) to the `style` group. - Promoted [`useUnifiedTypeSignatures`](https://biomejs.dev/linter/rules/use-unified-type-signatures) to the `style` group. - Promoted [`noBitwiseOperators`](https://biomejs.dev/linter/rules/no-bitwise-operators) to the `suspicious` group. - Promoted [`noConstantBinaryExpressions`](https://biomejs.dev/linter/rules/no-constant-binary-expressions) to the `suspicious` group. - Promoted [`noTsIgnore`](https://biomejs.dev/linter/rules/no-ts-ignore) to the `suspicious` group. - Promoted [`noUnassignedVariables`](https://biomejs.dev/linter/rules/no-unassigned-variables) to the `suspicious` group. - Promoted [`noUselessRegexBackrefs`](https://biomejs.dev/linter/rules/no-useless-regex-backrefs) to the `suspicious` group. - Promoted [`noUselessStringEscapes`](https://biomejs.dev/linter/rules/no-useless-string-escapes) to the `suspicious` group. - Promoted [`useConsistentIterableCallbackReturnValues`](https://biomejs.dev/linter/rules/use-consistent-iterable-callback-return-values) to the `suspicious` group. - Promoted [`useStaticResponseMethods`](https://biomejs.dev/linter/rules/use-static-response-methods) to the `suspicious` group. ##### Renamed rules The following rules have been renamed during promotion. The migration tool will automatically update your configuration: - Renamed `noAwaitInLoop` to [`noAwaitInLoops`](https://biomejs.dev/linter/rules/no-await-in-loops). - Renamed `noConstantBinaryExpression` to [`noConstantBinaryExpressions`](https://biomejs.dev/linter/rules/no-constant-binary-expressions). - Renamed `noDestructuredProps` to [`noSolidDestructuredProps`](https://biomejs.dev/linter/rules/no-solid-destructured-props). - Renamed `noImplicitCoercion` to [`noImplicitCoercions`](https://biomejs.dev/linter/rules/no-implicit-coercions). - Renamed `noReactPropAssign` to [`noReactPropAssignments`](https://biomejs.dev/linter/rules/no-react-prop-assignments). - Renamed `noUnknownAtRule` to [`noUnknownAtRules`](https://biomejs.dev/linter/rules/no-unknown-at-rules). - Renamed `noUselessBackrefInRegex` to [`noUselessRegexBackrefs`](https://biomejs.dev/linter/rules/no-useless-regex-backrefs). - Renamed `useAdjacentGetterSetter` to [`useGroupedAccessorPairs`](https://biomejs.dev/linter/rules/use-grouped-accessor-pairs). - Renamed `useConsistentObjectDefinition` to [`useConsistentObjectDefinitions`](https://biomejs.dev/linter/rules/use-consistent-object-definitions). - Renamed `useConsistentResponse` to [`useStaticResponseMethods`](https://biomejs.dev/linter/rules/use-static-response-methods). - Renamed `useForComponent` to [`useSolidForComponent`](https://biomejs.dev/linter/rules/use-solid-for-component). - Renamed `useJsonImportAttribute` to [`useJsonImportAttributes`](https://biomejs.dev/linter/rules/use-json-import-attributes). - Renamed `useNamedOperation` to [`useGraphqlNamedOperations`](https://biomejs.dev/linter/rules/use-graphql-named-operations). - Renamed `useNamingConvention` to [`useGraphqlNamingConvention`](https://biomejs.dev/linter/rules/use-graphql-naming-convention). - Renamed `useUnifiedTypeSignature` to [`useUnifiedTypeSignatures`](https://biomejs.dev/linter/rules/use-unified-type-signatures). Configuration files using the old rule names will need to be updated. Use the migration tool to automatically update your configuration: ```bash biome migrate --write ``` - [#&#8203;7159](https://github.com/biomejs/biome/pull/7159) [`df3afdf`](https://github.com/biomejs/biome/commit/df3afdf0e29ebb1db6ec4cf6f54ec822c82e38ab) Thanks [@&#8203;ematipico](https://github.com/ematipico)! - Added the new rule `noBiomeFirstException`. This rule prevents the incorrect usage of patterns inside `files.includes`. This rule catches if the first element of the array contains `!`. This mistake will cause Biome to analyze no files: ```json5 // biome.json { files: { includes: ["!dist/**"], // this is an error }, } ``` - [#&#8203;6923](https://github.com/biomejs/biome/pull/6923) [`0589f08`](https://github.com/biomejs/biome/commit/0589f085ee444418c742f5e5eb7fae0522d83ea0) Thanks [@&#8203;ptkagori](https://github.com/ptkagori)! - Added Qwik Domain to Biome This release introduces **Qwik domain support** in Biome, enabling Qwik developers to use Biome as a linter and formatter for their projects. - Added the Qwik domain infrastructure to Biome. - Enabled the following rules for Qwik: - [`useJsxKeyInIterable`](https://biomejs.dev/linter/rules/use-jsx-key-in-iterable) - [`noReactSpecificProps`](https://biomejs.dev/linter/rules/no-react-specific-props) - [#&#8203;6989](https://github.com/biomejs/biome/pull/6989) [`85b1128`](https://github.com/biomejs/biome/commit/85b11289efbda3061438dfb52ceb186d2142a646) Thanks [@&#8203;arendjr](https://github.com/arendjr)! - Fixed [#&#8203;6965](https://github.com/biomejs/biome/issues/6965): Implemented smarter scanner for project rules. Previously, if project rules were enabled, Biome's scanner would scan all dependencies regardless of whether they were used by/reachable from source files or not. While this worked for a first version, it was far from optimal. The new scanner first scans everything listed under the `files.includes` setting, and then descends into the dependencies that were discovered there, including transitive dependencies. This has three main advantages: - Dependencies that are not reachable from your source files don't get indexed. - Dependencies that have multiple type definitions, such as those with separate definitions for CommonJS and ESM imports, only have the relevant definitions indexed. - If `vcs.useIgnoreFile` is enabled, `.gitignore` gets respected as well. Assuming you have folders such as `build/` or `dist/` configured there, those will be automatically ignored by the scanner. The change in the scanner also has a more nuanced impact: Previously, if you used `files.includes` to ignore a file in an included folder, the scanner would still index this file. Now the file is fully ignored, *unless you import it*. As a user you should notice better scanner performance (if you have project rules enabled), and hopefully you need to worry less about configuring [`files.experimentalScannerIgnores`](https://biomejs.dev/reference/configuration/#filesexperimentalscannerignores). Eventually our goal is still to deprecate that setting, so if you're using it today, we encourage you to see which ignores are still necessary there, and whether you can achieve the same effect by ignoring paths using `files.includes` instead. None of these changes affect the scanner if no project rules are enabled. - [#&#8203;6731](https://github.com/biomejs/biome/pull/6731) [`d6a05b5`](https://github.com/biomejs/biome/commit/d6a05b5fa9358a5b1689b326724eaa7e2a86468d) Thanks [@&#8203;ematipico](https://github.com/ematipico)! - The `--reporter=summary` has been greatly enhanced. It now shows the list of files that contains violations, the files shown are clickable and can be opened from the editor. Below an example of the new version: ``` reporter/parse ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ i The following files have parsing errors. - index.css reporter/format ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ i The following files needs to be formatted. - index.css - index.ts - main.ts reporter/violations ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ i Some lint rules or assist actions reported some violations. Rule Name Diagnostics lint/correctness/noUnknownFunction 14 (2 error(s), 12 warning(s), 0 info(s)) lint/suspicious/noImplicitAnyLet 16 (12 error(s), 4 warning(s), 0 info(s)) lint/suspicious/noDoubleEquals 8 (8 error(s), 0 warning(s), 0 info(s)) assist/source/organizeImports 2 (2 error(s), 0 warning(s), 0 info(s)) lint/suspicious/noRedeclare 12 (12 error(s), 0 warning(s), 0 info(s)) lint/suspicious/noDebugger 8 (8 error(s), 0 warning(s), 0 info(s)) ``` - [#&#8203;6896](https://github.com/biomejs/biome/pull/6896) [`527db7f`](https://github.com/biomejs/biome/commit/527db7f7c142f8c95c6d4513603530220a4cc95c) Thanks [@&#8203;ematipico](https://github.com/ematipico)! - Added new functions to the `@biomejs/wasm-*` packages: - `fileExists`: returns whether the input file exists in the workspace. - `isPathIgnored`: returns whether the input path is ignored. - `updateModuleGraph`: updates the internal module graph of the input path. - `getModuleGraph`: it returns a serialized version of the internal module graph. - `scanProject`: scans the files and directories in the project to build the internal module graph. - [#&#8203;6398](https://github.com/biomejs/biome/pull/6398) [`d1a315d`](https://github.com/biomejs/biome/commit/d1a315d19e970341c8e6582c1f6f80b42c77ecb5) Thanks [@&#8203;josh-](https://github.com/josh-)! - Added support for tracking stable results in user-provided React hooks that return objects to [`useExhaustiveDependencies`](https://biomejs.dev/linter/rules/use-exhaustive-dependencies/) to compliment existing support for array return values. For example: ```json5 // biome.json { // rule options useExhaustiveDependencies: { level: "error", options: { hooks: [ { name: "useCustomHook", stableResult: ["setMyState"], }, ], }, }, } ``` This will allow the following to be validated: ```js const { myState, setMyState } = useCustomHook(); const toggleMyState = useCallback(() => { setMyState(!myState); }, [myState]); // Only `myState` needs to be specified here. ``` - [#&#8203;7201](https://github.com/biomejs/biome/pull/7201) [`2afaa49`](https://github.com/biomejs/biome/commit/2afaa49b814b12b52a1ffa06ed6c67d21ea57e1a) Thanks [@&#8203;Conaclos](https://github.com/Conaclos)! - Implemented [#&#8203;7174](https://github.com/biomejs/biome/issues/7174). [`useConst`](https://biomejs.dev/linter/rules/use-const/) no longer reports variables that are read before being written. Previously, `useConst` reported uninitialised variables that were read in an inner function before being written, as shown in the following example: ```js let v; function f() { return v; } v = 0; ``` This can produce false positives in the case where `f` is called before `v` has been written, as in the following code: ```js let v; function f() { return v; } console.log(f()); // print `undefined` v = 0; ``` Although this is an expected behavior of the original implementation, we consider it problematic since the rule’s fix is marked as safe. To avoid false positives like this, the rule now ignores the previous examples. However, this has the disadvantage of resulting in false negatives, such as not reporting the first example. ##### Patch Changes - [#&#8203;7156](https://github.com/biomejs/biome/pull/7156) [`137d111`](https://github.com/biomejs/biome/commit/137d1118e4598a0ef2c0104e45cb00a8bf179199) Thanks [@&#8203;ematipico](https://github.com/ematipico)! - Fixed [#&#8203;7152](https://github.com/biomejs/biome/issues/7152). Now the rule `noDuplicateFontNames` correctly detects font names with spaces e.g. `Liberation Mono`. The diagnostic of the rule now points to the first instances of the repeated font. The following example doesn't trigger the rule anymore: ```css c { font-family: SF Mono, Liberation Mono, sans-serif; } d { font: 1em SF Mono, Liberation Mono, sans-serif; } ``` - [#&#8203;6907](https://github.com/biomejs/biome/pull/6907) [`7331bb9`](https://github.com/biomejs/biome/commit/7331bb9979143c355d861eadcde4f075e6b70910) Thanks [@&#8203;ematipico](https://github.com/ematipico)! - Added a new **experimental option** that allows parsing of `.html` files that contain interpolation syntax. ```json5 // biome.json { html: { // This is the new, experimental option. parser: { interpolation: true, }, }, } ``` ```html <h1>{{ $title }}</h1> ``` - [#&#8203;7124](https://github.com/biomejs/biome/pull/7124) [`3f436b8`](https://github.com/biomejs/biome/commit/3f436b84bb62320c16c1ca1ac5b419e4d9abefb3) Thanks [@&#8203;Jayllyz](https://github.com/Jayllyz)! - Added the rule [`useMaxParams`](https://biomejs.dev/linter/rules/use-max-params). This rule enforces a maximum number of parameters for functions to improve code readability and maintainability. Functions with many parameters are difficult to read, understand, and maintain because they require memorizing parameter order and types. ```js // Invalid - too many parameters (default max: 4) function processData( name, age, email, phone, address, city, country, zipCode, ) { // ... } // Valid - within parameter limit function processData(userData) { const { name, age, email, phone, address, city, country, zipCode } = userData; // ... } function calculateSum(a, b, c) { return a + b + c; } ``` - [#&#8203;7161](https://github.com/biomejs/biome/pull/7161) [`1a14a59`](https://github.com/biomejs/biome/commit/1a14a59c52f9389220e7682de5632b7d7291a4e4) Thanks [@&#8203;ematipico](https://github.com/ematipico)! - Fixed [#&#8203;7160](https://github.com/biomejs/biome/issues/7160). Now Biome correctly computes ignored files when using `formatter.includes`, `linter.includes` and `assist.includes` inside nested configurations that use `"extends": "//"`. - [#&#8203;7081](https://github.com/biomejs/biome/pull/7081) [`a081bbe`](https://github.com/biomejs/biome/commit/a081bbef37a4b329ace1cb0eb88c36f6c6162af1) Thanks [@&#8203;Jayllyz](https://github.com/Jayllyz)! - Added the rule [`noNextAsyncClientComponent`](https://biomejs.dev/linter/rules/no-next-async-client-component). This rule prevents the use of async functions for client components in Next.js applications. Client components marked with "use client" directive should not be async as this can cause hydration mismatches, break component rendering lifecycle, and lead to unexpected behavior with React's concurrent features. ```jsx "use client"; // Invalid - async client component export default async function MyComponent() { return <div>Hello</div>; } // Valid - synchronous client component export default function MyComponent() { return <div>Hello</div>; } ``` - [#&#8203;7171](https://github.com/biomejs/biome/pull/7171) [`5241690`](https://github.com/biomejs/biome/commit/5241690265c584cfb4e6827e82a496801f039197) Thanks [@&#8203;siketyan](https://github.com/siketyan)! - Fixed [#&#8203;7162](https://github.com/biomejs/biome/issues/7162): The `noUndeclaredDependencies` rule now considers a type-only import as a dev dependency. For example, the following code is no longer reported: **`package.json`**: ```json { "devDependencies": { "type-fest": "*" } } ``` **`foo.ts`**: ```ts import type { SetRequired } from "type-fest"; ``` Note that you still need to declare the package in the `devDependencies` section in `package.json`. ### [`v2.1.4`](https://github.com/biomejs/biome/blob/HEAD/packages/@&#8203;biomejs/biome/CHANGELOG.md#214) [Compare Source](https://github.com/biomejs/biome/compare/@biomejs/biome@2.1.3...@biomejs/biome@2.1.4) ##### Patch Changes - [#&#8203;7121](https://github.com/biomejs/biome/pull/7121) [`b9642ab`](https://github.com/biomejs/biome/commit/b9642abc6d05135180f4243df30524cf40ba12df) Thanks [@&#8203;arendjr](https://github.com/arendjr)! - Fixed [#&#8203;7111](https://github.com/biomejs/biome/issues/7111): Imported symbols using aliases are now correctly recognised. - [#&#8203;7103](https://github.com/biomejs/biome/pull/7103) [`80515ec`](https://github.com/biomejs/biome/commit/80515ecad8cc272feeae4c17762d3b150acd88e7) Thanks [@&#8203;omasakun](https://github.com/omasakun)! - Fixed [#&#8203;6933](https://github.com/biomejs/biome/issues/6933) and [#&#8203;6994](https://github.com/biomejs/biome/issues/6994). When the values of private member assignment expressions, increment expressions, etc. are used, those private members are no longer marked as unused. - [#&#8203;6887](https://github.com/biomejs/biome/pull/6887) [`0cc38f5`](https://github.com/biomejs/biome/commit/0cc38f59cd9ddf0fdcd12d6f8cb3642743cc4406) Thanks [@&#8203;ptkagori](https://github.com/ptkagori)! - Added the [`noQwikUseVisibleTask`](https://biomejs.dev/linter/rules/no-qwik-use-visible-task) rule to Qwik. This rule is intended for use in Qwik applications to warn about the use of `useVisibleTask$()` functions which require careful consideration before use. **Invalid:** ```js useVisibleTask$(() => { console.log("Component is visible"); }); ``` **Valid:** ```js useTask$(() => { console.log("Task executed"); }); ``` - [#&#8203;7084](https://github.com/biomejs/biome/pull/7084) [`50ca155`](https://github.com/biomejs/biome/commit/50ca1553f08348ab1e92dc7cf04013c85ff743a4) Thanks [@&#8203;ematipico](https://github.com/ematipico)! - Added the new nursery rule `noUnnecessararyConditions`, which detects whenever some conditions don't change during the life cycle of the program, and truthy or false, hence deemed redundant. For example, the following snippets will trigger the rule: ```js // Always truthy literal conditions if (true) { console.log("always runs"); } ``` ```ts // Unnecessary condition on constrained string type function foo(arg: "bar" | "baz") { if (arg) { // This check is unnecessary } } ``` - [#&#8203;6887](https://github.com/biomejs/biome/pull/6887) [`0cc38f5`](https://github.com/biomejs/biome/commit/0cc38f59cd9ddf0fdcd12d6f8cb3642743cc4406) Thanks [@&#8203;ptkagori](https://github.com/ptkagori)! - Added the [`useImageSize`](https://biomejs.dev/linter/rules/use-image-size) rule to Biome. The `useImageSize` rule enforces the use of width and height attributes on `<img>` elements for performance reasons. This rule is intended to prevent layout shifts and improve Core Web Vitals by ensuring images have explicit dimensions. **Invalid:** ```jsx <img src="/image.png" /> <img src="https://example.com/image.png" /> <img src="/image.png" width="200" /> <img src="/image.png" height="200" /> ``` **Valid:** ```jsx <img width="200" height="600" src="/static/images/portrait-01.webp" /> <img width="100" height="100" src="https://example.com/image.png" /> ``` - [#&#8203;6887](https://github.com/biomejs/biome/pull/6887) [`0cc38f5`](https://github.com/biomejs/biome/commit/0cc38f59cd9ddf0fdcd12d6f8cb3642743cc4406) Thanks [@&#8203;ptkagori](https://github.com/ptkagori)! - Added the [`useAnchorHref`](https://biomejs.dev/linter/rules/use-anchor-href) rule to Biome. The `useAnchorHref` rule enforces the presence of an `href` attribute on `<a>` elements in JSX. This rule is intended to ensure that anchor elements are always valid and accessible. **Invalid:** ```jsx <a>Link</a> ``` ```jsx <a target="_blank">External</a> ``` **Valid:** ```jsx <a href="/home">Home</a> ``` ```jsx <a href="https://example.com" target="_blank"> External </a> ``` - [#&#8203;7100](https://github.com/biomejs/biome/pull/7100) [`29fcb05`](https://github.com/biomejs/biome/commit/29fcb0540ed817d92a3f663132b658541706765b) Thanks [@&#8203;Jayllyz](https://github.com/Jayllyz)! - Added the rule [`noNonNullAssertedOptionalChain`](https://biomejs.dev/linter/rules/no-non-null-asserted-optional-chain). This rule prevents the use of non-null assertions (`!`) immediately after optional chaining expressions (`?.`). Optional chaining is designed to safely handle nullable values by returning `undefined` when the chain encounters `null` or `undefined`. Using a non-null assertion defeats this purpose and can lead to runtime errors. ```ts // Invalid - non-null assertion after optional chaining obj?.prop!; obj?.method()!; obj?.[key]!; obj?.prop!; // Valid - proper optional chaining usage obj?.prop; obj?.method(); obj?.prop ?? defaultValue; obj!.prop?.method(); ``` - [#&#8203;7129](https://github.com/biomejs/biome/pull/7129) [`9f4538a`](https://github.com/biomejs/biome/commit/9f4538ab8bad8a974b8e408641b1fd4770d26c79) Thanks [@&#8203;drwpow](https://github.com/drwpow)! - Removed option, combobox, listbox roles from [useSemanticElements](https://biomejs.dev/linter/rules/use-semantic-elements/) suggestions - [#&#8203;7106](https://github.com/biomejs/biome/pull/7106) [`236deaa`](https://github.com/biomejs/biome/commit/236deaadca077051f6e2ef01cfdbbc55cc1c3d78) Thanks [@&#8203;arendjr](https://github.com/arendjr)! - Fixed [#&#8203;6985](https://github.com/biomejs/biome/issues/6985): Inference of return types no longer mistakenly picks up return types of nested functions. - [#&#8203;7102](https://github.com/biomejs/biome/pull/7102) [`d3118c6`](https://github.com/biomejs/biome/commit/d3118c6ac3bba0ca29251fa7fc5ba36a9e4456b0) Thanks [@&#8203;omasakun](https://github.com/omasakun)! - Fixed [#&#8203;7101](https://github.com/biomejs/biome/issues/7101): [`noUnusedPrivateClassMembers`](https://biomejs.dev/linter/rules/no-unused-private-class-members/) now handles members declared as part of constructor arguments: 1. If a class member defined in a constructor argument is only used within the constructor, it removes the `private` modifier and makes it a plain method argument. 2. If it is not used at all, it will prefix it with an underscore, similar to `noUnusedFunctionParameter`. - [#&#8203;7104](https://github.com/biomejs/biome/pull/7104) [`5395297`](https://github.com/biomejs/biome/commit/53952972cd5786cfdcc3deda0c226d6488ef1aee) Thanks [@&#8203;harxki](https://github.com/harxki)! - Reverting to prevent regressions around ref handling - [#&#8203;7143](https://github.com/biomejs/biome/pull/7143) [`1a6933a`](https://github.com/biomejs/biome/commit/1a6933aaf2c5b57d70a60d607b5cab68d532eeb4) Thanks [@&#8203;siketyan](https://github.com/siketyan)! - Fixed [#&#8203;6799](https://github.com/biomejs/biome/issues/6799): The [`noImportCycles`](https://biomejs.dev/linter/rules/no-import-cycles/) rule now ignores type-only imports if the new `ignoreTypes` option is enabled (enabled by default). > \[!WARNING] > **Breaking Change**: The `noImportCycles` rule no longer detects import cycles that include one or more type-only imports by default. > To keep the old behaviour, you can turn off the `ignoreTypes` option explicitly: > > ```json > { > "linter": { > "rules": { > "nursery": { > "noImportCycles": { > "options": { > "ignoreTypes": false > } > } > } > } > } > } > ``` - [#&#8203;7099](https://github.com/biomejs/biome/pull/7099) [`6cc84cb`](https://github.com/biomejs/biome/commit/6cc84cb547480f83119d2cba5542e2d2afc65b4d) Thanks [@&#8203;arendjr](https://github.com/arendjr)! - Fixed [#&#8203;7062](https://github.com/biomejs/biome/issues/7062): Biome now correctly considers extended configs when determining the mode for the scanner. - [#&#8203;6887](https://github.com/biomejs/biome/pull/6887) [`0cc38f5`](https://github.com/biomejs/biome/commit/0cc38f59cd9ddf0fdcd12d6f8cb3642743cc4406) Thanks [@&#8203;ptkagori](https://github.com/ptkagori)! - Added the [`useQwikClasslist`](https://biomejs.dev/linter/rules/use-qwik-classlist) rule to Biome. This rule is intended for use in Qwik applications to encourage the use of the built-in `class` prop (which accepts a string, object, or array) instead of the `classnames` utility library. **Invalid:** ```jsx <div class={classnames({ active: true, disabled: false })} /> ``` **Valid:** ```jsx <div classlist={{ active: true, disabled: false }} /> ``` - [#&#8203;7019](https://github.com/biomejs/biome/pull/7019) [`57c15e6`](https://github.com/biomejs/biome/commit/57c15e6df5b6257ffb9f69d7614c3455a1f5c870) Thanks [@&#8203;fireairforce](https://github.com/fireairforce)! - Added support in the JS parser for `import source`(a [stage3 proposal](https://github.com/tc39/proposal-source-phase-imports)). The syntax looks like: ```ts import source foo from "<specifier>"; ``` - [#&#8203;7053](https://github.com/biomejs/biome/pull/7053) [`655049e`](https://github.com/biomejs/biome/commit/655049e9e38f536b33fff6d7b160299f0b446908) Thanks [@&#8203;jakeleventhal](https://github.com/jakeleventhal)! - Added the [`useConsistentTypeDefinitions`](https://biomejs.dev/linter/rules/use-consistent-type-definitions) rule. This rule enforces consistent usage of either `interface` or `type` for object type definitions in TypeScript. The rule accepts an option to specify the preferred style: - `interface` (default): Prefer using `interface` for object type definitions - `type`: Prefer using `type` for object type definitions Examples: ```ts // With default option (interface) // ❌ Invalid type Point = { x: number; y: number }; // ✅ Valid interface Point { x: number; y: number; } // With option { style: "type" } // ❌ Invalid interface Point { x: number; y: number; } // ✅ Valid type Point = { x: number; y: number }; ``` The rule will automatically fix simple cases where conversion is straightforward. </details> --- ### Configuration 📅 **Schedule**: Branch creation - Between 12:00 AM and 03:59 AM ( * 0-3 * * * ) (UTC), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0MS41MS4wIiwidXBkYXRlZEluVmVyIjoiNDEuNTEuMCIsInRhcmdldEJyYW5jaCI6Im1haW4iLCJsYWJlbHMiOltdfQ==-->
chore(deps): update dependency @biomejs/biome to v2.1.4
Some checks failed
renovate/artifacts Artifact file update failure
Build and Push Docker Image / build-and-push (pull_request) Successful in 1m23s
Details
0fac059f80
Renovate commented 2025-08-08 02:00:14 +02:00
Author
Collaborator
Copy link

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: bun.lock
Command failed: bun install --ignore-scripts
/usr/local/bin/bun: line 19:    79 Illegal instruction     (core dumped) /opt/containerbase/tools/bun/1.2.19/bin/bun "$@"
### ⚠️ Artifact update problem Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is. ♻ Renovate will retry this branch, including artifacts, only when one of the following happens: - any of the package files in this branch needs updating, or - the branch becomes conflicted, or - you click the rebase/retry checkbox if found above, or - you rename this PR's title to start with "rebase!" to trigger it manually The artifact failure details are included below: ##### File name: bun.lock ``` Command failed: bun install --ignore-scripts /usr/local/bin/bun: line 19: 79 Illegal instruction (core dumped) /opt/containerbase/tools/bun/1.2.19/bin/bun "$@" ```
Renovate force-pushed renovate/biomejs-biome-2.x from 0fac059f80
Some checks failed
renovate/artifacts Artifact file update failure
Build and Push Docker Image / build-and-push (pull_request) Successful in 1m23s
Details
to 46c43f3882
Some checks failed
renovate/artifacts Artifact file update failure
Build and Push Docker Image / build-and-push (pull_request) Successful in 1m11s
Details
2025-08-08 21:59:27 +02:00 Compare
Renovate force-pushed renovate/biomejs-biome-2.x from 46c43f3882
Some checks failed
renovate/artifacts Artifact file update failure
Build and Push Docker Image / build-and-push (pull_request) Successful in 1m11s
Details
to d3d13e6069
Some checks failed
renovate/artifacts Artifact file update failure
Build and Push Docker Image / build-and-push (pull_request) Successful in 1m12s
Details
2025-08-09 15:32:40 +02:00 Compare
Renovate force-pushed renovate/biomejs-biome-2.x from d3d13e6069
Some checks failed
renovate/artifacts Artifact file update failure
Build and Push Docker Image / build-and-push (pull_request) Successful in 1m12s
Details
to 76d3f57bb1
Some checks failed
renovate/artifacts Artifact file update failure
Build and Push Docker Image / build-and-push (pull_request) Successful in 1m18s
Details
2025-08-10 20:22:27 +02:00 Compare
Renovate force-pushed renovate/biomejs-biome-2.x from 76d3f57bb1
Some checks failed
renovate/artifacts Artifact file update failure
Build and Push Docker Image / build-and-push (pull_request) Successful in 1m18s
Details
to bd268cc23c
Some checks failed
renovate/artifacts Artifact file update failure
Build and Push Docker Image / build-and-push (pull_request) Successful in 1m56s
Details
2025-08-11 23:51:56 +02:00 Compare
Renovate force-pushed renovate/biomejs-biome-2.x from bd268cc23c
Some checks failed
renovate/artifacts Artifact file update failure
Build and Push Docker Image / build-and-push (pull_request) Successful in 1m56s
Details
to 4b552df25e
Some checks failed
renovate/artifacts Artifact file update failure
Build and Push Docker Image / build-and-push (pull_request) Successful in 1m26s
Details
2025-08-12 00:35:55 +02:00 Compare
Renovate force-pushed renovate/biomejs-biome-2.x from 4b552df25e
Some checks failed
renovate/artifacts Artifact file update failure
Build and Push Docker Image / build-and-push (pull_request) Successful in 1m26s
Details
to 7e00e49141
Some checks failed
renovate/artifacts Artifact file update failure
Build and Push Docker Image / build-and-push (pull_request) Successful in 1m28s
Details
2025-08-12 12:40:12 +02:00 Compare
Renovate force-pushed renovate/biomejs-biome-2.x from 7e00e49141
Some checks failed
renovate/artifacts Artifact file update failure
Build and Push Docker Image / build-and-push (pull_request) Successful in 1m28s
Details
to bfb3bded52
Some checks failed
renovate/artifacts Artifact file update failure
Build and Push Docker Image / build-and-push (pull_request) Successful in 1m12s
Details
2025-08-13 17:07:18 +02:00 Compare
Renovate force-pushed renovate/biomejs-biome-2.x from bfb3bded52
Some checks failed
renovate/artifacts Artifact file update failure
Build and Push Docker Image / build-and-push (pull_request) Successful in 1m12s
Details
to 30a02732ac
Some checks failed
renovate/artifacts Artifact file update failure
Build and Push Docker Image / build-and-push (pull_request) Successful in 2m16s
Details
2025-08-13 23:18:57 +02:00 Compare
Renovate force-pushed renovate/biomejs-biome-2.x from 30a02732ac
Some checks failed
renovate/artifacts Artifact file update failure
Build and Push Docker Image / build-and-push (pull_request) Successful in 2m16s
Details
to 0344dd9a46
Some checks failed
renovate/artifacts Artifact file update failure
Build and Push Docker Image / build-and-push (pull_request) Successful in 1m11s
Details
2025-08-14 11:26:46 +02:00 Compare
Renovate changed title from chore(deps): update dependency @biomejs/biome to v2.1.4 to chore(deps): update dependency @biomejs/biome to v2.2.0 2025-08-14 11:26:48 +02:00
Renovate force-pushed renovate/biomejs-biome-2.x from 0344dd9a46
Some checks failed
renovate/artifacts Artifact file update failure
Build and Push Docker Image / build-and-push (pull_request) Successful in 1m11s
Details
to ba205a5ab9
Some checks failed
renovate/artifacts Artifact file update failure
Build and Push Docker Image / build-and-push (pull_request) Successful in 1m38s
Details
2025-08-16 07:27:44 +02:00 Compare
Renovate changed title from chore(deps): update dependency @biomejs/biome to v2.2.0 to chore(deps): update dependency @biomejs/biome to v2.2.0 - autoclosed 2025-08-16 16:29:19 +02:00
Renovate closed this pull request 2025-08-16 16:29:19 +02:00
Some checks failed
renovate/artifacts Artifact file update failure
Build and Push Docker Image / build-and-push (pull_request) Successful in 1m38s
Details

Pull request closed

This pull request cannot be reopened because the branch was deleted.
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Yumeo/Glorpcha!22
No description provided.