fix(deps): update all non-major dependencies #11

renovate · 2025-10-01T03:21:07Z

This PR contains the following updates:

Package	Change	Type	Update
@biomejs/biome (source)	`^2.1.4` -> `^2.3.6`	devDependencies	minor
@iconify-json/carbon	`^1.2.11` -> `^1.2.14`	devDependencies	patch
@iconify-json/icon-park	`^1.2.2` -> `^1.2.4`	devDependencies	patch
@iconify-json/logos	`^1.2.5` -> `^1.2.10`	devDependencies	patch
@iconify-json/noto-v1	`^1.2.2` -> `^1.2.5`	devDependencies	patch
@iconify-json/ri	`^1.2.5` -> `^1.2.6`	devDependencies	patch
@playwright/test (source)	`^1.54.2` -> `^1.56.1`	devDependencies	minor
@rsbuild/core (source)	`^1.4.15` -> `^1.6.6`	devDependencies	minor
@rslib/core (source)	`^0.11.2` -> `^0.18.0`	devDependencies	minor
@types/node (source)	`^22.17.1` -> `^22.19.1`	devDependencies	minor
@winner-fed/utils	`^0.16.10` -> `^0.18.7`	devDependencies	minor
@winner-fed/winjs	`^0.16.10` -> `^0.18.7`	devDependencies	minor
node	`22` -> `22.21.1`	uses-with	minor
pnpm (source)	`10` -> `10.22.0`	uses-with	minor
typescript (source)	`^5.9.2` -> `^5.9.3`	devDependencies	patch
unplugin-icons	`^22.2.0` -> `^22.5.0`	dependencies	minor

Release Notes

biomejs/biome (@biomejs/biome)

`v2.3.6`

Compare Source

Patch Changes

#8100 82b9a8e Thanks @Netail! - Added the nursery rule useFind. Enforce the use of Array.prototype.find() over Array.prototype.filter() followed by [0] when looking for a single result.

Invalid:
```
[1, 2, 3].filter((x) => x > 1)[0];

[1, 2, 3].filter((x) => x > 1).at(0);
```
#8118 dbc7021 Thanks @hirokiokada77! - Fixed #8117: useValidLang now accepts valid BCP 47 language tags with script subtags.

Valid:
```
<html lang="zh-Hans-CN"></html>
```
#7672 f1d5725 Thanks @Netail! - Added the nursery rule useConsistentGraphqlDescriptions, requiring all descriptions to follow the same style (either block or inline) inside GraphQL files.

Invalid:
```
enum EnumValue {
  "this is a description"
  DEFAULT
}
```
Valid:
```
enum EnumValue {
  """
  this is a description
  """
  DEFAULT
}
```
#8026 f102661 Thanks @matanshavit! - Fixed #8004: noParametersOnlyUsedInRecursion now correctly detects recursion by comparing function bindings instead of just names.

Previously, the rule incorrectly flagged parameters when a method had the same name as an outer function but called the outer function (not itself):
```
function notRecursive(arg) {
  return arg;
}

const obj = {
  notRecursive(arg) {
    return notRecursive(arg); // This calls the outer function, not the method itself
  },
};
```
Biome now properly distinguishes between these cases and will not report false positives.
#8097 5fc5416 Thanks @dyc3! - Added the nursery rule noVueVIfWithVFor. This rule disallows v-for and v-if on the same element.
```

<div v-for="item in items" v-if="item.isActive">
  {{ item.name }}
</div>
```
#8085 7983940 Thanks @Netail! - Added the nursery rule noForIn. Disallow iterating using a for-in loop.

Invalid:
```
for (const i in array) {
  console.log(i, array[i]);
}
```
#8086 2b41e82 Thanks @matanshavit! - Fixed #8045: The noNestedTernary rule now correctly detects nested ternary expressions even when they are wrapped in parentheses (e.g. foo ? (bar ? 1 : 2) : 3).

Previously, the rule would not flag nested ternaries like foo ? (bar ? 1 : 2) : 3 because the parentheses prevented detection. The rule now looks through parentheses to identify nested conditionals.

