chore(deps): update dependency @biomejs/biome to v2#8

renovate · 2025-06-21T03:37:46Z

Note: This PR body was truncated due to platform limits.

This PR contains the following updates:

Package	Change	Age	Confidence
@biomejs/biome (source)	`1.9.4` -> `2.3.10`

Release Notes

biomejs/biome (@biomejs/biome)

`v2.3.10`

Compare Source

Patch Changes

#8417 c3a2557 Thanks @taga3s! - Fixed #7809: noRedeclare no longer reports redeclarations for infer type in conditional types.
#8477 90e8684 Thanks @dyc3! - Fixed #8475: fixed a regression in how noExtraNonNullAssertion flags extra non-null assertions
#8479 250b519 Thanks @dyc3! - Fixed #8473: The semantic model now indexes typescript constructor method definitions, and no longer panics if you use one (a regression in 2.3.9).
#8448 2af85c1 Thanks @mdevils! - Improved handling of defineProps() macro in Vue components. The noVueReservedKeys rule now avoids false positives in non-setup scripts.
#8420 42033b0 Thanks @vsn4ik! - Fixed the nursery rule noLeakedRender.
The biome migrate eslint command now correctly detects the rule react/jsx-no-leaked-render in your eslint configurations.
#8426 285d932 Thanks @anthonyshew! - Added a Turborepo domain and a new "noUndeclaredEnvVars" rule in it for warning users of unsafe environment variable usage in Turborepos.
#8410 a21db74 Thanks @ematipico! - Fixed #2988 where Biome couldn't handle properly characters that contain multiple code points when running in stdin mode.
#8372 b352ee4 Thanks @Netail! - Added the nursery rule noAmbiguousAnchorText, which disallows ambiguous anchor descriptions.

Invalid

<a>learn more</a>

`v2.3.9`

Compare Source

Patch Changes

#8232 84c9e08 Thanks @ruidosujeira! - Added the nursery rule noScriptUrl.
This rule disallows the use of javascript: URLs, which are considered a form of eval and can pose security risks such as XSS vulnerabilities.
```
<ahref="javascript:alert('XSS')">Click me</a>
```
#8341 343dc4d Thanks @arendjr! - Added the nursery rule useAwaitThenable, which enforces that await is only used on Promise values.

Invalid

await"value";constcreateValue=()=>"value";awaitcreateValue();

Caution

This is a first iteration of the rule, and does not yet detect generic "thenable" values.

#8034 e7e0f6c Thanks @Netail! - Added the nursery rule useRegexpExec. Enforce RegExp#exec over String#match if no global flag is provided.
#8137 d407efb Thanks @denbezrukov! - Reduced the internal memory used by the Biome formatter.
#8281 30b046f Thanks @tylersayshi! - Added the rule useRequiredScripts, which enforces presence of configurable entries in the scripts section of package.json files.

#8290 d74c8bd Thanks @dyc3! - The HTML formatter has been updated to match Prettier 3.7's behavior for handling <iframe>'s allow attribute.

- <iframe allow="layout-animations 'none'; unoptimized-images 'none'; oversized-images 'none'; sync-script 'none'; sync-xhr 'none'; unsized-media 'none';"></iframe>+ <iframe+ allow="+ layout-animations 'none';+ unoptimized-images 'none';+ oversized-images 'none';+ sync-script 'none';+ sync-xhr 'none';+ unsized-media 'none';+ "+ ></iframe>

#8302 d1d5014 Thanks @mlafeldt! - Fixed #8109: return statements in Astro frontmatter no longer trigger "Illegal return statement" errors when using experimentalFullSupportEnabled.
#8346 f3aee1a Thanks @arendjr! - Fixed #8292: Implement tracking
of types of TypeScript constructor parameter properties.
This resolves certain false negatives in noFloatingPromises and other typed
rules.

Example

