Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Jul 17, 2025

This PR contains the following updates:

Package Change Age Confidence Type Update
@biomejs/biome (source) ^2.1.1 -> ^2.1.4 age confidence devDependencies patch
@playwright/test (source) ^1.53.2 -> ^1.54.2 age confidence devDependencies patch
@rsbuild/core (source) ^1.4.2 -> ^1.4.15 age confidence devDependencies patch
@rslib/core (source) ^0.10.4 -> ^0.11.2 age confidence devDependencies minor
@types/node (source) ^22.15.34 -> ^22.17.1 age confidence devDependencies minor
node 18 -> 18.20.8 age confidence uses-with minor
playwright (source) ^1.53.2 -> ^1.54.2 age confidence devDependencies patch
simple-git-hooks ^2.13.0 -> ^2.13.1 age confidence devDependencies patch
typescript (source) ^5.0.3 -> ^5.9.2 age confidence devDependencies minor
typescript (source) ^5.8.3 -> ^5.9.2 age confidence devDependencies minor

Release Notes

biomejs/biome (@​biomejs/biome)

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.

v2.1.3

Compare Source

Patch Changes
  • #​7057 634a667 Thanks @​mdevils! - Added the rule noVueReservedKeys, which prevents the use of reserved Vue keys.

    It prevents the use of Vue reserved keys such as those starting with # @&#8203;biomejs/biome (like $el, $data, $props) and keys starting with _` in data properties, which can cause conflicts and unexpected behavior in Vue components.

    Invalid example
    <script>
    export default {
      data: {
        $el: "",
        _foo: "bar",
      },
    };
    </script>
    <script>
    export default {
      computed: {
        $data() {
          return this.someData;
        },
      },
    };
    </script>
    Valid examples
    <script>
    export default {
      data() {
        return {
          message: "Hello Vue!",
          count: 0,
        };
      },
    };
    </script>
    <script>
    export default {
      computed: {
        displayMessage() {
          return this.message;
        },
      },
    };
    </script>
  • #​6941 734d708 Thanks @​JamBalaya56562! - Added @eslint-react/no-nested-component-definitions as a rule source for noNestedComponentDefinitions. Now it will get picked up by biome migrate --eslint.

  • #​6463 0a16d54 Thanks @​JamBalaya56562! - Fixed a website link for the useComponentExportOnlyModules linter rule to point to the correct URL.

  • #​6944 e53f2fe Thanks @​sterliakov! - Fixed #​6910: Biome now ignores type casts and assertions when evaluating numbers for noMagicNumbers rule.

  • #​6991 476cd55 Thanks @​denbezrukov! - Fixed #​6973: Add support for parsing the :active-view-transition-type() pseudo-class

    :active-view-transition-type(first second) {
    }
  • #​6992 0b1e194 Thanks @​ematipico! - Added a new JSON rule called noQuickfixBiome, which disallow the use of code action quickfix.biome inside code editor settings.

  • #​6943 249306d Thanks @​JamBalaya56562! - Fixed @vitest/eslint-plugin source url.

  • #​6947 4c7ed0f Thanks @​JamBalaya56562! - Fixed ESLint migration for the rule prefer-for from eslint-plugin-solid to Biome's useForComponent.

  • #​6976 72ebadc Thanks @​siketyan! - Fixed #​6692: The rules noUnusedVariables and noUnusedFunctionParameters no longer cause an infinite loop when the suggested name is not applicable (e.g. the suggested name is already declared in the scope).

  • #​6990 333f5d0 Thanks @​rvanlaarhoven! - Fixed the documentation URL for lint/correctness/noUnknownPseudoClass

  • #​7000 4021165 Thanks @​harxki! - Fixed #​6795: noUnassignedVariables now correctly recognizes variables used in JSX ref attributes.

  • #​7044 b091ddf Thanks @​ematipico! - Fixed #​6622, now the rule useSemanticElements works for JSX self-closing elements too.

  • #​7014 c4864e8 Thanks @​siketyan! - Fixed #​6516: The biome migrate command no longer break the member list with trailing comments.

  • #​6979 29cb6da Thanks @​unvalley! - Fixed #​6767: useSortedClasses now correctly removes leading and trailing whitespace in className.

    Previously, trailing spaces in className were not fully removed.

    // Think we have this code:
    <div className="text-sm font-bold            " />
    
    // Before: applied fix, but a trailing space was preserved
    <div className="font-bold text-sm " />
    
    // After: applied fix, trailing spaces removed
    <div className="font-bold text-sm" />
  • #​7055 ee4828d Thanks @​dyc3! - Added the nursery rule useReactFunctionComponents. This rule enforces the preference to use function components instead of class components.

    Valid:

    function Foo() {
      return <div>Hello, world!</div>;
    }

    Invalid:

    class Foo extends React.Component {
      render() {
        return <div>Hello, world!</div>;
      }
    }
  • #​6924 2d21be9 Thanks @​ematipico! - Fixed #​113, where the Biome Language Server didn't correctly update the diagnostics when the configuration file is modified in the editor. Now the diagnostics are correctly updated every time the configuration file is modified and saved.

  • #​6931 e6b2380 Thanks @​arendjr! - Fixed #​6915: useHookAtTopLevel no longer hangs when rules call themselves recursively.

  • #​7012 01c0ab4 Thanks @​siketyan! - Fixed #​5837: Invalid suppression comments such as biome-ignore-all-start or biome-ignore-all-end no longer causes a panic.

  • #​6949 48462f8 Thanks @​fireairforce! - Support parse import defer(which is a stage3 proposal). The syntax look like this:

    import defer * as foo from "<specifier>";
  • #​6938 5feb5a6 Thanks @​vladimir-ivanov! - Fixed #​6919 and #​6920:
    useReadonlyClassProperties now does checks for mutations in async class methods.

    Example:

    class Counter3 {
      private counter: number;
      async count() {
        this.counter = 1;
        const counterString = `${this.counter++}`;
      }
    }
  • #​6942 cfda528 Thanks @​sterliakov! - Fixed #​6939. Biome now understands this binding in classes outside of methods.

