Commit 1584450
authored
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?v=4&size=40){kind=avatar}
chore(deps): update dependency @biomejs/biome to v2 (#831)
This PR contains the following updates:
| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
| [@biomejs/biome](https://biomejs.dev)
([source](https://redirect.github.com/biomejs/biome/tree/HEAD/packages/@biomejs/biome))
| [`^1.9.4` ->
`^2.0.0`](https://renovatebot.com/diffs/npm/@biomejs%2fbiome/1.9.4/2.0.0)
|
[](https://docs.renovatebot.com/merge-confidence/)
|
[](https://docs.renovatebot.com/merge-confidence/)
|
[](https://docs.renovatebot.com/merge-confidence/)
|
[](https://docs.renovatebot.com/merge-confidence/)
|
---
### Release Notes
<details>
<summary>biomejs/biome (@​biomejs/biome)</summary>
###
[`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/[email protected])
##### Major Changes
-
[`9d5d95f`](https://redirect.github.com/biomejs/biome/commit/9d5d95fffd5734522c8911db18c6d16ee6a96756)
Thanks [@​arendjr](https://redirect.github.com/arendjr)! - Biome
now resolves globs and paths from the configuration. Before, paths and
globs were resolved from the working directory.
-
[`9d5d95f`](https://redirect.github.com/biomejs/biome/commit/9d5d95fffd5734522c8911db18c6d16ee6a96756)
Thanks [@​arendjr](https://redirect.github.com/arendjr)! - 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.
-
[`9d5d95f`](https://redirect.github.com/biomejs/biome/commit/9d5d95fffd5734522c8911db18c6d16ee6a96756)
Thanks [@​arendjr](https://redirect.github.com/arendjr)! - 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.
-
[`9d5d95f`](https://redirect.github.com/biomejs/biome/commit/9d5d95fffd5734522c8911db18c6d16ee6a96756)
Thanks [@​arendjr](https://redirect.github.com/arendjr)! -
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"
}
}
}
}
}
```
-
[`9d5d95f`](https://redirect.github.com/biomejs/biome/commit/9d5d95fffd5734522c8911db18c6d16ee6a96756)
Thanks [@​arendjr](https://redirect.github.com/arendjr)! -
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.
-
[`9d5d95f`](https://redirect.github.com/biomejs/biome/commit/9d5d95fffd5734522c8911db18c6d16ee6a96756)
Thanks [@​arendjr](https://redirect.github.com/arendjr)! - 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.
-
[`9d5d95f`](https://redirect.github.com/biomejs/biome/commit/9d5d95fffd5734522c8911db18c6d16ee6a96756)
Thanks [@​arendjr](https://redirect.github.com/arendjr)! - 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.
-
[`9d5d95f`](https://redirect.github.com/biomejs/biome/commit/9d5d95fffd5734522c8911db18c6d16ee6a96756)
Thanks [@​arendjr](https://redirect.github.com/arendjr)! -
`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 }
}
}
}
}
}
```
-
[`9d5d95f`](https://redirect.github.com/biomejs/biome/commit/9d5d95fffd5734522c8911db18c6d16ee6a96756)
Thanks [@​arendjr](https://redirect.github.com/arendjr)! - The
rule `noUnusedVariables` no longer reports unused function parameters.
Use
[`noUnusedFunctionParameters`](https://biomejs.dev/linter/rules/no-unused-function-parameters/).
-
[`9d5d95f`](https://redirect.github.com/biomejs/biome/commit/9d5d95fffd5734522c8911db18c6d16ee6a96756)
Thanks [@​arendjr](https://redirect.github.com/arendjr)! - 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`.
-
[`9d5d95f`](https://redirect.github.com/biomejs/biome/commit/9d5d95fffd5734522c8911db18c6d16ee6a96756)
Thanks [@​arendjr](https://redirect.github.com/arendjr)! - The
Biome formatter no longer adds a trailing comma in `.json` files, even
when `json.formatter.trailingCommas` is set to `true`.
-
[`9d5d95f`](https://redirect.github.com/biomejs/biome/commit/9d5d95fffd5734522c8911db18c6d16ee6a96756)
Thanks [@​arendjr](https://redirect.github.com/arendjr)! -
[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.
-
[`9d5d95f`](https://redirect.github.com/biomejs/biome/commit/9d5d95fffd5734522c8911db18c6d16ee6a96756)
Thanks [@​arendjr](https://redirect.github.com/arendjr)! - 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.
-
[`9d5d95f`](https://redirect.github.com/biomejs/biome/commit/9d5d95fffd5734522c8911db18c6d16ee6a96756)
Thanks [@​arendjr](https://redirect.github.com/arendjr)! - 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.
-
[`9d5d95f`](https://redirect.github.com/biomejs/biome/commit/9d5d95fffd5734522c8911db18c6d16ee6a96756)
Thanks [@​arendjr](https://redirect.github.com/arendjr)! - Removed
support for `BIOME_LOG_DIR`.
The environment variable `BIOME_LOG_DIR` isn't supported anymore.
Use `BIOME_LOG_PATH` instead.
-
[`9d5d95f`](https://redirect.github.com/biomejs/biome/commit/9d5d95fffd5734522c8911db18c6d16ee6a96756)
Thanks [@​arendjr](https://redirect.github.com/arendjr)! - 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.
-
[`9d5d95f`](https://redirect.github.com/biomejs/biome/commit/9d5d95fffd5734522c8911db18c6d16ee6a96756)
Thanks [@​arendjr](https://redirect.github.com/arendjr)! - 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.
-
[`9d5d95f`](https://redirect.github.com/biomejs/biome/commit/9d5d95fffd5734522c8911db18c6d16ee6a96756)
Thanks [@​arendjr](https://redirect.github.com/arendjr)! - Removed
`ROME_BINARY`. Use `BIOME_BINARY` instead.
-
[`9d5d95f`](https://redirect.github.com/biomejs/biome/commit/9d5d95fffd5734522c8911db18c6d16ee6a96756)
Thanks [@​arendjr](https://redirect.github.com/arendjr)! - 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.
-
[`9d5d95f`](https://redirect.github.com/biomejs/biome/commit/9d5d95fffd5734522c8911db18c6d16ee6a96756)
Thanks [@​arendjr](https://redirect.github.com/arendjr)! - Removed
support for `max_line_length` from `.editorconfig`, as it isn't part of
the official spec anymore.
-
[`9d5d95f`](https://redirect.github.com/biomejs/biome/commit/9d5d95fffd5734522c8911db18c6d16ee6a96756)
Thanks [@​arendjr](https://redirect.github.com/arendjr)! - Removed
support for `rome-ignore` suppression comments.
Use `biome-ignore` suppression comments instead.
-
[`9d5d95f`](https://redirect.github.com/biomejs/biome/commit/9d5d95fffd5734522c8911db18c6d16ee6a96756)
Thanks [@​arendjr](https://redirect.github.com/arendjr)! - Removed
support for `rome.json`.
Use `biome.json` or `biome.jsonc` instead.
-
[`9d5d95f`](https://redirect.github.com/biomejs/biome/commit/9d5d95fffd5734522c8911db18c6d16ee6a96756)
Thanks [@​arendjr](https://redirect.github.com/arendjr)! - 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
```
-
[`9d5d95f`](https://redirect.github.com/biomejs/biome/commit/9d5d95fffd5734522c8911db18c6d16ee6a96756)
Thanks [@​arendjr](https://redirect.github.com/arendjr)! - 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
```
-
[`9d5d95f`](https://redirect.github.com/biomejs/biome/commit/9d5d95fffd5734522c8911db18c6d16ee6a96756)
Thanks [@​arendjr](https://redirect.github.com/arendjr)! - 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
```
-
[`9d5d95f`](https://redirect.github.com/biomejs/biome/commit/9d5d95fffd5734522c8911db18c6d16ee6a96756)
Thanks [@​arendjr](https://redirect.github.com/arendjr)! - 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" }
```
-
[`9d5d95f`](https://redirect.github.com/biomejs/biome/commit/9d5d95fffd5734522c8911db18c6d16ee6a96756)
Thanks [@​arendjr](https://redirect.github.com/arendjr)! - 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.
-
[`9d5d95f`](https://redirect.github.com/biomejs/biome/commit/9d5d95fffd5734522c8911db18c6d16ee6a96756)
Thanks [@​arendjr](https://redirect.github.com/arendjr)! - 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.
-
[`9d5d95f`](https://redirect.github.com/biomejs/biome/commit/9d5d95fffd5734522c8911db18c6d16ee6a96756)
Thanks [@​arendjr](https://redirect.github.com/arendjr)! - 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.
-
[`9d5d95f`](https://redirect.github.com/biomejs/biome/commit/9d5d95fffd5734522c8911db18c6d16ee6a96756)
Thanks [@​arendjr](https://redirect.github.com/arendjr)! - 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.
-
[`9d5d95f`](https://redirect.github.com/biomejs/biome/commit/9d5d95fffd5734522c8911db18c6d16ee6a96756)
Thanks [@​arendjr](https://redirect.github.com/arendjr)! - 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 `biomem igrate` 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)
-
[`9d5d95f`](https://redirect.github.com/biomejs/biome/commit/9d5d95fffd5734522c8911db18c6d16ee6a96756)
Thanks [@​arendjr](https://redirect.github.com/arendjr)! - 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.
-
[`9d5d95f`](https://redirect.github.com/biomejs/biome/commit/9d5d95fffd5734522c8911db18c6d16ee6a96756)
Thanks [@​arendjr](https://redirect.github.com/arendjr)! -
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.
-
[`9d5d95f`](https://redirect.github.com/biomejs/biome/commit/9d5d95fffd5734522c8911db18c6d16ee6a96756)
Thanks [@​arendjr](https://redirect.github.com/arendjr)! - Renamed
the global option `--skip-errors` to `--skip-parse-errors`.
-
[`9d5d95f`](https://redirect.github.com/biomejs/biome/commit/9d5d95fffd5734522c8911db18c6d16ee6a96756)
Thanks [@​arendjr](https://redirect.github.com/arendjr)! - 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;
```
-
[`9d5d95f`](https://redirect.github.com/biomejs/biome/commit/9d5d95fffd5734522c8911db18c6d16ee6a96756)
Thanks [@​arendjr](https://redirect.github.com/arendjr)! - 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"
+ }
+ }
```
-
[`9d5d95f`](https://redirect.github.com/biomejs/biome/commit/9d5d95fffd5734522c8911db18c6d16ee6a96756)
Thanks [@​arendjr](https://redirect.github.com/arendjr)! - The
`organizeImports` is now part of Biome Assist.
-
[`9d5d95f`](https://redirect.github.com/biomejs/biome/commit/9d5d95fffd5734522c8911db18c6d16ee6a96756)
Thanks [@​arendjr](https://redirect.github.com/arendjr)! - The
rule [`noVar`](https://biomejs.dev/linter/rules/no-var/) now belongs to
the `suspicious` group
-
[`9d5d95f`](https://redirect.github.com/biomejs/biome/commit/9d5d95fffd5734522c8911db18c6d16ee6a96756)
Thanks [@​arendjr](https://redirect.github.com/arendjr)! - The
rule [`useWhile`](https://biomejs.dev/linter/rules/use-while/) now
belongs to the `complexity` group.
-
[`9d5d95f`](https://redirect.github.com/biomejs/biome/commit/9d5d95fffd5734522c8911db18c6d16ee6a96756)
Thanks [@​arendjr](https://redirect.github.com/arendjr)! - 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.
-
[`9d5d95f`](https://redirect.github.com/biomejs/biome/commit/9d5d95fffd5734522c8911db18c6d16ee6a96756)
Thanks [@​arendjr](https://redirect.github.com/arendjr)! - 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 {}
}
```
-
[`9d5d95f`](https://redirect.github.com/biomejs/biome/commit/9d5d95fffd5734522c8911db18c6d16ee6a96756)
Thanks [@​arendjr](https://redirect.github.com/arendjr)! - 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>
```
-
[`9d5d95f`](https://redirect.github.com/biomejs/biome/commit/9d5d95fffd5734522c8911db18c6d16ee6a96756)
Thanks [@​arendjr](https://redirect.github.com/arendjr)! - 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
}
}
}
}
}
}
```
-
[`9d5d95f`](https://redirect.github.com/biomejs/biome/commit/9d5d95fffd5734522c8911db18c6d16ee6a96756)
Thanks [@​arendjr](https://redirect.github.com/arendjr)! - Renamed
the rule `noUnnecessaryContinue` to `noUselessContinue`. Run the command
`biome migrate` to update your configuration.
-
[`9d5d95f`](https://redirect.github.com/biomejs/biome/commit/9d5d95fffd5734522c8911db18c6d16ee6a96756)
Thanks [@​arendjr](https://redirect.github.com/arendjr)! - Renamed
the rule `noMultipleSpacesInRegularExpressionLiterals` to
`noAdjacentSpacesInRegex`. Run the command `biome migrate` to update
your configuration.
##### Minor Changes
-
[`9d5d95f`](https://redirect.github.com/biomejs/biome/commit/9d5d95fffd5734522c8911db18c6d16ee6a96756)
Thanks [@​arendjr](https://redirect.github.com/arendjr)! - 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"`.
-
[`9d5d95f`](https://redirect.github.com/biomejs/biome/commit/9d5d95fffd5734522c8911db18c6d16ee6a96756)
Thanks [@​arendjr](https://redirect.github.com/arendjr)! - 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`.
-
[`9d5d95f`](https://redirect.github.com/biomejs/biome/commit/9d5d95fffd5734522c8911db18c6d16ee6a96756)
Thanks [@​arendjr](https://redirect.github.com/arendjr)! - 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,
};
```
-
[`9d5d95f`](https://redirect.github.com/biomejs/biome/commit/9d5d95fffd5734522c8911db18c6d16ee6a96756)
Thanks [@​arendjr](https://redirect.github.com/arendjr)! - Added
the new rule
[`noFloatingPromises`](https://biomejs.dev/linter/rules/no-floating-promises).
-
[`9d5d95f`](https://redirect.github.com/biomejs/biome/commit/9d5d95fffd5734522c8911db18c6d16ee6a96756)
Thanks [@​arendjr](https://redirect.github.com/arendjr)! - Added
the new rule
[`noImportCycles`](https://biomejs.dev/linter/rules/no-import-cycles).
-
[`9d5d95f`](https://redirect.github.com/biomejs/biome/commit/9d5d95fffd5734522c8911db18c6d16ee6a96756)
Thanks [@​arendjr](https://redirect.github.com/arendjr)! - Added
the new rule
[`noTsIgnore`](https://biomejs.dev/linter/rules/no-ts-ignore).
-
[`9d5d95f`](https://redirect.github.com/biomejs/biome/commit/9d5d95fffd5734522c8911db18c6d16ee6a96756)
Thanks [@​arendjr](https://redirect.github.com/arendjr)! - Added
the new rule
[`noUnwantedPolyfillio`](https://biomejs.dev/linter/rules/no-unwanted-polyfillio).
-
[`9d5d95f`](https://redirect.github.com/biomejs/biome/commit/9d5d95fffd5734522c8911db18c6d16ee6a96756)
Thanks [@​arendjr](https://redirect.github.com/arendjr)! - 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`.
-
[`9d5d95f`](https://redirect.github.com/biomejs/biome/commit/9d5d95fffd5734522c8911db18c6d16ee6a96756)
Thanks [@​arendjr](https://redirect.github.com/arendjr)! - 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.
-
[`9d5d95f`](https://redirect.github.com/biomejs/biome/commit/9d5d95fffd5734522c8911db18c6d16ee6a96756)
Thanks [@​arendjr](https://redirect.github.com/arendjr)! - 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) => {});
```
-
[`9d5d95f`](https://redirect.github.com/biomejs/biome/commit/9d5d95fffd5734522c8911db18c6d16ee6a96756)
Thanks [@​arendjr](https://redirect.github.com/arendjr)! - 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"
}
}
}
```
-
[`9d5d95f`](https://redirect.github.com/biomejs/biome/commit/9d5d95fffd5734522c8911db18c6d16ee6a96756)
Thanks [@​arendjr](https://redirect.github.com/arendjr)! - 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
}
}
```
-
[`9d5d95f`](https://redirect.github.com/biomejs/biome/commit/9d5d95fffd5734522c8911db18c6d16ee6a96756)
Thanks [@​arendjr](https://redirect.github.com/arendjr)! - 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": "error",
"dot-notation": "off"
}
}
```
...is now migrated to...
```json
{
"linter": {
"rules": {
"complexity": {
"useLiteralKeys": "error"
}
}
}
}
```
...because `error` is higher than `off`.
-
[`9d5d95f`](https://redirect.github.com/biomejs/biome/commit/9d5d95fffd5734522c8911db18c6d16ee6a96756)
Thanks [@​arendjr](https://redirect.github.com/arendjr)! - Add
[useSymbolDescription](https://biomejs.dev/linter/rules/use-symbol-description/).
-
[`9d5d95f`](https://redirect.github.com/biomejs/biome/commit/9d5d95fffd5734522c8911db18c6d16ee6a96756)
Thanks [@​arendjr](https://redirect.github.com/arendjr)! -
Enhanced the command `migrate eslint`. Now the command shows which
ESLint rules were migrated,
and which rules aren't supported yet.
./eslint.config.js migrate
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
ℹ 42% (3/7) of the rules have been migrated.
ℹ Migrated rules:
- getter-return
- prefer-const
- @​typescript-eslint/require-await
ℹ Rules that can be migrated to an inspired rule using
--include-inspired:
- @​typescript-eslint/parameter-properties
ℹ Rules that can be migrated to a nursery rule using --include-nursery:
- @​typescript-eslint/switch-exhaustiveness-check
ℹ Stylistic rules that the formatter may support (manual migration
required):
- semi
ℹ Unsupported rules:
- block-scoped-var
configuration
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
ℹ Migration results:
- ./biome.json: configuration successfully migrated.
-
[`9d5d95f`](https://redirect.github.com/biomejs/biome/commit/9d5d95fffd5734522c8911db18c6d16ee6a96756)
Thanks [@​arendjr](https://redirect.github.com/arendjr)! -
Suppression of syntax rules
Added support for suppressing syntax rules. Syntax rules are particular
rules meant **to complement the parser**, hence they can't be
configured.
Biome now allows to suppress those rules. This can, for example, be
useful in case the rule is affected by a bug. However, this is more an
escape hatch, so if a syntax rule requires a suppression, please file an
issue.
Example:
```typescript
// biome-ignore syntax/correctness/noTypeOnlyImportAttributes: bug
import type { MyType } from "my-esm-pkg" with { "resolution-mode":
"import" };
```
Biome now requires all `biome-ignore-start` suppressions to have an
equivalent `biome-ignore-end` comment.
-
[`9d5d95f`](https://redirect.github.com/biomejs/biome/commit/9d5d95fffd5734522c8911db18c6d16ee6a96756)
Thanks [@​arendjr](https://redirect.github.com/arendjr)! - Add a
new lint rule `noConstantBinaryExpression`.
This rule is inspired from ESLint's
[no-constant-binary-expression](https://eslint.org/docs/latest/rules/no-constant-binary-expression)
rule.
-
[`9d5d95f`](https://redirect.github.com/biomejs/biome/commit/9d5d95fffd5734522c8911db18c6d16ee6a96756)
Thanks [@​arendjr](https://redirect.github.com/arendjr)! - The CLI
options `--only` and `--skip` now accept rule and action names without
prefixing the group name.
Previously `--only=noDebugger` was rejected.
You had to add the group name: `--only=suspicious/noDebugger`.
-
[`9d5d95f`](https://redirect.github.com/biomejs/biome/commit/9d5d95fffd5734522c8911db18c6d16ee6a96756)
Thanks [@​arendjr](https://redirect.github.com/arendjr)! - Fixed
[#​3574](https://redirect.github.com/biomejs/biome/issues/3574):
`noUnusedImports` now reports empty named imports and suggests their
removal.
The rule now suggests the removal of empty named imports such as:
```diff
- import {} from "mod";
```
-
[`9d5d95f`](https://redirect.github.com/biomejs/biome/commit/9d5d95fffd5734522c8911db18c6d16ee6a96756)
Thanks [@​arendjr](https://redirect.github.com/arendjr)! - Added
the new rule
[`useAdjacentGetterSetter`](https://biomejs.dev/linter/rules/use-adjacent-getter-setter),
which enforces getters and setters for the same property
to be adjacent in class and object definitions.
**Example (Invalid): Name getter and setter are not adjacent:**
```js
class User {
get name() {
return this._name;
}
constructor() {}
set name(value) {
this._name = value;
}
}
```
\*\*Example (Invalid): Getter should go before the setter.
```js
const user = {
set name(value) {
this._name = value;
},
get name() {
return this._name;
},
};
```
**Example (Valid): Name getter and setter are adjacent:**
```js
class User {
get name() {
return this._name;
}
set name(value) {
this._name = value;
}
get age() {
return this._age;
}
set age(age) {
this._age = age;
}
}
```
-
[`9d5d95f`](https://redirect.github.com/biomejs/biome/commit/9d5d95fffd5734522c8911db18c6d16ee6a96756)
Thanks [@​arendjr](https://redirect.github.com/arendjr)! - Added
new rule
[useConsistentResponse](https://biomejs.dev/linter/rules/use-consistent-response)
which suggests to use static
[Response.json()](https://developer.mozilla.org/en-US/docs/Web/API/Response/json)
and
[Response.redirect()](https://developer.mozilla.org/en-US/docs/Web/API/Response/redirect_static)
methods instead of `new Response` when possible.
Example:
```js
new Response(JSON.stringify({ value: 1 }));
Response.json({ value: 1 });
```
-
[`9d5d95f`](https://redirect.github.com/biomejs/biome/commit/9d5d95fffd5734522c8911db18c6d16ee6a96756)
Thanks [@​arendjr](https://redirect.github.com/arendjr)! - Biome
users can now configure code actions from linter rules as well as assist
actions directly in the settings of their IDE/editor.
For example, let's consider the lint rule
[`noSwitchDeclarations`](https://biomejs.dev/linter/rules/no-switch-declarations/),
which has an unsafe fix.
Previously, if you wanted to use this rule, you were "forced" to enable
it via configuration, and if you wanted to apply its fix when you saved
a file, you were forced to mark the fix as safe:
```json
{
"linter": {
"rules": {
"correctness": {
"noSwitchDeclarations": {
"level": "error",
"fix": "safe"
}
}
}
}
}
```
Now, you can benefit from the code action without making the fix safe
for the entire project. IDEs and editors that are LSP compatible allow
to list a series of "filters" or code actions that can be applied on
save. In the case of VS Code, you will need to add the following snippet
in the `settings.json`:
```json
{
"editor.codeActionsOnSave": {
"quickfix.biome.correctness.noSwitchDeclarations": "explicit"
}
}
```
Upon save, Biome will inform the editor the apply the code action of the
rule `noSwitchDeclarations`.
-
[`9d5d95f`](https://redirect.github.com/biomejs/biome/commit/9d5d95fffd5734522c8911db18c6d16ee6a96756)
Thanks [@​arendjr](https://redirect.github.com/arendjr)! - Fixed
[#​3401](https://redirect.github.com/biomejs/biome/issues/3401):
`noUnusedImports` now keeps comments separated from the import with a
blank line.
For example:
```diff
// Orphan comment
- // Header comment
- import {} from "mod";
```
-
[`9d5d95f`](https://redirect.github.com/biomejs/biome/commit/9d5d95fffd5734522c8911db18c6d16ee6a96756)
Thanks [@​arendjr](https://redirect.github.com/arendjr)! - Added a
new `propertyAssignment` option to the `noParameterAssign` rule.
This option allows to configure whether property assignments on function
parameters are permitted.
By default, `propertyAssignment` is set to `allow`.
Setting it to `deny` enforces stricter immutability by disallowing
property mutations on function parameters.
-
[`9d5d95f`](https://redirect.github.com/biomejs/biome/commit/9d5d95fffd5734522c8911db18c6d16ee6a96756)
Thanks [@​arendjr](https://redirect.github.com/arendjr)! - The
formatter option `bracketSpacing` is now also supported in JSON files.
-
[`9d5d95f`](https://redirect.github.com/biomejs/biome/commit/9d5d95fffd5734522c8911db18c6d16ee6a96756)
Thanks [@​arendjr](https://redirect.github.com/arendjr)! -
`useValidTypeof` now accepts comparisons with variables.
Previously, the rule required to compare a `typeof` expression against
another `typeof` expression or a valid string literal. We now accept
more cases, notably comparison against a variable:
```js
if (typeof foo === bar) {
// ...
}
```
-
[`9d5d95f`](https://redirect.github.com/biomejs/biome/commit/9d5d95fffd5734522c8911db18c6d16ee6a96756)
Thanks [@​arendjr](https://redirect.github.com/arendjr)! - Added
the new rule
[`noNestedComponentDefinitions`](https://biomejs.dev/linter/rules/no-nested-component-definitions),
which disallows nested component definitions in React components.
This rule is useful for preventing potential performance issues and
improving code readability by ensuring that components are defined at
the top level.
**Example (Invalid):**
```jsx
function ParentComponent() {
function ChildComponent() {
return <div>Hello</div>;
}
return <ChildComponent />;
}
```
**Example (Valid):**
```jsx
function ChildComponent() {
return <div>Hello</div>;
}
function ParentComponent() {
return <ChildComponent />;
}
```
-
[`9d5d95f`](https://redirect.github.com/biomejs/biome/commit/9d5d95fffd5734522c8911db18c6d16ee6a96756)
Thanks [@​arendjr](https://redirect.github.com/arendjr)! - Added
the new rule
[`noDestructuredProps`](https://biomejs.dev/linter/rules/no-destructured-props/),
which disallow the use of destructured props in Solid projects.
-
[`9d5d95f`](https://redirect.github.com/biomejs/biome/commit/9d5d95fffd5734522c8911db18c6d16ee6a96756)
Thanks [@​arendjr](https://redirect.github.com/arendjr)! - You can
now enable lint rules using the default severity suggested by Biome
using the new variant `"on"`, when enabling a rule.
For example, the default severity of the rule `style.noVar` is `e
</details>
---
### Configuration
📅 **Schedule**: Branch creation - "every weekday" (UTC), Automerge - At
any time (no schedule defined).
🚦 **Automerge**: Enabled.
♻ **Rebasing**: Whenever PR is behind base branch, 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/apify/apify-cli).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0MC41MC4wIiwidXBkYXRlZEluVmVyIjoiNDAuNTAuMCIsInRhcmdldEJyYW5jaCI6Im1hc3RlciIsImxhYmVscyI6W119-->
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>1 parent 67c1543 commit 1584450
2 files changed
+39
-39
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
111 | 111 | | |
112 | 112 | | |
113 | 113 | | |
114 | | - | |
| 114 | + | |
115 | 115 | | |
116 | 116 | | |
117 | 117 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
154 | 154 | | |
155 | 155 | | |
156 | 156 | | |
157 | | - | |
158 | | - | |
159 | | - | |
160 | | - | |
161 | | - | |
162 | | - | |
163 | | - | |
164 | | - | |
165 | | - | |
166 | | - | |
167 | | - | |
168 | | - | |
| 157 | + | |
| 158 | + | |
| 159 | + | |
| 160 | + | |
| 161 | + | |
| 162 | + | |
| 163 | + | |
| 164 | + | |
| 165 | + | |
| 166 | + | |
| 167 | + | |
| 168 | + | |
169 | 169 | | |
170 | 170 | | |
171 | 171 | | |
| |||
185 | 185 | | |
186 | 186 | | |
187 | 187 | | |
188 | | - | |
| 188 | + | |
189 | 189 | | |
190 | 190 | | |
191 | 191 | | |
192 | | - | |
193 | | - | |
194 | | - | |
| 192 | + | |
| 193 | + | |
| 194 | + | |
195 | 195 | | |
196 | 196 | | |
197 | 197 | | |
198 | 198 | | |
199 | | - | |
200 | | - | |
201 | | - | |
| 199 | + | |
| 200 | + | |
| 201 | + | |
202 | 202 | | |
203 | 203 | | |
204 | 204 | | |
205 | 205 | | |
206 | | - | |
207 | | - | |
208 | | - | |
| 206 | + | |
| 207 | + | |
| 208 | + | |
209 | 209 | | |
210 | 210 | | |
211 | 211 | | |
212 | 212 | | |
213 | | - | |
214 | | - | |
215 | | - | |
| 213 | + | |
| 214 | + | |
| 215 | + | |
216 | 216 | | |
217 | 217 | | |
218 | 218 | | |
219 | 219 | | |
220 | | - | |
221 | | - | |
222 | | - | |
| 220 | + | |
| 221 | + | |
| 222 | + | |
223 | 223 | | |
224 | 224 | | |
225 | 225 | | |
226 | 226 | | |
227 | | - | |
228 | | - | |
229 | | - | |
| 227 | + | |
| 228 | + | |
| 229 | + | |
230 | 230 | | |
231 | 231 | | |
232 | 232 | | |
233 | 233 | | |
234 | | - | |
235 | | - | |
236 | | - | |
| 234 | + | |
| 235 | + | |
| 236 | + | |
237 | 237 | | |
238 | 238 | | |
239 | 239 | | |
240 | 240 | | |
241 | | - | |
242 | | - | |
243 | | - | |
| 241 | + | |
| 242 | + | |
| 243 | + | |
244 | 244 | | |
245 | 245 | | |
246 | 246 | | |
| |||
2412 | 2412 | | |
2413 | 2413 | | |
2414 | 2414 | | |
2415 | | - | |
| 2415 | + | |
2416 | 2416 | | |
2417 | 2417 | | |
2418 | 2418 | | |
| |||
0 commit comments