classAsyncClass{asyncreturnsPromise(){return"value";}}classShouldBeReported{constructor(publicfield: AsyncClass){}// ^^^^^^^^^^^^----------------- Parameter property declarationasyncshouldBeReported(){// `noFloatingPromises` will now report the following usage:this.field.returnsPromise();}}

#8326 153e3c6 Thanks @ematipico! - Improved the rule noBiomeFirstException. The rule can now inspect if extended configurations already contain the catch-all ** inside files.includes and, if so, the rule suggests removing ** from the user configuration.
#8433 397547a Thanks @dyc3! - Fixed #7920: The CSS parser, with Tailwind directives enabled, will no longer error when you use things like prefix(tw) in @import at rules.
#8378 cc2a62e Thanks @Bertie690! - Clarify diagnostic message for lint/style/useUnifiedTypeSignatures
The rule's diagnostic message now clearly states that multiple similar overload signatures are hard to read & maintain, as opposed to overload signatures in general.
#8296 9d3ef10 Thanks @dyc3! - biome rage now shows if you have experimental HTML full support enabled.
#8414 09acf2a Thanks @Bertie690! - Updated the documentation & diagnostic message for lint/nursery/noProto, mentioning the reasons for its longstanding deprecation and why more modern alternatives are preferred.
Notably, the rule clearly states that using __proto__ inside object literal definitions is still allowed, being a standard way to set the prototype of a newly created object.
#8445 c3df0e0 Thanks @tt-a1i! - Fix --changed and --staged flags throwing "No such file or directory" error when a file has been deleted or renamed in the working directory. The CLI now filters out files that no longer exist before processing.
#8459 b17d12b Thanks @ruidosujeira! - Fix #8435: resolved false positive in noUnusedVariables for generic type parameters in construct signature type members (new <T>(): T).
#8439 a78774b Thanks @tt-a1i! - Fixed #8011: useConsistentCurlyBraces no longer suggests removing curly braces from JSX expression children containing characters that would cause parsing issues or semantic changes when converted to plain JSX text ({, }, <, >, &).
#8436 a392c06 Thanks @ruidosujeira! - Fixed #8429. Formatter, linter, and assist settings now correctly inherit from global configuration when not explicitly specified in overrides.
Before this fix, when an override specified only one feature (e.g., only linter), other features would be incorrectly disabled instead of inheriting from global settings.
Example configuration that now works correctly:
```
{"formatter":{"enabled": true }, "overrides": [{"includes": ["*.vue"], "linter":{"enabled": false } } ] }
```
After this fix, .vue files will have the linter disabled (as specified in the override) but the formatter enabled (inherited from global settings).
#8411 9f1b3b0 Thanks @rriski! - Properly handle name, type_arguments, and attributes slots for JsxOpeningElement and JsxSelfClosingElement GritQL patterns.
The following biome search commands no longer throw errors:
```
biome search 'JsxOpeningElement(name = $elem_name) where{$elem_name <: "div" }' biome search 'JsxSelfClosingElement(name = $elem_name) where{$elem_name <: "div" }'
```
#8441 cf37d0d Thanks @tt-a1i! - Fixed #6577: noUselessUndefined no longer reports () => undefined in arrow function expression bodies. Previously, the rule would flag this pattern and suggest replacing it with () =>{}, which conflicts with the noEmptyBlockStatements rule.
#8444 8caa7a0 Thanks @tt-a1i! - Fix noUnknownMediaFeatureName false positive for prefers-reduced-transparency media feature. The feature name was misspelled as prefers-reduded-transparency in the keywords list.
#8443 c3fa5a1 Thanks @tt-a1i! - Fix useGenericFontNames false positive when a CSS variable is used as the last value in font-family or font. The rule now correctly ignores cases like font-family: "Noto Serif", var(--serif) and font: 1em Arial, var(--fallback).
#8281 30b046f Thanks @tylersayshi! - Fixed noDuplicateDependencies incorrectly triggering on files like _package.json.
#8315 c7915c4 Thanks @hirokiokada77! - Fixed #5213: The noDoneCallback rule no longer flags false positives when a method is called on a regular variable bound to identifiers such as before, after, beforeEach, and afterEach.
#8398 204844f Thanks @Bertie690! - The default value of the ignoreRestSiblings option for noUnusedVariables'
has been reverted to its prior value of true after an internal refactor accidentally changed it.
The diagnostic message has also been tweaked for readability.
#8242 9694e37 Thanks @dyc3! - Fixed bugs in the HTML parser so that it will flag invalid shorthand syntaxes instead of silently accepting them. For example, <Foo : foo="5" /> is now invalid because there is a space after the :.
#8297 efa694c Thanks @Yonom! - Added support for negative value utilities in useSortedClasses. Negative value utilities such as -ml-2 or -top-4 are now recognized and sorted correctly alongside their positive counterparts.
```
// Now detected as unsorted:<divclass="-ml-2 p-4 -mt-1"/>// Suggested fix:<divclass="-mt-1 -ml-2 p-4"/>
```
#8335 3710702 Thanks @dibashthapa! - Added the new nursery rule useDestructuring. This rule helps to encourage destructuring from arrays and objects.
For example, the following code triggers because the variable name x matches the property foo.x, making it ideal for object destructuring syntax.
```
varx=foo.x;
```
#8383 59b2f9a Thanks @ematipico! - Fixed #7927: noExtraNonNullAssertion incorrectly flagged separate non-null assertions on both sides of an assignment.
The rule now correctly distinguishes between nested non-null assertions (still flagged) and separate non-null assertions on different sides of an assignment (allowed).

Examples

Valid (now allowed)

arr[0]!^=arr[1]!;

Invalid (still flagged)

arr[0]!!^=arr[1];arr[0]^=arr[1]!!;

#8401 382786b Thanks @Bertie690! - useExhaustiveDependencies now correctly validates custom hooks whose dependency arrays come before their callbacks.
Previously, a logical error caused the rule to be unable to detect dependency arrays placed before hook callbacks, producing spurious errors and blocking further diagnostics.
```
{"linter":{"rules":{"correctness":{"useExhaustiveDependencies":{"level": "error", "options":{"hooks": [{"name": "doSomething", "closureIndex": 2, "dependenciesIndex": 0 } ] } } } } } }
```
```
functioncomponent(){letthing=5;// The rule will now correctly recognize `thing` as being specified// instead of erroring due to "missing" dependency arraysdoSomething([thing],"blah",()=>{console.log(thing);});}
```
The rule documentation & diagnostic messages have also been reworked for improved clarity.
#8365 8f36051 Thanks @JacquesLeupin! - Fixed #8360: GritQL plugins defined in child configurations with extends: "//" now work correctly.
#8306 8de2774 Thanks @dibashthapa! - Fixed #8288: Fixed the issue with false positive errors
This new change will ignore attribute and only show diagnostics for JSX Expressions
For example
Valid:
```
<Somethingchecked={isOpen&&items.length}/>
```
Invalid:
```
constComponent=()=>{returnisOpen&&items.length;};
```
#8356 f9673fc Thanks @ematipico! - Fixed #7917, where Biome removed the styles contained in a <style lang="scss">, when experimentalFullSupportEnabled is enabled.
#8371 d71924e Thanks @ematipico! - Fixed #7343, where Biome failed to resolve extended configurations from parent directories using relative paths.
#8404 6a221f9 Thanks @fireairforce! - Fixed #7826, where a class member named async will not cause the parse error.
#8249 893e36c Thanks @cormacrelf! - Addressed #7538. Reduced the
volume of logging from the LSP server.
Use biome clean to remove large logs.

#8303 db2c65b Thanks @hirokiokada77! - Fixed #8300: noUnusedImports now detects JSDoc tags on object properties.

importtypeLinkOnObjectPropertyfrom"mod";consttestLinkOnObjectProperty={/** *{@&#8203;link LinkOnObjectProperty} */property: 0,};

#8328 9cf2332 Thanks @Netail! - Corrected rule source reference. biome migrate eslint should do a bit better detecting rules in your eslint configurations.
#8403 c96dcf2 Thanks @dyc3! - Fixed #8340: noUnknownProperty will no longer flag anything in @plugin when the parser option tailwindDirectives is enabled
#8284 4976d1b Thanks @denbezrukov! - Improved the performance of the Biome Formatter by enabling the internal source maps only when needed.
#8260 a226b28 Thanks @ho991217! - Fixed biome-vscode#817: Biome now updates documents when the textDocument/didSave notification is received.
#8183 b064786 Thanks @hornta! - Fixed #8179: The useConsistentArrowReturn rule now correctly handles multiline expressions in its autofix when the style option is set to "always".
Previously, the autofix would incorrectly place a newline after the return keyword, causing unexpected behavior.
Example:
```
constfoo=(l)=>l.split("\n");
```
Now correctly autofixes to:
```
const foo = (l) =>{- return- l.split('\n');+ return l.split('\n'); }
```
#8382 7409cba Thanks @fireairforce! - Fixed #8338: Ignored the noUnknownTypeSelector check when the root selector is used under View Transition pseudo-elements.
Example
```
::view-transition-old(root), ::view-transition-new(root){z-index:1}
```
#7513 e039f3b Thanks @AsherDe! - Added the nursery rule noVueSetupPropsReactivityLoss.
This new rule disallows usages that cause the reactivity of props passed to the setup function to be lost.
Invalid code example:
```
exportdefault{setup({ count }){// `count` is no longer reactive here.return()=>h("div",count);},};
```

`v2.3.8`

Compare Source

Patch Changes

#8188 4ca088c Thanks @ematipico! - Fixed #7390, where Biome couldn't apply the correct configuration passed via --config-path.
If you have multiple root configuration files, running any command with --config-path will now apply the chosen configuration file.
#8171 79adaea Thanks @dibashthapa! - Added the new rule noLeakedRender. This rule helps prevent potential leaks when rendering components that use binary expressions or ternaries.
For example, the following code triggers the rule because the component would render 0:
```
constComponent=()=>{constcount=0;return<div>{count&&<span>Count: {count}</span>}</div>;};
```
#8116 b537918 Thanks @Netail! - Added the nursery rule noDuplicatedSpreadProps. Disallow JSX prop spreading the same identifier multiple times.
Invalid:
```
<div{...props}something="else"{...props}/>
```
#8256 f1e4696 Thanks @cormacrelf! - Fixed a bug where logs were discarded (the kind from --log-level=info etc.). This is a regression introduced after an internal refactor that wasn't adequately tested.
#8226 3f19b52 Thanks @dyc3! - Fixed #8222: The HTML parser, with Vue directives enabled, can now parse v-slot shorthand syntax, e.g. <template #foo>.
#8007 182ecdc Thanks @brandonmcconnell! - Added support for dollar-sign-prefixed filenames in the useFilenamingConvention rule.
Biome now allows filenames starting with the dollar-sign (e.g. $postId.tsx) by default to support naming conventions used by frameworks such as TanStack Start for file-based-routing.
#8218 91484d1 Thanks @hirokiokada77! - Added the noMultiStr rule, which disallows creating multiline strings by escaping newlines.
Invalid:
```
constfoo="Line 1\n\Line 2";
```
Valid:
```
constfoo="Line 1\nLine 2";constbar=`Line 1Line 2`;
```

#8225 98ca2ae Thanks @ongyuxing! - Fixed #7806: Prefer breaking after the assignment operator for conditional types with generic parameters to match Prettier.

-type True = unknown extends Type<- "many",- "generic",- "parameters",- "one",- "two",- "three"->- ? true- : false;+type True =+ unknown extends Type<"many", "generic", "parameters", "one", "two", "three">+ ? true+ : false;

#6765 23f7855 Thanks @emilyinure! - Fixed #6569: Allow files to export from themselves with noImportCycles.

This means the following is now allowed:

// example.jsexportfunctionexample(){return1;}// Re-exports all named exports from the current module under a single namespace// and then imports the namespace from the current module.// Allows for encapsulating functions/variables into a namespace instead// of using a static class.export*asExamplefrom"./example.js";import{Example}from"./example.js";

#8214 68c052e Thanks @hirokiokada77! - Added the noEqualsToNull rule, which enforces the use of === and !== for comparison with null instead of == or !=.
Invalid:
```
foo==null;foo!=null;
```
Valid:
```
foo===null;foo!==null;
```
#8219 793bb9a Thanks @dyc3! - Fixed #8190: The HTML parser will now parse Vue event handlers that contain : correctly, e.g. @update:modelValue="onUpdate".
#8259 4a9139b Thanks @hirokiokada77! - Fixed #8254: The noParameterAssign rule with propertyAssignment: "deny" was incorrectly reporting an error when a function parameter was used on the right-hand side of an assignment to a local variable's property.
The rule should only flag assignments that modify the parameter binding or its properties (L-value), not the use of its value.
Valid:
```
(input)=>{constlocal={property: 0};local.property=input;};
```
#8201 cd2edd7 Thanks @Netail! - Added the nursery rule noTernary. Disallow ternary operators.
Invalid:
```
constfoo=isBar ? baz : qux;
```
#8172 de98933 Thanks @JeremyMoeglich! - Fixed #8145: handling of large hex literals, which previously caused both false positives and false negatives.
This affects noPrecisionLoss and noConstantMathMinMaxClamp.
#8210 7b44e9e Thanks @Netail! - Corrected rule source reference. biome migrate eslint should do a bit better detecting rules in your eslint configurations.
#8213 e430555 Thanks @ruidosujeira! - Fixed #8209: Recognized formatting capability when either range or on-type formatting is supported, not only full-file formatting. This ensures editors and the language server correctly detect formatting support in files like JSONC.
#8202 6f49d95 Thanks @hirokiokada77! - Fixed #8079: Properly handle name and value metavariables for JsxAttribute GritQL queries.
The following biome search command no longer throws an error:
```
biome search 'JsxAttribute($name, $value) as $attr where{$name <: "style" }' 
```
#8276 f7e836f Thanks @hirokiokada77! - Added the noProto rule, which disallows the use of the __proto__ property for getting or setting the prototype of an object.
Invalid:
```
obj.__proto__=a;constb=obj.__proto__;
```
Valid:
```
consta=Object.getPrototypeOf(obj);Object.setPrototypeOf(obj,b);
```

`v2.3.7`

Compare Source

Patch Changes

#8169 7fdcec8 Thanks @arendjr! - Fixed #7999: Correctly place await after leading comment in auto-fix action from noFloatingPromises rule.
#8157 12d5b42 Thanks @Conaclos! - Fixed #8148. noInvalidUseBeforeDeclaration no longer reports some valid use before declarations.
The following code is no longer reported as invalid:
```
classclassA{C=C;}constC=0;
```
#8178 6ba4157 Thanks @dyc3! - Fixed #8174, where the HTML parser would parse 2 directives as a single directive because it would not reject whitespace in Vue directives. This would cause the formatter to erroneously merge the 2 directives into one, resulting in broken code.
```
- <Component v-else:property="123" />+ <Component v-else :property="123" />
```
#8088 0eb08e8 Thanks @db295! - Fixed #7876: The noUnusedImports rule now ignores imports that are used by @linkcode and @linkplain (previously supported @link and @see).
The following code will no longer be a false positive:
```
importtype{a}from"a"/** *{@&#8203;linkcode a} */functionfunc(){}
```
#8119 8d64655 Thanks @ematipico! - Improved the detection of the rule noUnnecessaryConditions. Now the rule isn't triggered for variables that are mutated inside a module.
This logic deviates from the original rule, hence noUnnecessaryConditions is now marked as "inspired".
In the following example, hey starts as false, but then it's assigned to a string. The rule isn't triggered inside the if check.
```
lethey=false;functiontest(){hey="string";}if(hey){}
```
#8149 e0a02bf Thanks @Netail! - Fixed #8144: Improve noSyncScripts, ignore script tags with type="module" as these are always non-blocking.
#8182 e9f068e Thanks @hirokiokada77! - Fixed #7877: Range suppressions now handle suppressed categories properly.
Valid:
```
// biome-ignore-start lint: explanationconstfoo=1;// biome-ignore-end lint: explanation
```
#8111 bf1a836 Thanks @ryan-m-walker! - Added support for parsing and formatting the CSS if function.
Example
```
.basic-style{color:if(style(--scheme: dark):#eeeeee; else: #&#8203;000000;)}
```
#8173 7fc07c1 Thanks @ematipico! - Fixed #8138 by reverting an internal refactor that caused a regression to the rule noUnusedPrivateClassMembers.
#8119 8d64655 Thanks @ematipico! - Improved the type inference engine, by resolving types for variables that are assigned to multiple values.
#8158 fb1458b Thanks @dyc3! - Added the useVueValidVText lint rule to enforce valid v-text directives. The rule reports when v-text has an argument, has modifiers, or is missing a value.
Invalid:
```
<divv-text />  <divv-text:aaa="foo" />  <divv-text.bbb="foo" /> 
```
#8158 fb1458b Thanks @dyc3! - Fixed useVueValidVHtml so that it will now flag empty strings, e.g. v-html=""
#7078 bb7a15c Thanks @emilyinure! - Fixed #6675: Now only flags
noAccumulatingSpread on Object.assign when a new object is being allocated on
each iteration. Before, all cases using Object.assign with reduce parameters
were warned despite not making new allocations.
The following code will no longer be a false positive:
```
foo.reduce((acc,bar)=>Object.assign(acc,bar),{});
```
The following cases which do make new allocations will continue to warn:
```
foo.reduce((acc,bar)=>Object.assign({},acc,bar),{});
```
#8175 0c8349e Thanks @ryan-m-walker! - Fixed CSS formatting of dimension units to use correct casing for Q, Hz and kHz.
Before:
```
.cssUnits{a:1Q; b:1Hz; c:1kHz}
```
After:
```
.cssUnits{a:1Q; b:1Hz; c:1kHz}
```

`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:
```
<htmllang="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:
```
enumEnumValue{"this is a description" DEFAULT }
```
Valid:
```
enumEnumValue{""" 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):
```
functionnotRecursive(arg){returnarg;}constobj={notRecursive(arg){returnnotRecursive(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.
```
 <divv-for="iteminitems"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(constiinarray){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):
```
constresult=foo ? (bar ? 1 : 2) : 3;
```
Still valid (non-nested with parentheses):
```
constresult=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:
```
constErrorBoundary=classextendsComponent{componentDidCatch(error,info){}render(){returnthis.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:

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

Valid:

<scriptsrc="https://third-party-script.js"async/><scriptsrc="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)
```
classUsedMember{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)
```
classFoo{ #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

Configuration

📅 Schedule: Branch creation - Only on Sunday and Saturday ( * * * * 0,6 ) (UTC), Automerge - Between 12:00 AM and 03:59 AM ( * 0-3 * * * ) (UTC).

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

♻ Rebasing: Whenever PR is behind base branch, 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.

renovatebot added automated scope:deps labels Jun 21, 2025

renovatebotforce-pushed the renovate/biomejs-biome-2.x branch 3 times, most recently from a71f6c5 to 4f3e13aCompare June 27, 2025 11:36

renovatebotforce-pushed the renovate/biomejs-biome-2.x branch 2 times, most recently from fef67a9 to 3354972Compare July 8, 2025 16:26

renovatebotforce-pushed the renovate/biomejs-biome-2.x branch from 3354972 to 07bbd44Compare July 17, 2025 16:43

renovatebotforce-pushed the renovate/biomejs-biome-2.x branch from 07bbd44 to 40e3093Compare July 29, 2025 17:49

renovatebotforce-pushed the renovate/biomejs-biome-2.x branch 2 times, most recently from 8dea863 to 59c5461Compare August 14, 2025 09:56

renovatebotforce-pushed the renovate/biomejs-biome-2.x branch from 59c5461 to 2c68f17Compare August 23, 2025 14:33

renovatebotforce-pushed the renovate/biomejs-biome-2.x branch 2 times, most recently from 8b5a8c8 to fe85c0dCompare September 10, 2025 12:47

renovatebotforce-pushed the renovate/biomejs-biome-2.x branch from fe85c0d to ec2c8c1Compare October 2, 2025 13:30

renovatebotforce-pushed the renovate/biomejs-biome-2.x branch 2 times, most recently from 3989a73 to 546db8cCompare October 13, 2025 10:42

renovatebotforce-pushed the renovate/biomejs-biome-2.x branch 4 times, most recently from f0783fb to 6db9599Compare October 28, 2025 19:59

renovatebotforce-pushed the renovate/biomejs-biome-2.x branch 2 times, most recently from db8c9cc to 2e08a1bCompare November 5, 2025 18:05

renovatebotforce-pushed the renovate/biomejs-biome-2.x branch 2 times, most recently from aa2c8d1 to c064e56Compare November 17, 2025 13:02

renovatebotforce-pushed the renovate/biomejs-biome-2.x branch 2 times, most recently from 7efa5a4 to d6f11ceCompare November 27, 2025 15:36

renovatebotforce-pushed the renovate/biomejs-biome-2.x branch from d6f11ce to 02c8c10Compare December 15, 2025 17:06

chore(deps): update dependency @biomejs/biome to v2
93ecdc6

renovatebotforce-pushed the renovate/biomejs-biome-2.x branch from 02c8c10 to 93ecdc6Compare December 17, 2025 15:34

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

chore(deps): update dependency @biomejs/biome to v2#8

chore(deps): update dependency @biomejs/biome to v2 #8

Uh oh!

renovatebot commented Jun 21, 2025•
edited
Loading

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

chore(deps): update dependency @biomejs/biome to v2#8

Are you sure you want to change the base?

chore(deps): update dependency @biomejs/biome to v2 #8

Uh oh!

Conversation

renovatebot commented Jun 21, 2025• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release Notes

v2.3.10

Patch Changes

Invalid

v2.3.9

Patch Changes

Invalid

Caution

Example

Examples

Valid (now allowed)

Invalid (still flagged)

v2.3.8

Patch Changes

v2.3.7

Patch Changes

v2.3.6

Patch Changes

Configuration

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

renovatebot commented Jun 21, 2025•
edited
Loading

`v2.3.10`

`v2.3.9`

`v2.3.8`

`v2.3.7`

`v2.3.6`