v2.1.2

Compare Source

Patch Changes
  • #​6865 b35bf64 Thanks @​denbezrukov! - Fix #​6485: Handle multiple semicolons correctly in blocks (#​6485)

    div {
      box-sizing: border-box;
      color: red;
    }
  • #​6798 3579ffa Thanks @​dyc3! - Fixed #​6762, Biome now knows that ~/.config/zed/settings.json and ~/.config/Code/User/settings.json allows comments by default.

  • #​6839 4cd62d8 Thanks @​ematipico! - Fixed #​6838, where the Biome File Watcher incorrectly watched and stored ignored files, causing possible memory leaks when those files were dynamically created (e.g. built files).

  • #​6879 0059cd9 Thanks @​denbezrukov! - Refactor: remove one level of indirection for CSS declarations with semicolon
    Previously, accessing a declaration from a list required an extra step:

    item
    .as_any_css_declaration_with_semicolon()
    .as_css_declaration_with_semicolon()

    Now, it can be done directly with:

    item.as_css_declaration_with_semicolon()
  • #​6839 4cd62d8 Thanks @​ematipico! - Fixed a bug where the Biome Language Server didn't correctly ignore specific files when vcs.useIgnoreFile is set to true.

  • #​6884 5ff50f8 Thanks @​arendjr! - Improved the performance of noImportCycles by ~30%.

  • #​6903 241dd9e Thanks @​arendjr! - Fixed #​6829: Fixed a false positive reported by useImportExtensions when importing a .js file that had a matching .d.ts file in the same folder.

  • #​6846 446112e Thanks @​darricheng! - Fixed an issue where biome was using the wrong string quotes when the classes string has quotes, resulting in invalid code after applying the fix.

  • #​6823 eebc48e Thanks @​arendjr! - Improved #​6172: Optimised the way function arguments are stored in Biome's type inference. This led to about 10% performance improvement in RedisCommander.d.ts and about 2% on @next/font type definitions.

  • #​6878 3402976 Thanks @​ematipico! - Fixed a bug where the Biome Language Server would apply an unsafe fix when using the code action quickfix.biome.

    Now Biome no longer applies an unsafe code fix when using the code action quickfix.biome.

  • #​6794 4d5fc0e Thanks @​vladimir-ivanov! - Fixed #​6719: The noInvalidUseBeforeDeclaration rule covers additional use cases.

    Examples:

    type Bar = { [BAR]: true };
    const BAR = "bar";
    interface Bar {
      child: { grandChild: { [BAR]: typeof BAR; enumFoo: EnumFoo } };
    }
    const BAR = "bar";
    enum EnumFoo {
      BAR = "bar",
    }
  • #​6863 531e97e Thanks @​dyc3! - Biome now considers whether the linter is enabled when figuring out how the project should be scanned. Resolves #​6815.

  • #​6832 bdbc2b1 Thanks @​togami2864! - Fixed #​6165: Fixed false negative in noUnusedPrivateClassMembers rule when checking member usage in classes

  • #​6839 4cd62d8 Thanks @​ematipico! - Fixed a bug where the root ignore file wasn't correctly loaded during the scanning phase, causing false positives and incorrect expectations among users.

    Now, when using vcs.useIgnoreFile, the the globs specified in the ignore file from the project root will have the same semantics as the files.includes setting of the root configuration.

    Refer to the relative web page to understand how they work.

  • #​6898 5beb024 Thanks @​arendjr! - Fixed #​6891: Improved type inference for array indices.

    Example:

    const numbers: number[];
    numbers[42]; // This now infers to `number | undefined`.
  • #​6809 8192451 Thanks @​arendjr! - Fixed #​6796: Fixed a false positive that happened in noFloatingPromises when calling functions that were declared as part of for ... of syntax inside async functions.

    Instead, the variables declared inside for ... of loops are now correctly
    inferred if the expression being iterated evaluates to an Array (support for other iterables will follow later).

    Invalid example

    const txStatements: Array<(tx) => Promise<any>> = [];
    
    db.transaction((tx: any) => {
      for (const stmt of txStatements) {
        // We correctly flag this resolves to a `Promise`:
        stmt(tx);
      }
    });

    Valid example

    async function valid(db) {
      const txStatements: Array<(tx: any) => void> = [(tx) => tx.insert().run()];
    
      db.transaction((tx: any) => {
        for (const stmt of txStatements) {
          // We don't flag a false positive here anymore:
          stmt(tx);
        }
      });
    }
  • #​6757 13a0818 Thanks @​mdevils! - Added the rule noVueReservedProps, resolves #​6309.

    It prevents the use of reserved Vue prop names such as key and ref which can cause conflicts and unexpected behavior in Vue components.

    Invalid example
    import { defineComponent } from "vue";
    
    export default defineComponent({
      props: ["ref", "key", "foo"],
    });
    <script setup>
    defineProps({
      ref: String,
      key: String,
      foo: String,
    });
    </script>
    Valid examples
    import { defineComponent } from "vue";
    
    export default defineComponent({
      props: ["foo"],
    });
    <script setup>
    defineProps({ foo: String });
    </script>
  • #​6840 1a57b51 Thanks @​denbezrukov! - Allow multiple identifiers in ::part() pseudo-element selector.

    ::part(first second) {
    }
  • #​6845 4fd44ec Thanks @​arendjr! - Fixed #​6510: The scanner no longer shows diagnostics on inaccessible files unless --verbose is used.

  • #​6844 b7e2d4d Thanks @​sterliakov! - Fixed #​6837: Fixed regression with multiple consecutive line suppression comments using instances (like // biome-ignore lint/correctness/useExhaustiveDependencies(depName): reason).

  • #​6818 5f3f5a6 Thanks @​siketyan! - Fixed an issue where textDocument/codeAction in the LSP could respond with outdated text edits after the workspace watcher observed outdated changes to the file.

  • #​6804 3e6ab16 Thanks @​arendjr! - noFloatingPromises will no longer suggest to add await keyword inside synchronous callbacks nested inside async functions.

  • #​6901 c9e969a Thanks @​arendjr! - Fixed #​6777: Fixed type inference handling of this to avoid infinite recursion.

    Thanks to @​sterliakov for the thorough investigation!

  • #​6855 d1581c7 Thanks @​vladimir-ivanov! - Fixed #​6775: useReadonlyClassProperties now also captures mutations inside function arguments.

    Example:

    class Counter {
      private counter: number;
      count() {
        console.log(this.counter++);
        const counterString = `${this.counter++}`;
      }
    }
  • #​6839 4cd62d8 Thanks @​ematipico! - Fixed a bug where Biome didn't throw any error when vcs.useIgnoreFile is set to true, and there wasn't any ignore file read. Now Biome correctly throws an error if no ignore files are found.

  • #​6911 6d68074 Thanks @​arendjr! - Fixed #​6838: Reduce resource consumption in the Biome Language Server by using non-recursive filesystem watchers instead of recursive ones.

    Watchers are responsible for notifying Biome of changes to files in the filesystem. We used to set up a single recursive watcher, but that meant that Biome would receive filesystem notifications for all files in your project, even for ignored folders such as build/ or dist/ folders.

    With this patch, we set up non-recursive watchers only for the folders that are relevant to a project.

    Related to this, we also solved an issue where incoming notifications were incorrectly filtered, causing ignored files to be processed and stored in our module graph anyway.

