Skip to content

chore(deps): update dependency biome to v2 #1109

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
Merged
merged 1 commit into from
Jul 31, 2025
Merged

chore(deps): update dependency biome to v2 #1109

merged 1 commit into from
Jul 31, 2025

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jul 21, 2025 •
edited
Loading

This PR contains the following updates:

Package Update Change
biome major 1.9.4 -> 2.1.3

Release Notes

biomejs/biome (biome)

v2.1.3: Biome CLI v2.1.3

2.1.3

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 # @​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.

What's Changed

New Contributors

Full Changelog: https://github.com/biomejs/biome/compare/[@&#8203;biomejs/biome](https://redirect.github.com/biomejs/biome)@&#8203;2.1.2...[@&#8203;biomejs/biome](https://redirect.github.com/biomejs/biome)@&#8203;2.1.3

v2.1.2: Biome CLI v2.1.2

2.1.2

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.

What's Changed

New Contributors

Full Changelog: https://github.com/biomejs/biome/compare/[@&#8203;biomejs/js-api](https://redirect.github.com/biomejs/js-api)@&#8203;2.0.3...[@&#8203;biomejs/biome](https://redirect.github.com/biomejs/biome)@&#8203;2.1.2

v2.1.1: Biome CLI v2.1.1

2.1.1

Patch Changes

  • #​6781 9bbd34f Thanks @​siketyan! - Fixed the FileFeaturesResult interface in the WASM API was defined as a mapped object but the actual value was a Map object.

  • #​6761 cf3c2ce Thanks @​dyc3! - Fixed #​6759, a false positive for noFocusedTests that was triggered by calling any function with the name fit on any object.

    The following code will now pass the noFocusedTests rule:

    import foo from "foo";
foo.fit();

What's Changed

Full Changelog: https://github.com/biomejs/biome/compare/[@&#8203;biomejs/js-api](https://redirect.github.com/biomejs/js-api)@&#8203;2.0.1...[@&#8203;biomejs/biome](https://redirect.github.com/biomejs/biome)@&#8203;2.1.1

v2.1.0: Biome CLI v2.1.0

2.1.0

Minor Changes

  • #​6512 0c0bf82 Thanks @​arendjr! - The rule noFloatingPromises can now detect floating arrays of Promises.

    Invalid examples

    // This gets flagged because the Promises are not handled.
[1, 2, 3].map(async (x) => x + 1);

    Valid examples

    await Promise.all([1, 2, 3].map(async (x) => x + 1));

  • #​6637 6918085 Thanks @​arendjr! - Type inference is now able to handle the sequence operator (,), as well as post- and pre-update operators: ++.

    Example

    let x = 5;

// We now infer that `x++` resolves to a number, while the expression as a whole
// becomes a Promise:
x++, new Promise((resolve) => resolve("comma"));

  • #​6752 c9eaca4 Thanks @​arendjr! - Fixed #​6646: .gitignore files are now picked up even when running Biome from a nested directory, or when the ignore file itself is ignored through files.includes.

  • #​6746 90aeead Thanks @​arendjr! - biome migrate no longer enables style rules that were recommended in v1, because that would be undesirable for users upgrading from 2.0.

    Users who are upgrading from Biome 1.x are therefore advised to first upgrade to Biome 2.0, and run the migration, before continuing to Biome 2.1 or later.

  • #​6583 d415a3f Thanks @​arendjr! - Added the nursery rule noMisusedPromises.

    It signals Promises in places where conditionals or iterables are expected.

    Invalid examples

    const promise = Promise.resolve("value");

// Using a `Promise` as conditional is always truthy:
if (promise) {
  /* ... */
}

// Spreading a `Promise` has no effect:
console.log({ foo: 42, ...promise });

// This does not `await` the `Promise`s from the callbacks,
// so it does not behave as you may expect:
[1, 2, 3].forEach(async (value) => {
  await fetch(`/${value}`);
});

    Valid examples

    const promise = Promise.resolve("value");

if (await promise) {
  /* ... */
}

console.log({ foo: 42, ...(await promise) });

  • #​6405 cd4a9bb Thanks @​vladimir-ivanov! - Added the ignoreRestSiblings option to the noUnusedFunctionParameters rule.

    This option is used to ignore unused function parameters that are siblings of the rest parameter.

    The default is false, which means that unused function parameters that are siblings of the rest parameter will be reported.

    Example

    {
  "rules": {
    "noUnusedFunctionParameters": ["error", { "ignoreRestSiblings": true }]
  }
}

  • #​6614 0840021 Thanks @​arendjr! - We have implemented a more targeted version of the scanner, which ensures that if you provide file paths to handle on the CLI, the scanner will exclude directories that are not relevant to those paths.

    Note that for many commands, such as biome check and biome format, the file paths to handle are implicitly set to the current working directory if you do not provide any path explicitly. The targeted scanner also works with such implicit paths, which means that if you run Biome from a subfolder, other folders that are part of the project are automatically exempted.

    Use cases where you invoke Biome from the root of the project without providing a path, as well as those where project rules are enabled, are not expected to see performance benefits from this.

    Implemented #​6234, and fixed #​6483 and #​6563.

  • #​6488 c5ee385 Thanks @​ianzone! - nx.json and project.json have been added to the list of well-known files.

  • #​6720 52e36ae Thanks @​minht11! - Added # @&#8203;biomejs/biome symbol to [organizeImports](https://biomejs.dev/assist/actions/organize-imports) :ALIAS:` group.

    import { action } from '$lib' will be treated as alias import.

Patch Changes

  • #​6712 2649ac6 Thanks @​sterliakov! - Fixed #​6595: Biome now supports // biome-ignore-all file-level suppressions in files that start with a shebang (#!).

  • #​6758 28dc49e Thanks @​arendjr! - Fixed #​6573: Grit plugins can now match bare imports.

    Example

    The following snippet:

    `import $source`

    will now match:

    import "main.css";

  • #​6550 b424f46 Thanks @​arendjr! - Type inference is now able to handle logical expressions: &&, ||, and ??.

    Examples

    // We can now infer that because `true` is truthy, the entire expression
// evaluates to a `Promise`.
true && Promise.reject("logical operator bypass");

// And we know that this doesn't:
false && Promise.reject("logical operator bypass");

// Truthiness, falsiness, and non-nullishness can all be determined on more
// complex expressions as well. So the following also works:
type Nullish = null | undefined;

type Params = {
  booleanOption: boolean | Nullish;
  falsyOption: false | Nullish;
};

function foo({ booleanOption, falsyOption }: Params) {
  // This may be a Promise:
  booleanOption ?? Promise.reject("logical operator bypass");

  // But this never is:
  falsyOption && Promise.reject("logical operator bypass");
}

  • #​6413 4aa0e50 Thanks @​wojtekmaj! - Improved error message in useDateNow rule.

  • #​6673 341e062 Thanks @​dyc3! - Fixed a case where the HTML formatter would mangle embedded language tags if whitespaceSensitivity was set to strict

  • #​6642 a991229 Thanks @​unvalley! - Fixed #​4494: The noSecrets rule now correctly uses the entropyThreshold option to detect secret like strings.

  • #​6520 0c43545 Thanks @​arendjr! - Type inference is now able to handle ternary

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: 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 was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/biome-2.x branch from 1c11933 to 915b2e8 Compare July 30, 2025 04:35
@alecthomas alecthomas merged commit 14227ee into master Jul 31, 2025
2 checks passed
@alecthomas alecthomas deleted the renovate/biome-2.x branch July 31, 2025 21:24
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
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@alecthomas