Previously not detected (now flagged):
```
const result = foo ? (bar ? 1 : 2) : 3;
```
Still valid (non-nested with parentheses):
```
const result = foo ? bar : baz;
```
#8075 e403868 Thanks @YTomm! - Fixed #7948: The useReadonlyClassProperties code fix when checkAllProperties is enabled will no longer insert a newline after readonly and the class property.
#8102 47d940e Thanks @lucasweng! - Fixed #8027. useReactFunctionComponents no longer reports class components that implement componentDidCatch using class expressions.

The rule now correctly recognizes error boundaries defined as class expressions:
```
const ErrorBoundary = class extends Component {
  componentDidCatch(error, info) {}

  render() {
    return this.props.children;
  }
};
```
#8097 5fc5416 Thanks @dyc3! - Added the nursery rule useVueHyphenatedAttributes, which encourages using kebab case for attribute names, per the Vue style guide's recommendations.
```

<MyComponent myProp="value" />


<MyComponent my-prop="value" />
```

#8108 0f0a658 Thanks @Netail! - Added the nursery rule noSyncScripts. Prevent the usage of synchronous scripts.

Invalid:

<script src="https://third-party-script.js" />

Valid:

<script src="https://third-party-script.js" async />
<script src="https://third-party-script.js" defer />

#8098 1fdcaf0 Thanks @Jayllyz! - Added documentation URLs to rule descriptions in the JSON schema.
#8097 5fc5416 Thanks @dyc3! - Fixed an issue with the HTML parser where it would treat Vue directives with dynamic arguments as static arguments instead.
#7684 f4433b3 Thanks @vladimir-ivanov! - Changed noUnusedPrivateClassMembers to align more fully with meaningful reads.