microsoft/playwright (@​playwright/test)

v1.54.2

Compare Source

Highlights

https://github.com/microsoft/playwright/issues/36714 - [Regression]: Codegen is not able to launch in Administrator Terminal on Windows (ProtocolError: Protocol error)https://github.com/microsoft/playwright/issues/368288 - [Regression]: Playwright Codegen keeps spamming with selected optiohttps://github.com/microsoft/playwright/issues/3681010 - [Regression]: Starting Codegen with target language doesn't work anymore

Browser Versions

  • Chromium 139.0.7258.5
  • Mozilla Firefox 140.0.2
  • WebKit 26.0

This version was also tested against the following stable channels:

  • Google Chrome 140
  • Microsoft Edge 140
web-infra-dev/rsbuild (@​rsbuild/core)

v1.4.15

Compare Source

What's Changed

New Features 🎉
Bug Fixes 🐞
Refactor 🔨
Document 📖
Other Changes

Full Changelog: web-infra-dev/rsbuild@v1.4.14...v1.4.15

v1.4.14

Compare Source

What's Changed

Trusted Publishing

All Rsbuild npm packages are now published based on npm's trusted publishing, making Rsbuild's npm packages more secure and transparent.

See:

Screenshot 2025-08-04 at 22 25 28
Other Changes

Full Changelog: web-infra-dev/rsbuild@v1.4.13...v1.4.14

v1.4.13

Compare Source

What's Changed

New Features 🎉
Bug Fixes 🐞
Refactor 🔨
Document 📖
Other Changes

Full Changelog: web-infra-dev/rsbuild@v1.4.12...v1.4.13

v1.4.12

Compare Source

What's Changed

New Features 🎉
Performance 🚀

Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, on day 1 of the month ( * 0-3 1 * * ) (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.

👻 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.

@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from e1c7b47 to 8d775d0 Compare July 21, 2025 03:23
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 5 times, most recently from 05bd174 to f116079 Compare August 8, 2025 06:33
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from f116079 to f52d6e7 Compare August 9, 2025 04:10
@cklwblove cklwblove merged commit 415a3f3 into main Aug 10, 2025
@renovate renovate bot deleted the renovate/all-minor-patch branch August 10, 2025 10:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants