Commit 1d9068a
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?v=4&size=40){kind=avatar}
chore(deps): update dependency @biomejs/biome to v2 (#155)
This PR contains the following updates:
| Package | Type | Update | Change | OpenSSF |
|---|---|---|---|---|
| [@biomejs/biome](https://biomejs.dev)
([source](https://redirect.github.com/biomejs/biome/tree/HEAD/packages/@biomejs/biome))
| devDependencies | major | [`^1.9.4` ->
`^2.0.0`](https://renovatebot.com/diffs/npm/@biomejs%2fbiome/1.9.4/2.0.6)
| [](https://securityscorecards.dev/viewer/?uri=github.com/biomejs/biome)
|
---
> [!WARNING]
> Some dependencies could not be looked up. Check the Dependency
Dashboard for more information.
---
### Release Notes
<details>
<summary>biomejs/biome (@​biomejs/biome)</summary>
###
[`v2.0.6`](https://redirect.github.com/biomejs/biome/blob/HEAD/packages/@​biomejs/biome/CHANGELOG.md#206)
[Compare
Source](https://redirect.github.com/biomejs/biome/compare/@biomejs/biome@2.0.5...@biomejs/biome@2.0.6)
##### Patch Changes
- [#​6557](https://redirect.github.com/biomejs/biome/pull/6557)
[`fd68458`](https://redirect.github.com/biomejs/biome/commit/fd68458f40767cb1aeb9eb444a03c5dd6f3f7c0d)
Thanks [@​ematipico](https://redirect.github.com/ematipico)! -
Fixed a bug where Biome didn't provide all the available code actions
when requested by the editor.
- [#​6511](https://redirect.github.com/biomejs/biome/pull/6511)
[`72623fa`](https://redirect.github.com/biomejs/biome/commit/72623fa30470bbb97bae24514233d4d8a39507ec)
Thanks [@​Conaclos](https://redirect.github.com/Conaclos)! - Fixed
[#​6492](https://redirect.github.com/biomejs/biome/issues/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](https://redirect.github.com/biomejs/biome/pull/6557)
[`fd68458`](https://redirect.github.com/biomejs/biome/commit/fd68458f40767cb1aeb9eb444a03c5dd6f3f7c0d)
Thanks [@​ematipico](https://redirect.github.com/ematipico)! -
Fixed
[#​6287](https://redirect.github.com/biomejs/biome/issues/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](https://redirect.github.com/biomejs/biome/pull/6551)
[`0b63b1d`](https://redirect.github.com/biomejs/biome/commit/0b63b1d95c32ba61b2dcda4195d860397de3b589)
Thanks [@​Conaclos](https://redirect.github.com/Conaclos)! - Fixed
[#​6536](https://redirect.github.com/biomejs/biome/issues/6536).
`useSortedKeys` no longer panics in some edge cases where object spreads
are involved.
- [#​6503](https://redirect.github.com/biomejs/biome/pull/6503)
[`9a8fe0f`](https://redirect.github.com/biomejs/biome/commit/9a8fe0f9313b2df93df56b3446340cc04a0e1958)
Thanks [@​ematipico](https://redirect.github.com/ematipico)! -
Fixed
[#​6482](https://redirect.github.com/biomejs/biome/issues/6482)
where nursery rules that belonged to a domain were incorrectly enabled.
- [#​6565](https://redirect.github.com/biomejs/biome/pull/6565)
[`e85761c`](https://redirect.github.com/biomejs/biome/commit/e85761c72058e2c039ff16707781f7e0aa19d2a9)
Thanks [@​daivinhtran](https://redirect.github.com/daivinhtran)! -
Fixed
[#​4677](https://redirect.github.com/biomejs/biome/issues/4677):
Now the `noUnusedImports` rule won't produce diagnostics for types used
in JSDoc comment of exports.
- [#​6166](https://redirect.github.com/biomejs/biome/pull/6166)
[`b8cbd83`](https://redirect.github.com/biomejs/biome/commit/b8cbd839935fd0e672cb0fc2051df0e2fb9e5d1a)
Thanks [@​mehm8128](https://redirect.github.com/mehm8128)! - Added
the nursery rule
[noExcessiveLinesPerFunction](https://biomejs.dev/linter/rules/no-excessive-lines-per-function/).
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:
```js
function foo() {
const x = 0;
const y = 1;
const z = 2;
}
```
The following code is now reported as valid when the limit of maximum
lines is set to 3:
```jsx
const bar = () => {
const x = 0;
const z = 2;
};
```
- [#​6553](https://redirect.github.com/biomejs/biome/pull/6553)
[`5f42630`](https://redirect.github.com/biomejs/biome/commit/5f42630f7b457070c7c1ad17cee28eae2e9951cc)
Thanks [@​denbezrukov](https://redirect.github.com/denbezrukov)! -
Fixed
[#​6547](https://redirect.github.com/biomejs/biome/issues/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:
```css
@​layer my-demo-layer {
@​starting-style {
div.showing {
background-color: red;
}
}
}
```
- [#​6458](https://redirect.github.com/biomejs/biome/pull/6458)
[`05402e3`](https://redirect.github.com/biomejs/biome/commit/05402e395f6e356b690e1cad740294183fafeb84)
Thanks [@​ematipico](https://redirect.github.com/ematipico)! -
Fixed an issue where the rule `useSemanticElements` used the incorrect
range when positioning suppression comments.
- [#​6560](https://redirect.github.com/biomejs/biome/pull/6560)
[`6d8a6b9`](https://redirect.github.com/biomejs/biome/commit/6d8a6b9a31788565455d6a6138ef6c1fe67421d5)
Thanks [@​siketyan](https://redirect.github.com/siketyan)! - Fixed
[#​6559](https://redirect.github.com/biomejs/biome/issues/6559):
the error message on detected a large file was outdated and referred a
removed configuration option `files.ignore`.
- [#​6458](https://redirect.github.com/biomejs/biome/pull/6458)
[`05402e3`](https://redirect.github.com/biomejs/biome/commit/05402e395f6e356b690e1cad740294183fafeb84)
Thanks [@​ematipico](https://redirect.github.com/ematipico)! -
Fixed
[#​6384](https://redirect.github.com/biomejs/biome/issues/6384).
The rule [`useAltText`](https://biomejs/dev/linter/rules/no-alt-text)
now emits a diagnostic with a correct range, so suppression comments can
work correctly.
- [#​6518](https://redirect.github.com/biomejs/biome/pull/6518)
[`7a56288`](https://redirect.github.com/biomejs/biome/commit/7a56288e0c7f366d6aa30100432227f3501afb61)
Thanks [@​wojtekmaj](https://redirect.github.com/wojtekmaj)! -
Fixed
[#​6508](https://redirect.github.com/biomejs/biome/issues/6508),
where the rule `noUselessFragments` incorrectly flagged Fragments
containing HTML entities as unnecessary.
- [#​6517](https://redirect.github.com/biomejs/biome/pull/6517)
[`c5217cf`](https://redirect.github.com/biomejs/biome/commit/c5217cfb21653add3d3add930102bea8fb7b5833)
Thanks [@​arendjr](https://redirect.github.com/arendjr)! - Fixed
[#​6515](https://redirect.github.com/biomejs/biome/issues/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:
```json
{
"exports": {
".": "./biome.json"
}
}
```
You may now use one of these as well:
```json
{
"exports": {
".": {
"biome": "./biome.json"
}
}
}
```
Or:
```json
{
"exports": {
".": {
"default": "./biome.json"
}
}
}
```
- [#​6219](https://redirect.github.com/biomejs/biome/pull/6219)
[`a3a3715`](https://redirect.github.com/biomejs/biome/commit/a3a371552a84eaaf24ce1bd8e63e3c1243b285a9)
Thanks
[@​huangtiandi1999](https://redirect.github.com/huangtiandi1999)!
- Added new nursery rule
[`noUnassignedVariables`](https://biomejs.dev/linter/rules/no-unassigned-variables/),
which disallows `let` or `var` variables that are read but never
assigned.
The following code is now reported as invalid:
```js
let x;
if (x) {
console.log(1);
}
```
The following code is now reported as valid:
```js
let x = 1;
if (x) {
console.log(1);
}
```
- [#​6395](https://redirect.github.com/biomejs/biome/pull/6395)
[`f62e748`](https://redirect.github.com/biomejs/biome/commit/f62e7481c2a94271869651d2b32bde5d54adbc73)
Thanks [@​mdevils](https://redirect.github.com/mdevils)! - Added
the new nursery rule
[`noImplicitCoercion`](https://biomejs.dev/linter/rules/no-implicit-coercion),
which disallows shorthand type conversions in favor of explicit type
conversion functions.
**Example (Invalid): Boolean conversion using double negation:**
```js
!!foo;
!!(foo + bar);
```
**Example (Invalid): Number conversion using unary operators:**
```js
+foo;
-(-foo);
foo - 0;
foo * 1;
foo / 1;
```
**Example (Invalid): String conversion using concatenation:**
```js
"" + foo;
foo + "";
`` + foo;
foo += "";
```
**Example (Invalid): Index checking using bitwise NOT:**
```js
~foo.indexOf(1);
~foo.bar.indexOf(2);
```
**Example (Valid): Using explicit type conversion functions:**
```js
Boolean(foo);
Number(foo);
String(foo);
foo.indexOf(1) !== -1;
```
- [#​6544](https://redirect.github.com/biomejs/biome/pull/6544)
[`f28b075`](https://redirect.github.com/biomejs/biome/commit/f28b075b4fd28e49f18ae131878f67ce9a831c5a)
Thanks [@​daivinhtran](https://redirect.github.com/daivinhtran)! -
Fixed
[#​6536](https://redirect.github.com/biomejs/biome/issues/6530).
Now the rule `noUselessFragments` produces diagnostics for a top-level
useless fragment that is in a return statement.
- [#​6320](https://redirect.github.com/biomejs/biome/pull/6320)
[`5705f1a`](https://redirect.github.com/biomejs/biome/commit/5705f1aa9e41bfaea53edf255a18167b52a5fd9b)
Thanks [@​mdevils](https://redirect.github.com/mdevils)! - Added
the new nursery rule
[`useUnifiedTypeSignature`](https://biomejs.dev/linter/rules/use-unified-type-signature),
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:**
```ts
function f(a: number): void;
function f(a: string): void;
```
```ts
interface I {
a(): void;
a(x: number): void;
}
```
**Example (Valid): Unified signatures:**
```ts
function f(a: number | string): void {}
```
```ts
interface I {
a(x?: number): void;
}
```
**Example (Valid): Different return types cannot be merged:**
```ts
interface I {
f(): void;
f(x: number): number;
}
```
- [#​6545](https://redirect.github.com/biomejs/biome/pull/6545)
[`2782175`](https://redirect.github.com/biomejs/biome/commit/2782175c445d4e5f979497ea76beda0276783909)
Thanks [@​ematipico](https://redirect.github.com/ematipico)! -
Fixed
[#​6529](https://redirect.github.com/biomejs/biome/issues/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](https://redirect.github.com/biomejs/biome/pull/6524)
[`a27b825`](https://redirect.github.com/biomejs/biome/commit/a27b8253b2f0d5e5618e9b26eebaaa5da55ed69a)
Thanks
[@​vladimir-ivanov](https://redirect.github.com/vladimir-ivanov)!
- Fixed
[#​6500](https://redirect.github.com/biomejs/biome/issues/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:
```ts
class Price {
#price: string;
@​Input()
set some(value: string | number) {
if (
value === undefined ||
value === null ||
value === "undefined" ||
value === "null" ||
Number.isNaN(value)
) {
this.#price = "";
} else {
this.#price = "" + value;
}
}
}
```
- [#​6355](https://redirect.github.com/biomejs/biome/pull/6355)
[`e128ea9`](https://redirect.github.com/biomejs/biome/commit/e128ea9eb44bcf5558ab6b08214884d1c087686d)
Thanks [@​anthonyshew](https://redirect.github.com/anthonyshew)! -
Added a new nursery rule `noAlert` that disallows the use of `alert`,
`confirm` and `prompt`.
The following code is deemed incorrect:
```js
alert("here!");
```
- [#​6548](https://redirect.github.com/biomejs/biome/pull/6548)
[`37e9799`](https://redirect.github.com/biomejs/biome/commit/37e979978b406c3e132fd5093bfb21e811c93d2d)
Thanks [@​ematipico](https://redirect.github.com/ematipico)! -
Fixed
[#​6459](https://redirect.github.com/biomejs/biome/issues/6459),
where the Biome LSP was not taking into account the correct settings
when applying `source.fixAll.biome` code action.
###
[`v2.0.5`](https://redirect.github.com/biomejs/biome/blob/HEAD/packages/@​biomejs/biome/CHANGELOG.md#205)
[Compare
Source](https://redirect.github.com/biomejs/biome/compare/@biomejs/biome@2.0.4...@biomejs/biome@2.0.5)
##### Patch Changes
- [#​6461](https://redirect.github.com/biomejs/biome/pull/6461)
[`38862e6`](https://redirect.github.com/biomejs/biome/commit/38862e645c07935f2daf52799dce38656d589d40)
Thanks [@​ematipico](https://redirect.github.com/ematipico)! -
Fixed
[#​6419](https://redirect.github.com/biomejs/biome/issues/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](https://redirect.github.com/biomejs/biome/pull/6480)
[`050047f`](https://redirect.github.com/biomejs/biome/commit/050047f4a3c1379abcf3cf57f1bfecd20bb7d8c1)
Thanks [@​Conaclos](https://redirect.github.com/Conaclos)! - Fixed
[#​6371](https://redirect.github.com/biomejs/biome/issues/6371).
[useNamingConvention](https://biomejs.dev/linter/rules/use-naming-convention/)
now checks the string case of objects' property shorthand.
- [#​6477](https://redirect.github.com/biomejs/biome/pull/6477)
[`b98379d`](https://redirect.github.com/biomejs/biome/commit/b98379d42d97540c3bd911263a0af1eb7bc4803e)
Thanks [@​ematipico](https://redirect.github.com/ematipico)! -
Fixed an issue where Biome formatter didn't format consistently CSS
value separated by commas.
```diff
.font-heading {
- font-feature-settings: var(--heading-salt), var(--heading-ss06),
- var(--heading-ss11), var(--heading-cv09), var(--heading-liga),
- var(--heading-calt);
+ font-feature-settings:
+ var(--heading-salt), var(--heading-ss06), var(--heading-ss11),
+ var(--heading-cv09), var(--heading-liga), var(--heading-calt);
}
```
- [#​6248](https://redirect.github.com/biomejs/biome/pull/6248)
[`ec7126c`](https://redirect.github.com/biomejs/biome/commit/ec7126ca3d6777344191f3463b430a44fce02489)
Thanks [@​fireairforce](https://redirect.github.com/fireairforce)!
- Fixed grit pattern matching for different kinds of import statements.
The grit pattern `import $imports from "foo"` will match the following
code:
```ts
import bar from "foo";
import { bar } from "foo";
import { bar, baz } from "foo";
```
###
[`v2.0.4`](https://redirect.github.com/biomejs/biome/blob/HEAD/packages/@​biomejs/biome/CHANGELOG.md#204)
[Compare
Source](https://redirect.github.com/biomejs/biome/compare/2c9cdd5860954292dbeefa1162d19f4bae23c859...@biomejs/biome@2.0.4)
##### Patch Changes
- [#​6450](https://redirect.github.com/biomejs/biome/pull/6450)
[`7472d9e`](https://redirect.github.com/biomejs/biome/commit/7472d9e07fd6e8afab385276678f3d39c7497bab)
Thanks [@​ematipico](https://redirect.github.com/ematipico)! -
Fixed an issue where the binary wasn't correctly mapped.
###
[`v2.0.3`](https://redirect.github.com/biomejs/biome/blob/HEAD/packages/@​biomejs/biome/CHANGELOG.md#203)
##### Patch Changes
- [#​6439](https://redirect.github.com/biomejs/biome/pull/6439)
[`7e4da4e`](https://redirect.github.com/biomejs/biome/commit/7e4da4edb811f9598e446c77fd26bc3802b6d3dd)
Thanks [@​ematipico](https://redirect.github.com/ematipico)! -
Fixed an issue where the correct rights aren't added to the binary
during publishing
- [#​6297](https://redirect.github.com/biomejs/biome/pull/6297)
[`cc4b8c9`](https://redirect.github.com/biomejs/biome/commit/cc4b8c90017f9c04eab393abc60b3f94a35e3cfa)
Thanks
[@​vladimir-ivanov](https://redirect.github.com/vladimir-ivanov)!
- Added a new lint `useReadonlyClassProperties` rule.
This rule is a port of ESLint's
[prefer-readonly](https://typescript-eslint.io/rules/prefer-readonly/)
rule.
Example:
```ts
class Example {
// All properties below can be marked as readonly
public constantValue = 42;
protected initializedInConstructor: string;
private privateField = true;
constructor(initializedInConstructor: string) {
this.initializedInConstructor = initializedInConstructor;
}
}
```
###
[`v2.0.2`](https://redirect.github.com/biomejs/biome/blob/HEAD/packages/@​biomejs/biome/CHANGELOG.md#202)
##### Patch Changes
- [#​6436](https://redirect.github.com/biomejs/biome/pull/6436)
[`ec7c63d`](https://redirect.github.com/biomejs/biome/commit/ec7c63df520103b5d8ea0090c59486574e7370dd)
Thanks [@​ematipico](https://redirect.github.com/ematipico)! -
Fixed an issue where binaries weren't copied anymore inside the
`@biomejs/cli-*` packages.
###
[`v2.0.1`](https://redirect.github.com/biomejs/biome/blob/HEAD/packages/@​biomejs/biome/CHANGELOG.md#201)
[Compare
Source](https://redirect.github.com/biomejs/biome/compare/@biomejs/biome@2.0.0...@biomejs/biome@2.0.1)
##### Patch Changes
- [#​6425](https://redirect.github.com/biomejs/biome/pull/6425)
[`00e97ad`](https://redirect.github.com/biomejs/biome/commit/00e97aded825e72e63db7827de20dc84ac8a123b)
Thanks [@​siketyan](https://redirect.github.com/siketyan)! - Fixed
[#​6391](https://redirect.github.com/biomejs/biome/issues/6391):
the rule
[`noUselessFragments`](https://biomejs.dev/linter/rules/no-useless-fragments/)
no longer reports a fragment that contains whitespaces which aren't
trimmed by the runtime.
- [#​6417](https://redirect.github.com/biomejs/biome/pull/6417)
[`dd88565`](https://redirect.github.com/biomejs/biome/commit/dd885655b576869eb624d4a31d2d09bcb6c623a4)
Thanks [@​ematipico](https://redirect.github.com/ematipico)! -
Fixed
[#​6360](https://redirect.github.com/biomejs/biome/issues/6360):
The following pseudo classes and elements are no longer reported by
`noUnknownPseudoClass` or `noUnknownPseudoElement` rules.
- `:open`
- `::details-content`
- `::prefix`
- `::search-text`
- `::suffix`
- [#​6417](https://redirect.github.com/biomejs/biome/pull/6417)
[`dd88565`](https://redirect.github.com/biomejs/biome/commit/dd885655b576869eb624d4a31d2d09bcb6c623a4)
Thanks [@​ematipico](https://redirect.github.com/ematipico)! -
Fixed
[#​6357](https://redirect.github.com/biomejs/biome/issues/6357),
where the boolean values weren't correctly merged when using the
`extends` functionality. Now Biome correctly merges the values.
- [#​6417](https://redirect.github.com/biomejs/biome/pull/6417)
[`dd88565`](https://redirect.github.com/biomejs/biome/commit/dd885655b576869eb624d4a31d2d09bcb6c623a4)
Thanks [@​ematipico](https://redirect.github.com/ematipico)! -
Fixed
[#​6341](https://redirect.github.com/biomejs/biome/issues/6341):
Fixed an issue where Biome would throw an error for the language tags
`nb` and `nn`.
- [#​6385](https://redirect.github.com/biomejs/biome/pull/6385)
[`94142dd`](https://redirect.github.com/biomejs/biome/commit/94142dd84b3a4b680c08007cd4947ca7d44273a8)
Thanks [@​siketyan](https://redirect.github.com/siketyan)! - Fixed
[#​6377](https://redirect.github.com/biomejs/biome/issues/6377):
The rule
[noSelfCompare](https://biomejs.dev/linter/rules/no-self-compare/) now
correctly compares two function calls with different arguments.
- [#​6417](https://redirect.github.com/biomejs/biome/pull/6417)
[`dd88565`](https://redirect.github.com/biomejs/biome/commit/dd885655b576869eb624d4a31d2d09bcb6c623a4)
Thanks [@​ematipico](https://redirect.github.com/ematipico)! -
Fixed
[#​6278](https://redirect.github.com/biomejs/biome/issues/6278):
`useExhaustiveDependencies` no longer adds duplicated dependencies into
the list.
- [#​6417](https://redirect.github.com/biomejs/biome/pull/6417)
[`dd88565`](https://redirect.github.com/biomejs/biome/commit/dd885655b576869eb624d4a31d2d09bcb6c623a4)
Thanks [@​ematipico](https://redirect.github.com/ematipico)! - Fix
[#​6396](https://redirect.github.com/biomejs/biome/issues/6396),
where `vi.useFakeTimers()` and `vi.useRealTimers()` incorrectly
triggered React Hooks-related rules
- [#​6417](https://redirect.github.com/biomejs/biome/pull/6417)
[`dd88565`](https://redirect.github.com/biomejs/biome/commit/dd885655b576869eb624d4a31d2d09bcb6c623a4)
Thanks [@​ematipico](https://redirect.github.com/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](https://redirect.github.com/biomejs/biome/pull/6422)
[`594ec50`](https://redirect.github.com/biomejs/biome/commit/594ec5008761c6263a43f72f1cbb7e9aafaf8a46)
Thanks [@​ematipico](https://redirect.github.com/ematipico)! -
Removed the experimental rename feature from Biome LSP, which caused
some issues inside existing editors such as Zed.
- [#​6388](https://redirect.github.com/biomejs/biome/pull/6388)
[`c6942d2`](https://redirect.github.com/biomejs/biome/commit/c6942d291297322234f9f145fc2fbf8506dc7673)
Thanks [@​siketyan](https://redirect.github.com/siketyan)! - Fixed
[#​6375](https://redirect.github.com/biomejs/biome/issues/6375):
the formatter no longer inserts an extra empty line before a semicolon
when it has leading comments.
###
[`v2.0.0`](https://redirect.github.com/biomejs/biome/blob/HEAD/packages/@​biomejs/biome/CHANGELOG.md#200)
[Compare
Source](https://redirect.github.com/biomejs/biome/compare/fa93a147abe64e9c85908d317a8dd1de343ad132...@biomejs/biome@2.0.0)
##### Major Changes
- Biome now resolves globs and paths from the configuration. Before,
paths and globs were resolved from the working directory.
- Biome now raises a **warning** diagnostic for suppression comments
that have `<explanation>` as reason.
`<explanation>` is provided as a placeholder when applying the
suppression code fix from LSP editors.
- Removed the `--config-path` argument from the `biome lsp-proxy` and
`biome start` commands.
The option was overriding the configuration path for all workspaces
opened in the Biome daemon, which led to a configuration mismatch
problem when multiple projects are opened in some editors or IDEs.
If you are using one of our official plugins for IDEs or editors, it is
recommended to update it to the latest version of the plugin, or you
will get unexpected behavior.
If you are a developer of a plugin, please update your plugin to use the
`workspace/configuration` response instead of using the `--config-path`
argument. Biome's LSP will resolve a configuration in the workspace
automatically, so it is recommended to keep it empty unless you are
using a custom configuration path.
- Downgraded some code fixes to unsafe which were previously safe.
The following rules have now a unsafe fix:
-
[`noFlatMapIdentity`](https://biomejs.dev/linter/rules/no-flat-map-identity)
-
[`noUnusedImports`](https://biomejs.dev/linter/rules/no-unused-imports)
If you want to keep applying these fixes automatically, [configure the
rule fix](https://next.biomejs.dev/linter/#configure-the-code-fix) as
safe:
```json
{
"linter": {
"rules": {
"correctness": {
"noFlatMapIdentity": {
"level": "error",
"fix": "safe"
},
"noUnusedImports": {
"level": "error",
"fix": "safe"
}
}
}
}
}
```
- Previously the lint rules `noControlCharactersInRegex` and
`noMisleadingCharacterClass` checked both regular expression literals
like `/regex/` and dynamically built regular expressions like `new
RegExp("regex")`.
Checking dynamically built regular expressions has many limitations,
edge cases, and complexities.
In addition, other rules that lint regular expressions don't check
dynamically built regular expressions.
Rather than add support for other rules and have half-baked checking, we
decided to remove support for dynamically built regular expressions.
Now the lint rules `noControlCharactersInRegex` and
`noMisleadingCharacterClass` only check literals of regular expressions.
- The lint rule
[`noRestrictedGlobals`](https://biomejs.dev/linter/rules/no-restricted-globals/)
now supports customizing message for each global name.
For example, the following configuration:
```json
{
"options": {
"deniedGlobals": {
"$": "jQuery is not allowed. Use native DOM manipulation instead."
}
}
}
```
emits a diagnostic:
```
index.js:1:13 lint/style/noRestrictedGlobals
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
⚠ Do not use the global variable $.
> 1 │ console.log($)
│ ^
2 │
ℹ jQuery is not allowed. Use native DOM manipulation instead.
```
Breaking Change: The option `deniedGlobals` is now a record instead of
an array. Run `biome migrate` to migrate the configuration
automatically.
- Removed `include` and `ignore` fields in favor of the new field
`includes`.
The Biome configuration file allows users to specify which files should
be processed using [glob
patterns](https://en.wikipedia.org/wiki/Glob_\(programming\)).
Prior to Biome 2.0, this was done using the `include` and `ignore`
fields.
In Biome 2.0, `include` and `ignore` are removed and replaced by
`includes`.
You can run `biome migrate` to convert `include` and `ignore` into
`includes` automatically.
`includes` uses a different glob pattern format that fixes
[many](https://redirect.github.com/biomejs/biome/issues/2421)
[issues](https://redirect.github.com/biomejs/biome/issues/3345) and many
other limitations that Biome users reported.
`includes` accepts an array of glob patterns.
A glob pattern starting with a `!` is a negated pattern also called
exception.
This replaces `ignore` patterns and allows users to create chains of
include and ignore patterns.
Thus, it is now possible to include again a file previously ignored.
This was not possible with `include` and `ignore`, because `ignore` has
priority over `include`.
The semantics of `*` and `**/*` have changed too.
Before, with `include` and `ignore`, the glob `*` was interpreted as
`**/*`.
Now, with `includes`, the globs `*` and `**/*` are interpreted
differently.
The first pattern matches all files that are inside a folder.
The second pattern recursively matches all files **and sub-folders**
inside a folder.
Let's take an example.
Given the following file hierarchy of a project...
```
├── biome.json
├── src
│ ├── file.js
│ ├── file.ts
│ ├── out.gen.js
│ ├── file.test.js
│ └── test
│ └── special.test.js
└── test ...
```
...we want:
1. Ignore all files ending with `.test.js`, except `special.test.ts`.
2. Ignore all files of the `test` directory.
The `test` directory is located at the root of the project.
3. Execute the linter on files in the `src` directory, that don't end
with `.gen.js`.
The `src` directory is located at the root of the project.
4. Enable the `noDefaultExport` lint rule on files ending with `.ts`.
Prior to Biome 2.0, the configuration might look like:
```json
{
"files": {
"ignore": ["*.test.js", "test"]
},
"linter": {
"include": ["src/**"],
"ignore": ["*.gen.js"],
"enabled": true
},
"overrides": [
{
"include": ["*.ts"],
"linter": { "rules": { "style": { "noDefaultExport": "on" } } }
}
]
}
```
Unfortunately, the configuration doesn't quite fit what we want:
1. There is no way to ignore files and unignore one of them.
Thus, we ignore all files ending with `.test.js`, including
`special.test.ts`.
2. The configuration ignores all directories named `test`, including
`src/test`.
3. The linter is executed on all files of all directories named `src`
All these issues and limitations are fixed with `includes`.
Here the migrated configuration:
```json
{
"files": {
"includes": ["**", "!**/*.test.js", "**/special.test.ts", "!test"]
},
"linter": {
"includes": ["src/**", "!**/*.gen.js"],
"enabled": true
},
"overrides": [
{
"includes": ["**/*.ts"],
"linter": { "rules": { "style": { "noDefaultExport": "on" } } }
}
]
}
```
1. All files named `special.test.ts` are unignored because the pattern
appear after the pattern that ignore files ending with `.test.js`.
2. Only the `test` directory at the project's root is ignored because
the pattern doesn't start with `**/`.
3. The linter is executed on the `src` directory at the project's root
only.
Because `includes` pattern have a different pattern format than
`include` and `ignore` we made some adjustments:
- We added the pattern `**` in `files.includes` to ensure that all files
are included before ignoring some of them.
- We added the prefix `**/` for patterns that must match at any level of
the file hierarchy.
- `noUndeclaredVariables` no longer reports TypeScript types.
In TypeScript projects, developers often use global declaration files to
declare global types.
Biome is currently unable to detect these global types.
This creates many false positives for `noUndeclaredVariables`.
TypeScript is better suited to perform this kind of check.
As proof of this, TypeScript ESLint doesn't provide any rule that
extends the `no-undef` ESLint rule.
This is why Biome 1.9 introduced a new option `checkTypes` which, when
it is set to false, ignores undeclared type references.
The option was set to `true` by default.
This option is now set to `false` by default.
To get the previous behavior, you have to set `checkTypes` to `true`:
```json
{
"linter": {
"rules": {
"correctness": {
"noUndeclaredVariables": {
"level": "on",
"options": { "checkTypes": true }
}
}
}
}
}
```
- The rule `noUnusedVariables` no longer reports unused function
parameters. Use
[`noUnusedFunctionParameters`](https://biomejs.dev/linter/rules/no-unused-function-parameters/).
- Fixed
[#​5564](https://redirect.github.com/biomejs/biome/issues/5564).
`noTypeOnlyImportAttributes` now ignores files ending with the extension
`.ts` when the type field of `package.json` is set to `commonjs`.
- The Biome formatter no longer adds a trailing comma in `.json` files,
even when `json.formatter.trailingCommas` is set to `true`.
- [Prettier 3.4](https://prettier.io/blog/2024/11/26/3.4.0.html)
introduced a change in their normalization process of string literals:
it no longer unescapes useless escape sequences.
Biome now matches the new behavior of Prettier when formatting code.
This affects the JSON and JavaScript formatters.
- Reduced accepted values for formatter options:
- The option `--quote-style` doesn't accept `Single` and `Double`
anymore.
- The option `--quote-properties` doesn't accept `AsNeeded` and
`Preserve` anymore.
- The option `--semicolons` doesn't accept `AsNeeded` and `Always`
anymore.
- The option `--arrow-parenthesis` doesn't accept `AsNeeded` and
`Always` anymore.
- The option `--trailing-commas` doesn't accept `ES5`, `All` and `None`
anymore.
- The option `--attribute-position` doesn't accept `Single` and
`Multiline` anymore.
- Removed the option `enumMemberCase` from the lint rule
`useNamingConvention`.
`enumMemberCase` is an option that allows to customize the enforced case
for TypeScript's enum members.
The option was introduced prior to the `conventions` option that allows
to do the same thing.
The following configuration...
```json
{
"linter": {
"rules": {
"style": {
"useNamingConvention": {
"level": "on",
"options": {
"enumMemberCase": "PascalCase"
}
}
}
}
}
}
```
...must be rewritten as:
```json
{
"linter": {
"rules": {
"style": {
"useNamingConvention": {
"level": "on",
"options": {
"conventions": [
{
"selector": { "kind": "enumMember" },
"formats": ["PascalCase"]
}
]
}
}
}
}
}
}
```
Run `biome migrate --write` to turn `enumMemberCase` into `conventions`
automatically.
- Removed support for `BIOME_LOG_DIR`.
The environment variable `BIOME_LOG_DIR` isn't supported anymore.
Use `BIOME_LOG_PATH` instead.
- Remove deprecated rules.
The following *deprecated* rules have been deleted:
- `noInvalidNewBuiltin`
- `noNewSymbol`
- `useShorthandArrayType`
- `useSingleCaseStatement`
- `noConsoleLog`
Run the command `biome migrate --write` to update the configuration.
- Removed the deprecated `indentSize` option.
The deprecated option `indentSize`, and its relative CLI options, has
been removed:
- Configuration file: `formatter.indentSize`
- Configuration file: `javascript.formatter.indentSize`
- Configuration file: `json.formatter.indentSize`
- CLI option `--indent-size`
- CLI option `--javascript-formatter-indent-size`
- CLI option `--json-formatter-indent-size`
Use `indentWidth` and its relative CLI options instead.
- Removed `ROME_BINARY`. Use `BIOME_BINARY` instead.
- Removed support for legacy suppressions.
Biome used to support "legacy suppressions" that looked like this:
```js
// biome-ignore lint(complexity/useWhile): reason
```
This format is no longer supported.
- Removed support for `max_line_length` from `.editorconfig`, as it
isn't part of the official spec anymore.
- Removed support for `rome-ignore` suppression comments.
Use `biome-ignore` suppression comments instead.
- Removed support for `rome.json`.
Use `biome.json` or `biome.jsonc` instead.
- Removed the option `all` from the linter.
The options `linter.rules.all` and `linter.rules.<group>.all` has been
removed.
The number of rules in Biome have increased in scope and use cases, and
sometimes some of them can conflict with each other.
The option was useful at the beginning, but now it's deemed harmful,
because it can unexpected behaviours in users projects.
To automatically remove it, run the following command:
```shell
biome migrate --write
```
- Removed the option `trailingComma` from the configuration and the CLI.
Use the option `trailingCommas` instead:
```diff
{
"javascript": {
"formatter": {
- "trailingComma": "es5"
+ "trailingCommas": "es5"
}
}
}
```
```diff
-biome format --trailing-comma=es5
+biome format --trailing-commas=es5
```
- Removed `--apply` and `--apply-unsafe`.
The CLI options `--apply` and `--apply-unasfe` aren't accepted anymore.
Use `--write` and `--write --unafe` instead:
```diff
-biome check --apply-unsafe
+biome check --write --unsafe
```
```diff
-biome check --apply
+biome check --write
```
- Removed support for `assert` syntax.
Biome now longer supports the `assert` syntax, use the new `with` syntax
instead
```diff
-import {test} from "foo.json" assert { for: "for" }
-export * from "mod" assert { type: "json" }
+import {test} from "foo.json" with { for: "for" }
+export * from "mod" with { type: "json" }
```
- Fixed
[#​5495](https://redirect.github.com/biomejs/biome/issues/5495):
The rule
[`noBlankTarget`](https://biomejs.dev/linter/rules/no-blank-target/) has
been
updated to accept the `rel="noopener"` in addition to
`rel="noreferrer"`.
In addition, an option has been added that allows `rel="noreferrer"` to
be
disabled.
The rule has been moved from the `a11y` group to the `security` group.
- The rule `useImportRestrictions` has been renamed to
[`noPrivateImports`](https://biomejs.dev/linter/rules/no-private-imports),
and its
functionality has been significantly upgraded.
Previously, the rule would assume that any direct imports from modules
inside
other directories should be forbidden due to their *package private*
visibility.
The updated rule allows configuring the default visibility of exports,
and
recognises JSDoc comments to override this visibility. The default
visibility
is now `**public**`, but can be set to `**package**`, or even
`**private**`.
Refer to the [documentation of the
rule](https://biomejs.dev/linter/rules/no-private-imports) to understand
how to leverage the JSDoc comments.
`noPrivateImports` is now recommended by default.
- The Biome daemon now reuses its workspace across connections. This
allows multiple clients to
reuse the same documents and other cached data that we extract from
them.
This primarily affects our IDE extensions: If you open multiple
IDEs/windows for the same project,
they'll connect to the same daemon and reuse each other's workspace.
The Biome CLI is unaffected unless you opt in with the `--use-server`
argument.
- Biome no longer treats too large files as errors.
Previously, files that exceed the configured size limit would throw an
error, and the CLI would exit with an error code.
Now, the CLI ignores the file, emits an *information* diagnostic and
doesn't exit with an error code.
- Change the group of some rules, promote nursery rules and update the
recommended rule set.
The following rules have been moved to a new group:
-
[complexity/noArguments](https://biomejs.dev/linter/rules/no-arguments)
-
[complexity/noCommaOperator](https://biomejs.dev/linter/rules/no-comma-operator)
-
[complexity/noFlatMapIdentity](https://biomejs.dev/linter/rules/no-flat-map-identity)
-
[complexity/noUselessContinue](https://biomejs.dev/linter/rules/no-useless-continue)
-
[complexity/useNumericLiterals](https://biomejs.dev/linter/rules/use-numeric-literals)
-
[correctness/useValidTypeof](https://biomejs.dev/linter/rules/use-valid-typeof)
-
[performance/noNamespaceImport](https://biomejs.dev/linter/rules/no-namespace-import/)
-
[style/useArrayLiterals](https://biomejs.dev/linter/rules/use-array-literals)
- [suspicious/noWith](https://biomejs.dev/linter/rules/no-with)
New rules are incubated in the nursery group.
Once stable, we promote them to a stable group.
Use the `biome migrate` command to automatically migrate nursery rules
that have been promoted.
The following CSS rules have been promoted:
-
[correctness/noMissingVarFunction](https://biomejs.dev/linter/rules/no-missing-var-function)
-
[correctness/noUnknownPseudoClass](https://biomejs.dev/linter/rules/no-unknown-pseudo-class)
-
[correctness/noUnknownPseudoElement](https://biomejs.dev/linter/rules/no-unknown-pseudo-element)
-
[correctness/noUnknownTypeSelector](https://biomejs.dev/linter/rules/no-unknown-type-selector)
-
[style/noDescendingSpecificity](https://biomejs.dev/linter/rules/no-descending-specificity)
-
[style/noValueAtRule](https://biomejs.dev/linter/rules/no-value-at-rule)
-
[suspcious/noDuplicateCustomProperties](https://biomejs.dev/linter/rules/no-duplicate-custom-properties)
-
[suspcious/noDuplicateProperties](https://biomejs.dev/linter/rules/no-duplicate-properties)
The following GraphQL rules have been promoted:
-
[style/useDeprecatedReason](https://biomejs.dev/linter/rules/use-deprecated-reason)
-
[suspicious/noDuplicatedFields](https://biomejs.dev/linter/rules/no-duplicated-fields)
The following JavaScript rules have been promoted:
-
[a11y/noStaticElementInteractions](https://biomejs.dev/linter/rules/no-static-element-interactions)
-
[a11y/useAriaPropsSupportedByRole](https://biomejs.dev/linter/rules/use-aria-props-supported-by-role)(recommended)
-
[a11y/useValidAutocomplete](https://biomejs.dev/linter/rules/use-valid-autocomplete)
-
[complexity/noUselessEscapeInRegex](https://biomejs.dev/linter/rules/no-useless-escape-in-regex)
-
[complexity/noUselessStringRaw](https://biomejs.dev/linter/rules/no-useless-string-raw)
-
[performance/noDynamicNamespaceImportAccess](https://biomejs.dev/linter/rules/no-dynamic-namespace-import-access)
-
[performance/noImgElement](https://biomejs.dev/linter/rules/no-img-element)
- [style/noCommonJs](https://biomejs.dev/linter/rules/no-common-js)
- [style/noEnum](https://biomejs.dev/linter/rules/no-enum)
-
[style/noExportedImports](https://biomejs.dev/linter/rules/no-exported-imports)
-
[style/noHeadElement](https://biomejs.dev/linter/rules/no-head-element)
-
[style/noNestedTernary](https://biomejs.dev/linter/rules/no-nested-ternary)
- [style/noProcessEnv](https://biomejs.dev/linter/rules/no-process-env)
-
[style/noRestrictedImports](https://biomejs.dev/linter/rules/no-restricted-imports)
-
[style/noRestrictedTypes](https://biomejs.dev/linter/rules/no-restricted-types)
- [style/noSubstr](https://biomejs.dev/linter/rules/no-substr)
- [style/useAtIndex](https://biomejs.dev/linter/rules/use-at-index)
-
[style/useCollapsedIf](https://biomejs.dev/linter/rules/use-collapsed-if)
-
[style/useComponentExportOnlyModules](https://biomejs.dev/linter/rules/use-component-export-only-modules)
-
[style/useConsistentCurlyBraces](https://biomejs.dev/linter/rules/use-consistent-curly-braces)
-
[style/useConsistentMemberAccessibility](https://biomejs.dev/linter/rules/use-consistent-member-accessibility)
-
[style/useTrimStartEnd](https://biomejs.dev/linter/rules/use-trim-start-end)
-
[suspicious/noDocumentCookie](https://biomejs.dev/linter/rules/no-document-cookie)
-
[suspicious/noDocumentImportInPage](https://biomejs.dev/linter/rules/no-document-import-in-page)
-
[suspicious/noDuplicateElseIf](https://biomejs.dev/linter/rules/no-duplicate-else-if)
-
[suspicious/noHeadImportInDocument](https://biomejs.dev/linter/rules/no-head-import-in-document)
-
[suspicious/noIrregularWhitespace](https://biomejs.dev/linter/rules/no-irregular-whitespace)
-
[suspicious/noOctalEscape](https://biomejs.dev/linter/rules/no-octal-escape)
-
[suspicious/noTemplateCurlyInString](https://biomejs.dev/linter/rules/no-template-curly-in-string)
-
[suspicious/useAdjacentOverloadSignatures](https://biomejs.dev/linter/rules/use-adjacent-overload-signatures)
-
[suspicious/useGoogleFontDisplay](https://biomejs.dev/linter/rules/use-google-font-display)
-
[suspicious/useGuardForIn](https://biomejs.dev/linter/rules/use-guard-for-in)
-
[suspicious/useStrictMode](https://biomejs.dev/linter/rules/use-strict-mode)
Moreover, the following JavaScript rules are now recommended:
-
[complexity/noUselessUndefinedInitialization](https://biomejs.dev/linter/rules/no-useless-undefined-initialization)
-
[complexity/useArrayLiterals](https://biomejs.dev/linter/rules/use-array-literals)
-
[correctness/noConstantMathMinMaxClamp](https://biomejs.dev/linter/rules/no-constant-math-min-max-clamp)
-
[correctness/noUnusedFunctionParameters](https://biomejs.dev/linter/rules/no-unused-function-parameters)
(recommended by ESLint)
-
[correctness/noUnusedImports](https://biomejs.dev/linter/rules/no-unused-imports)
-
[correctness/noUnusedPrivateClassMembers](https://biomejs.dev/linter/rules/no-unused-private-class-members)
(recommended by ESLint)
-
[correctness/noUnusedVariables](https://biomejs.dev/linter/rules/no-unused-variables)
(recommended by ESLint)
- [complexity/useDateNow](https://biomejs.dev/linter/rules/use-date-now)
And the following style rules are no longer recommended:
-
[style/useNumberNamespace](https://biomejs.dev/linter/rules/use-number-namespace)
-
[style/useAsConstAssertion](https://biomejs.dev/linter/rules/use-as-const-assertion)
-
[style/noParameterAssign](https://biomejs.dev/linter/rules/no-parameter-assign)
-
[style/noInferrableTypes](https://biomejs.dev/linter/rules/no-inferrable-types)
-
[style/useDefaultParameterLast](https://biomejs.dev/linter/rules/use-default-parameter-last)
-
[style/noUnusedTemplateLiteral](https://biomejs.dev/linter/rules/no-unused-template-literal)
-
[style/useEnumInitializers](https://biomejs.dev/linter/rules/use-enum-initializers)
-
[style/noUselessElse](https://biomejs.dev/linter/rules/no-useless-else)
-
[style/useSelfClosingElements](https://biomejs.dev/linter/rules/use-self-closing-elements)
-
[style/useSingleVarDeclarator](https://biomejs.dev/linter/rules/use-single-var-declarator)
- Update the default severity level of lint rules.
Every diagnostic emitted by Biome has a severity level set to `error`,
`warn`, or `info`.
Previously, all recommended lint rules had a default severity level set
to `error`.
All other lint rules had a default severity level set to `warn`.
We have adjusted the default severity level of every rule, whether
recommended or not, to better communicate the *severity* that a
diagnostic highlights.
- Rules that report hard errors, likely erroneous code, dangerous code,
or accessibility issues now have a default severity level of `error`.
- Rules that report possibly erroneous codes, or code that could be
cleaner if rewritten in another way now have a default severity level of
`warn`.
- Rules that reports stylistic suggestions now have a default severity
level of `info`.
You can use the CLI option `--diagnostic-level=error` to display only
errors, or `--diagnostic-level=warning` to display both errors and
warnings.
By default, all diagnostics are shown.
You can also use the CLI option `--error-on-warnings` to make the
command fail when warnings are emitted.
- Reworked some recommended rules recommended to be less pedantic and
blocking. This is a **breaking change** if your project relied on those
rules to block the CI in case of violations; if that's the case, you
should raise their severity level to **error**.
Some rules aren't recommended anymore, and some others return a
different severity.
The following rules return a **warning** diagnostic:
- `noDelete`
- `noForEach`
- `noSuspiciousSemicolonInJsx`
- `noThisInStatic`
- `noUnusedLabels`
The following rules return an **information** diagnostic:
- `noUselessCatch`
- `noUselessConstructor`
- `noUselessEmptyExport`
- `noUselessFragments`
- `noUselessLabel`
- `noUselessLoneBlockStatements`
- `noUselessSwitchCase`
- `noUselessTernary`
- `noUselessThisAlias`
- `noUselessTypeConstraint`
- `noFlatMapIdentity`
The following rules aren't recommended anymore:
- `noDelete`
- `noForEach`
The rule `noRenderReturnValue` and `useExhaustiveDependencies` are only
recommended when the `react` domain is enabled.
- Renamed the global option `--skip-errors` to `--skip-parse-errors`.
- Remove the code action `quickfix.suppressRule`.
The code action `quickfix.suppressRule` was removed in favour of two new
code actions:
- `quickfix.suppressRule.inline.biome`: a code action that adds a
suppression comment for each violation.
- `quickfix.suppressRule.topLevel.biome`: a code action that adds a
suppression comment at the top of the file which suppresses a rule for
the whole file.
Given the following code
```js
let foo = "one";
debugger;
```
The code action `quickfix.suppressRule.inline.biome` will result in the
following code:
```js
// biome-ignore lint/style/useConst: <explanation>
let foo = "one";
// biome-ignore lint/suspicious/noDebugger: <explanation>
debugger;
```
The code action `quickfix.suppressRule.topLevel.biome`, instead, will
result in the following code:
```js
/** biome-ignore lint/suspicious/noDebugger: <explanation> */
/** biome-ignore lint/style/useConst: <explanation> */
let foo = "one";
debugger;
```
- Changed default formatting of `package.json`.
When Biome encounters a file called `package.json`, by default it will
format the file with all objects and arrays expanded.
```diff
- { "name": "project", "dependencies": { "foo": "latest" } }
+ {
+ "projectName": "project",
+ "dependencies": {
+ "foo": "^1.0.0"
+ }
+ }
```
- The `organizeImports` is now part of Biome Assist.
- The rule [`noVar`](https://biomejs.dev/linter/rules/no-var/) now
belongs to the `suspicious` group
- The rule [`useWhile`](https://biomejs.dev/linter/rules/use-while/) now
belongs to the `complexity` group.
- The rule
[`useImportExtensions`](https://biomejs.dev/linter/rules/use-import-extensions/)
has been updated to suggest actual file extensions instead of guesses
based on hueristics.
As part of this, the `suggestedExtensions` option has been removed. A
simpler,
new option called `forceJsExtensions` has been introduced for those who
use
`tsc`'s `"module": "node16"` setting.
The rule also no longer reports diagnostics to add an extension when the
path
doesn't exist at all, with or without extension.
- Fixed
[#​4545](https://redirect.github.com/biomejs/biome/issues/4545):
[`useNamingConvention`](https://biomejs.dev/linter/rules/use-naming-convention/)
now correctly ignores declarations inside TypeScript's external modules.
The following interface name is no longer reported by the rule:
```ts
declare module "myExternalModule" {
export interface my_INTERFACE {}
}
```
- The rule
[`useAltText`](https://biomejs.dev/linter/rules/use-alt-text/) no longer
checks the element's attributes containing object spread.
The following code doesn't trigger the rule anymore:
```jsx
<img src="test.png" alt={alt} {...restProps}></img>
```
- The rule
[`useNamingConvention`](https://biomejs.dev/linter/rules/use-naming-convention/)
no longer accepts non-ASCII characters by default.
Prior to Biome 2.0, non-ASCII names were accepted by default. They are
now rejected.
For example, the following code is now reported as invalid by the
`useNamingConvention` rule.
```js
let johnCafé;
```
If you want to allow non ASCII filenames and non-ASCII identifiers, you
need to set the `requireAscii` options in your Biome configuration file
to `false`:
```json
{
"linter": {
"rules": {
"style": {
"useFilenamingConvention": {
"level": "on",
"options": {
"requireAscii": false
}
}
"useFilenamingConvention": {
"level": "on",
"options": {
"requireAscii": false
}
}
}
}
}
}
```
- Renamed the rule `noUnnecessaryContinue` to `noUselessContinue`. Run
the command `biome migrate` to update your configuration.
- Renamed the rule `noMultipleSpacesInRegularExpressionLiterals` to
`noAdjacentSpacesInRegex`. Run the command `biome migrate` to update
your configuration.
##### Minor Changes
- An option called `allowNoReferrer` has been added to the
[`noBlankTarget`](https://biomejs.dev/linter/rules/no-blank-target/)
rule.
By default, `noBlankTarget` accepts both `rel="noopener"` and
`rel="noreferrer"`
with links that have `target="_blank"`. This is because the latter
*implies* the
former, so either one is sufficient to mitigate the security risk.
However, allowing `rel="noreferrer"` may still be undesirable, because
it can
break tracking, which may be an undesirable side-effect. As such, you
can set
`allowNoReferrer: false` to *only* accept `rel="noopener"`.
- Added new option `javascript.parser.jsxEverywhere`. This new option
allows to control whether Biome should expect JSX syntax in
`.js`/`.mjs`/`.cjs` files.
When `jsxEverywhere` is set to `false`, having JSX syntax like
`<div></div>` inside `.js`/`.mjs`/`.cjs` files will result in a
**parsing error**.
Despite the name of the option, JSX is never supported inside `.ts`
files. This is because TypeScript generics syntax may conflict with JSX
in such files.
This option defaults to `true`.
- Add a new JS assist rule - `useSortedKeys` which enforces ordering of
a JS object properties.
This rule will consider spread/calculated keys e.g `[k]: 1` as
non-sortable.
Instead, whenever it encounters a non-sortable key, it will sort all the
previous sortable keys up until the nearest non-sortable key, if one
exist.
This prevents breaking the override of certain keys using spread keys.
Source: https://perfectionist.dev/rules/sort-objects
```js
// Base
// from
const obj = {
b: 1,
a: 1,
...g,
ba: 2,
ab: 1,
set aab(v) {
this._aab = v;
},
[getProp()]: 2,
aba: 2,
abc: 3,
abb: 3,
get aaa() {
return "";
},
};
// to
const obj = {
a: 1,
b: 1,
...g,
set aab(v) {
this._aab = v;
},
ab: 1,
ba: 2,
[getProp()]: 2,
get aaa() {
return "";
},
aba: 2,
abb: 3,
abc: 3,
};
```
- Added the new rule
[`noFloatingPromises`](https://biomejs.dev/linter/rules/no-floating-promises).
- Added the new rule
[`noImportCycles`](https://biomejs.dev/linter/rules/no-import-cycles).
- Added the new rule
[`noTsIgnore`](https://biomejs.dev/linter/rules/no-ts-ignore).
- Added the new rule
[`noUnwantedPolyfillio`](https://biomejs.dev/linter/rules/no-unwanted-polyfillio).
- Added a format option `expand` for Javascript and JSON formatters.
The option allows to enforce the formatting of arrays and objects on
multiple lines, regardless of their length.
It has three options:
When set to `auto` (default), objects are expanded if the first property
has a leading newline.
Arrays are collapsed when they fit to a single line.
For example, both styles below are considered as already formatted:
```js
const obj = {
foo: "bar",
};
```
```js
const obj = { foo: "bar" };
```
When set to `always`, objects and arrays are always expanded.
When set to `never`, objects and arrays are never expanded when they fit
in a single line.
It is equivalent to Prettier's [Object
Wrap](https://prettier.io/docs/options#object-wrap) option with
`collapse`.
- The nursery rule
[`noUnresolvedImports`](https://biomejs.dev/linter/rules/no-unresolved-imports/)
has been added.
Importing a non-existing export is an error at runtime or build time.
With this
rule, Biome can detect such incorrect imports and report errors for
them.
Note that if you use TypeScript, you probably don't want to use this
rule, since
TypeScript already performs such checks for you.
- The rule
[`noFocusedTests`](https://biomejs.dev/linter/rules/no-focused-tests/)
can now detect the usage of focused tests inside loops.
```js
// invalid
describe.only.each([["a"], ["b"]])("%s", (a) => {});
it.only.each([["a"], ["b"]])("%s", (a) => {});
test.only.each([["a"], ["b"]])("%s", (a) => {});
// valid
describe.each([["a"], ["b"]])("%s", (a) => {});
it.each([["a"], ["b"]])("%s", (a) => {});
test.each([["a"], ["b"]])("%s", (a) => {});
```
- Linter groups now accept new options to enable/disable all rules that
belong to a group, and control the severity
of the rules that belong to those groups.
For example, you can downgrade the severity of rules that belong to
`"style"` to emit `"info"` diagnostics:
```json
{
"linter": {
"rules": {
"style": "info"
}
}
}
```
You can also enable all rules that belong to a group using the default
severity of the rule using the `"on"` option:
```json
{
"linter": {
"rules": {
"complexity": "on"
}
}
}
```
- Biome assist is a new feature of the Biome analyzer. The assist is
meant to provide **actions**. Actions differ from linter rules in that
they aren't meant to signal errors.
The assist will provide code actions that users can opt into via
configuration or via IDEs/editors, using the Language Server Protocol.
The assist **is enabled by default**. However, you can turn if off via
configuration:
```json
{
"assist": {
"enabled": false
}
}
```
You can turn on the actions that you want to use in your configuration.
For example, you can enable the `useSortedKeys` action like this:
```json
{
"assist": {
"actions": {
"source": {
"useSortedKeys": "on"
}
}
}
}
```
Alternatively, IDE/editor users can decide which action to apply on save
*directly from the editor settings*, as long as the assist is enabled.
For example, in VS Code you can apply the `useSortedKeys` action when
saving a file by adding the following snippet in `settings.json`:
```json
{
"editor.codeActionsOnSave": {
"source.biome.useSortedKeys": "explicit"
}
}
```
In Zed, you can achieve the same by adding the following snippet in
`~/.config/zed/settings.json`:
```json
{
"code_actions_on_format": {
"source.biome.useSortedKeys": true
}
}
```
- Biome migrate eslint outputs a better overriding behavior.
A Biome rule can have multiple ESLint equivalent rules.
For example,
[useLiteralKeys](https://biomejs.dev/linter/rules/use-literal-keys/) has
two ESLint equivalent rules:
[dot-notation](https://eslint.org/docs/latest/rules/dot-notation) and
[@​typescript-eslint/dot-notation](https://typescript-eslint.io/rules/dot-notation/).
Previously, Biome wouldn't always enable a Biome rule even if one of its
equivalent rules was enabled.
Now Biome uses the higher severity level of all the equivalent ESLint
rules to set the severity level of the Biome rule.
The following ESLint configuration...
```json
{
"rules": {
"@​typescript-eslint/dot-notation": "
</details>
---
### Configuration
📅 **Schedule**: Branch creation - At 12:00 AM through 04:59 AM and 10:00
PM through 11:59 PM, Monday through Friday ( * 0-4,22-23 * * 1-5 ), Only
on Sunday and Saturday ( * * * * 0,6 ) (UTC), 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.
---
- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check
this box
---
This PR was generated by [Mend Renovate](https://mend.io/renovate/).
View the [repository job
log](https://developer.mend.io/github/settlemint/settlemint-action).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0MC41MC4wIiwidXBkYXRlZEluVmVyIjoiNDEuMTcuMiIsInRhcmdldEJyYW5jaCI6Im1haW4iLCJsYWJlbHMiOlsiZGVwZW5kZW5jaWVzIl19-->
---------
Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: janb87 <12234016+janb87@users.noreply.github.com>1 parent 7a7baec commit 1d9068a
8 files changed
Lines changed: 1153 additions & 98 deletions
File tree
- .github
- __tests__
- dist
- src
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
25 | 25 | | |
26 | 26 | | |
27 | 27 | | |
28 | | - | |
| 28 | + | |
| 29 | + | |
| 30 | + | |
29 | 31 | | |
30 | 32 | | |
31 | 33 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
87 | 87 | | |
88 | 88 | | |
89 | 89 | | |
90 | | - | |
| 90 | + | |
91 | 91 | | |
92 | 92 | | |
93 | 93 | | |
| |||
117 | 117 | | |
118 | 118 | | |
119 | 119 | | |
120 | | - | |
| 120 | + | |
121 | 121 | | |
122 | 122 | | |
123 | 123 | | |
| |||
147 | 147 | | |
148 | 148 | | |
149 | 149 | | |
150 | | - | |
| 150 | + | |
151 | 151 | | |
152 | 152 | | |
153 | 153 | | |
| |||
172 | 172 | | |
173 | 173 | | |
174 | 174 | | |
175 | | - | |
| 175 | + | |
176 | 176 | | |
177 | 177 | | |
178 | 178 | | |
| |||
190 | 190 | | |
191 | 191 | | |
192 | 192 | | |
193 | | - | |
| 193 | + | |
194 | 194 | | |
195 | 195 | | |
196 | 196 | | |
| |||
210 | 210 | | |
211 | 211 | | |
212 | 212 | | |
213 | | - | |
| 213 | + | |
214 | 214 | | |
215 | 215 | | |
216 | 216 | | |
| |||
234 | 234 | | |
235 | 235 | | |
236 | 236 | | |
237 | | - | |
| 237 | + | |
238 | 238 | | |
239 | 239 | | |
240 | 240 | | |
| |||
254 | 254 | | |
255 | 255 | | |
256 | 256 | | |
257 | | - | |
| 257 | + | |
258 | 258 | | |
259 | 259 | | |
260 | 260 | | |
| |||
278 | 278 | | |
279 | 279 | | |
280 | 280 | | |
281 | | - | |
| 281 | + | |
282 | 282 | | |
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
1 | 1 | | |
| 2 | + | |
2 | 3 | | |
| 4 | + | |
| 5 | + | |
| 6 | + | |
| 7 | + | |
| 8 | + | |
| 9 | + | |
| 10 | + | |
3 | 11 | | |
4 | | - | |
| 12 | + | |
5 | 13 | | |
6 | 14 | | |
| 15 | + | |
7 | 16 | | |
8 | 17 | | |
9 | | - | |
10 | | - | |
| 18 | + | |
11 | 19 | | |
12 | | - | |
13 | | - | |
| 20 | + | |
| 21 | + | |
14 | 22 | | |
15 | 23 | | |
16 | 24 | | |
| 25 | + | |
| 26 | + | |
| 27 | + | |
| 28 | + | |
| 29 | + | |
| 30 | + | |
| 31 | + | |
| 32 | + | |
| 33 | + | |
17 | 34 | | |
18 | | - | |
19 | | - | |
20 | | - | |
21 | 35 | | |
22 | 36 | | |
23 | | - | |
24 | | - | |
25 | | - | |
26 | | - | |
27 | | - | |
28 | | - | |
29 | | - | |
30 | | - | |
31 | | - | |
| 37 | + | |
| 38 | + | |
| 39 | + | |
| 40 | + | |
32 | 41 | | |
33 | 42 | | |
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.
0 commit comments