chore(deps): update all non-major dependencies

[renovate-bot]

This PR contains the following updates:

Package	Change	Age	Confidence
@biomejs/biome (source)	^2.1.1 -> ^2.1.2
@types/node (source)	^24.0.14 -> ^24.1.0
esbuild	^0.25.6 -> ^0.25.8
remove-glob	^0.3.4 -> ^0.3.5

---

Release Notes

biomejs/biome (@​biomejs/biome)

v2.1.2

Compare Source

Patch Changes

• #​6908 d77eaff Thanks @​ematipico! - Fix #​6485: Handle multiple semicolons correctly in blocks (#​6485)

  div {
    box-sizing: border-box;
    color: red;
  }

• #​6908 d77eaff Thanks @​ematipico! - Fixed #​6762, Biome now knows that ~/.config/zed/settings.json and ~/.config/Code/User/settings.json allows comments by default.

• #​6908 d77eaff Thanks @​ematipico! - 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()

• #​6908 d77eaff Thanks @​ematipico! - Fixed a bug where the Biome Language Server didn't correctly ignore specific files when vcs.useIgnoreFile is set to true.

• #​6908 d77eaff Thanks @​ematipico! - Improved the performance of noImportCycles by ~30%.

• #​6908 d77eaff Thanks @​ematipico! - 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.

• #​6908 d77eaff Thanks @​ematipico! - 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.

• #​6908 d77eaff Thanks @​ematipico! - 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.

• #​6908 d77eaff 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.

• #​6908 d77eaff Thanks @​ematipico! - 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",
  }

• #​6908 d77eaff Thanks @​ematipico! - Biome now considers whether the linter is enabled when figuring out how the project should be scanned. Resolves #​6815.

• #​6908 d77eaff Thanks @​ematipico! - Fixed #​6165: Fixed false negative in noUnusedPrivateClassMembers rule when checking member usage in classes

• #​6908 d77eaff 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.

• #​6908 d77eaff Thanks @​ematipico! - Fixed #​6891: Improved type inference for array indices.

  Example:

  const numbers: number[];
  numbers[42]; // This now infers to `number | undefined`.

• #​6908 d77eaff Thanks @​ematipico! - 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);
      }
    });
  }

• #​6908 d77eaff Thanks @​ematipico! - 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>

• #​6912 af7c6c0 Thanks @​ematipico! - Fixed #​6904. Now Biome correctly applies the argument --assist-enabled=false when running the command ci and the command check.

• #​6908 d77eaff Thanks @​ematipico! - Allow multiple identifiers in ::part() pseudo-element selector.

  ::part(first second) {
  }

• #​6908 d77eaff Thanks @​ematipico! - Fixed #​6510: The scanner no longer shows diagnostics on inaccessible files unless --verbose is used.

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

• #​6908 d77eaff Thanks @​ematipico! - 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.

• #​6908 d77eaff Thanks @​ematipico! - noFloatingPromises will no longer suggest to add await keyword inside synchronous callbacks nested inside async functions.

• #​6908 d77eaff Thanks @​ematipico! - Fixed #​6777: Fixed type inference handling of this to avoid infinite recursion.

  Thanks to @​sterliakov for the thorough investigation!

• #​6908 d77eaff Thanks @​ematipico! - 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++}`;
    }
  }

• #​6723 c434f01 Thanks @​sterliakov! - useUniqueElementIds now has an excludedComponents option to support elements using id prop for reasons not related to DOM element id. Fixed #​6722.

• #​6908 d77eaff 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.

evanw/esbuild (esbuild)

v0.25.8

Compare Source

