Update dependency @biomejs/biome to v2.2.2 - #417
Merged
Conversation
renovate
Bot
force-pushed
the
renovate/dependencies-(patch)
branch
from
September 6, 2025 16:09
130195c to
f2461c2
Compare
renovate
Bot
force-pushed
the
renovate/dependencies-(patch)
branch
from
September 9, 2025 13:47
f2461c2 to
475eee6
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
2.2.0->2.2.2Release Notes
biomejs/biome (@biomejs/biome)
v2.2.2Compare Source
Patch Changes
#7266
b270bb5Thanks @ematipico! - Fixed an issue where Biome got stuck when analyzing some files. This is usually caused by a bug in the inference engine. Now Biome has some guards in place in case the number of types grows too much, and if that happens, a diagnostic is emitted and the inference is halted.#7281
6436180Thanks @ematipico! - Fixed an issue where the functionscanProjectwouldn't work as expected.#7285
1511d0cThanks @rriski! - Partially fixed #6782: JSX node kinds are now supported in GritQL AST nodes.#7249
dff85c0Thanks @ematipico! - Fixed #748, where Biome Language Server didn't show the unsafe fixes when requesting the quick fixes. Now all LSP editors will show also opt-in, unsafe fixes.#7266
b270bb5Thanks @ematipico! - Fixed #7020: Resolved an issue with analysing types of static member expressions involving unions. If the object type was a union that referenced nested unions, it would trigger an infinite loop as it tried to keep expanding nested unions, and the set of types would grow indefinitely.#7209
679b70eThanks @patrickshipe! - Resolved an overcorrection inuseImportExtensionswhen importing explicit index files.Imports that explicitly reference an index file are now preserved and no longer rewritten to nested index paths.
Example
#7270
953f9c6Thanks @arendjr! - Fixed #6172: Resolved an issue with inferring types for rest parameters. This issue caused rest-parameter types to be incorrect, and in some cases caused extreme performance regressions in files that contained many methods with rest-parameter definitions.#7234
b7aa111Thanks @JeetuSuthar! - Fixed #7233: The useIndexOf rule now correctly suggests using indexOf() instead of findIndex().The diagnostic message was incorrectly recommending Array#findIndex() over Array#indexOf(), when it should recommend the opposite for simple equality checks.
#7283
0b07f45Thanks @ematipico! - Fixed #7236. Now Biome correctly migrates JSONC configuration files when they are passed using--config-path.#7239
1d643d8Thanks @minht11! - Fixed an issue where Svelte globals ($state and so on) were not properly recognized inside.svelte.test.ts/jsand.svelte.spec.ts/jsfiles.#7264
62fdbc8Thanks @ematipico! - Fixed a regression where when using--log-kind-prettywasn't working anymore as expected.#7244
660031bThanks @JeetuSuthar! - Fixed #7225: ThenoExtraBooleanCastrule now preserves parentheses when removingBooleancalls inside negations.#7298
46a8e93Thanks @unvalley! - Fixed #6695:useNamingConventionnow correctly reports TypeScript parameter properties with modifiers.Previously, constructor parameter properties with modifiers like
privateorreadonlywere not checked against naming conventions. These properties are now treated consistently with regular class properties.Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.