Version History

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 like $el, $data, $props) and keys starting with \_ in data properties, which can cause conflicts and unexpected behavior in Vue components.

Invalid example

1
<script>
2
export default {
3
  data: {
4
    $el: "",
5
    _foo: "bar",
6
  },
7
};
8
</script>

1
<script>
2
export default {
3
  computed: {
4
    $data() {
5
      return this.someData;
6
    },
7
  },
8
};
9
</script>

Valid examples

1
<script>
2
export default {
3
  data() {
4
    return {
5
      message: "Hello Vue!",
6
      count: 0,
7
    };
8
  },
9
};
10
</script>

1
<script>
2
export default {
3
  computed: {
4
    displayMessage() {
5
      return this.message;
6
    },
7
  },
8
};
9
</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
```
1
:active-view-transition-type(first second) {
2
}
```
#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.

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

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

7
// After: applied fix, trailing spaces removed
8
<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:
```
1
function Foo() {
2
  return <div>Hello, world!</div>;
3
}
```
Invalid:
```
1
class Foo extends React.Component {
2
  render() {
3
    return <div>Hello, world!</div>;
4
  }
5
}
```
#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:
```
1
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:

1
class Counter3 {
2
  private counter: number;
3
  async count() {
4
    this.counter = 1;
5
    const counterString = `${this.counter++}`;
6
  }
7
}

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

2.1.2

Patch Changes

#6865 b35bf64 Thanks @denbezrukov! - Fix #6485: Handle multiple semicolons correctly in blocks (#6485)
```
1
div {
2
  box-sizing: border-box;
3
  color: red;
4
}
```
#6798 3579ffa Thanks @dyc3! - Fixed #6762, Biome now knows that ~/.config/zed/settings.json and ~/.config/Code/User/settings.json allows comments by default.
#6839 4cd62d8 Thanks @ematipico! - Fixed #6838, where the Biome File Watcher incorrectly watched and stored ignored files, causing possible memory leaks when those files were dynamically created (e.g. built files).
#6879 0059cd9 Thanks @denbezrukov! - Refactor: remove one level of indirection for CSS declarations with semicolon Previously, accessing a declaration from a list required an extra step:
```
1
item
2
.as_any_css_declaration_with_semicolon()
3
.as_css_declaration_with_semicolon()
```
Now, it can be done directly with:
```
1
item.as_css_declaration_with_semicolon()
```
#6839 4cd62d8 Thanks @ematipico! - Fixed a bug where the Biome Language Server didn’t correctly ignore specific files when vcs.useIgnoreFile is set to true.
#6884 5ff50f8 Thanks @arendjr! - Improved the performance of noImportCycles by ~30%.
#6903 241dd9e Thanks @arendjr! - Fixed #6829: Fixed a false positive reported by useImportExtensions when importing a .js file that had a matching .d.ts file in the same folder.
#6846 446112e Thanks @darricheng! - Fixed an issue where biome was using the wrong string quotes when the classes string has quotes, resulting in invalid code after applying the fix.
#6823 eebc48e Thanks @arendjr! - Improved #6172: Optimised the way function arguments are stored in Biome’s type inference. This led to about 10% performance improvement in RedisCommander.d.ts and about 2% on @next/font type definitions.
#6878 3402976 Thanks @ematipico! - Fixed a bug where the Biome Language Server would apply an unsafe fix when using the code action quickfix.biome.

Now Biome no longer applies an unsafe code fix when using the code action quickfix.biome.

#6794 4d5fc0e Thanks @vladimir-ivanov! - Fixed #6719: The noInvalidUseBeforeDeclaration rule covers additional use cases.

Examples:

1
type Bar = { [BAR]: true };
2
const BAR = "bar";

1
interface Bar {
2
  child: { grandChild: { [BAR]: typeof BAR; enumFoo: EnumFoo } };
3
}
4
const BAR = "bar";
5
enum EnumFoo {
6
  BAR = "bar",
7
}

#6863 531e97e Thanks @dyc3! - Biome now considers whether the linter is enabled when figuring out how the project should be scanned. Resolves #6815.
#6832 bdbc2b1 Thanks @togami2864! - Fixed #6165: Fixed false negative in noUnusedPrivateClassMembers rule when checking member usage in classes
#6839 4cd62d8 Thanks @ematipico! - Fixed a bug where the root ignore file wasn’t correctly loaded during the scanning phase, causing false positives and incorrect expectations among users.

Now, when using vcs.useIgnoreFile, the **the globs specified in the ignore file from the project root ** will have the same semantics as the files.includes setting of the root configuration.

Refer to the relative web page to understand how they work.
#6898 5beb024 Thanks @arendjr! - Fixed #6891: Improved type inference for array indices.

Example:
```
1
const numbers: number[];
2
numbers[42]; // This now infers to `number | undefined`.
```

#6809 8192451 Thanks @arendjr! - Fixed #6796: Fixed a false positive that happened in noFloatingPromises when calling functions that were declared as part of for ... of syntax inside async functions.

Instead, the variables declared inside for ... of loops are now correctly inferred if the expression being iterated evaluates to an Array (support for other iterables will follow later).

Invalid example

1
const txStatements: Array<(tx) => Promise<any>> = [];
2

3
db.transaction((tx: any) => {
4
  for (const stmt of txStatements) {
5
    // We correctly flag this resolves to a `Promise`:
6
    stmt(tx);
7
  }
8
});

Valid example

1
async function valid(db) {
2
  const txStatements: Array<(tx: any) => void> = [(tx) => tx.insert().run()];
3

4
  db.transaction((tx: any) => {
5
    for (const stmt of txStatements) {
6
      // We don't flag a false positive here anymore:
7
      stmt(tx);
8
    }
9
  });
10
}

#6757 13a0818 Thanks @mdevils! - Added the rule noVueReservedProps, resolves #6309.

It prevents the use of reserved Vue prop names such as key and ref which can cause conflicts and unexpected behavior in Vue components.

Invalid example

1
import { defineComponent } from "vue";
2

3
export default defineComponent({
4
  props: ["ref", "key", "foo"],
5
});

1
<script setup>
2
defineProps({
3
  ref: String,
4
  key: String,
5
  foo: String,
6
});
7
</script>

Valid examples

1
import { defineComponent } from "vue";
2

3
export default defineComponent({
4
  props: ["foo"],
5
});

1
<script setup>
2
defineProps({ foo: String });
3
</script>

#6840 1a57b51 Thanks @denbezrukov! - Allow multiple identifiers in ::part() pseudo-element selector.
```
1
::part(first second) {
2
}
```
#6845 4fd44ec Thanks @arendjr! - Fixed #6510: The scanner no longer shows diagnostics on inaccessible files unless --verbose is used.
#6844 b7e2d4d Thanks @sterliakov! - Fixed #6837: Fixed regression with multiple consecutive line suppression comments using instances (like // biome-ignore lint/correctness/useExhaustiveDependencies(depName): reason).
#6818 5f3f5a6 Thanks @siketyan! - Fixed an issue where textDocument/codeAction in the LSP could respond with outdated text edits after the workspace watcher observed outdated changes to the file.
#6804 3e6ab16 Thanks @arendjr! - noFloatingPromises will no longer suggest to add await keyword inside synchronous callbacks nested inside async functions.
#6901 c9e969a Thanks @arendjr! - Fixed #6777: Fixed type inference handling of this to avoid infinite recursion.

Thanks to @sterliakov for the thorough investigation!

#6855 d1581c7 Thanks @vladimir-ivanov! - Fixed #6775: useReadonlyClassProperties now also captures mutations inside function arguments.

Example:

1
class Counter {
2
  private counter: number;
3
  count() {
4
    console.log(this.counter++);
5
    const counterString = `${this.counter++}`;
6
  }
7
}

#6839 4cd62d8 Thanks @ematipico! - Fixed a bug where Biome didn’t throw any error when vcs.useIgnoreFile is set to true, and there wasn’t any ignore file read. Now Biome correctly throws an error if no ignore files are found.
#6911 6d68074 Thanks @arendjr! - Fixed #6838: Reduce resource consumption in the Biome Language Server by using non-recursive filesystem watchers instead of recursive ones.

Watchers are responsible for notifying Biome of changes to files in the filesystem. We used to set up a single recursive watcher, but that meant that Biome would receive filesystem notifications for all files in your project, even for ignored folders such as build/ or dist/ folders.

With this patch, we set up non-recursive watchers only for the folders that are relevant to a project.

Related to this, we also solved an issue where incoming notifications were incorrectly filtered, causing ignored files to be processed and stored in our module graph anyway.

2.1.1

Patch Changes

#6781 9bbd34f Thanks @siketyan! - Fixed the FileFeaturesResult interface in the WASM API was defined as a mapped object but the actual value was a Map object.
#6761 cf3c2ce Thanks @dyc3! - Fixed #6759, a false positive for noFocusedTests that was triggered by calling any function with the name fit on any object.

The following code will now pass the noFocusedTests rule:
```
1
import foo from "foo";
2
foo.fit();
```

2.1.0

Minor Changes

#6512 0c0bf82 Thanks @arendjr! - The rule noFloatingPromises can now detect floating arrays of Promises.

Invalid examples

1
// This gets flagged because the Promises are not handled.
2
[1, 2, 3].map(async (x) => x + 1);

Valid examples

1
await Promise.all([1, 2, 3].map(async (x) => x + 1));

#6637 6918085 Thanks @arendjr! - Type inference is now able to handle the sequence operator ( ,), as well as post- and pre-update operators: ++.

Example

1
let x = 5;
2

3
// We now infer that `x++` resolves to a number, while the expression as a whole
4
// becomes a Promise:
5
(x++, new Promise((resolve) => resolve("comma")));

#6752 c9eaca4 Thanks @arendjr! - Fixed #6646: .gitignore files are now picked up even when running Biome from a nested directory, or when the ignore file itself is ignored through files.includes.
#6746 90aeead Thanks @arendjr! - biome migrate no longer enables style rules that were recommended in v1, because that would be undesirable for users upgrading from 2.0.

Users who are upgrading from Biome 1.x are therefore advised to first upgrade to Biome 2.0, and run the migration, before continuing to Biome 2.1 or later.

#6583 d415a3f Thanks @arendjr! - Added the nursery rule noMisusedPromises.

It signals Promises in places where conditionals or iterables are expected.

Invalid examples

1
const promise = Promise.resolve("value");
2

3
// Using a `Promise` as conditional is always truthy:
4
if (promise) {
5
  /* ... */
6
}
7

8
// Spreading a `Promise` has no effect:
9
console.log({ foo: 42, ...promise });
10

11
// This does not `await` the `Promise`s from the callbacks,
12
// so it does not behave as you may expect:
13
[1, 2, 3].forEach(async (value) => {
14
  await fetch(`/${value}`);
15
});

Valid examples

1
const promise = Promise.resolve("value");
2

3
if (await promise) {
4
  /* ... */
5
}
6

7
console.log({ foo: 42, ...(await promise) });

#6405 cd4a9bb Thanks @vladimir-ivanov! - Added the ignoreRestSiblings option to the noUnusedFunctionParameters rule.

This option is used to ignore unused function parameters that are siblings of the rest parameter.

The default is false, which means that unused function parameters that are siblings of the rest parameter will be reported.

Example
```
1
{
2
  "rules": {
3
    "noUnusedFunctionParameters": ["error", { "ignoreRestSiblings": true }]
4
  }
5
}
```
#6614 0840021 Thanks @arendjr! - We have implemented a more targeted version of the scanner, which ensures that if you provide file paths to handle on the CLI, the scanner will exclude directories that are not relevant to those paths.

Note that for many commands, such as biome check and biome format, the file paths to handle are implicitly set to the current working directory if you do not provide any path explicitly. The targeted scanner also works with such implicit paths, which means that if you run Biome from a subfolder, other folders that are part of the project are automatically exempted.

Use cases where you invoke Biome from the root of the project without providing a path, as well as those where project rules are enabled, are not expected to see performance benefits from this.

Implemented #6234, and fixed #6483 and #6563.
#6488 c5ee385 Thanks @ianzone! - nx.json and project.json have been added to the list of well-known files.
#6720 52e36ae Thanks @minht11! - Added $ symbol to organizeImports :ALIAS: group.

import { action } from '$lib' will be treated as alias import.

Patch Changes

#6712 2649ac6 Thanks @sterliakov! - Fixed #6595: Biome now supports // biome-ignore-all file-level suppressions in files that start with a shebang (#!).
#6758 28dc49e Thanks @arendjr! - Fixed #6573: Grit plugins can now match bare imports.

Example

The following snippet:
```
1
`import $source`
```
will now match:
```
1
import "main.css";
```

#6550 b424f46 Thanks @arendjr! - Type inference is now able to handle logical expressions: &&, ||, and ??.

Examples

1
// We can now infer that because `true` is truthy, the entire expression
2
// evaluates to a `Promise`.
3
true && Promise.reject("logical operator bypass");
4

5
// And we know that this doesn't:
6
false && Promise.reject("logical operator bypass");
7

8
// Truthiness, falsiness, and non-nullishness can all be determined on more
9
// complex expressions as well. So the following also works:
10
type Nullish = null | undefined;
11

12
type Params = {
13
  booleanOption: boolean | Nullish;
14
  falsyOption: false | Nullish;
15
};
16

17
function foo({ booleanOption, falsyOption }: Params) {
18
  // This may be a Promise:
19
  booleanOption ?? Promise.reject("logical operator bypass");
20

21
  // But this never is:
22
  falsyOption && Promise.reject("logical operator bypass");
23
}

#6413 4aa0e50 Thanks @wojtekmaj! - Improved error message in useDateNow rule.
#6673 341e062 Thanks @dyc3! - Fixed a case where the HTML formatter would mangle embedded language tags if whitespaceSensitivity was set to strict
#6642 a991229 Thanks @unvalley! - Fixed #4494: The noSecrets rule now correctly uses the entropyThreshold option to detect secret like strings.
#6520 0c43545 Thanks @arendjr! - Type inference is now able to handle ternary conditions in type aliases.

Note that we don’t attempt to evaluate the condition itself. The resulting type is simply a union of both conditional outcomes.

Example
```
1
type MaybeResult<T> = T extends Function ? Promise<string> : undefined;
2

