Releases · biomejs/biome

@renovate

2.2.7

Patch Changes

#7715 b622425 Thanks @Netail! - Added the nursery rule noEmptySource, disallowing meaningless js, css, json & graphql files to prevent codebase clutter.
#7714 c7e5a14 Thanks @MeGaNeKoS! - Increased the maximum line limit for noExcessiveLinesPerFunction from 255 to 65,535 to better support large JSX/front-end components.
#5868 2db73ae Thanks @bushuai! - Fixed #5856, noRedundantUseStrict now keeps leading trivia
#7756 d665c97 Thanks @ematipico! - Improved the diagnostic message of the rule noDuplicateTestHooks.

What's Changed

fix(deps): update dependency happy-dom to v20 [security] by @renovate[bot] in #7729
chore(deps): update docker/dockerfile:1 docker digest to b6afd42 by @renovate[bot] in #7735
perf: use the PathsMut API to watch/unwatch folders by @siketyan in #7750
feat(lint): implement noEmptySource by @Netail in #7715
docs: slight useEmptySource improvement by @Netail in #7757
fix(noRedundantUseStrict): keeps leading trivia by @bushuai in #5868
chore: add some Web Platform Tests testcases by @drwpow in #7135
chore: accept snapshots that were failing CI by @dyc3 in #7767
fix: detect inifinite loops caused by conflicting rule fixes by @dyc3 in #7732
chore(deps): update dependency happy-dom to v20.0.2 [security] by @renovate[bot] in #7768
fix(noDuplicateTestHooks): diagnostic message by @ematipico in #7756
fix(no_excessive_lines_per_function): expand max_lines Range in NoExcessiveLinesPerFunctionOptions by @MeGaNeKoS in #7714
ci: add CI workflow for trusted publishers for crates by @ematipico in #7769
chore: improve rule templates by @Netail in #7781
fix(workspace): unload plugin cache when project closes by @dyc3 in #7790
chore(deps): update rust crate cfg-if to 1.0.4 by @renovate[bot] in #7793
chore(deps): update rust crate globset to 0.4.17 by @renovate[bot] in #7794
ci: use classic tokens for crate publishing by @ematipico in #7801
chore(deps): update github-actions by @renovate[bot] in #7791
chore(deps): update dependency vite to v7.1.11 [security] by @renovate[bot] in #7807
Revert "fix(lint/useExhaustiveDependencies): correct fix for method calls" by @siketyan in #7810
chore(deps): update pnpm to v10.19.0 by @renovate[bot] in #7739
chore(deps): update dependency @types/node to v22.18.12 by @renovate[bot] in #7792
ci: release by @github-actions[bot] in #7755
chore: fix formatting and code of script by @ematipico in #7821
test: ignore tests on macos by @ematipico in #7820

New Contributors

@MeGaNeKoS made their first contribution in #7714

Full Changelog: https://github.com/biomejs/biome/compare/@biomejs/biome@2.2.6...@biomejs/biome@2.2.7

@daivinhtran

2.2.6

Patch Changes

#7071 a8e7301 Thanks @ptkagori! - Added the useQwikMethodUsage lint rule for the Qwik domain.

This rule validates Qwik hook usage. Identifiers matching useXxx must be called only within serialisable reactive contexts (for example, inside component$, route loaders/actions, or within other Qwik hooks), preventing common Qwik antipatterns.

Invalid:

// Top-level hook call is invalid.
const state = useStore({ count: 0 });

function helper() {
  // Calling a hook in a non-reactive function is invalid.
  const loc = useLocation();
}

Valid:

component$(() => {
  const state = useStore({ count: 0 }); // OK inside component$.
  return <div>{state.count}</div>;
});

const handler = $(() => {
  const loc = useLocation(); // OK inside a $-wrapped closure.
  console.log(loc.params);
});

#7685 52071f5 Thanks @denbezrukov! - Fixed #6981: The NoUnknownPseudoClass rule no longer reports local pseudo-classes when CSS Modules are used.
#7640 899f7b2 Thanks @arendjr! - Fixed #7638: useImportExtensions no longer emits diagnostics on valid import paths that end with a query or hash.

Example
```
// This no longer warns if `index.css` exists:
import style from "../theme/index.css?inline";
```

#7071 a8e7301 Thanks @ptkagori! - Added the useQwikValidLexicalScope rule to the Qwik domain.

This rule helps you avoid common bugs in Qwik components by checking that your variables and functions are declared in the correct place.

Invalid:

// Invalid: state defined outside the component's lexical scope.
let state = useStore({ count: 0 });
const Component = component$(() => {
  return (
    <button onClick$={() => state.count++}>Invalid: {state.count}</button>
  );
});

Valid:

// Valid: state initialised within the component's lexical scope and captured by the event.
const Component = component$(() => {
  const state = useStore({ count: 0 });
  return <button onClick$={() => state.count++}>Valid: {state.count}</button>;
});

#7620 5beb1ee Thanks @Netail! - Added the rule useDeprecatedDate, which makes a deprecation date required for the graphql @deprecated directive.

Invalid

query {
  member @deprecated(reason: "Use `members` instead") {
    id
  }
}

Valid

query {
  member
    @deprecated(reason: "Use `members` instead", deletionDate: "2099-12-25") {
    id
  }
}

#7709 d6da4d5 Thanks @siketyan! - Fixed #7704: The useExhaustiveDependencies rule now correctly adds an object dependency when its method is called within the closure.

For example:
```
function Component(props) {
  useEffect(() => {
    props.foo();
  }, []);
}
```
will now be fixed to:
```
function Component(props) {
  useEffect(() => {
    props.foo();
  }, [props]);
}
```
#7624 309ae41 Thanks @lucasweng! - Fixed #7595: noUselessEscapeInString no longer reports $\{ escape in template literals.
#7665 29e4229 Thanks @ryan-m-walker! - Fixed #7619: Added support for parsing the CSS :state() pseudo-class.
```
custom-selector:state(checked) {
}
```
#7608 41df59b Thanks @ritoban23! - Fixed #7604: the useMaxParams rule now highlights parameter lists instead of entire function bodies. This provides more precise error highlighting. Previously, the entire function was highlighted; now only the parameter list is highlighted, such as (a, b, c, d, e, f, g, h).
#7643 459a6ac Thanks @daivinhtran! - Fixed #7580: Include plugin in summary report

What's Changed

