-
Notifications
You must be signed in to change notification settings - Fork 171
chore(deps): update non-major dependencies #63
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.
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
base: main
Are you sure you want to change the base?
Conversation
📝 WalkthroughWalkthroughDev tooling and metadata were updated: multiple devDependencies in package.json were bumped ( 🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Warning Review ran into problems🔥 ProblemsErrors were encountered while retrieving linked issues. Errors (1)
Comment |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #63 +/- ##
=======================================
Coverage 95.24% 95.24%
=======================================
Files 25 25
Lines 715 715
Branches 207 207
=======================================
Hits 681 681
Misses 34 34 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 1
📜 Review details
Configuration used: CodeRabbit UI
Review profile: ASSERTIVE
Plan: Pro
⛔ Files ignored due to path filters (1)
pnpm-lock.yamlis excluded by!**/pnpm-lock.yaml
📒 Files selected for processing (1)
package.json(1 hunks)
🔇 Additional comments (1)
package.json (1)
49-49: lint-staged patch update is safe.The 16.2.6 bump fixes a bug in --continue-on-error task handling—low risk.
package.json
Outdated
| }, | ||
| "devDependencies": { | ||
| "@biomejs/biome": "2.2.7", | ||
| "@biomejs/biome": "2.3.0", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
Verify biome 2.3.0 compatibility with existing linting/formatting.
The bump to 2.3.0 introduces new lint rules and formatting options (lineEnding: auto, indentScriptAndStyle). Confirm the pipeline passes linting and formatting checks.
🏁 Script executed:
#!/bin/bash
# Verify lock file is updated and biome configuration remains compatible
# Check if pnpm-lock.yaml exists and contains the updated biome version
fd "pnpm-lock.yaml" -x grep -q "@biomejs/[email protected]" && echo "✓ Lock file contains biome 2.3.0" || echo "✗ Lock file may need update"
# Check for biome config file and its content
fd "biome.json|biome.jsonc" -x catLength of output: 3953
Update biome.json schema reference to match 2.3.0 version.
Lock file is properly updated, but the schema URL still references 2.2.7. Update "$schema" in biome.json to https://biomejs.dev/schemas/2.3.0/schema.json to avoid validation mismatches.
Also confirm whether the new formatting options (lineEnding: auto, indentScriptAndStyle) mentioned in the PR should be adopted or remain as-is.
🤖 Prompt for AI Agents
In package.json around line 43 (the Biome dependency bump to 2.3.0), update the
"$schema" field in biome.json from the old 2.2.7 URL to
https://biomejs.dev/schemas/2.3.0/schema.json so the schema version matches the
installed biome package; open biome.json, replace the schema URL accordingly,
and then run biome/format or validation to ensure no schema errors. While here,
confirm whether to adopt the new formatting options (lineEnding: "auto" and
indentScriptAndStyle) by either adding them to biome.json if you want those
behaviors or leaving them out to preserve current formatting, and run the
formatter to verify the resulting diffs are acceptable.
e1d63fb to
81f4f99
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 1
📜 Review details
Configuration used: CodeRabbit UI
Review profile: ASSERTIVE
Plan: Pro
Disabled knowledge base sources:
- Linear integration is disabled by default for public repositories
You can enable these sources in your CodeRabbit configuration.
⛔ Files ignored due to path filters (1)
pnpm-lock.yamlis excluded by!**/pnpm-lock.yaml
📒 Files selected for processing (1)
package.json(1 hunks)
🔇 Additional comments (2)
package.json (2)
49-49: Confirm lint-staged 16.2.6 patch resolves --continue-on-error issue.The patch addresses task failures with the
--continue-on-errorflag. If your CI/hooks use this flag, verify it now works as expected.
52-52: LGTM.tsdown 0.15.10 patch is low-risk (rolldown-plugin-dts upgrade, nested index fix).
81f4f99 to
e517470
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 1
📜 Review details
Configuration used: CodeRabbit UI
Review profile: ASSERTIVE
Plan: Pro
Disabled knowledge base sources:
- Linear integration is disabled by default for public repositories
You can enable these sources in your CodeRabbit configuration.
⛔ Files ignored due to path filters (1)
pnpm-lock.yamlis excluded by!**/pnpm-lock.yaml
📒 Files selected for processing (2)
.nvmrc(1 hunks)package.json(1 hunks)
🔇 Additional comments (3)
.nvmrc (1)
1-1: LGTM!Node patch version bump (22.21.0 → 22.21.1) is routine and safe.
package.json (2)
49-49: LGTM!lint-staged 16.2.5 → 16.2.6 is a patch fix for --continue-on-error task handling. No breaking changes.
52-52: LGTM!tsdown 0.15.9 → 0.15.11 (per AI summary; PR objectives mention 0.15.10) includes rolldown-plugin-dts upgrade and index file export fixes. Routine patch bump.
package.json
Outdated
| }, | ||
| "devDependencies": { | ||
| "@biomejs/biome": "2.2.7", | ||
| "@biomejs/biome": "2.3.1", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
Dependency update approved; schema URL verification required.
@biomejs/biome 2.2.7 → 2.3.1 looks good. However, previous reviews flagged that biome.json's "$schema" URL still referenced 2.2.7. Confirm the schema URL has been updated to match 2.3.1.
🏁 Script executed:
#!/bin/bash
# Verify biome.json schema URL matches installed version and lock file is current
echo "=== biome.json schema URL ==="
fd "biome.json|biome.jsonc" -x grep '"$schema"' || echo "No biome config found"
echo -e "\n=== pnpm-lock.yaml @biomejs/biome version ==="
grep -A 2 '"@biomejs/biome":' pnpm-lock.yaml | head -5 || echo "biome not found in lock file"
echo -e "\n=== Confirm schema matches package.json version ==="
SCHEMA=$(fd "biome.json|biome.jsonc" -x grep -oP '(?<=schemas/)[^/]+' || echo "not found")
echo "Schema version from biome.json: $SCHEMA (should be 2.3.1)"Length of output: 247
biome.json schema URL must be updated to 2.3.1.
The schema URL in biome.json is still 2.2.7 but the package is 2.3.1. Update to https://biomejs.dev/schemas/2.3.1/schema.json.
🤖 Prompt for AI Agents
In package.json around line 43, the project depends on "@biomejs/biome": "2.3.1"
but the biome.json schema URL still points to 2.2.7; update the schema URL in
biome.json to "https://biomejs.dev/schemas/2.3.1/schema.json" so it matches the
installed biome version, ensuring the schema version string and path reflect
2.3.1.
e517470 to
8982ea7
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 1
📜 Review details
Configuration used: CodeRabbit UI
Review profile: ASSERTIVE
Plan: Pro
Disabled knowledge base sources:
- Linear integration is disabled by default for public repositories
You can enable these sources in your CodeRabbit configuration.
⛔ Files ignored due to path filters (1)
pnpm-lock.yamlis excluded by!**/pnpm-lock.yaml
📒 Files selected for processing (2)
.nvmrc(1 hunks)package.json(1 hunks)
🔇 Additional comments (5)
.nvmrc (1)
1-1: Routine patch bump; no concerns.Node.js 22.21.1 is a patch release with minor fixes and improvements. Safe to update.
package.json (4)
44-44: Approve @types/node patch bump.Update from 22.18.12 to 22.18.13 is a safe patch with type corrections.
49-49: Approve lint-staged patch bump.Update from 16.2.5 to 16.2.6 fixes --continue-on-error task handling. No breaking changes.
52-52: Approve tsdown patch bumps.Updates from 0.15.9 to 0.15.11 include rolldown-plugin-dts upgrade and export path fixes. No concerns.
56-56: Approve pnpm packageManager update.Bump from 10.19.0 to 10.20.0 is a minor release. Ensure lock file is regenerated with
pnpm installor equivalent if needed.
8982ea7 to
1e78a91
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 1
📜 Review details
Configuration used: CodeRabbit UI
Review profile: ASSERTIVE
Plan: Pro
Disabled knowledge base sources:
- Linear integration is disabled by default for public repositories
You can enable these sources in your CodeRabbit configuration.
⛔ Files ignored due to path filters (1)
pnpm-lock.yamlis excluded by!**/pnpm-lock.yaml
📒 Files selected for processing (2)
.nvmrc(1 hunks)package.json(1 hunks)
🔇 Additional comments (1)
.nvmrc (1)
1-1: Node.js patch bump approved.Routine runtime update; no issues.
1e78a91 to
32c61f3
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 1
📜 Review details
Configuration used: CodeRabbit UI
Review profile: ASSERTIVE
Plan: Pro
Disabled knowledge base sources:
- Linear integration is disabled by default for public repositories
You can enable these sources in your CodeRabbit configuration.
⛔ Files ignored due to path filters (1)
pnpm-lock.yamlis excluded by!**/pnpm-lock.yaml
📒 Files selected for processing (2)
.nvmrc(1 hunks)package.json(1 hunks)
🔇 Additional comments (1)
.nvmrc (1)
1-1: Node patch update looks good.Straightforward patch version bump that aligns with the broader toolchain updates.
239fb8f to
1e0991c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 1
📜 Review details
Configuration used: CodeRabbit UI
Review profile: ASSERTIVE
Plan: Pro
Disabled knowledge base sources:
- Linear integration is disabled by default for public repositories
You can enable these sources in your CodeRabbit configuration.
⛔ Files ignored due to path filters (1)
pnpm-lock.yamlis excluded by!**/pnpm-lock.yaml
📒 Files selected for processing (2)
.nvmrc(1 hunks)package.json(1 hunks)
🔇 Additional comments (1)
.nvmrc (1)
1-1: Node version patch bump is safe.Straightforward patch version update; no behavioral changes.
1e0991c to
e319653
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 1
📜 Review details
Configuration used: CodeRabbit UI
Review profile: ASSERTIVE
Plan: Pro
Disabled knowledge base sources:
- Linear integration is disabled by default for public repositories
You can enable these sources in your CodeRabbit configuration.
⛔ Files ignored due to path filters (1)
pnpm-lock.yamlis excluded by!**/pnpm-lock.yaml
📒 Files selected for processing (2)
.nvmrc(1 hunks)package.json(1 hunks)
🔇 Additional comments (1)
.nvmrc (1)
1-1: Node.js patch update approved.Straightforward patch bump (22.21.0 → 22.21.1) aligned with the PR strategy.
e319653 to
57b736a
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 1
📜 Review details
Configuration used: CodeRabbit UI
Review profile: ASSERTIVE
Plan: Pro
Disabled knowledge base sources:
- Linear integration is disabled by default for public repositories
You can enable these sources in your CodeRabbit configuration.
⛔ Files ignored due to path filters (1)
pnpm-lock.yamlis excluded by!**/pnpm-lock.yaml
📒 Files selected for processing (2)
.nvmrc(1 hunks)package.json(1 hunks)
🔇 Additional comments (3)
package.json (2)
56-56: pnpm version bump is safe.The packageManager field correctly pins pnpm to 10.20.0 (minor bump from 10.19.0). This ensures consistent builds across environments and includes patch fixes.
43-44: Lock file is properly updated.All four version bumps are confirmed in pnpm-lock.yaml and maintain non-major semantics (no breaking changes).
.nvmrc (1)
1-1: Node.js patch version aligned with package.json engines constraint.The .nvmrc update from 22.21.0 to 22.21.1 is a safe patch-level bump and satisfies the
engines.nodeconstraint (≥22.14.0) in package.json. No behavioral changes expected.
57b736a to
c838298
Compare
1b4b94a to
ffadf75
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 1
🤖 Fix all issues with AI agents
In `@package.json`:
- Around line 43-55: biome.json currently points its $schema to 2.2.7 while
package.json lists `@biomejs/biome`@2.3.12 — update the $schema value in
biome.json to "https://biomejs.dev/schemas/2.3.12/schema.json" so the schema
version matches the `@biomejs/biome` dependency; also, in package.json change the
vite-tsconfig-paths entry (currently "^6.0.0") to the exact pinned version
"6.0.0" to match the other devDependencies' exact versioning style (refer to the
`@biomejs/biome` devDependency and vite-tsconfig-paths symbol names to locate
these entries).
♻️ Duplicate comments (1)
package.json (1)
54-54: Inconsistent version pinning.
vite-tsconfig-pathsuses^6.0.0; others are exact. Pin to6.0.0for consistency.
package.json
Outdated
| "@biomejs/biome": "2.3.12", | ||
| "@types/node": "22.19.7", | ||
| "@vitest/coverage-v8": "4.0.18", | ||
| "cspell": "9.6.0", | ||
| "husky": "9.1.7", | ||
| "license-checker-rseidelsohn": "4.4.2", | ||
| "lint-staged": "16.2.5", | ||
| "prettier": "3.6.2", | ||
| "sort-package-json": "3.4.0", | ||
| "tsdown": "0.15.9", | ||
| "lint-staged": "16.2.7", | ||
| "prettier": "3.8.1", | ||
| "sort-package-json": "3.6.0", | ||
| "tsdown": "0.20.1", | ||
| "typescript": "5.9.3", | ||
| "vite-tsconfig-paths": "^6.0.0", | ||
| "vitest": "4.0.5" | ||
| "vitest": "4.0.18" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
echo "=== Checking biome.json schema ==="
if [ -f "biome.json" ]; then
cat biome.json | head -20
echo ""
echo "=== Schema URL extraction ==="
grep '$schema' biome.json 2>/dev/null || echo "No \$schema field found"
else
echo "✗ biome.json not found"
fi
echo ""
echo "=== Checking vite-tsconfig-paths in package.json ==="
grep 'vite-tsconfig-paths' package.jsonRepository: deepnote/deepnote
Length of output: 872
Update biome.json $schema from 2.2.7 to 2.3.12.
The schema URL is pinned to 2.2.7 but package.json requires @biomejs/[email protected]. Change to https://biomejs.dev/schemas/2.3.12/schema.json.
Also, vite-tsconfig-paths uses ^6.0.0 (caret) while other devDependencies are pinned exactly—consider aligning for consistency.
🤖 Prompt for AI Agents
In `@package.json` around lines 43 - 55, biome.json currently points its $schema
to 2.2.7 while package.json lists `@biomejs/biome`@2.3.12 — update the $schema
value in biome.json to "https://biomejs.dev/schemas/2.3.12/schema.json" so the
schema version matches the `@biomejs/biome` dependency; also, in package.json
change the vite-tsconfig-paths entry (currently "^6.0.0") to the exact pinned
version "6.0.0" to match the other devDependencies' exact versioning style
(refer to the `@biomejs/biome` devDependency and vite-tsconfig-paths symbol names
to locate these entries).
7956fdd to
f0f9cc8
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 1
🤖 Fix all issues with AI agents
In `@package.json`:
- Line 57: package.json's "packageManager": "[email protected]" was updated but
pnpm-lock.yaml wasn't regenerated; run pnpm install using pnpm v10.28.1 (or run
core command `pnpm install` after switching to that version) to regenerate
pnpm-lock.yaml so lockfileVersion and metadata match the packageManager entry;
verify pnpm-lock.yaml is updated and commit the updated lockfile alongside the
package.json change.
package.json
Outdated
| "vitest": "4.0.18" | ||
| }, | ||
| "packageManager": "pnpm@10.19.0", | ||
| "packageManager": "pnpm@10.28.1", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Check lockfile version and packageManager alignment
rg -n "packageManager" package.json
if [ -f "pnpm-lock.yaml" ]; then
rg -n "lockfileVersion" pnpm-lock.yaml
rg -n "pnpm@10\.28\.1" pnpm-lock.yaml || echo "[email protected] not recorded in lockfile"
else
echo "pnpm-lock.yaml not found"
fiRepository: deepnote/deepnote
Length of output: 162
Regenerate pnpm-lock.yaml with pnpm 10.28.1.
The lockfile was not updated when the packageManager version changed. Run pnpm install to sync pnpm-lock.yaml with the new version and prevent lockfileVersion drift.
🤖 Prompt for AI Agents
In `@package.json` at line 57, package.json's "packageManager": "[email protected]" was
updated but pnpm-lock.yaml wasn't regenerated; run pnpm install using pnpm
v10.28.1 (or run core command `pnpm install` after switching to that version) to
regenerate pnpm-lock.yaml so lockfileVersion and metadata match the
packageManager entry; verify pnpm-lock.yaml is updated and commit the updated
lockfile alongside the package.json change.
acd21b0 to
60bb69d
Compare
60bb69d to
d42f235
Compare
This PR contains the following updates:
2.2.7→2.3.134.5.2→4.5.37.5.2→7.5.322.18.12→22.19.74.0.5→4.0.182.0.0→2.2.19.2.2→9.6.216.2.5→16.2.722.21.0→22.22.09.0.0→9.1.010.19.0→10.28.23.6.2→3.8.13.4.0→3.6.10.15.9→0.20.14.20.6→4.21.06.0.3→6.0.54.0.5→4.0.182.8.1→2.8.2Release Notes
biomejs/biome (@biomejs/biome)
v2.3.13Compare Source
Patch Changes
#8815
f924f23Thanks @dyc3! - ImproveduseVueValidVOnto be more closely aligned with the source rule. It will now properly allow modifiers for all possible keyboard events. It should have better performance when there are no violations of the rule as well.Now treated valid:
#8856
85f81f9Thanks @dyc3! - Fixed #8710: Biome now parses Vue dynamic slot shorthand arguments that use template literals in[].#8850
2a190e0Thanks @dyc3! - Fixed #8708: Tailwind@utilitydirectives now parse functional utility names likepx-*when Tailwind directives are enabled.#8863
79386e0Thanks @dyc3! - Fixed an issue withbiome migrate eslintwhere it couldn't detect rules for CSS, GraphQL, and HTML.#8771
6f56b6eThanks @lghuahua! - Fix the--reporter=summaryoutput incorrectly merging and displaying wrong issue counts for different rules. Fixes #8730#8714
ac3a71fThanks @Netail! - Added new nursery ruleuse-consistent-enum-value-type. This rule disallows enums from having both number and string members.v2.3.12Compare Source
Patch Changes
#8653
047576dThanks @dyc3! - Added new nursery rulenoDuplicateAttributesto forbid duplicate attributes in HTML elements.#8648
96d09f4Thanks @BaeSeokJae! - Added a new nursery rulenoVueOptionsApi.Biome now reports Vue Options API usage, which is incompatible with Vue 3.6's Vapor Mode.
This rule detects Options API patterns in
<script>blocks,defineComponent(), andcreateApp()calls,helping prepare codebases for Vapor Mode adoption.
For example, the following now triggers this rule:
#8832
b08270bThanks @Exudev! - Fixed #8809, #7985, and #8136: thenoSecretsrule no longer reports false positives on common CamelCase identifiers likepaddingBottom,backgroundColor,unhandledRejection,uncaughtException, andIngestGatewayLogGroup.The entropy calculation algorithm now uses "average run length" to distinguish between legitimate CamelCase patterns (which have longer runs of same-case letters) and suspicious alternating case patterns (which have short runs).
#8793
c19fb0eThanks @TheBaconWizard! - Properly handleparametersmetavariables forarrow_functionGritQL queries. The followingbiome searchcommand no longer throws an error:biome search 'arrow_function(parameters=$parameters, body=$body)'#8561
981affbThanks @wataryooou! - FixednoUnusedVariablesto ignore type parameters declared in ambient contexts such asdeclare moduleblocks.#8817
652cfbbThanks @dyc3! - Fixed #8765: The HTML parser can now parse directive modifiers with a single colon, e.g.@keydown.:.#8704
a1914d4Thanks @Netail! - Added the nursery rulenoRootType.Disallow the usage of specified root types. (e.g.
mutationand/orsubscription)Invalid:
{ "options": { "disallow": ["mutation"] } }#8712
251b47bThanks @Netail! - Renamed the following GraphQL nursery rules to match the Biome standard:useUniqueArgumentNames->noDuplicateArgumentNamesuseUniqueFieldDefinitionNames->noDuplicateFieldDefinitionNamesuseUniqueGraphqlOperationName->noDuplicateGraphqlOperationNameuseUniqueInputFieldNames->noDuplicateInputFieldNamesuseUniqueVariableNames->noDuplicateVariableNamesRun the
biome migrate --writecommand to automatically update the configuration file.#7602
957cd8eThanks @kedevked! - Added the nursery lint ruleuseErrorCause.This rule enforces that errors caught in a
catchclause are not rethrown without wrapping them in a newErrorobject and specifying the original error as thecause. This helps preserve the error’s stack trace and context for better debugging.It can be configured with the following option:
requireCatchParameter: (default:true)true, the rule requires thatcatchclauses have a parameter. If athrowstatement appears inside acatchclause without a parameter, it will be flagged.Invalid examples:
Valid examples:
Valid example when
requireCatchParameterisfalse:Valid:
#8725
95aba98Thanks @dyc3! - Fixed #8715: The CSS parser will now recover slightly better if a semicolon is missing from Tailwind's@applyat-rule.#8616
4ee3bdaThanks @Netail! - Added the nursery ruleuseLoneAnonymousOperation. Disallow anonymous operations when more than one operation specified in document.Invalid:
#8624
291c9f2Thanks @taga3s! - Added the nursery ruleuseInlineScriptIdto the Next.js domain.This rule enforces
idattribute onnext/scriptcomponents with inline content ordangerouslySetInnerHTML.The following code is invalid:
#8767
0d15370Thanks @mdevils! - Fixed #3512:useExhaustiveDependenciesnow properly handles nested destructuring patternsfrom hook results.
#8757
17ed9d3Thanks @Netail! - Added the nursery rulenoDivRegex. Disallow equal signs explicitly at the beginning of regular expressions.Invalid:
#8836
aab1d17Thanks @dyc3! - Fixed #7858: Biome now parses Astro files with empty frontmatter blocks.#8755
3a15c29Thanks @arturalkaim! - Fixed #6670. The$filenamemetavariable can now be used in GritQLwhereclauses to filter matches by filename.#8821
63e68a1Thanks @playhardgopro! - Fixed several bugs in Vue conditional rules (useVueValidVIf,useVueValidVElse, anduseVueValidVElseIf) related to whitespace handling, newlines, and self-closing tags.#8767
0d15370Thanks @mdevils! - Fixed #3685:useExhaustiveDependenciesnow properly handles transparent expressionwrappers like non-null assertions and type assertions in dependency comparisons.
#8597
f764007Thanks @Netail! - Added the nursery rulenoDuplicateEnumValueNames. Enforce unique enum value names.Invalid:
#8679
33dfd7cThanks @ematipico! - Fixed #8678. Now Biome correctly parses components inside Vue, Svelte and Astro files when they have the same name of self-closing elements.#8617
31a9bfeThanks @Netail! - Added the nursery ruleuseLoneExecutableDefinition. Require queries, mutations, subscriptions or fragments to be located in separate files.Invalid:
#8697
8519669Thanks @Faizanq! - Added the nursery lint rulenoExcessiveLinesPerFileto CSS and GraphQL.#8711
365f7aaThanks @Netail! - Added new nursery rulenoDuplicateEnumValues, which disallows defining an enum with multiple members initialized to the same value.#8767
0d15370Thanks @mdevils! - Fixed #5914:useExhaustiveDependenciesnow properly handles variables declared in the samestatement.
#8767
0d15370Thanks @mdevils! - Fixed #8427:useExhaustiveDependenciesnow properly resolves variable references to detectcaptured dependencies.
#8767
0d15370Thanks @mdevils! - Fixed #8484:useExhaustiveDependenciesnow properly handles member access on stable hookresults.
#8767
0d15370Thanks @mdevils! - Fixed #7982:useExhaustiveDependenciesnow properly handles callback expressions with typeassertions.
#8766
39eb545Thanks @Netail! - Fixed #8761: Reverted wrapping the URL of rule descriptions with<>, causing broken URLs in VSCode.#8767
0d15370Thanks @mdevils! - Fixed #3080:useExhaustiveDependenciesnow properly analyzes captures within referencedfunctions passed to hooks.
#8740
4962ed0Thanks @Netail! - Extra rule source references.biome migrate eslintshould do a bit better detecting rules in your eslint configurations.#8776
395746fThanks @codiini! - Fixed #6003:noUselessUndefinedInitializationno longer reports exported variables initialized toundefined. In Svelte 4, this pattern is used to declare optional component props.#8767
0d15370Thanks @mdevils! - Fixed #4248:useExhaustiveDependenciesnow correctly handles function props passed ascallbacks.
#8819
bc191ffThanks @Netail! - Fixed #6567:noUnknownPropertynow ignores unknown properties in at-rules which support descriptors.#8787
adb652fThanks @tuyuritio! - Fixed #8777: Add support for:active-view-transitionpseudo-class.#8639
6577e32Thanks @ohnoah! - Added the nursery lint rulenoExcessiveLinesPerFile.Biome now reports files that exceed a configurable line limit.
#8753
71b5c6eThanks @Netail! - Added the nursery rulenoExcessiveClassesPerFile. Enforce a maximum number of classes per file.Invalid:
#8754
d6b2bdaThanks @Netail! - Added the nursery rulenoFloatingClasses. Disallownewoperators outside of assignments or comparisons.Invalid:
v2.3.11Compare Source
Patch Changes
#8583
83be210Thanks @dyc3! - Added the new nursery ruleuseVueValidTemplateRoot.This rule validates only root-level
<template>elements in Vue single-file components. If the<template>has asrcattribute, it must be empty. Otherwise, it must contain content.Invalid examples:
Valid examples:
#8586
df8fe06Thanks @dyc3! - Added a new nursery ruleuseVueConsistentVBindStyle. Enforces consistentv-bindstyle (:propshorthand vsv-bind:proplonghand). Default prefers shorthand; configurable via rule options.#8587
9a8c98dThanks @dyc3! - Added the ruleuseVueVForKey, which enforces that any element usingv-foralso specifies akey.Invalid
Valid
#8586
df8fe06Thanks @dyc3! - Added a new nursery ruleuseVueConsistentVOnStyle. Enforces consistentv-onstyle (@eventshorthand vsv-on:eventlonghand). Default prefers shorthand; configurable via rule options.#8583
83be210Thanks @dyc3! - Added the new nursery ruleuseVueValidVOnce. Enforces that usages of thev-oncedirective in Vue.js SFC are valid.#8498
d80fa41Thanks @tt-a1i! - Fixed #8494. ExtendednoUndeclaredEnvVarsto support bracket notation (process.env["VAR"],import.meta.env["VAR"]), Bun runtime (Bun.env.VAR,Bun.env["VAR"]), and Deno runtime (Deno.env.get("VAR")).#8509
574a909Thanks @ematipico! - Added support for parsing and formatting the Svelte{#await}syntax, whenhtml.experimentalFullSupportEnabledis set totrue.#8316
d64e92dThanks @washbin! - Added the new nursery rulenoMultiAssign. This rule helps to prevent multiple chained assignments.For example, the following code triggers because there are two assignment expressions in the same statement.
#8592
a5f59cdThanks @Netail! - Added the nursery ruleuseUniqueInputFieldNames. Require fields within an input object to be unique.Invalid:
#8524
17a6156Thanks @JacquesLeupin! - Fixed #8488: Relative plugin paths are now resolved from the configuration file directory, including when configurations are merged (e.g.extends: "//").#8655
3260ec9Thanks @JacquesLeupin! - Fixed #8636: Biome's CSS formatter now breaks comma-separated declaration values at top-level commas when wrapping.#8537
cc3e851Thanks @dibashthapa! - Fixed #8491: Resolved false positive errors for safe boolean expressions. There are still pending fixes. Head to #8491 (comment) for more detailsThis new change will check for safe boolean expressions in variable declarations.
For example,
Valid:
Invalid:
#8511
16a9036Thanks @ematipico! - Improved the diagnostics of the rulesuseSortedClassesandnoUnnecessaryConditions. The diagnostics now state that these rules are a work in progress and link to the relevant GitHub issue.#8521
a704be9Thanks @ToBinio! - Added the nursery ruleuseVueConsistentDefinePropsDeclaration, which enforces consistentdefinePropsdeclaration style.Invalid
Valid
#8595
7c85bf0Thanks @dyc3! - Fixed #8584: The HTML formatter will preserve whitespace after some elements and embedded expressions, which more closely aligns with Prettier's behavior.#8598
5e85d43Thanks @Netail! - Added the nursery ruleuseUniqueFieldDefinitionNames. Require all fields of a type to be unique.Invalid:
#8495
b573d14Thanks @taga3s! - Fixed #8405:noMisusedPromisesnow emits warnings/errors when a function returns union types such asT | Promise<T>which is used in conditionals.#8632
0be7d12Thanks @Bertie690! - The documentation & rule sources forlint/complexity/noBannedTypeshave been updated to fix a few oversights.In addition to some general typo fixes:
The rule now recommends
Record<keyof any, never>instead ofRecord<string, never>(the latter of which incorrectly allows symbol-keyed properties).The rule mentions an alternate method to enforce object emptiness involving
unique symbol-based guards used bytype-festand many other packages:The rule's listed sources have been updated as well to reflect the original source rule (
ban-types) having been split into 3 separate rules circa April 2024.#8580
a3a1ad2Thanks @taga3s! - Added the nursery rulenoBeforeInteractiveScriptOutsideDocumentto the Next.js domain.This rule prevents usage of
next/script'sbeforeInteractivestrategy outside ofpages/_document.js.#8493
5fc24f4Thanks @ematipico! - Added support for parsing and formatting the Svelte{#each}syntax, whenhtml.experimentalFullSupportEnabledis set totrue.#8546
0196c0eThanks @Zaczero! - Hardened union static-member type flattening in edge cases (e.g. unions containingunknownor inferred expression types). This keeps inference conservative and avoids unstable type growth innode = node.parent-style loops.#8569
1022c76Thanks @ematipico! - Fixed an issue where the Biome HTML parser would emit a parse error when certain keywords are inside the text of HTML tags.#8606
f50723bThanks @dyc3! - Fixed #8563: fixed a bounds check on bogus regex literals that caused panics when doing type inference#7410
ab9af9aThanks @sgarcialaguna! - Added the new nursery rulenoJsxPropsBind. This rule disallows .bind(), arrow functions, or function expressions in JSX props.Invalid:
#8523
5f22f1cThanks @ematipico! - Improved the diagnostics of nursery rules. Added a message to diagnostics emitted by nursery rules, so that users are aware of nature of nursery rules.#8571
03666fdThanks @dyc3! - Improved the performance ofnoRedeclareby eliminating string allocations#8591
9dd9ca7Thanks @Netail! - Added the nursery ruleuseUniqueArgumentNames. Enforce unique arguments for GraphQL fields & directives.Invalid:
#8521
a704be9Thanks @ToBinio! - Update useVueDefineMacrosOrder to only run on <script setup> blocks.#8344
7b982baThanks @ematipico! - Reduced the system calls when running the CLI. The performances might be noticeable in big projects that have multiple libraries and enable project rules.#8588
958e24bThanks @Netail! - Added the nursery ruleuseUniqueVariableNames. Enforce unique variable names for GraphQL operations.Invalid:
#8529
8794883Thanks @mdevils! - Fixed #8499:useExhaustiveDependenciesproperly handles aliased destructured object keys when usingstableResultconfiguration.#8557
4df2f4dThanks @dyc3! - Fixed an issue with the HTML formatter where it wouldn't add a space before the/>in self closing elements. This brings the HTML formatter more in line with Prettier.#8509
574a909Thanks @ematipico! - Added support for parsing and formatting the Svelte{#snippet}syntax, whenhtml.experimentalFullSupportEnabledis set totrue.#8248
1231a5cThanks @emilyinure! - Added new nursery rulenoReturnAssign, which disallows assignments inside return statements.Invalid:
#8531
6b09620Thanks @taga3s! - Fixed #8472: The CSS parser can now accept multiple comma separated parameters in:active-view-transition-type.#8615
b9da66dThanks @taga3s! - Removenext/scriptcomponent name check fromnoBeforeInteractiveScriptOutsideDocumentsince it is a default export.#8536
efbfbe2Thanks @dyc3! - Fixed #8527: Improved type inference where analyzing code with repeated object property access and assignments (e.g.node = node.parent, a pattern common when traversing trees in a while loop) could hit an internal type limit. Biome now handles these cases without exceeding the type limit.#8583
83be210Thanks @dyc3! - Added the new nursery ruleuseVueValidVCloak. Enforces that usages of thev-cloakdirective in Vue.js SFC are valid.#8583
83be210Thanks @dyc3! - Added the new nursery ruleuseVueValidVPre. Enforces that usages of thev-predirective in Vue.js SFC are valid.#8644
a3a27a7Thanks @JacquesLeupin! - Added the nursery ruleuseVueVaporto enforce<script setup vapor>in Vue SFCs. For example<script setup>is invalid.#8508
b86842cThanks @tt-a1i! - Fixed #6783: now, when a path is provided via--stdin-file-path, Biome checks whether the file exists on disk. If the path doesn't exist (virtual path), ignore checks (files.includesand VCS ignore rules) are skipped.v2.3.10Compare Source
Patch Changes
#8417
c3a2557Thanks @taga3s! - Fixed #7809:noRedeclareno longer reports redeclarations forinfertype in conditional types.#8477
90e8684Thanks @dyc3! - Fixed #8475: fixed a regression in hownoExtraNonNullAssertionflags extra non-null assertions#8479
250b519Thanks @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
2af85c1Thanks @mdevils! - Improved handling ofdefineProps()macro in Vue components. ThenoVueReservedKeysrule now avoids false positives in non-setup scripts.#8420
42033b0Thanks @vsn4ik! - Fixed the nursery rulenoLeakedRender.The
biome migrate eslintcommand now correctly detects the rulereact/jsx-no-leaked-renderin your eslint configurations.#8426
285d932Thanks @anthonyshew! - Added a Turborepo domain and a new "noUndeclaredEnvVars" rule in it for warning users of unsafe environment variable usage in Turborepos.#8410
a21db74Thanks @ematipico! - Fixed #2988 where Biome couldn't handle properly characters that contain multiple code points when running instdinmode.#8372
b352ee4Thanks @Netail! - Added the nursery rulenoAmbiguousAnchorText, which disallows ambiguous anchor descriptions.Invalid
v2.3.9Compare Source
Patch Changes
84c9e08](https://redirect.githubConfiguration
📅 Schedule: Branch creation - "before 9am on Monday" in timezone UTC, Automerge - At any time (no schedule defined).
🚦 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.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.