• Fix another TypeScript parsing edge case (#​4248)

  This fixes a regression with a change in the previous release that tries to more accurately parse TypeScript arrow functions inside the ?: operator. The regression specifically involves parsing an arrow function containing a #private identifier inside the middle of a ?: ternary operator inside a class body. This was fixed by propagating private identifier state into the parser clone used to speculatively parse the arrow function body. Here is an example of some affected code:

  class CachedDict {
    #has = (a: string) => dict.has(a);
    has = window
      ? (word: string): boolean => this.#has(word)
      : this.#has;
  }

• Fix a regression with the parsing of source phase imports

  The change in the previous release to parse source phase imports failed to properly handle the following cases:

  import source from 'bar'
  import source from from 'bar'
  import source type foo from 'bar'

  Parsing for these cases should now be fixed. The first case was incorrectly treated as a syntax error because esbuild was expecting the second case. And the last case was previously allowed but is now forbidden. TypeScript hasn't added this feature yet so it remains to be seen whether the last case will be allowed, but it's safer to disallow it for now. At least Babel doesn't allow the last case when parsing TypeScript, and Babel was involved with the source phase import specification.

v0.25.7

Compare Source

• Parse and print JavaScript imports with an explicit phase (#​4238)

  This release adds basic syntax support for the defer and source import phases in JavaScript:

  • defer

    This is a stage 3 proposal for an upcoming JavaScript feature that will provide one way to eagerly load but lazily initialize imported modules. The imported module is automatically initialized on first use. Support for this syntax will also be part of the upcoming release of TypeScript 5.9. The syntax looks like this:

    import defer * as foo from "<specifier>";
    const bar = await import.defer("<specifier>");

    Note that this feature deliberately cannot be used with the syntax import defer foo from "<specifier>" or import defer { foo } from "<specifier>".

  • source

    This is a stage 3 proposal for an upcoming JavaScript feature that will provide another way to eagerly load but lazily initialize imported modules. The imported module is returned in an uninitialized state. Support for this syntax may or may not be a part of TypeScript 5.9 (see this issue for details). The syntax looks like this:

    import source foo from "<specifier>";
    const bar = await import.source("<specifier>");

    Note that this feature deliberately cannot be used with the syntax import defer * as foo from "<specifier>" or import defer { foo } from "<specifier>".

  This change only adds support for this syntax. These imports cannot currently be bundled by esbuild. To use these new features with esbuild's bundler, the imported paths must be external to the bundle and the output format must be set to esm.

• Support optionally emitting absolute paths instead of relative paths (#​338, #​2082, #​3023)

  This release introduces the --abs-paths= feature which takes a comma-separated list of situations where esbuild should use absolute paths instead of relative paths. There are currently three supported situations: code (comments and string literals), log (log message text and location info), and metafile (the JSON build metadata).

  Using absolute paths instead of relative paths is not the default behavior because it means that the build results are no longer machine-independent (which means builds are no longer reproducible). Absolute paths can be useful when used with certain terminal emulators that allow you to click on absolute paths in the terminal text and/or when esbuild is being automatically invoked from several different directories within the same script.

• Fix a TypeScript parsing edge case (#​4241)

  This release fixes an edge case with parsing an arrow function in TypeScript with a return type that's in the middle of a ?: ternary operator. For example:

  x = a ? (b) : c => d;
  y = a ? (b) : c => d : e;

  The : token in the value assigned to x pairs with the ? token, so it's not the start of a return type annotation. However, the first : token in the value assigned to y is the start of a return type annotation because after parsing the arrow function body, it turns out there's another : token that can be used to pair with the ? token. This case is notable as it's the first TypeScript edge case that esbuild has needed a backtracking parser to parse. It has been addressed by a quick hack (cloning the whole parser) as it's a rare edge case and esbuild doesn't otherwise need a backtracking parser. Hopefully this is sufficient and doesn't cause any issues.

• Inline small constant strings when minifying

  Previously esbuild's minifier didn't inline string constants because strings can be arbitrarily long, and this isn't necessarily a size win if the string is used more than once. Starting with this release, esbuild will now inline string constants when the length of the string is three code units or less. For example:

  // Original code
  const foo = 'foo'
  console.log({ [foo]: true })
  
  // Old output (with --minify --bundle --format=esm)
  var o="foo";console.log({[o]:!0});
  
  // New output (with --minify --bundle --format=esm)
  console.log({foo:!0});

  Note that esbuild's constant inlining only happens in very restrictive scenarios to avoid issues with TDZ handling. This change doesn't change when esbuild's constant inlining happens. It only expands the scope of it to include certain string literals in addition to numeric and boolean literals.

ghiscoding/remove-glob (remove-glob)

v0.3.5

Compare Source

Bug Fixes

• add maxRetries to rmSync on Windows OS (67527a0)

---

Configuration

📅 Schedule: Branch creation - "every 3 months" (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.

[bolt-new-by-stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[github-actions]

Playwright E2E Test Results

83 tests  ±0   83 ✅ ±0   1m 35s ⏱️ -4s
73 suites ±0    0 💤 ±0 
 1 files   ±0    0 ❌ ±0 

Results for commit 1afeefb. ± Comparison against base commit 186d9a2.

♻️ This comment has been updated with latest results.