chore: add .zed to gitignore by @daivinhtran in #7634
fix(lint/noUselessEscapeInString): avoid false positive for ${ escape in template literals by @lucasweng in #7624
fix(lint): only highlight function names in useMaxParams rule by @ritoban23 in #7608
docs: add Polish translation of Biome README by @SzymCode in #7630
fix(linter): useImportExtensions handles queries and hashes by @arendjr in #7640
ci: breakdown benchmarks by @ematipico in #7641
chore: upgrade to rust 1.90.0 by @ematipico in #7642
fix(css_parser): add support for parsing :state() (#7619) by @ryan-m-walker in #7665
fix(cli): include plugin rule in summary report by @daivinhtran in #7643
feat(qwik): add useQwikMethodUsage & useQwikValidLexicalScope by @ptkagori in #7071
fix: replace domains polyfill.io to Cloudflare by @You-saku in #7678
feat(biome_graphql_analyze): implement useDeprecatedDate by @Netail in #7620
chore(deps): update dependency @types/node to v22.18.8 by @renovate[bot] in #7686
chore(deps): update github-actions by @renovate[bot] in #7687
chore(deps): update rust crate regex to 1.11.3 by @renovate[bot] in #7689
chore(deps): update rust crate quote to 1.0.41 by @renovate[bot] in #7688
chore(deps): update dependency eslint to v9.37.0 by @renovate[bot] in #7691
chore(deps): update rust crate serde to 1.0.228 by @renovate[bot] in #7690
fix(css_analyze): handle CSS Modules pseudo-class 'local' in NoUnknownPseudoClass rule (#6981) by @denbezrukov in #7685
chore(deps): update pnpm to v10.18.0 by @renovate[bot] in #7693
chore(deps): update taiki-e/install-action action to v2.62.21 by @renovate[bot] in #7692
chore(deps): update rust crate camino to 1.2.1 by @renovate[bot] in #7694
fix(deps): update rust crates by @renovate[bot] in #7562
fix(lint/useExhaustiveDependencies): correct fix for method calls by @siketyan in #7709
chore(deps): update dependency @types/node to v22.18.10 by @renovate[bot] in #7738
chore(deps): update rust crate libc to 0.2.177 by @renovate[bot] in #7740
chore(deps): update rust crate ureq to 3.1.2 - autoclosed by @renovate[bot] in #7741
ci: release by @github-actions[bot] in #7637
chore(deps): update github-actions by @renovate[bot] in #7736

New Contributors

@ritoban23 made their first contribution in #7608
@SzymCode made their first contribution in #7630
@You-saku made their first contribution in #7678

Full Changelog: https://github.com/biomejs/biome/compare/@biomejs/biome@2.2.5...@biomejs/biome@2.2.6

2.2.5

Patch Changes

#7597 5c3d542 Thanks @arendjr! - Fixed #6432: useImportExtensions now works correctly with aliased paths.
#7269 f18dac1 Thanks @CDGardner! - Fixed #6648, where Biome's noUselessFragments contained inconsistencies with ESLint for fragments only containing text.

Previously, Biome would report that fragments with only text were unnecessary under the noUselessFragments rule. Further analysis of ESLint's behavior towards these cases revealed that text-only fragments (<>A</a>, <React.Fragment>B</React.Fragment>, <RenamedFragment>B</RenamedFragment>) would not have noUselessFragments emitted for them.

On the Biome side, instances such as these would emit noUselessFragments, and applying the suggested fix would turn the text content into a proper JS string.
```
// Ended up as: - const t = "Text"
const t = <>Text</>

// Ended up as: - const e = t ? "Option A" : "Option B"
const e = t ? <>Option A</> : <>Option B</>

/* Ended up as:
  function someFunc() {
    return "Content desired to be a multi-line block of text."
  }
*/
function someFunc() {
  return <>
    Content desired to be a multi-line
    block of text.
  <>
}
```
The proposed update was to align Biome's reaction to this rule with ESLint's; the aforementioned examples will now be supported from Biome's perspective, thus valid use of fragments.
```
// These instances are now valid and won't be called out by noUselessFragments.

const t = <>Text</>
const e = t ? <>Option A</> : <>Option B</>

function someFunc() {
  return <>
    Content desired to be a multi-line
    block of text.
  <>
}
```
#7498 002cded Thanks @siketyan! - Fixed #6893: The useExhaustiveDependencies rule now correctly adds a dependency that is captured in a shorthand object member. For example:
```
useEffect(() => {
  console.log({ firstId, secondId });
}, []);
```
is now correctly fixed to:
```
useEffect(() => {
  console.log({ firstId, secondId });
}, [firstId, secondId]);
```
#7509 1b61631 Thanks @siketyan! - Added a new lint rule noReactForwardRef, which detects usages of forwardRef that is no longer needed and deprecated in React 19.

For example:
```
export const Component = forwardRef(function Component(props, ref) {
  return <div ref={ref} />;
});
```
will be fixed to:
```
export const Component = function Component({ ref, ...props }) {
  return <div ref={ref} />;
};
```
Note that the rule provides an unsafe fix, which may break the code. Don't forget to review the code after applying the fix.

#7520 3f06e19 Thanks @arendjr! - Added new nursery rule noDeprecatedImports to flag imports of deprecated symbols.

Invalid example

// foo.js
import { oldUtility } from "./utils.js";

// utils.js
/**
 * @deprecated
 */
export function oldUtility() {}

Valid examples

// foo.js
import { newUtility, oldUtility } from "./utils.js";

// utils.js
export function newUtility() {}

// @deprecated (this is not a JSDoc comment)
export function oldUtility() {}

#7457 9637f93 Thanks @kedevked! - Added style and requireForObjectLiteral options to the lint rule useConsistentArrowReturn.

This rule enforces a consistent return style for arrow functions. It can be configured with the following options:
- style: (default: asNeeded)
  - always: enforces that arrow functions always have a block body.
  - never: enforces that arrow functions never have a block body, when possible.
  - asNeeded: enforces that arrow functions have a block body only when necessary (e.g. for object literals).
style: "always"

Invalid:
```
const f = () => 1;
```
Valid:
```
const f = () => {
  return 1;
};
```
style: "never"

Invalid:
```
const f = () => {
  return 1;
};
```
Valid:
```
const f = () => 1;
```
style: "asNeeded"

Invalid:
```
const f = () => {
  return 1;
};
```
Valid:
```
const f = () => 1;
```
style: "asNeeded" and requireForObjectLiteral: true

Valid:
```
const f = () => {
  return { a: 1 };
};
```

#7510 527cec2 Thanks @rriski! - Implements #7339. GritQL patterns can now use native Biome AST nodes using their PascalCase names, in addition to the existing TreeSitter-compatible snake_case names.

engine biome(1.0)
language js(typescript,jsx)

or {
  // TreeSitter-compatible pattern
  if_statement(),

  // Native Biome AST node pattern
  JsIfStatement()
} as $stmt where {
  register_diagnostic(
    span=$stmt,
    message="Found an if statement"
  )
}

#7574 47907e7 Thanks @kedevked! - Fixed 7574. The diagnostic message for the rule useSolidForComponent now correctly emphasizes <For /> and provides a working hyperlink to the Solid documentation.
#7497 bd70f40 Thanks @siketyan! - Fixed #7320: The useConsistentCurlyBraces rule now correctly detects a string literal including " inside a JSX attribute value.
#7522 1af9931 Thanks @Netail! - Added extra references to external rules to improve migration for the following rules: noUselessFragments & noNestedComponentDefinitions
#7597 5c3d542 Thanks @arendjr! - Fixed an issue where package.json manifests would not be correctly discovered
when evaluating files in the same directory.
#7565 38d2098 Thanks @siketyan! - The resolver can now correctly resolve .ts, .tsx, .d.ts, .js files by .js extension if exists, based on the file extension substitution in TypeScript.

For example, the linter can now detect the floating promise in the following situation, if you have enabled the noFloatingPromises rule.

foo.ts
```
export async function doSomething(): Promise<void> {}
```
bar.ts
```
import { doSomething } from "./foo.js"; // doesn't exist actually, but it is resolved to `foo.ts`

doSomething(); // floating promise!
```

#7542 cadad2c Thanks @mdevils! - Added the rule noVueDuplicateKeys, which prevents duplicate keys in Vue component definitions.

This rule prevents the use of duplicate keys across different Vue component options such as props, data, computed, methods, and setup. Even if keys don't conflict in the script tag, they may cause issues in the template since Vue allows direct access to these keys.

Invalid examples

<script>
export default {
  props: ["foo"],
  data() {
    return {
      foo: "bar",
    };
  },
};
</script>

<script>
export default {
  data() {
    return {
      message: "hello",
    };
  },
  methods: {
    message() {
      console.log("duplicate key");
    },
  },
};
</script>

<script>
export default {
  computed: {
    count() {
      return this.value * 2;
    },
...

2.2.4

Patch Changes

#7453
aa8cea3 Thanks @arendjr! - Fixed #7242: Aliases specified in
package.json's imports section now support having multiple targets as part of an array.
#7454
ac17183 Thanks @arendjr! - Greatly improved performance of
noImportCycles by eliminating allocations.

In one repository, the total runtime of Biome with only noImportCycles enabled went from ~23s down to ~4s.
#7447
7139aad Thanks @rriski! - Fixes #7446. The GritQL
$... spread metavariable now correctly matches members in object literals, aligning its behavior with arrays and function calls.

#6710
98cf9af Thanks @arendjr! - Fixed #4723: Type inference now recognises
index signatures and their accesses when they are being indexed as a string.

Example

type BagOfPromises = {
  // This is an index signature definition. It declares that instances of type
  // `BagOfPromises` can be indexed using arbitrary strings.
  [property: string]: Promise<void>;
};

let bag: BagOfPromises = {};
// Because `bag.iAmAPromise` is equivalent to `bag["iAmAPromise"]`, this is
// considered an access to the string index, and a Promise is expected.
bag.iAmAPromise;

#7415
d042f18 Thanks @qraqras! - Fixed #7212, now the
useOptionalChain rule recognizes optional chaining using
typeof (e.g., typeof foo !== 'undefined' && foo.bar).
#7419
576baf4 Thanks @Conaclos! - Fixed #7323.
noUnusedPrivateClassMembers no longer reports as unused TypeScript
private members if the rule encounters a computed access on this.

In the following example, member as previously reported as unused. It is no longer reported.
```
class TsBioo {
  private member: number;

  set_with_name(name: string, value: number) {
    this[name] = value;
  }
}
```

351bccd Thanks @ematipico! - Added the new nursery lint rule
noJsxLiterals, which disallows the use of string literals inside JSX.

The rule catches these cases:

<>
  <div>test</div> {/* test is invalid */}
  <>test</>
  <div>
    {/* this string is invalid */}
    asdjfl test foo
  </div>
</>

#7406
b906112 Thanks @mdevils! - Fixed an issue (#6393) where the useHookAtTopLevel rule reported excessive diagnostics for nested hook calls.

The rule now reports only the offending top-level call site, not sub-hooks of composite hooks.
```
// Before: reported twice (useFoo and useBar).
function useFoo() {
  return useBar();
}
function Component() {
  if (cond) useFoo();
}
// After: reported once at the call to useFoo().
```
#7461
ea585a9 Thanks @arendjr! - Improved performance of
noPrivateImports by eliminating allocations.

In one repository, the total runtime of Biome with only noPrivateImports enabled went from ~3.2s down to ~1.4s.
351bccd Thanks @ematipico! - Fixed #7411. The Biome Language Server had a regression where opening an editor with a file already open wouldn't load the project settings correctly.
#7142
53ff5ae Thanks @Netail! - Added the new nursery rule
noDuplicateDependencies, which verifies that no dependencies are duplicated between the
bundledDependencies, bundleDependencies, dependencies, devDependencies, overrides,
optionalDependencies, and peerDependencies sections.

For example, the following snippets will trigger the rule:
```
{
  "dependencies": {
    "foo": ""
  },
  "devDependencies": {
    "foo": ""
  }
}
```
```
{
  "dependencies": {
    "foo": ""
  },
  "optionalDependencies": {
    "foo": ""
  }
}
```
```
{
  "dependencies": {
    "foo": ""
  },
  "peerDependencies": {
    "foo": ""
  }
}
```
351bccd Thanks @ematipico! - Fixed #3824. Now the option CLI
--color is correctly applied to logging too.

2.2.3

Patch Changes

#7353 4d2b719 Thanks @JeetuSuthar! - Fixed #7340: The linter now allows the navigation property for view-transition in CSS.

Previously, the linter incorrectly flagged navigation: auto as an unknown property. This fix adds navigation to the list of known CSS properties, following the CSS View Transitions spec.
#7275 560de1b Thanks @arendjr! - Fixed #7268: Files that are explicitly passed as CLI arguments are now correctly ignored if they reside in an ignored folder.
#7358 963a246 Thanks @ematipico! - Fixed #7085, now the rule noDescendingSpecificity correctly calculates the specificity of selectors when they are included inside a media query.
#7387 923674d Thanks @qraqras! - Fixed #7381, now the useOptionalChain rule recognizes optional chaining using Yoda expressions (e.g., undefined !== foo && foo.bar).
#7316 f9636d5 Thanks @Conaclos! - Fixed #7289. The rule useImportType now inlines import type into import { type } when the style option is set to inlineType.

Example:
```
import type { T } from "mod";
// becomes
import { type T } from "mod";
```
#7350 bb4d407 Thanks @siketyan! - Fixed #7261: two characters ・ (KATAKANA MIDDLE DOT, U+30FB) and ･ (HALFWIDTH KATAKANA MIDDLE DOT, U+FF65) are no longer considered as valid characters in identifiers. Property keys containing these character(s) are now preserved as string literals.
#7377 811f47b Thanks @ematipico! - Fixed a bug where the Biome Language Server didn't correctly compute the diagnostics of a monorepo setting, caused by an incorrect handling of the project status.
#7245 fad34b9 Thanks @kedevked! - Added the new lint rule useConsistentArrowReturn.

This rule enforces a consistent return style for arrow functions.

Invalid
```
const f = () => {
  return 1;
};
```
This rule is a port of ESLint's arrow-body-style rule.

#7370 e8032dd Thanks @fireairforce! - Support dynamic import defer and import source. The syntax looks like:

import.source("foo");
import.source("x", { with: { attr: "val" } });
import.defer("foo");
import.defer("x", { with: { attr: "val" } });

#7369 b1f8cbd Thanks @siketyan! - Range suppressions are now supported for Grit plugins.

For JavaScript, you can suppress a plugin as follows:

// biome-ignore-start lint/plugin/preferObjectSpread: reason
Object.assign({ foo: "bar" }, baz);
// biome-ignore-end lint/plugin/preferObjectSpread: reason

For CSS, you can suppress a plugin as follows:

body {
  /* biome-ignore-start lint/plugin/useLowercaseColors: reason */
  color: #fff;
  /* biome-ignore-end lint/plugin/useLowercaseColors: reason */
}

#7384 099507e Thanks @ematipico! - Reduced the severity of certain diagnostics emitted when Biome deserializes the configuration files.
Now these diagnostics are emitted as Information severity, which means that they won't interfere when running commands with --error-on-warnings
#7302 2af2380 Thanks @unvalley! - Fixed #7301: useReadonlyClassProperties now correctly skips JavaScript files.
#7288 94d85f8 Thanks @ThiefMaster! - Fixed #7286. Files are now formatted with JSX behavior when javascript.parser.jsxEverywhere is explicitly set.

Previously, this flag was only used for parsing, but not for formatting, which resulted in incorrect formatting of conditional expressions when JSX syntax is used in .js files.
#7311 62154b9 Thanks @qraqras! - Added the new nursery rule noUselessCatchBinding. This rule disallows unnecessary catch bindings.
```
try {
    // Do something
- } catch (unused) {}
+ } catch {}
```

#7349 45c1dfe Thanks @ematipico! - Fixed #4298. Biome now correctly formats CSS declarations when it contains one single value:

.bar {
-  --123456789012345678901234567890: var(--1234567890123456789012345678901234567);
+  --123456789012345678901234567890: var(
+    --1234567890123456789012345678901234567
+  );
}

#7295 7638e84 Thanks @ematipico! - Fixed #7130. Removed the emission of a false-positive diagnostic. Biome no longer emits the following diagnostic:

lib/main.ts:1:5 suppressions/unused ━━━━━━━━━━━━━━━━━━━━━━━━━

  ⚠ Suppression comment has no effect because the tool is not enabled.

  > 1 │ /** biome-ignore-all assist/source/organizeImports: For the lib root file, we don't want to organize exports */
      │     ^^^^^^^^^^^^^^^^

#7377 811f47b Thanks @ematipico! - Fixed #7371 where the Biome Language Server didn't correctly recompute the diagnostics when updating a nested configuration file.
#7348 ac27fc5 Thanks @ematipico! - Fixed #7079. Now the rule useSemanticElements doesn't trigger components and custom elements.
#7389 ab06a7e Thanks @Conaclos! - Fixed #7344. useNamingConvention no longer reports interfaces defined in global declarations.

Interfaces declared in global declarations augment existing interfaces.
Thus, they must be ignored.

In the following example, useNamingConvention reported HTMLElement.
It is now ignored.
```
export {};
declare global {
  interface HTMLElement {
    foo(): void;
  }
}
```
#7315 4a2bd2f Thanks @vladimir-ivanov! - Fixed #7310: useReadonlyClassProperties correctly handles nested assignments, avoiding false posi...

@arendjr

2.2.2

Patch Changes

#7266 b270bb5 Thanks @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 6436180 Thanks @ematipico! - Fixed an issue where the function scanProject wouldn't work as expected.
#7285 1511d0c Thanks @rriski! - Partially fixed #6782: JSX node kinds are now supported in GritQL AST nodes.
#7249 dff85c0 Thanks @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 b270bb5 Thanks @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 679b70e Thanks @patrickshipe! - Resolved an overcorrection in useImportExtensions when importing explicit index files.

Imports that explicitly reference an index file are now preserved and no longer rewritten to nested index paths.

Example
```
// Before
-      import "./sub/index";
+      import "./sub/index/index.js";

// After
-      import "./sub/index";
+      import "./sub/index.js";
```
#7270 953f9c6 Thanks @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 b7aa111 Thanks @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 0b07f45 Thanks @ematipico! - Fixed #7236. Now Biome correctly migrates JSONC configuration files when they are passed using --config-path.
#7239 1d643d8 Thanks @minht11! - Fixed an issue where Svelte globals ($state and so on) were not properly recognized inside .svelte.test.ts/js and .svelte.spec.ts/js files.
#7264 62fdbc8 Thanks @ematipico! - Fixed a regression where when using --log-kind-pretty wasn't working anymore as expected.
#7244 660031b Thanks @JeetuSuthar! - Fixed #7225: The noExtraBooleanCast rule now preserves parentheses when removing Boolean calls inside negations.
```
// Before
!Boolean(b0 && b1);
// After
!(b0 && b1); // instead of !b0 && b1
```
#7298 46a8e93 Thanks @unvalley! - Fixed #6695: useNamingConvention now correctly reports TypeScript parameter properties with modifiers.

Previously, constructor parameter properties with modifiers like private or readonly were not checked against naming conventions. These properties are now treated consistently with regular class properties.

What's Changed

perf: determine folders more efficiently by @arendjr in #7220
chore: use divan for module graph benchmarks by @arendjr in #7231
chore: add repository dispatch to kick off docker image build on release by @stathis-alexander in #7235
fix: correct error message in useIndexOf rule by @JeetuSuthar in #7234
fix(changelog): correct dead links in 2.2 by @Jayllyz in #7243
chore: fix image sponsor by @ematipico in #7250
docs: fix CHANGELOG to reflect operatorLinebreak by @blfpd in #7253
chore(deps): update github-actions by @renovate[bot] in #7251
chore(deps): update rust:1.89.0-bookworm docker digest to e090f7b by @renovate[bot] in #7252
chore(deps): update rust:1.89.0-bullseye docker digest to 5b0defc - autoclosed by @renovate[bot] in #7254
chore(deps): update dependency @changesets/cli to v2.29.6 by @renovate[bot] in #7255
fix(lsp): unsafe fixes when pulling code actions by @ematipico in #7249
feat(linter): auto add Svelte globals for .svelte.test/spec files by @minht11 in #7239
fix(cli): pretty logger by @ematipico in #7264
fix(core): resolve issue with rest params in type inference by @arendjr in #7270
chore: remove duplicated fixture by @arendjr in #7273
fix(linter): fix useImportExtensions handling of index files by @patrickshipe in #7209
chore: unduplicate branch by @arendjr in #7274
docs(lint): improve noUndeclaredDependencies by @ematipico in #7272
fix(wasm): scanProject being stuck by @ematipico in #7281
fix(semantic): missing references in namespaces by @ematipico in #7282
fix(module_graph): limit flattening to hardcoded value by @ematipico in #7266
fix(migrate): jsonc configuration files by @ematipico in #7283
feat(grit): add JSX node name mappings for GritQL patterns by @rriski in #7285
fix(noExtraBooleanCast): preserve parentheses to maintain operator precedence by @JeetuSuthar in #7244
fix(lint/useNamingConvention): detects ts property parameter with modifier by @unvalley in #7298
ci: release by @github-actions[bot] in #7238
ci: release by @github-actions[bot] in #7303

New Contributors

@stathis-alexander made their first contribution in #7235
@JeetuSuthar made their first contribution in #7234
@blfpd made their first contribution in #7253
@patrickshipe made their first contribution in #7209
@rriski made their first contribution in #7285

Full Changelog: https://github.com/biomejs/biome/compare/@biomejs/biome@2.2.0...@biomejs/biome@2.2.2

@ematipico

3.0.0

Patch Changes

Updated dependencies [527db7f]:
- @biomejs/wasm-bundler@2.2.0
- @biomejs/wasm-nodejs@2.2.0
- @biomejs/wasm-web@2.2.0

What's Changed

feat(cli): enhanced summary reporter by @ematipico in #6731
feat(biome_js_analyze): allow specifying stable object keys in useExhaustiveDependencies configuration by @josh- in #6398
feat(noRestrictedImports): add the patterns option by @sakai-ast in #5506
feat: support configureable sorting mode for imports, keys and attributes by @nazarhussain in #6506
feat(wasm): expose new functions by @ematipico in #6896
ci: sync next branch to the website repo by @siketyan in #7011
feat(wasm): expose Workspace::scan_project_folder by @siketyan in #7005
feat(formatter): add option to split binary expressions before operators by @bavalpey in #6159
feat(qwik): add domain setup and enable some pre-existing rules by @ptkagori in #6923
feat(core): scanner v2 by @arendjr in #6989
chore: tweak CodeRabbit by @arendjr in #7132
perf: minor performance tweaks by @siketyan in #7122
fix: revive wasm build by @siketyan in #7136
feat(lint): add ignoreTypes option to the noImportCycles rule by @siketyan in #7017
fix: set language of noVueDataObjectDeclaration to js by @dyc3 in #7144
docs: remove the mention of a fix by @ematipico in #7146
ci: use github.sha for dispatch event on release by @siketyan in #7145
chore(lint): version released rules by @siketyan in #7147
chore(lint): remove extra v from rule metadata by @siketyan in #7150
docs(changelog): fix wrong useConsistentTypeDefinitions URL by @JamBalaya56562 in #7151
feat(analyze/js): add useMaxParams by @Jayllyz in #7124
feat(analyze/js): add noNextAsyncClientComponent rule in Next domain by @Jayllyz in #7081
refactor(test): make generated snapshot tests have module stucture that matches folder structure by @dyc3 in #7163
fix(core): included files in nested configurations by @ematipico in #7161
feat(parser/html): text expressions in attributes by @ematipico in #6907
feat: promote rules by @ematipico in #7137
fix(linter): false positive for noDuplicateFontNames by @ematipico in #7156
feat(parse/tailwind): handle most basenames with dashes by @dyc3 in #7068
feat(parser/tailwind): support arbitrary candidates by @dyc3 in #7086
refactor: use if-let-chain if possible (applying clippy fixes) by @siketyan in #7169
build: upgrade to Rust 1.89 by @siketyan in #7170
feat(resolver): resolve extension alias by @siketyan in #7158
chore(coderabbit): dont review generated files by @Jayllyz in #7172
fix(yaml_parser): tokens out of order by @vohoanglong0107 in #7168
chore(deps): update github-actions by @renovate[bot] in #7178
chore(deps): update rust crate camino to 1.1.11 by @renovate[bot] in #7180
chore(deps): update rust crate hashbrown to 0.15.5 by @renovate[bot] in #7181
chore(deps): update dependency @types/node to v22.17.1 by @renovate[bot] in #7177
chore(deps): update docker/dockerfile:1 docker digest to 3838752 by @renovate[bot] in #7175
chore(deps): update @biomejs packages by @renovate[bot] in #7176
chore(deps): update rust crate proc-macro2 to 1.0.96 by @renovate[bot] in #7182
chore(deps): update rust crate tower-lsp-server to 0.22.1 by @renovate[bot] in #7183
chore: fix typos messsage → message by @JamBalaya56562 in #7186
chore: fix typos in biome_cli crates by @JamBalaya56562 in #7185
feat(lint): add useBiomeIgnoreFolder and noBiomeFirstException by @ematipico in #7159
chore: fix typos in biome css analyze crates by @JamBalaya56562 in #7187
chore: fix various typos in biome css formatter crates by @JamBalaya56562 in #7190
docs: fix path to perfectionist docs by @azat-io in #7193
docs: fix broken link, update rule count by @9romise in #7194
fix: consider type-only imports as dev dependency by @siketyan in #7171
chore: add Vercel to sponsors by @arendjr in #7200
Revert "feat(resolver): resolve extension alias" by @siketyan in #7199
feat(useConst): don't report uninit variables read befroe to be written by @Conaclos in #7201
feat(core): add support for .graphqls files by @avshalomt2 in #7118
chore: merge next into main by @ematipico in #7167
fix(core): fix semver handling by @arendjr in #7197
chore: fix changesets by @ematipico in #7202
docs: update documentation for useForOf; fix typos by @Bertie690 in #7204
chore: fix typos in biome formatter and grit crates by @JamBalaya56562 in #7207
chore: fix typos in biome html crates by @JamBalaya56562 in #7208
chore: fix typos in biome crates by @JamBalaya56562 in #7215
chore: fix typos in biome js analyze crate by @JamBalaya56562 in #7210
chore: fix typos in biome js formatter crate by @JamBalaya56562 in #7213
chore: fix various typos across codebase by @JamBalaya56562 in #7216
ci: release by @github-actions[bot] in #7157

New Contributors

@josh- made their first contribution in #6398
@sakai-ast made their first contribution in #5506
@nazarhussain made their first contribution in #6506
@bavalpey made their first contribution in #6159
@azat-io made their first contribution in #7193
@9romise made their first contribution in #7194
@avshalomt2 made their first contribution in #7118
@Bertie690 made their first contribution in #7204

Full Changelog: https://github.com/biomejs/biome/compare/@biomejs/biome@2.1.4...@biomejs/js-api@3.0.0

2.2.0

Minor Changes

#5506 1f8755b Thanks @sakai-ast! - The noRestrictedImports rule has been enhanced with a new patterns option. This option allows for more flexible and powerful import restrictions using gitignore-style patterns.

You can now define patterns to restrict entire groups of modules. For example, you can disallow imports from any path under import-foo/ except for import-foo/baz.
```
{
  "options": {
    "patterns": [
      {
        "group": ["import-foo/*", "!import-foo/baz"],
        "message": "import-foo is deprecated, except for modules in import-foo/baz."
      }
    ]
  }
}
```
Invalid examples
```
import foo from "import-foo/foo";
import bar from "import-foo/bar";
```
Valid examples
```
import baz from "import-foo/baz";
```
Additionally, the patterns option introduces importNamePattern to restrict specific import names using regular expressions.
The following example restricts the import names that match x , y or z letters from modules under import-foo/.
```
{
  "options": {
    "patterns": [
      {
        "group": ["import-foo/*"],
        "importNamePattern": "[xyz]"
      }
    ]
  }
}
```
Invalid examples
```
import { x } from "import-foo/foo";
```
Valid examples
```
import { foo } from "import-foo/foo";
```
Furthermore, you can use the invertImportNamePattern boolean option to reverse this logic. When set to true, only the import names that match the importNamePattern will be allowed. The following configuration only allows the import names that match x , y or z letters from modules under import-foo/.
```
{
  "options": {
    "patterns": [
      {
        "group": ["import-foo/*"],
        "importNamePattern": "[xyz]",
        "invertImportNamePattern": true
      }
    ]
  }
}
```
Invalid examples
```
import { foo } from "import-foo/foo";
```
Valid examples
```
import { x } from "import-foo/foo";
```
#6506 90c5d6b Thanks @nazarhussain! - Allow customization of the sort order for different sorting actions. These actions now support a sort option:
- assist/source/useSortedKeys now has a sortOrder option
- assist/source/useSortedAttributes now has a sortOrder option
- assist/source/organizeImports now has an identifierOrder option
For each of these options, the supported values are the same:
1. natural. Compares two strings using a natural ASCII order. Uppercase letters come first (e.g. A < a < B < b) and number are compared in a human way (e.g. 9 < 10). This is the default value.
2. lexicographic. Strings are ordered lexicographically by their byte values. This orders Unicode code points based on their positions in the code charts. This is not necessarily the same as “alphabetical” order, which varies by language and locale.
#7159 df3afdf Thanks @ematipico! - Added the new rule useBiomeIgnoreFolder. Since v2.2, Biome correctly prevents the indexing and crawling of folders.

However, the correct pattern has changed. This rule attempts to detect incorrect usage, and promote the new pattern:
```
// biome.json
{
  "files": {
    "includes": [
-      "!dist/**",
-      "!**/fixtures/**",
+      "!dist",
+      "!**/fixtures",
    ]
  }
}
```
#6989 85b1128 Thanks @arendjr! - Fixed minor inconsistencies in how files.includes was being handled.

Previously, Biome sometimes failed to properly ignore the contents of a folder if you didn't specify the /** at the end of a glob pattern. This was unfortunate, because it meant we still had to traverse the folder and then apply the glob to every entry inside it.

This is no longer an issue and we now recommend to ignore folders without using the /** suffix.
#7118 a78e878 Thanks @avshalomt2! - Added support for .graphqls files. Biome can now format and lint GraphQL files that have the extension .graphqls

#6159 f02a296 Thanks @bavalpey! - Added a new option to Biome's JavaScript formatter, javascript.formatter.operatorLinebreak, to configure whether long lines should be broken before or after binary operators.

For example, the following configuration:

{
  formatter: {
    javascript: {
      operatorLinebreak: "before", // defaults to "after"
    },
  },
}

Will cause this JavaScript file:

const VERY_LONG_CONDITION_1234123412341234123412341234 = false;

if (
  VERY_LONG_CONDITION_1234123412341234123412341234 &&
  VERY_LONG_CONDITION_1234123412341234123412341234 &&
  VERY_LONG_CONDITION_1234123412341234123412341234 &&
  VERY_LONG_CONDITION_1234123412341234123412341234
) {
  console.log("DONE");
}

to be formatted like this:

const VERY_LONG_CONDITION_1234123412341234123412341234 = false;
if (
  VERY_LONG_CONDITION_1234123412341234123412341234 &&
  VERY_LONG_CONDITION_1234123412341234123412341234 &&
  VERY_LONG_CONDITION_1234123412341234123412341234 &&
  VERY_LONG_CONDITION_1234123412341234123412341234
) {
  console.log("DONE");
}

#7137 a653a0f Thanks @ematipico! - Promoted multiple lint rules from nursery to stable groups and renamed several rules for consistency.

Promoted rules

The following rules have been promoted from nursery to stable groups:

CSS
- Promoted noImportantStyles to the complexity group.
- Promoted noUnknownAtRules to the suspicious group.
GraphQL
- Promoted useGraphqlNamedOperations to the correctness group.
- Promoted useGraphqlNamingConvention to the style group.
JavaScript/TypeScript
- Promoted noExcessiveLinesPerFunction to the complexity group.
- Promoted noImplicitCoercions to the complexity group.
- Promoted useIndexOf to the complexity group.
- Promoted noGlobalDirnameFilename to the correctness group.
- Promoted noNestedComponentDefinitions to the correctness group.
- Promoted noProcessGlobal to the correctness group.
- Promoted noReactPropAssignments to the correctness group.
- Promoted noRestrictedElements to the correctness group.
- Promoted noSolidDestructuredProps to the correctness group.
- Promoted useJsonImportAttributes to the correctness group.
- Promoted useParseIntRadix to the correctness group.
- Promoted useSingleJsDocAsterisk to the correctness group.
- Promoted useUniqueElementIds to the correctness group.
- Promoted noAwaitInLoops to the performance group.
- Promoted noUnwantedPolyfillio to the performance group.
- Promoted useGoogleFontPreconnect to the performance group.
- Promoted useSolidForComponent to the performance group.
- Promoted noMagicNumbers to the style group.
- Promoted useConsistentObjectDefinitions to the style group.
- Promoted useExportsLast to the style group.
- Promoted useGroupedAccessorPairs to the style group.
- Promoted [useNumericSeparators](https://biomejs.dev/linter/rule...

@ematipico

2.1.4

Patch Changes

#7121 b9642ab Thanks @arendjr! - Fixed #7111: Imported symbols using aliases are now correctly recognised.
#7103 80515ec Thanks @omasakun! - Fixed #6933 and #6994.

When the values of private member assignment expressions, increment expressions, etc. are used, those private members are no longer marked as unused.
#6887 0cc38f5 Thanks @ptkagori! - Added the noQwikUseVisibleTask rule to Qwik.

This rule is intended for use in Qwik applications to warn about the use of useVisibleTask$() functions which require careful consideration before use.

Invalid:
```
useVisibleTask$(() => {
  console.log("Component is visible");
});
```
Valid:
```
useTask$(() => {
  console.log("Task executed");
});
```
#7084 50ca155 Thanks @ematipico! - Added the new nursery rule noUnnecessararyConditions, which detects whenever some conditions don't
change during the life cycle of the program, and truthy or false, hence deemed redundant.

For example, the following snippets will trigger the rule:
```
// Always truthy literal conditions
if (true) {
  console.log("always runs");
}
```
```
// Unnecessary condition on constrained string type
function foo(arg: "bar" | "baz") {
  if (arg) {
    // This check is unnecessary
  }
}
```
#6887 0cc38f5 Thanks @ptkagori! - Added the useImageSize rule to Biome.

The useImageSize rule enforces the use of width and height attributes on <img> elements for performance reasons. This rule is intended to prevent layout shifts and improve Core Web Vitals by ensuring images have explicit dimensions.

Invalid:
```
<img src="/image.png" />
<img src="https://example.com/image.png" />
<img src="/image.png" width="200" />
<img src="/image.png" height="200" />
```
Valid:
```
<img width="200" height="600" src="/static/images/portrait-01.webp" />
<img width="100" height="100" src="https://example.com/image.png" />
```
#6887 0cc38f5 Thanks @ptkagori! - Added the useAnchorHref rule to Biome.

The useAnchorHref rule enforces the presence of an href attribute on <a> elements in JSX. This rule is intended to ensure that anchor elements are always valid and accessible.

Invalid:
```
<a>Link</a>
```
```
<a target="_blank">External</a>
```
Valid:
```
<a href="/home">Home</a>
```
```
<a href="https://example.com" target="_blank">
  External
</a>
```
#7100 29fcb05 Thanks @Jayllyz! - Added the rule noNonNullAssertedOptionalChain.

This rule prevents the use of non-null assertions (!) immediately after optional chaining expressions (?.). Optional chaining is designed to safely handle nullable values by returning undefined when the chain encounters null or undefined. Using a non-null assertion defeats this purpose and can lead to runtime errors.
```
// Invalid - non-null assertion after optional chaining
obj?.prop!;
obj?.method()!;
obj?.[key]!;
obj?.prop!;

// Valid - proper optional chaining usage
obj?.prop;
obj?.method();
obj?.prop ?? defaultValue;
obj!.prop?.method();
```
#7129 9f4538a Thanks @drwpow! - Removed option, combobox, listbox roles from useSemanticElements suggestions
#7106 236deaa Thanks @arendjr! - Fixed #6985: Inference of return types no longer mistakenly picks up return types of nested functions.
#7102 d3118c6 Thanks @omasakun! - Fixed #7101: noUnusedPrivateClassMembers now handles members declared as part of constructor arguments:
1. If a class member defined in a constructor argument is only used within the constructor, it removes the private modifier and makes it a plain method argument.
2. If it is not used at all, it will prefix it with an underscore, similar to noUnusedFunctionParameter.
#7104 5395297 Thanks @harxki! - Reverting to prevent regressions around ref handling
#7143 1a6933a Thanks @siketyan! - Fixed #6799: The noImportCycles rule now ignores type-only imports if the new ignoreTypes option is enabled (enabled by default).
[!WARNING]
Breaking Change: The noImportCycles rule no longer detects import cycles that include one or more type-only imports by default.
To keep the old behaviour, you can turn off the ignoreTypes option explicitly:
```
{
  "linter": {
    "rules": {
      "nursery": {
        "noImportCycles": {
          "options": {
            "ignoreTypes": false
          }
        }
      }
    }
  }
}
```
#7099 6cc84cb Thanks @arendjr! - Fixed #7062: Biome now correctly considers extended configs when determining the mode for the scanner.
#6887 0cc38f5 Thanks @ptkagori! - Added the useQwikClasslist rule to Biome.

This rule is intended for use in Qwik applications to encourage the use of the built-in class prop (which accepts a string, object, or array) instead of the classnames utility library.

Invalid:
```
<div class={classnames({ active: true, disabled: false })} />
```
Valid:
```
<div classlist={{ active: true, disabled: false }} />
```
#7019 57c15e6 Thanks @fireairforce! - Added support in the JS parser for import source(a stage3 proposal). The syntax looks like:
```
import source foo from "<specifier>";
```
#7053 655049e Thanks @jakeleventhal! - Added the useConsistentTypeDefinitions rule.

This rule enforces consistent usage of either interface or type for object type definitions in TypeScript.

The rule accepts an option to specify the preferred style:
- interface (default): Prefer using interface for object type definitions
- type: Prefer using type for object type definitions
Examples:
```
// With default option (interface)
// ❌ Invalid
type Point = { x: number; y: number };

// ✅ Valid
interface Point {
  x: number;
  y: number;
}

// With option { style: "type" }
// ❌ Invalid
interface Point {
  x: number;
  y: number;
}

// ✅ Valid
type Point = { x: number; y: number };
```
The rule will automatically fix simple cases where conversion is straightforward.

What's Changed

ci: use faster runners on Windows by @ematipico in #7041
chore: use own semver parser by @ematipico in #7061
docs(ana...

@ematipico

2.1.3

Patch Changes

#7057 634a667 Thanks @mdevils! - Added the rule noVueReservedKeys, which prevents the use of reserved Vue keys.

It prevents the use of Vue reserved keys such as those starting with # @biomejs/biome (like $el, $data, $props) and keys starting with _` in data properties, which can cause conflicts and unexpected behavior in Vue components.

Invalid example

<script>
export default {
  data: {
    $el: "",
    _foo: "bar",
  },
};
</script>

<script>
export default {
  computed: {
    $data() {
      return this.someData;
    },
  },
};
</script>

Valid examples

<script>
export default {
  data() {
    return {
      message: "Hello Vue!",
      count: 0,
    };
  },
};
</script>

<script>
export default {
  computed: {
    displayMessage() {
      return this.message;
    },
  },
};
</script>

#6941 734d708 Thanks @JamBalaya56562! - Added @eslint-react/no-nested-component-definitions as a rule source for noNestedComponentDefinitions. Now it will get picked up by biome migrate --eslint.
#6463 0a16d54 Thanks @JamBalaya56562! - Fixed a website link for the useComponentExportOnlyModules linter rule to point to the correct URL.
#6944 e53f2fe Thanks @sterliakov! - Fixed #6910: Biome now ignores type casts and assertions when evaluating numbers for noMagicNumbers rule.
#6991 476cd55 Thanks @denbezrukov! - Fixed #6973: Add support for parsing the :active-view-transition-type() pseudo-class
```
:active-view-transition-type(first second) {
}
```
#6992 0b1e194 Thanks @ematipico! - Added a new JSON rule called noQuickfixBiome, which disallow the use of code action quickfix.biome inside code editor settings.
#6943 249306d Thanks @JamBalaya56562! - Fixed @vitest/eslint-plugin source url.
#6947 4c7ed0f Thanks @JamBalaya56562! - Fixed ESLint migration for the rule prefer-for from eslint-plugin-solid to Biome's useForComponent.
#6976 72ebadc Thanks @siketyan! - Fixed #6692: The rules noUnusedVariables and noUnusedFunctionParameters no longer cause an infinite loop when the suggested name is not applicable (e.g. the suggested name is already declared in the scope).
#6990 333f5d0 Thanks @rvanlaarhoven! - Fixed the documentation URL for lint/correctness/noUnknownPseudoClass
#7000 4021165 Thanks @harxki! - Fixed #6795: noUnassignedVariables now correctly recognizes variables used in JSX ref attributes.
#7044 b091ddf Thanks @ematipico! - Fixed #6622, now the rule useSemanticElements works for JSX self-closing elements too.
#7014 c4864e8 Thanks @siketyan! - Fixed #6516: The biome migrate command no longer break the member list with trailing comments.

#6979 29cb6da Thanks @unvalley! - Fixed #6767: useSortedClasses now correctly removes leading and trailing whitespace in className.

Previously, trailing spaces in className were not fully removed.

// Think we have this code:
<div className="text-sm font-bold            " />

// Before: applied fix, but a trailing space was preserved
<div className="font-bold text-sm " />

// After: applied fix, trailing spaces removed
<div className="font-bold text-sm" />

#7055 ee4828d Thanks @dyc3! - Added the nursery rule useReactFunctionComponents. This rule enforces the preference to use function components instead of class components.

Valid:
```
function Foo() {
  return <div>Hello, world!</div>;
}
```
Invalid:
```
class Foo extends React.Component {
  render() {
    return <div>Hello, world!</div>;
  }
}
```
#6924 2d21be9 Thanks @ematipico! - Fixed #113, where the Biome Language Server didn't correctly update the diagnostics when the configuration file is modified in the editor. Now the diagnostics are correctly updated every time the configuration file is modified and saved.
#6931 e6b2380 Thanks @arendjr! - Fixed #6915: useHookAtTopLevel no longer hangs when rules call themselves recursively.
#7012 01c0ab4 Thanks @siketyan! - Fixed #5837: Invalid suppression comments such as biome-ignore-all-start or biome-ignore-all-end no longer causes a panic.
#6949 48462f8 Thanks @fireairforce! - Support parse import defer(which is a stage3 proposal). The syntax look like this:
```
import defer * as foo from "<specifier>";
```

#6938 5feb5a6 Thanks @vladimir-ivanov! - Fixed #6919 and #6920:
useReadonlyClassProperties now does checks for mutations in async class methods.

Example:

class Counter3 {
  private counter: number;
  async count() {
    this.counter = 1;
    const counterString = `${this.counter++}`;
  }
}

#6942 cfda528 Thanks @sterliakov! - Fixed #6939. Biome now understands this binding in classes outside of methods.

What's Changed

docs: explain how to document options by @ematipico in #6916
chore: fix changelog by @dyc3 in #6917
fix: update useComponentExportOnlyModules website link by @JamBalaya56562 in #6463
fix(lsp): update diagnostics on watched files by @ematipico in #6924
fix(linter): fix recursive hooks by @arendjr in #6931
perf: introduce Path type by @arendjr in #6935
ci: add French, Spanish and Ukrainian to labeler by @JamBalaya56562 in #6926
refactor: add no-nested-component-definitions rule...

Uh oh!

Releases: biomejs/biome

Biome CLI v2.2.7

2.2.7

Patch Changes

What's Changed

New Contributors

Contributors

Uh oh!

Biome CLI v2.2.6

2.2.6

Patch Changes

Example

Invalid

Valid

What's Changed

New Contributors

Contributors

Uh oh!

Biome CLI v2.2.5

2.2.5

Patch Changes

Invalid example

Valid examples

style: "always"

style: "never"

style: "asNeeded"

style: "asNeeded" and requireForObjectLiteral: true

Invalid examples

Contributors

Uh oh!

Biome CLI v2.2.4

2.2.4

Patch Changes

Example

Uh oh!

Biome CLI v2.2.3

2.2.3

Patch Changes

Invalid

Contributors

Uh oh!

Biome CLI v2.2.2

2.2.2

Patch Changes

Example

What's Changed

New Contributors

Contributors

Uh oh!

JavaScript APIs v3.0.0

3.0.0

Patch Changes

What's Changed

New Contributors

Contributors

Uh oh!

Biome CLI v2.2.0

2.2.0

Minor Changes

Promoted rules

CSS

GraphQL

JavaScript/TypeScript

Contributors

Uh oh!

Biome CLI v2.1.4

2.1.4

Patch Changes

What's Changed

Contributors

Uh oh!

Biome CLI v2.1.3

2.1.3

Patch Changes

Invalid example

Valid examples

What's Changed

Contributors

Uh oh!

`style: "always"`

`style: "never"`

`style: "asNeeded"`

`style: "asNeeded"` and `requireForObjectLiteral: true`