3
// We can now detect this function _might_ return a `Promise`:
4
function doStuff<T>(input: T): MaybeResult<T> {
5
  /* ... */
6
}
```
#6711 1937691 Thanks @sterliakov! - Fixed #6654: Fixed range highlighting of <explanation> placeholder in inline suppression block comments.
#6756 d12b26f Thanks @dyc3! - Fixed #6669: Added an exception to noUnusedImports to allow type augmentation imports.
```
1
import type {} from "@mui/lab/themeAugmentation";
```
#6643 df15ad6 Thanks @skewb1k!
Fixed #4994: LSP server registered some capabilities even when the client did not support dynamic registration.
#6599 5e611fa Thanks @vladimir-ivanov! - Fixed #6380: The noFocusedTests rule now correctly displays the function name in the diagnostic message when a test is focused.

Every instance of a focused test function (like fdescribe, fit, ftest and only) had the word ‘only’ hardcoded. This has been updated to use the actual function name, so the message is now more accurate and specific.

Example for fdescribe:
```
1
  i The 'fdescribe' method is often used for debugging or during implementation.
2

3
  i Consider removing 'f' prefix from 'fdescribe' to ensure all tests are executed.
```

#6671 0c9ab43 Thanks @vladimir-ivanov! - Fixed #6634: The useReadonlyClassProperties rule now correctly flags mutations in class getters and in arrow functions within class properties.

Examples:

1
class GetterWithMutationValue {
2
  #value: string;
3

4
  get value() {
5
    if (!this.#value) {
6
      this.#value = "defaultValue";
7
    }
8

9
    return this.#value;
10
  }
11
}

1
class ClassPropertyArrowFunctionWithMutation {
2
  private bar: string | null = null;
3

4
  readonly action = () => {
5
    this.bar = "init";
6
  };
7
}

#6682 ca04cea Thanks @ematipico! - Fixed #6668: Biome Assist is now enabled by default for CSS files.

#6525 66b089c Thanks @arendjr! - Type inference can now infer the return types of functions and methods without annotations.

Examples

1
const sneakyObject = {
2
  doSomething() {
3
    return Promise.resolve("This is a floating promise!");
4
  },
5
};
6

7
// We can now detect that `doSomething()` returns a `Promise`.
8
sneakyObject.doSomething();

#6531 c06df79 Thanks @arendjr! - Biome’s type inference now detects the type of properties with getters.

Examples

1
const sneakyObject2 = {
2
  get something() {
3
    return new Promise((_, reject) => reject("This is a floating promise!"));
4
  },
5
};
6
// We now detect this is a Promise:
7
sneakyObject2.something;

#6587 a330fcc Thanks @Conaclos! - organizeImports is now able to sort named specifiers and import attributes with bogus nodes.
#6618 6174869 Thanks @Shinyaigeek! - Fixed #6610: JSON import attributes are now correctly detected when they contain extra whitespace.
#6753 fce5d2c Thanks @dyc3! - Improved the error messages when Biome is provided incompatible arguments on the CLI.
#6587 a330fcc Thanks @Conaclos! - Fixed #6491: The action of useSortedKeys removed comments or wrongly transferred them to distinct nodes.
#6696 92964a7 Thanks @unvalley! - Fixed #6633: The noImplicitCoercion rule no longer reports diagnostics for 1 / value expressions.
```
1
1 / value; // no error
```
#6683 43d871e Thanks @ematipico! - Fixed #6537: Biome no longer removes the trailing comma from JSON files when formatter.json.trailingCommas is explicitly set to "all".
#6693 bfdce0b Thanks @dyc3! - Fixed #6691: The HTML parser will now consider . to be a valid character for tag names.
#6716 ead03d1 Thanks @siketyan! - The Biome LSP server no longer responds with an error for a textDocument/codeActions request when Biome doesn’t support a feature for the file (e.g. Code actions aren’t supported in GritQL files).
#6679 7bf9a60 Thanks @marko-hologram! - Fixed #6638: JavaScript formatter overrides options now correctly override expand option. JSON formatter overrides options now correctly override bracketSpacing and expand options.
#6717 7f5b541 Thanks @siketyan! - Fixed #6688: the noUselessFragments no longer reports <Fragment /> elements that includes HTML character entities.
#6600 853e1b5 Thanks @daivinhtran! - Fixed #4677: The noUnusedImports rule won’t produce diagnostics for types used in comments of static members anymore.
#6662 3afc804 Thanks @arendjr! - If a nested configuration file is ignored by the root configuration, it will now actually be ignored.

Biome has an exception in place for configuration files so they cannot be ignored, because the configuration files are vital to Biome itself. But this exception was incorrectly applied to nested configurations as well. Now only the root configuration is exempt from being ignored.
#6596 c0718ca Thanks @ematipico! - Fixed #6566: Biome no longer errors when using the option --files-ignore-unknown=true in stdin mode.

Biome has also become less strict when using --stdin-file-path in stdin mode. It will no longer error if the file path doesn’t contain an extension, but instead it will return the original content.
#6562 153eda7 Thanks @vladimir-ivanov! - Added the nursery rule noMagicNumbers. The rule detects and reports the use of “magic numbers” — numeric literals that are used directly in code without being assigned to a named constant.

Example
```
1
let total = price * 1.23; // Magic number for tax rate will highlight 1.23 as magic number
```
#6663 af78d6d Thanks @ematipico! - Fixed #6656: Biome now correctly formats HTML void elements such as <meta> when they contain a self-closing slash.
```
1
<meta foo="bar" />
2
<meta foo="bar">
```
#6732 31e4396 Thanks @vladimir-ivanov! - Resolved #6281: Improved performance of handling package.json files in the scanner.
#6625 19cb475 Thanks @arendjr! - Fixed #6616: Fixed an issue with extending configurations that contained an explicit root field while the configuration in the project did not.
#6650 19aab18 Thanks @sterliakov! - Fixed #6621: Improved handling of multiple adjacent line suppressions. Biome now handles such suppressions separately, tracking whether each one is used.
#6700 cdd6e17 Thanks @denbezrukov! - Fixed #6680: Biome incorrectly formatted container-style queries by inserting misplaced spaces.
```
1
@container style (--responsive: true) {}
2
@container style(--responsive: true) {}
```
#6709 ecf3954 Thanks @dyc3! - Fixed #6038: Fixed a false positive in noShadow where a function parameter in a type definition was erroneously flagged as a violation.

#6593 a4acbb7 Thanks @arendjr! - Type inference is now able to handle ternary conditions in expressions.

Examples

1
const condition = Math.random() > -1; // Always true, but dynamic to linter
2

3
// We now detect that this may return a `Promise`.
4
condition ? Promise.reject("ternary bypass") : null;
5

6
// On the other hand, we know the following is never a `Promise`:
7
const alwaysFalsy = 0;
8
alwaysFalsy ? Promise.reject("ternary bypass") : null;

#6428 4b501d3 Thanks @siketyan! - Added MemoryFileSystem to the WASM API.

You can now insert a file from your JS code:

1
import { MemoryFileSystem, Workspace } from "@biomejs/wasm-web";
2

3
const fs = new MemoryFileSystem();
4
const workspace = Workspace.withFileSystem(fs);
5

6
fs.insert("/index.js", new TextEncoder().encode("let foo = 1;"));
7
fs.remove("/index.js");

#6594 626d4a1 Thanks @ematipico! - Fixed #6528: Biome didn’t return the correct output when applying source.fixAll.biome inside Astro/Vue/Svelte files that contained safe fixed.

2.0.6

Patch Changes

#6557 fd68458 Thanks @ematipico! - Fixed a bug where Biome didn’t provide all the available code actions when requested by the editor.
#6511 72623fa Thanks @Conaclos! - Fixed #6492. The organizeImports assist action no longer duplicates a comment at the start of the file when :BLANK_LINE: precedes the first import group.
#6557 fd68458 Thanks @ematipico! - Fixed #6287 where Biome Language Server didn’t adhere to the settings.requireConfiguration option when pulling diagnostics and code actions. Note that for this configuration be correctly applied, your editor must support dynamic registration capabilities.
#6551 0b63b1d Thanks @Conaclos! - Fixed #6536. useSortedKeys no longer panics in some edge cases where object spreads are involved.
#6503 9a8fe0f Thanks @ematipico! - Fixed #6482 where nursery rules that belonged to a domain were incorrectly enabled.
#6565 e85761c Thanks @daivinhtran! - Fixed #4677: Now the noUnusedImports rule won’t produce diagnostics for types used in JSDoc comment of exports.
#6166 b8cbd83 Thanks @mehm8128! - Added the nursery rule noExcessiveLinesPerFunction. This rule restrict a maximum number of lines of code in a function body.

The following code is now reported as invalid when the limit of maximum lines is set to 2:
```
1
function foo() {
2
  const x = 0;
3
  const y = 1;
4
  const z = 2;
5
}
```
The following code is now reported as valid when the limit of maximum lines is set to 3:
```
1
const bar = () => {
2
  const x = 0;
3
  const z = 2;
4
};
```
#6553 5f42630 Thanks @denbezrukov! - Fixed #6547. Now the Biome CSS parser correctly parses @starting-style when it’s used inside other at-rules. The following example doesn’t raise an error anymore:
```
1
@layer my-demo-layer {
2
  @starting-style {
3
    div.showing {
4
      background-color: red;
5
    }
6
  }
7
}
```
#6458 05402e3 Thanks @ematipico! - Fixed an issue where the rule useSemanticElements used the incorrect range when positioning suppression comments.
#6560 6d8a6b9 Thanks @siketyan! - Fixed #6559: the error message on detected a large file was outdated and referred a removed configuration option files.ignore.
#6458 05402e3 Thanks @ematipico! - Fixed #6384. The rule useAltText now emits a diagnostic with a correct range, so suppression comments can work correctly.
#6518 7a56288 Thanks @wojtekmaj! - Fixed #6508, where the rule noUselessFragments incorrectly flagged Fragments containing HTML entities as unnecessary.
#6517 c5217cf Thanks @arendjr! - Fixed #6515. When using the extends field to extend a configuration from an NPM package, we now accept the condition names "biome" and "default" for exporting the configuration in the package.json.

This means that where previously your package.json had to contain an export declaration similar to this:
```
1
{
2
  "exports": {
3
    ".": "./biome.json"
4
  }
5
}
```
You may now use one of these as well:
```
1
{
2
  "exports": {
3
    ".": {
4
      "biome": "./biome.json"
5
    }
6
  }
7
}
```
Or:
```
1
{
2
  "exports": {
3
    ".": {
4
      "default": "./biome.json"
5
    }
6
  }
7
}
```
#6219 a3a3715 Thanks @huangtiandi1999! - Added new nursery rule noUnassignedVariables, which disallows let or var variables that are read but never assigned.

The following code is now reported as invalid:
```
1
let x;
2
if (x) {
3
  console.log(1);
4
}
```
The following code is now reported as valid:
```
1
let x = 1;
2
if (x) {
3
  console.log(1);
4
}
```
#6395 f62e748 Thanks @mdevils! - Added the new nursery rule noImplicitCoercion, which disallows shorthand type conversions in favor of explicit type conversion functions.

Example (Invalid): Boolean conversion using double negation:
```
1
!!foo;
2
!!(foo + bar);
```
Example (Invalid): Number conversion using unary operators:
```
1
+foo;
2
-(-foo);
3
foo - 0;
4
foo * 1;
5
foo / 1;
```
Example (Invalid): String conversion using concatenation:
```
1
"" + foo;
2
foo + "";
3
`` + foo;
4
foo += "";
```
Example (Invalid): Index checking using bitwise NOT:
```
1
~foo.indexOf(1);
2
~foo.bar.indexOf(2);
```
Example (Valid): Using explicit type conversion functions:
```
1
Boolean(foo);
2
Number(foo);
3
String(foo);
4
foo.indexOf(1) !== -1;
```
#6544 f28b075 Thanks @daivinhtran! - Fixed #6536. Now the rule noUselessFragments produces diagnostics for a top-level useless fragment that is in a return statement.
#6320 5705f1a Thanks @mdevils! - Added the new nursery rule useUnifiedTypeSignature, which disallows overload signatures that can be unified into a single signature.

Overload signatures that can be merged into a single signature are redundant and should be avoided. This rule helps simplify function signatures by combining overloads by making parameters optional and/or using type unions.

Example (Invalid): Overload signatures that can be unified:
```
1
function f(a: number): void;
2
function f(a: string): void;
```
```
1
interface I {
2
  a(): void;
3
  a(x: number): void;
4
}
```
Example (Valid): Unified signatures:
```
1
function f(a: number | string): void {}
```
```
1
interface I {
2
  a(x?: number): void;
3
}
```
Example (Valid): Different return types cannot be merged:
```
1
interface I {
2
  f(): void;
3
  f(x: number): number;
4
}
```
#6545 2782175 Thanks @ematipico! - Fixed #6529, where the Biome Language Server would emit an error when the user would open a file that isn’t part of its workspace ( node_modules or external files). Now the language server doesn’t emit any errors and it exits gracefully.

#6524 a27b825 Thanks @vladimir-ivanov! - Fixed #6500: The useReadonlyClassProperties rule now correctly marks class properties as readonly when they are assigned in a constructor, setter or method, even if the assignment occurs inside an if or else block.

The following code is now correctly detected by the rule:

1
class Price {
2
  #price: string;
3

4
  @Input()
5
  set some(value: string | number) {
6
    if (
7
      value === undefined ||
8
      value === null ||
9
      value === "undefined" ||
10
      value === "null" ||
11
      Number.isNaN(value)
12
    ) {
13
      this.#price = "";
14
    } else {
15
      this.#price = "" + value;
16
    }
17
  }
18
}

#6355 e128ea9 Thanks @anthonyshew! - Added a new nursery rule noAlert that disallows the use of alert, confirm and prompt.

The following code is deemed incorrect:
```
1
alert("here!");
```
#6548 37e9799 Thanks @ematipico! - Fixed #6459, where the Biome LSP was not taking into account the correct settings when applying source.fixAll.biome code action.

2.0.5

Patch Changes

#6461 38862e6 Thanks @ematipico! - Fixed #6419, a regression where stdin mode would create a temporary new file instead of using the one provided by the user. This was an intended regression.

Now Biome will use the file path passed via --std-file-path, and apply the configuration that matches it.
#6480 050047f Thanks @Conaclos! - Fixed #6371. useNamingConvention now checks the string case of objects’ property shorthand.

#6477 b98379d Thanks @ematipico! - Fixed an issue where Biome formatter didn’t format consistently CSS value separated by commas.

1
.font-heading {
2
 font-feature-settings: var(--heading-salt), var(--heading-ss06),
3
   var(--heading-ss11), var(--heading-cv09), var(--heading-liga),
4
   var(--heading-calt);
5

6
  font-feature-settings:
7
    var(--heading-salt), var(--heading-ss06), var(--heading-ss11),
8
    var(--heading-cv09), var(--heading-liga), var(--heading-calt);
9
}

#6248 ec7126c Thanks @fireairforce! - Fixed grit pattern matching for different kinds of import statements.

The grit pattern import $imports from "foo" will match the following code:
```
1
import bar from "foo";
2
import { bar } from "foo";
3
import { bar, baz } from "foo";
```

2.0.4

Patch Changes

#6450 7472d9e Thanks @ematipico! - Fixed an issue where the binary wasn’t correctly mapped.

2.0.3

Patch Changes

#6439 7e4da4e Thanks @ematipico! - Fixed an issue where the correct rights aren’t added to the binary during publishing

#6297 cc4b8c9 Thanks @vladimir-ivanov! - Added a new lint useReadonlyClassProperties rule. This rule is a port of ESLint’s prefer-readonly rule.

Example:

1
class Example {
2
  // All properties below can be marked as readonly
3
  public constantValue = 42;
4
  protected initializedInConstructor: string;
5
  private privateField = true;
6

7
  constructor(initializedInConstructor: string) {
8
    this.initializedInConstructor = initializedInConstructor;
9
  }
10
}

2.0.2

Patch Changes

#6436 ec7c63d Thanks @ematipico! - Fixed an issue where binaries weren’t copied anymore inside the @biomejs/cli-* packages.

2.0.1

Patch Changes

#6425 00e97ad Thanks @siketyan! - Fixed #6391: the rule noUselessFragments no longer reports a fragment that contains whitespaces which aren’t trimmed by the runtime.
#6417 dd88565 Thanks @ematipico! - Fixed #6360: The following pseudo classes and elements are no longer reported by noUnknownPseudoClass or noUnknownPseudoElement rules.
- :open
- ::details-content
- ::prefix
- ::search-text
- ::suffix
#6417 dd88565 Thanks @ematipico! - Fixed #6357, where the boolean values weren’t correctly merged when using the extends functionality. Now Biome correctly merges the values.
#6417 dd88565 Thanks @ematipico! - Fixed #6341: Fixed an issue where Biome would throw an error for the language tags nb and nn.
#6385 94142dd Thanks @siketyan! - Fixed #6377: The rule noSelfCompare now correctly compares two function calls with different arguments.
#6417 dd88565 Thanks @ematipico! - Fixed #6278: useExhaustiveDependencies no longer adds duplicated dependencies into the list.
#6417 dd88565 Thanks @ematipico! - Fix #6396, where vi.useFakeTimers() and vi.useRealTimers() incorrectly triggered React Hooks-related rules
#6417 dd88565 Thanks @ematipico! - Fixed a bug where Biome didn’t correctly discover nested configuration files when using the lint command and the linter is disabled in the root configuration.
#6422 594ec50 Thanks @ematipico! - Removed the experimental rename feature from Biome LSP, which caused some issues inside existing editors such as Zed.
#6388 c6942d2 Thanks @siketyan! - Fixed #6375: the formatter no longer inserts an extra empty line before a semicolon when it has leading comments.