This rule now distinguishes more carefully between writes and reads of private class members.
- A meaningful read is any access that affects program behavior.
- For example, this.#x += 1 both reads and writes #x, so it counts as usage.
- Pure writes without a read (e.g. this.#x = 1 with no getter) are no longer treated as usage.
This change ensures that private members are only considered “used” when they are actually read in a way that influences execution.

Invalid examples (previously valid)
```
class UsedMember {
  set #x(value) {
    doSomething(value);
  }

  foo() {
    // This assignment does not actually read #x, because there is no getter.
    // Previously, this was considered a usage, but now it’s correctly flagged.
    this.#x = 1;
  }
}
```
Valid example (Previously invalid)
```
class Foo {
  #usedOnlyInWriteStatement = 5;

  method() {
    // This counts as a meaningful read because we both read and write the value.
    this.#usedOnlyInWriteStatement += 42;
  }
}
```
#7684 f4433b3 Thanks @vladimir-ivanov! - Improved detection of used private class members

The analysis for private class members has been improved: now the tool only considers a private member “used” if it is actually referenced in the code.
- Previously, some private members might have been reported as used even if they weren’t actually accessed.
- With this change, only members that are truly read or called in the code are counted as used.
- Members that are never accessed will now be correctly reported as unused.
This makes reports about unused private members more accurate and helps you clean up truly unused code.

Example (previously valid)
```
type YesNo = "yes" | "no";

export class SampleYesNo {
  private yes: () => void;
  private no: () => void;
  private dontKnow: () => void; // <- will now report as unused

  on(action: YesNo): void {
    this[action]();
  }
}
```
#7681 b406db6 Thanks @kedevked! - Added the new lint rule, useSpread, ported from the ESLint rule prefer-spread.

This rule enforces the use of the spread syntax (...) over Function.prototype.apply() when calling variadic functions, as spread syntax is generally more concise and idiomatic in modern JavaScript (ES2015+).

The rule provides a safe fix.

Invalid

Math.max.apply(Math, args);
foo.apply(undefined, args);
obj.method.apply(obj, args);

Valid

Math.max(...args);
foo(...args);
obj.method(...args);

// Allowed: cases where the `this` binding is intentionally changed
foo.apply(otherObj, args);

#7287 aa55c8d Thanks @ToBinio! - Fixed #7205: The noDuplicateTestHooks rule now treats chained describe variants (e.g., describe.each/for/todo) as proper describe scopes, eliminating false positives.

The following code will no longer be a false positive:

describe("foo", () => {
  describe.for([])("baz", () => {
    beforeEach(() => {});
  });

  describe.todo("qux", () => {
    beforeEach(() => {});
  });

  describe.todo.each([])("baz", () => {
    beforeEach(() => {});
  });
});

#8013 0c0edd4 Thanks @Jayllyz! - Added the GraphQL nursery rule useUniqueGraphqlOperationName. This rule ensures that all GraphQL operations within a document have unique names.

Invalid:

query user {
  user {
    id
  }
}

query user {
  user {
    id
    email
  }
}

Valid:

query user {
  user {
    id
  }
}

query userWithEmail {
  user {
    id
    email
  }
}

#8084 c2983f9 Thanks @dyc3! - Fixed #8080: The HTML parser, when parsing Vue, can now properly handle Vue directives with no argument, modifiers, or initializer (e.g. v-else). It will no longer treat subsequent valid attributes as bogus.
```
<p v-else class="flex">World</p>

```
#8104 041196b Thanks @Conaclos! - Fixed noInvalidUseBeforeDeclaration.
The rule no longer reports a use of an ambient variable before its declarations.
The rule also completely ignores TypeScript declaration files.
The following code is no longer reported as invalid:
```
CONSTANT;
declare const CONSTANT: number;
```
#8060 ba7b076 Thanks @dyc3! - Added the nursery rule useVueValidVBind, which enforces the validity of v-bind directives in Vue files.

Invalid v-bind usages include:
```
<Foo v-bind />

<Foo v-bind:foo />

<Foo v-bind:foo.bar="baz" />

```
#8113 fb8e3e7 Thanks @Conaclos! - Fixed noInvalidUseBeforeDeclaration.
The rule now reports invalid use of classes, enums, and TypeScript's import-equals before their declarations.

The following code is now reported as invalid:
```
new C();
class C {}
```
#8077 0170dcb Thanks @dyc3! - Added the rule useVueValidVElseIf to enforce valid v-else-if directives in Vue templates. This rule reports invalid v-else-if directives with missing conditional expressions or when not preceded by a v-if or v-else-if directive.
#8077 0170dcb Thanks @dyc3! - Added the rule useVueValidVElse to enforce valid v-else directives in Vue templates. This rule reports v-else directives that are not preceded by a v-if or v-else-if directive.
#8077 0170dcb Thanks @dyc3! - Added the rule useVueValidVHtml to enforce valid usage of the v-html directive in Vue templates. This rule reports v-html directives with missing expressions, unexpected arguments, or unexpected modifiers.
#8077 0170dcb Thanks @dyc3! - Added the rule useVueValidVIf to enforce valid v-if directives in Vue templates. It disallows arguments and modifiers, and ensures a value is provided.
#8077 0170dcb Thanks @dyc3! - Added the rule useVueValidVOn to enforce valid v-on directives in Vue templates. This rule reports invalid v-on / shorthand @ directives with missing event names, invalid modifiers, or missing handler expressions.

`v2.3.5`

Compare Source

Patch Changes

#8023 96f3e77 Thanks @ematipico! - Added support Svelte syntax {@html}. Biome now is able to parse and format the Svelte syntax {@html}:
```
-{@&#8203;html   'div'}
+{@&#8203;html 'div'}
```
The contents of the expressions inside the {@html <expression>} aren't formatted yet.
#8058 5f68bcc Thanks @ematipico! - Fixed a bug where the Biome Language Server would enable its project file watcher even when no project rules were enabled.

Now the watching of nested configuration files and nested ignore files is delegated to the editor, if their LSP spec supports it.
#8023 96f3e77 Thanks @ematipico! - Added support Svelte syntax {@render}. Biome now is able to parse and format the Svelte syntax {@render}:
```
-{@&#8203;render   sum(1, 2)   }
+{@&#8203;render sum(1, 2)}
```
The contents of the expressions inside the {@render <expression>} aren't formatted yet.
#8006 f0612a5 Thanks @Bertie690! - Updated documentation and diagnostic for lint/complexity/noBannedTypes. The rule should have a more detailed description and diagnostic error message.
#8039 da70d8b Thanks @PFiS1737! - Biome now keeps a blank line after the frontmatter section in Astro files.
#8042 b7efa6f Thanks @dyc3! - The CSS Parser, with tailwindDirectives enabled, will now accept at rules like @media and @supports in @custom-variant shorthand syntax.
#8064 3ff9d45 Thanks @dibashthapa! - Fixed #7967: Fixed the issue with support for advanced SVG props
#8023 96f3e77 Thanks @ematipico! - Added support Svelte syntax {@attach}. Biome now is able to parse and format the Svelte syntax {@attach}:
```
-<div {@&#8203;attach    myAttachment   }>...</div>
+<div {@&#8203;attach myAttachment}>...</div>
```
The contents of the expressions inside the {@attach <expression>} aren't formatted yet.
#8001 6e8a50e Thanks @ematipico! - Added support Svelte syntax {#key}. Biome now is able to parse and format the Svelte syntax {#key}:
```
-{#key   expression} <div></div> {/key}
+{#key expression}
+  <div></div>
+{/key}
```
The contents of the expressions inside the {#key <expression>} aren't formatted yet.
#8023 96f3e77 Thanks @ematipico! - Added support Svelte syntax {@const}. Biome now is able to parse and format the Svelte syntax {@const}:
```
-{@&#8203;const   name = value}
+{@&#8203;const name = value}
```
The contents of the expressions inside the {@const <expression>} aren't formatted yet.
#8044 8f77d4a Thanks @Netail! - Corrected rule source references. biome migrate eslint should do a bit better detecting rules in your eslint configurations.
#8065 1a2d1af Thanks @Netail! - Added the nursery rule useArraySortCompare. Require Array#sort and Array#toSorted calls to always provide a compareFunction.

Invalid:
```
const array = [];
array.sort();
```
Valid:
```
const array = [];
array.sort((a, b) => a - b);
```
#7673 a3a713d Thanks @dyc3! - The HTML parser is now able to parse vue directives. This enables us to write/port Vue lint rules that require inspecting the <template> section. However, this more complex parsing may result in parsing errors where there was none before. For those of you that have opted in to the experimental support (aka experimentalFullSupportEnabled), we greatly appreciate your help testing this out, and your bug reports.

#8031 fa6798a Thanks @ematipico! - Added support for the Svelte syntax {#if}{/if}. The Biome HTML parser is now able to parse and format the {#if}{/if} blocks:

<!-- if / else-if / else -->
{#if porridge.temperature > 100}
-<p>too hot!</p>
+  <p>too hot!</p>
{:else if 80 > porridge.temperature}
-<p>too cold!</p>
+  <p>too cold!</p>
{:else if 100 > porridge.temperature}
-<p>too too cold!</p>
+  <p>too too cold!</p>
{:else}
-<p>just right!</p>
+  <p>just right!</p>
{/if}

#8041 beeb7bb Thanks @dyc3! - The CSS parser, with tailwindDirectives enabled, will now accept lists of selectors in @custom-variant shorthand syntax.
```
@&#8203;custom-variant cell (th:has(&), td:has(&));
```
#8028 c09e45c Thanks @fmajestic! - The GitLab reporter now outputs format errors.
#8037 78011b1 Thanks @PFiS1737! - indentScriptAndStyle no longer indents the frontmatter in Astro files.
#8009 6374b1f Thanks @tmcw! - Fixed an edge case in the useArrowFunction rule.

The rule no longer emits diagnostics for or offers to fix functions that reference
the arguments object,
because that object is undefined for arrow functions.

Valid example:
```
// Valid: this function cannot be transformed into an arrow function because
// arguments is not defined for arrow functions.
const getFirstArg = function () {
  return arguments[0];
};
```

`v2.3.4`

Compare Source

Patch Changes

#7989 4855c4a Thanks @alissonlauffer! - Fixed a regression in Astro frontmatter parsing where comments inside quoted strings were incorrectly detected as actual comments. This caused the parser to prematurely terminate frontmatter parsing when encountering strings like const test = "//";.
For example, the following Astro frontmatter now parses correctly:
```
---
const test = "// not a real comment";
---
```
#7968 0b28f5f Thanks @denbezrukov! - Refactored formatter to use strict Token element for better performance. The new Token variant is optimized for static, ASCII-only text (keywords, operators, punctuation) with the following constraints:
- ASCII only (no Unicode characters)
- No newlines (\n, \r)
- No tab characters (\t)
This enables faster printing and fitting logic by using bulk string operations (push_str, len()) instead of character-by-character iteration with Unicode width calculations.

#7941 19b8280 Thanks @Conaclos! - Fixed #7943. Rules' options are now properly merged with the inherited options from a shared configuration.

This means that you can now override a specific option from a rule without resetting the other options to their default.

Given the following shared configuration:

{
  "linter": {
    "rules": {
      "style": {
        "useNamingConvention": {
          "level": "on",
          "options": {
            "strictCase": false,
            "conventions": [
              {
                "selector": { "kind": "variable", "scope": "global" },
                "formats": ["CONSTANT_CASE"]
              }
            ]
          }
        }
      }
    }
  }
}

And the user configuration that extends this shared configuration:

{
  "extends": ["shared.json"],
  "linter": {
    "rules": {
      "style": {
        "useNamingConvention": {
          "level": "on",
          "options": { "strictCase": true }
        }
      }
    }
  }
}

The obtained merged configuration is now as follows:

{
  "extends": ["shared.json"],
  "linter": {
    "rules": {
      "style": {
        "useNamingConvention": {
          "level": "on",
          "options": {
            "strictCase": true,
            "conventions": [
              {
                "selector": { "kind": "variable", "scope": "global" },
                "formats": ["CONSTANT_CASE"]
              }
            ]
          }
        }
      }
    }
  }
}

#7969 425963d Thanks @ematipico! - Added support for the Svelte syntax {@debug}. The Biome HTML parser is now able to parse and format the blocks:
```
-{@&#8203;debug     foo,bar,    something}
+{@&#8203;debug foo, bar, something}
```
#7986 3256f82 Thanks @lisiur! - Fixed #7981. Now Biome correctly detects and parses lang='tsx' and lang='jsx' languages when used inside in .vue files, when .experimentalFullSupportEnabled is enabled.
#7921 547c2da Thanks @dyc3! - Fixed #7854: The CSS parser, with tailwindDirectives enabled, will now parse @source inline("underline");.

#7856 c9e20c3 Thanks @Netail! - Added the nursery rule noContinue. Disallowing the usage of the continue statement, structured control flow statements such as if should be used instead.

Invalid:

let sum = 0,
  i;

for (i = 0; i < 10; i++) {
  if (i >= 5) {
    continue;
  }

  sum += i;
}

Valid:

let sum = 0,
  i;

for (i = 0; i < 10; i++) {
  if (i < 5) {
    sum += i;
  }
}

`v2.3.3`

Compare Source

Patch Changes

#7907 57bd662 Thanks @ematipico! - Fixed #7839. Now the Biome parser correctly parses the Astro frontmatter even when a triple fence is inside quotes.
#7934 a35c496 Thanks @alissonlauffer! - Fixed #7919: The HTML parser now correctly handles Unicode BOM (Byte Order Mark) characters at the beginning of HTML files, ensuring proper parsing and tokenization.
#7869 c80361d Thanks @matanshavit! - Fixed #7864: Biome now preserves component tag name casing in Svelte, Astro, and Vue files.
#7926 69cecec Thanks @matanshavit! - Added the rule noParametersOnlyUsedInRecursion.

This rule detects function parameters that are exclusively used in recursive calls and can be removed to simplify the function signature since they are effectively unused.
```
function factorial(n, acc) {
  if (n === 0) return 1;
  return factorial(n - 1, acc); // acc is only used here
}
```
Fixes #6484.
#7774 2509b91 Thanks @dibashthapa! - Fixed #7657: Added the new rule no-unknown-property from ESLint
#7918 7165d06 Thanks @dyc3! - Fixed #7913: The CSS parser, with tailwindDirectives enabled, will now correctly handle @slot.
#7959 ffae203 Thanks @siketyan! - Fixed the Biome Language Server so it no longer returns an internal error when the formatter is disabled in the configuration.

`v2.3.2`

Compare Source

Patch Changes

#7859 c600618 Thanks @Netail! - Added the nursery rule noIncrementDecrement, disallows the usage of the unary operators ++ and --.
#7901 0d17b05 Thanks @ematipico! - Fixed #7837, where Biome couldn't properly parse text expressions that contained nested curly brackets. This was breaking parsing in Astro and Svelte files.
#7874 e617d36 Thanks @Bertie690! - Fixed #7230: noUselessStringConcat no longer emits false positives for multi-line strings with leading + operators.

Previously, the rule did not check for leading newlines on the + operator, emitting false positives if one occurred at the start of a line.
Notably, formatting with operatorLinebreak="before" would move the + operators to the start of lines automatically, resulting in spurious errors whenever a multi-line string was used.

Now, the rule correctly detects and ignores multi-line concatenations with leading operators as well, working regardless of the setting of operatorLinebreak.

Example
```
// The following code used to error if the `+` operators were at the start of lines (as opposed to the end).
// Now, the rule correctly recognizes this as a stylistic concatenation and ignores it.
const reallyLongStringThatShouldNotError =
  "Lorem ipsum dolor sit amet consectetur adipiscing elit." +
  "Quisque faucibus ex sapien vitae pellentesque sem placerat." +
  "In id cursus mi pretium tellus duis convallis." +
  "Tempus leo eu aenean sed diam urna tempor. Pulvinar vivamus fringilla";
```
#7786 33ffcd5 Thanks @daivinhtran! - Fixed #7601: Properly match Grit plugin's code snippet with only one child.
#7901 0d17b05 Thanks @ematipico! - Fixed #7837, where Biome Language Server panicked when opening HTML-ish files when the experimental full support is enabled.

`v2.3.1`

Compare Source

Patch Changes

#7840 72afdfa Thanks @ematipico! - Fixed #7838, which caused the new --css-parse-* arguments not being recognised by the ci command.
#7789 d5b416e Thanks @fronterior! - Fixed the LSP method workspace/didChangeWorkspaceFolders to perform incremental updates instead of replacing the entire folder list.
#7852 bd254c7 Thanks @dyc3! - Fixed #7843: The CSS parser, when tailwindDirectives is enabled, correctly parses --*: initial;.
#7872 0fe13fe Thanks @dyc3! - Fixed #7861: The HTML parser will now accept Svelte attribute shorthand syntax in .svelte files.
#7866 7b2600b Thanks @dyc3! - Fixed #7860: The css parser, with tailwindDirectives enabled, will now accept @plugin options.
#7853 fe90c78 Thanks @dyc3! - Fixed #7848: The css parser with tailwindDirectives enabled will now correctly parse tailwind's source exclude syntax: @source not "foo.css";
#7878 c9f7fe5 Thanks @ematipico! - Fixed #7857: Biome now parses <script> tags as TypeScript when analysing .astro files.
#7867 b42b718 Thanks @smorimoto! - Fixed incorrect option name in HTML parser error message.

The error message for disabled text expressions incorrectly referred
to the html.parser.textExpression option, which does not exist.
Updated it to reference the correct html.parser.interpolation option.

`v2.3.0`

Compare Source

Minor Changes

#7263 a3e3369 Thanks @arendjr! - Biome's resolver now supports baseUrl if specified in tsconfig.json.

Example

Given the following file structure:

tsconfig.json

{
  "compilerOptions": {
    "baseUrl": "./src"
  }
}

src/foo.ts

export function foo() {}

In this scenario, import { foo } from "foo"; should work regardless of the
location of the file containing the import statement.

Fixes #6432.

#7745 6fcbc07 Thanks @dyc3! - Added ignore option to noUnknownAtRules. If an unknown at-rule matches any of the items provided in ignore, a diagnostic won't be emitted.
#7753 63cb7ff Thanks @ematipico! - Enhanced the init command. The init command now checks if the existing project contains known ignore files and known generated folders.

If Biome finds .gitignore or .ignore files, it will add the following configuration to biome.json:
```
{
+  "vcs": {
+    "enabled": true,
+    "clientKind": "git",
+    "useIgnoreFile": true
+  }
}
```
If Biome finds a dist/ folder, it will exclude it automatically using the double-exclude syntax:
```
{
+  "files": {
+    "includes": ["**", "!!**/dist"]
+  }
}
```
#7548 85d3a3a Thanks @siketyan! - The rules in a domain are no longer enabled automatically by the installed dependencies unless the rule is recommended.

#7723 d3aac63 Thanks @ematipico! - Added --css-parse-css-modules CLI flag to control whether CSS Modules syntax is enabled.

You can now enable or disable CSS Modules parsing directly from the command line:

biome check --css-parse-css-modules=true file.module.css
biome format --css-parse-css-modules=true file.module.css
biome lint --css-parse-css-modules=true file.module.css
biome ci --css-parse-css-modules=true file.module.css

#7723 d3aac63 Thanks @ematipico! - Added --css-parse-tailwind-directives CLI flag to control whether Tailwind CSS 4.0 directives and functions are enabled.

You can now enable or disable Tailwind CSS 4.0 directive parsing directly from the command line:
```
biome check --css-parse-tailwind-directives=true file.css
biome format --css-parse-tailwind-directives=true file.css
biome lint --css-parse-tailwind-directives=true file.css
biome ci --css-parse-tailwind-directives=true file.css
```
#7330 272632f Thanks @ematipico! - Updated the formatting of .svelte and .vue files. Now the indentation of the JavaScript blocks matches Prettier's:
```
<script>
- import Component from "./Component"
+   import Component from "./Component"
</script>
```
#7333 de0d2d6 Thanks @dyc3! - Implemented the indentScriptAndStyle option for vue and svelte files, with the default set to false to match Prettier's vueIndentScriptAndStyle option. When enabled, this option indents the content within <script> and <style> tags to align with the surrounding HTML structure.

It can be enabled with this configuration:
```
{
  "html": {
    "formatter": {
      "indentScriptAndStyle": true
    }
```

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 bot force-pushed the renovate/all-minor-patch branch 6 times, most recently from c6eb68c to cf8ae23 Compare October 8, 2025 13:58

renovate bot force-pushed the renovate/all-minor-patch branch 10 times, most recently from 8ea569c to 264fc5b Compare October 16, 2025 01:53

renovate bot force-pushed the renovate/all-minor-patch branch 9 times, most recently from 5dc6fb7 to a1095f9 Compare October 23, 2025 10:33

renovate bot force-pushed the renovate/all-minor-patch branch 5 times, most recently from a24b22e to 25a7309 Compare October 28, 2025 20:06

renovate bot force-pushed the renovate/all-minor-patch branch 4 times, most recently from 1d654ad to 18d3daf Compare November 3, 2025 12:30

renovate bot force-pushed the renovate/all-minor-patch branch 6 times, most recently from 9793496 to ebb050f Compare November 12, 2025 03:58

renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from 73d4e95 to 06c9d85 Compare November 13, 2025 21:44

fix(deps): update all non-major dependencies

f5ff46b

renovate bot force-pushed the renovate/all-minor-patch branch from 06c9d85 to f5ff46b Compare November 17, 2025 10:56

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

fix(deps): update all non-major dependencies #11

fix(deps): update all non-major dependencies #11

Uh oh!

renovate bot commented Oct 1, 2025 •

edited

Loading

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

fix(deps): update all non-major dependencies #11

Are you sure you want to change the base?

fix(deps): update all non-major dependencies #11

Uh oh!

Conversation

renovate bot commented Oct 1, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release Notes

v2.3.6

Patch Changes

Invalid

Valid

v2.3.5

Patch Changes

v2.3.4

Patch Changes

v2.3.3

Patch Changes

v2.3.2

Patch Changes

v2.3.1

Patch Changes

v2.3.0

Minor Changes

Example

Configuration

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

renovate bot commented Oct 1, 2025 •

edited

Loading

`v2.3.6`

`v2.3.5`

`v2.3.4`

`v2.3.3`

`v2.3.2`

`v2.3.1`

`v2.3.0`