Releases · biomejs/biome

@unvalley

CLI

Bug fixes

Fix #3069, prevent overwriting paths when using --staged or --changed options. Contributed by @unvalley
Fix a case where the file link inside a diagnostic wasn't correctly displayed inside a terminal run by VSCode. Contributed by @uncenter

Configuration

Bug fixes

Fix #3067, by assigning the correct default value to indentWidth. Contributed by @ematipico

Formatter

Bug fixes

Fix the bug where whitespace after the & character in CSS nesting was incorrectly trimmed, ensuring proper targeting of child classes #3061. Contributed by @denbezrukov
Fix #3068 where the CSS formatter was inadvertently converting variable declarations and function calls to lowercase. Contributed by @denbezrukov
Fix the formatting of CSS grid layout properties. Contributed by @denbezrukov

Linter

Bug fixes

The noEmptyBlock css lint rule now treats empty blocks containing comments as valid ones. Contributed by @Sec-ant
useLiteralKeys no longer reports quoted member names (#3085).

Previously useLiteralKeys reported quoted member names that can be unquoted.
For example, the rule suggested the following fix:
```
- const x = { "prop": 0 };
+ const x = { prop: 0 };
```
This conflicted with the option quoteProperties of our formatter.

The rule now ignores quoted member names.

Contributed by @Conaclos
noEmptyInterface now ignores empty interfaces in ambient modules (#3110). Contributed by @Conaclos
noUnusedVariables and noUnusedFunctionParameters no longer report the parameters of a constructor type (#3135).

Previously, arg was reported as unused in a constructor type like:
```
export type Classlike = new (arg: unknown) => string;
```
Contributed by @Conaclos
noStringCaseMismatch now ignores escape sequences (#3134).

The following code is no longer reported by the rule:
```
s.toUpperCase() === "\u001b";
```
Contributed by @Conaclos

Parser

New features

Implemented CSS Unknown At-Rule parsing, allowing the parser to gracefully handle unsupported or unrecognized CSS at-rules. Contributed by @denbezrukov

Bug fixes

Fix #3055 CSS: Layout using named grid lines is now correctly parsed. Contributed by @denbezrukov
Fix #3091. Allows the parser to handle nested style rules and at-rules properly, enhancing the parser's compatibility with the CSS Nesting Module. Contributed by @denbezrukov

Other changes

fix(docs): incorrect snippets by @ematipico in #3059
feat(grit): parse Grit literal snippets by @arendjr in #3051
chore: delete stale snapshots by @siosio34 in #3062
fix(noUnusedFunctionParameters): fix typo in documentation code example by @printfn in #3065
feat(graphql_parser): parse enum extension by @vohoanglong0107 in #3044
docs(useNamingConvention): fix conventions example by @Conaclos in #3070
docs(readme): fix replace apply by write option by @Jayllyz in #3071
refactor: use --write instead of --apply in CLI advices by @Conaclos in #3083
fix: use-adjacent-overload-signature diagnostic by @chansuke in #3095
chore: fix JSON schema for biome config file by @Conaclos in #3109
chore(deps): update dependency dprint to v0.46.1 by @renovate in #3042
fix(deps): update rust crates by @renovate in #3041
refactor(lint): add SonarJs and UnusedImports rule sources by @Conaclos in #3128
fix(graphql_parser): allow backlash in block string by @vohoanglong0107 in #3113
feat(graphql_parser): parse input object type extension by @vohoanglong0107 in #3112
feat(biome_css_analyzer): implement selector-pseudo-class-no-unknown by @tunamaguro in #3034
fix(deps): update rust crate roaring to 0.10.5 by @renovate in #3144
chore(deps): update rust crate regex to 1.10.5 by @renovate in #3141
chore(deps): update rust crate enumflags2 to 0.7.10 by @renovate in #3139
chore(deps): update dependency dprint to v0.46.2 by @renovate in #3138
chore(deps): update rust docker tag to v1.78.0 by @renovate in #3147
ci: add check for rules docs by @ematipico in #3150
ci: add check for rules docs by @ematipico in #3152
chore: format package.json like npm does by @ematipico in #3155
feat(biome_css_analyzer): noShorthandPropertyOverrides by @neokidev in #2958
feat(biome_css_analyzer): useConsistentGridAreas by @chansuke in #2940

New Contributors

@siosio34 made their first contribution in #3062
@Jayllyz made their first contribution in #3071

Full Changelog: cli/v1.8.0...cli/v1.8.1

@arendjr

Analyzer

New features

Allow suppression comments to suppress individual instances of rules. This is
used for the lint rule useExhaustiveDependencies, which is now able to
suppress specific dependencies. Fixes #2509. Contributed by @arendjr

Enhancements

Assume Astro object is always a global when processing .astro files. Contributed by @minht11
Assume Vue compiler macros are globals when processing .vue files. (#2771) Contributed by @dyc3

CLI

New features

New clean command. Use this new command to clean after the biome-logs directory, and remove all the log files.
```
biome clean
```
Add two new options --only and --skip to the command biome lint (#58).

The --only option allows you to run a given rule or rule group,
For example, the following command runs only the style/useNamingConvention and style/noInferrableTypes rules.
If the rule is disabled in the configuration, then its severity level is set to error for a recommended rule or warn otherwise.
```
biome lint --only=style/useNamingConvention --only=style/noInferrableTypes
```
Passing a group does not change the severity level of the rules in the group.
All the disabled rules in the group will remain disabled.
To ensure that the group is run, the recommended field of the group is enabled.
The nursery group cannot be passed, as no rules are enabled by default in the nursery group.

The --skip option allows you to skip the execution of a given group or a given rule.
For example, the following command skips the style group and the suspicious/noExplicitAny rule.
```
biome lint --skip=style --skip=suspicious/noExplicitAny
```
You can also use --only and --skip together. --skip oevrrides --only.
The following command executes only the rules from the style group, but the style/useNamingConvention rule.
```
biome lint --only=style --skip=style/useNamingConvention
```
These options are compatible with other options such as --write (previously --apply), and --reporter.

Contributed by @Conaclos
Add new command biome clean. Use this command to purge all the logs emitted by the Biome daemon. This command is really useful, because the Biome daemon tends
log many files and contents during its lifecycle. This means that if your editor is open for hours (or even days), the biome-logs folder could become quite heavy. Contributed by @ematipico
Add support for formatting and linting CSS files from the CLI. These operations are opt-in for the time being.

If you don't have a configuration file, you can enable these features with --css-formatter-enabled and --css-linter-enabled:
```
biome check --css-formatter-enabled=true --css-linter-enabled=true ./
```
Contributed by @ematipico
Add new CLI options to control the CSS formatting. Check the CLI reference page for more details. Contributed by @ematipico
Add new options --write, --fix (alias of --write) and --unsafe to the command biome lint and biome check.
Add a new option --fix (alias of --write) to the command biome format and biome migrate.
```
biome <lint|check> --<write|fix> [--unsafe]
biome format --<write|fix>
biome migrate --<write|fix>
```
The biome <lint|check> --<write|fix> has the same behavior as biome <lint|check> --apply.
The biome <lint|check> --<write|fix> --unsafe has the same behavior as biome <lint|check> --apply-unsafe.
The biome format --fix has the same behavior as biome format --write.
The biome migrate --fix has the same behavior as biome migrate --write.

This change allows these commands to write modifications in the same options.
With this change, the --apply and --apply-unsafe options are deprecated.

Contributed by @unvalley

Enhancements

Biome now executes commands (lint, format, check and ci) on the working directory by default. #2266 Contributed by @unvalley
```
- biome check .
+ biome check    # You can run the command without the path
```
biome migrate eslint now tries to convert ESLint ignore patterns into Biome ignore patterns.

ESLint uses gitignore patterns.
Biome now tries to convert these patterns into Biome ignore patterns.

For example, the gitignore pattern /src is a relative path to the file in which it appears.
Biome now recognizes this and translates this pattern to ./src.

Contributed by @Conaclos
biome migrate eslint now supports the eslintIgnore field in package.json.

ESLint allows the use of package.json as an ESLint configuration file.
ESLint supports two fields: eslintConfig and eslintIgnore.
Biome only supported the former. It now supports both.

Contributed by @Conaclos
biome migrate eslint now propagates NodeJS errors to the user.

This will help users to identify why Biome is unable to load some ESLint configurations.

Contributed by @Conaclos

Add a new --reporter called summary. This reporter will print diagnostics in a different way, based on the tools (formatter, linter, etc.) that are executed.
Import sorting and formatter shows the name of the files that require formatting. Instead, the linter will group the number of rules triggered and the number of errors/warnings:

Formatter ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
The following files needs to be formatted:
main.ts
index.ts

Organize Imports ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
The following files needs to have their imports sorted:
main.ts
index.ts

Analyzer ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Some analyzer rules were triggered

Rule Name                                               Diagnostics
lint/suspicious/noImplicitAnyLet                        12 (12 error(s), 0 warning(s), 0 info(s))
lint/suspicious/noDoubleEquals                          8 (8 error(s), 0 warning(s), 0 info(s))
lint/suspicious/noRedeclare                             12 (12 error(s), 0 warning(s), 0 info(s))
lint/suspicious/noDebugger                              20 (20 error(s), 0 warning(s), 0 info(s))

Contributed by @ematipico

biome ci now enforces printing the output using colours. If you were previously using --colors=force, you can remove it because it's automatically set. Contributed by @ematipico

Add a new --reporter called github. This reporter will print diagnostics using GitHub workflow commands:

::error title=lint/suspicious/noDoubleEquals,file=main.ts,line=4,endLine=4,col=3,endColumn=5::Use === instead of ==
::error title=lint/suspicious/noDebugger,file=main.ts,line=6,endLine=6,col=1,endColumn=9::This is an unexpected use of the debugger statement.
::error title=lint/nursery/noEvolvingAny,file=main.ts,line=8,endLine=8,col=5,endColumn=6::This variable's type is not allowed to evolve implicitly, leading to potential any types.

Contributed by @ematipico

Add a new --reporter called junit. This reporter will print diagnostics using GitHub workflow commands:

<?xml version="1.0" encoding="UTF-8"?>
<testsuites name="Biome" tests="16" failures="16" errors="20" time="<TIME>">
  <testsuite name="main.ts" tests="1" disabled="0" errors="0" failures="1" package="org.biome">
      <testcase name="org.biome.lint.suspicious.noDoubleEquals" line="4" column="3">
          <failure message="Use === instead of ==. == is only allowed when comparing against `null`">line 3, col 2, Use === instead of ==. == is only allowed when comparing against `null`</failure>
      </testcase>
  </testsuite>
  <testsuite name="main.ts" tests="1" disabled="0" errors="0" failures="1" package="org.biome">
      <testcase name="org.biome.lint.suspicious.noDebugger" line="6" column="1">
          <failure message="This is an unexpected use of the debugger statement.">line 5, col 0, This is an unexpected use of the debugger statement.</failure>
      </testcase>
  </testsuite>
  <testsuite name="main.ts" tests="1" disabled="0" errors="0" failures="1" package="org.biome">
      <testcase name="org.biome.lint.nursery.noEvolvingAny" line="8" column="5">
          <failure message="This variable&apos;s type is not allowed to evolve implicitly, leading to potential any types.">line 7, col 4, This variable&apos;s type is not allowed to evolve implicitly, leading to potential any types.</failure>
      </testcase>
  </testsuite>
</testsuites>

Contributed by @ematipico

Bug fixes

Fix #3024, where running biome init would create biome.json even if biome.jsonc already exists. Contributed by @minht11

Configuration

New features

Add an rule option fix to override the code fix kind of a rule (#2882).

A rule can provide a safe or an unsafe code action.
You can now tune the kind of code actions thanks to the fix option.
This rule option takes a value among:
- none: the rule no longer emits code actions.
- safe: the rule emits safe code action.
- unsafe: the rule emits unsafe code action.
The following configuration disables the code actions of noUnusedVariables, makes the emitted code actions of style/useConst a...

@dyc3

Analyzer

Enhancements

Assume Vue compiler macros are globals when processing .vue files. (#2771) Contributed by @dyc3

CLI

New features

Add a new option --rule to the command biome lint (#58).

This new option allows you to execute a single rule or a rule group.
This option is convenient to test a rule or apply the code fixes of a single rule.

For example, you can execute the style/useNamingConvention rule on the working directory:
```
biome lint --rule=style/useNamingConvention ./
```
If the rule has a code action (autofix), you can use --apply to apply the fix:
```
biome lint --rule=style/useNamingConvention --apply ./
```
The option takes the rule options in the Biome configuration file into account.
Only, the severity level of the rule is overridden by its default value,
i.e. error for a recommended rule or warn otherwise.

You can also run a group of rules:
```
biome lint --rule=suspicious src/main.js
```
In this case, the severity level of a rule is not overridden.
Thus, the disabled rules stay disabled.
To ensure that the group is run, the recommended field of the group is turned on.
The nursery group cannot be passed because no rules are enabled in the nursery group by default.

The option is compatible with other options such as --apply, --apply-unsafe and --reporter.

Contributed by @Conaclos
Add new command biome clean. Use this command to purge all the logs emitted by the Biome daemon. This command is really useful, because the Biome daemon tends
log many files and contents during its lifecycle. This means that if your editor is open for hours (or even days), the biome-logs folder could become quite heavy. Contributed by @ematipico
Add support for formatting and linting CSS files from the CLI. These operations are opt-in for the time being.

If you don't have a configuration file, you can enable these features with --css-formatter-enabled and --css-linter-enabled:
```
biome check --css-formatter-enabled=true --css-linter-enabled=true ./
```
Contributed by @ematipico
Add new CLI options to control the CSS formatting. Check the CLI reference page for more details. Contributed by @ematipico
Add new options --write, --fix (alias of --write) and --unsafe to the command biome lint and biome check.
Add a new option --fix (alias of --write) to the command biome format and biome migrate.
```
biome <lint|check> --<write|fix> [--unsafe]
biome format --<write|fix>
biome migrate --<write|fix>
```
The biome <lint|check> --<write|fix> has the same behavior as biome <lint|check> --apply.
The biome <lint|check> --<write|fix> --unsafe has the same behavior as biome <lint|check> --apply-unsafe.
The biome format --fix has the same behavior as biome format --write.
The biome migrate --fix has the same behavior as biome migrate --write.

This change allows these commands to write modifications in the same options.
With this change, the --apply and --apply-unsafe options are deprecated.

Contributed by @unvalley

Enhancements

Biome now executes commands (lint, format, check and ci) on the working directory by default. #2266 Contributed by @unvalley
```
- biome check .
+ biome check    # You can run the command without the path
```
biome migrate eslint now tries to convert ESLint ignore patterns into Biome ignore patterns.

ESLint uses gitignore patterns.
Biome now tries to convert these patterns into Biome ignore patterns.

For example, the gitignore pattern /src is a relative path to the file in which it appears.
Biome now recognizes this and translates this pattern to ./src.

Contributed by @Conaclos
biome migrate eslint now supports the eslintIgnore field in package.json.

ESLint allows the use of package.json as an ESLint configuration file.
ESLint supports two fields: eslintConfig and eslintIgnore.
Biome only supported the former. It now supports both.

Contributed by @Conaclos
biome migrate eslint now propagates NodeJS errors to the user.

This will help users to identify why Biome is unable to load some ESLint configurations.

Contributed by @Conaclos

Add a new --reporter called summary. This reporter will print diagnostics in a different way, based on the tools (formatter, linter, etc.) that are executed.
Import sorting and formatter shows the name of the files that require formatting. Instead, the linter will group the number of rules triggered and the number of errors/warnings:

Formatter ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
The following files needs to be formatted:
main.ts
index.ts

Organize Imports ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
The following files needs to have their imports sorted:
main.ts
index.ts

Analyzer ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Some analyzer rules were triggered

Rule Name                                               Diagnostics
lint/suspicious/noImplicitAnyLet                        12 (12 error(s), 0 warning(s), 0 info(s))
lint/suspicious/noDoubleEquals                          8 (8 error(s), 0 warning(s), 0 info(s))
lint/suspicious/noRedeclare                             12 (12 error(s), 0 warning(s), 0 info(s))
lint/suspicious/noDebugger                              20 (20 error(s), 0 warning(s), 0 info(s))

Contributed by @ematipico

biome ci now enforces printing the output using colours. If you were previously using --colors=force, you can remove it because it's automatically set. Contributed by @ematipico

Configuration

New features

Add an rule option fix to override the code fix kind of a rule (#2882).

A rule can provide a safe or an unsafe code action.
You can now tune the kind of code actions thanks to the fix option.
This rule option takes a value among:

none: the rule no longer emits code actions.
safe: the rule emits safe code action.
unsafe: the rule emits unsafe code action.

The following configuration disables the code actions of noUnusedVariables, makes the emitted code actions of style/useConst and style/useTemplate unsafe and safe respectively.

{
  "linter": {
    "rules": {
      "correctness": {
        "noUnusedVariables": {
          "level": "error",
          "fix": "none"
        },
        "style": {
          "useConst": {
            "level": "warn",
            "fix": "unsafe"
          },
          "useTemplate": {
            "level": "warn",
            "fix": "safe"
          }
        }
      }
    }
  }
}

Contributed by @Conaclos

Add option javascript.linter.enabled to control the linter for JavaScript (and its super languages) files. Contributed by @ematipico
Add option json.linter.enabled to control the linter for JSON (and its super languages) files. Contributed by @ematipico
Add option css.linter.enabled to control the linter for CSS (and its super languages) files. Contributed by @ematipico
Add option css.formatter, to control the formatter options for CSS (and its super languages) files. Contributed by @ematipico

Enhancements

The javascript.formatter.trailingComma option is deprecated and renamed to javascript.formatter.trailingCommas. The corresponding CLI option --trailing-comma is also deprecated and renamed to --trailing-commas. Details can be checked in #2492. Contributed by @Sec-ant

Editors

New features

Add support for LSP Workspaces

Bug fixes

Fixes #2781, by correctly computing the configuration to apply to a specific file. Contributed by @ematipico

Formatter

Bug fixes

Fix #2470 by avoid introducing linebreaks in single line string interpolations. Contributed by @ah-yu
Resolve deadlocks by narrowing the scope of locks. Contributed by @mechairoi
Fix #2782 by computing the enabled rules by taking the override settings into consideration. Contributed by @ematipico

JavaScript APIs

Linter

New features

Add nursery/useThrowOnlyError. Contributed by @minht11
Add nursery/useImportExtensions. Contributed by @minht11

useNamingConvention now supports an option to enforce custom conventions (#1900).

For example, you can enforce the use of a prefix for private class members:

{
	"linter": {
		"rules": {
			"style": {
				"useNamingConvention": {
					"level": "error",
					"options": {
						"conventions": [
							{
								"selector": {
									"kind": "classMember",
									"modifiers": ["private"]
								},
								"match": "_(.*)",
                "formats": ["camelCase"]
							}
						]
					}
				}
			}
		}
	}
}

Please, find more details in the rule documentation.

Contributed by @Conaclos

Add [nursery/useNumberToFixedDigitsArgument](https://biomejs.dev/linter/rules/use-number-to-fixed-...

@dyc3

Analyzer

Enhancements

Assume Vue compiler macros are globals when processing .vue files. (#2771) Contributed by @dyc3

CLI

New features

Add a new option --rule to the command biome lint (#58).

This new option allows you to execute a single rule or a rule group.
This option is convenient to test a rule or apply the code fixes of a single rule.

For example, you can execute the style/useNamingConvention rule on the working directory:
```
biome lint --rule=style/useNamingConvention ./
```
If the rule has a code action (autofix), you can use --apply to apply the fix:
```
biome lint --rule=style/useNamingConvention --apply ./
```
The option takes the rule options in the Biome configuration file into account.
Only, the severity level of the rule is overridden by its default value,
i.e. error for a recommended rule or warn otherwise.

You can also run a group of rules:
```
biome lint --rule=suspicious src/main.js
```
In this case, the severity level of a rule is not overridden.
Thus, the disabled rules stay disabled.
To ensure that the group is run, the recommended field of the group is turned on.
The nursery group cannot be passed because no rules are enabled in the nursery group by default.

The option is compatible with other options such as --apply, --apply-unsafe and --reporter.

Contributed by @Conaclos
Add new command biome clean. Use this command to purge all the logs emitted by the Biome daemon. This command is really useful, because the Biome daemon tends
log many files and contents during its lifecycle. This means that if your editor is open for hours (or even days), the biome-logs folder could become quite heavy. Contributed by @ematipico
Add support for formatting and linting CSS files from the CLI. These operations are opt-in for the time being.

If you don't have a configuration file, you can enable these features with --css-formatter-enabled and --css-linter-enabled:
```
biome check --css-formatter-enabled=true --css-linter-enabled=true ./
```
Contributed by @ematipico
Add new CLI options to control the CSS formatting. Check the CLI reference page for more details. Contributed by @ematipico
Add new options --write, --fix (alias of --write) and --unsafe to the command biome lint and biome check.
Add a new option --fix (alias of --write) to the command biome format and biome migrate.
```
biome <lint|check> --<write|fix> [--unsafe]
biome format --<write|fix>
biome migrate --<write|fix>
```
The biome <lint|check> --<write|fix> has the same behavior as biome <lint|check> --apply.
The biome <lint|check> --<write|fix> --unsafe has the same behavior as biome <lint|check> --apply-unsafe.
The biome format --fix has the same behavior as biome format --write.
The biome migrate --fix has the same behavior as biome migrate --write.

This change allows these commands to write modifications in the same options.
With this change, the --apply and --apply-unsafe options are deprecated.

Contributed by @unvalley

Enhancements

Biome now executes commands (lint, format, check and ci) on the working directory by default. #2266 Contributed by @unvalley
```
- biome check .
+ biome check    # You can run the command without the path
```
biome migrate eslint now tries to convert ESLint ignore patterns into Biome ignore patterns.

ESLint uses gitignore patterns.
Biome now tries to convert these patterns into Biome ignore patterns.

For example, the gitignore pattern /src is a relative path to the file in which it appears.
Biome now recognizes this and translates this pattern to ./src.

Contributed by @Conaclos
biome migrate eslint now supports the eslintIgnore field in package.json.

ESLint allows the use of package.json as an ESLint configuration file.
ESLint supports two fields: eslintConfig and eslintIgnore.
Biome only supported the former. It now supports both.

Contributed by @Conaclos
biome migrate eslint now propagates NodeJS errors to the user.

This will help users to identify why Biome is unable to load some ESLint configurations.

Contributed by @Conaclos

Add a new --reporter called summary. This reporter will print diagnostics in a different way, based on the tools (formatter, linter, etc.) that are executed.
Import sorting and formatter shows the name of the files that require formatting. Instead, the linter will group the number of rules triggered and the number of errors/warnings:

Formatter ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
The following files needs to be formatted:
main.ts
index.ts

Organize Imports ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
The following files needs to have their imports sorted:
main.ts
index.ts

Analyzer ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Some analyzer rules were triggered

Rule Name                                               Diagnostics
lint/suspicious/noImplicitAnyLet                        12 (12 error(s), 0 warning(s), 0 info(s))
lint/suspicious/noDoubleEquals                          8 (8 error(s), 0 warning(s), 0 info(s))
lint/suspicious/noRedeclare                             12 (12 error(s), 0 warning(s), 0 info(s))
lint/suspicious/noDebugger                              20 (20 error(s), 0 warning(s), 0 info(s))

Contributed by @ematipico

biome ci now enforces printing the output using colours. If you were previously using --colors=force, you can remove it because it's automatically set. Contributed by @ematipico

Configuration

New features

Add an rule option fix to override the code fix kind of a rule (#2882).

A rule can provide a safe or an unsafe code action.
You can now tune the kind of code actions thanks to the fix option.
This rule option takes a value among:

none: the rule no longer emits code actions.
safe: the rule emits safe code action.
unsafe: the rule emits unsafe code action.

The following configuration disables the code actions of noUnusedVariables, makes the emitted code actions of style/useConst and style/useTemplate unsafe and safe respectively.

{
  "linter": {
    "rules": {
      "correctness": {
        "noUnusedVariables": {
          "level": "error",
          "fix": "none"
        },
        "style": {
          "useConst": {
            "level": "warn",
            "fix": "unsafe"
          },
          "useTemplate": {
            "level": "warn",
            "fix": "safe"
          }
        }
      }
    }
  }
}

Contributed by @Conaclos

Add option javascript.linter.enabled to control the linter for JavaScript (and its super languages) files. Contributed by @ematipico
Add option json.linter.enabled to control the linter for JSON (and its super languages) files. Contributed by @ematipico
Add option css.linter.enabled to control the linter for CSS (and its super languages) files. Contributed by @ematipico
Add option css.formatter, to control the formatter options for CSS (and its super languages) files. Contributed by @ematipico

Enhancements

The javascript.formatter.trailingComma option is deprecated and renamed to javascript.formatter.trailingCommas. The corresponding CLI option --trailing-comma is also deprecated and renamed to --trailing-commas. Details can be checked in #2492. Contributed by @Sec-ant

Editors

New features

Add support for LSP Workspaces

Bug fixes

Fixes #2781, by correctly computing the configuration to apply to a specific file. Contributed by @ematipico

Formatter

Bug fixes

Fix #2470 by avoid introducing linebreaks in single line string interpolations. Contributed by @ah-yu
Resolve deadlocks by narrowing the scope of locks. Contributed by @mechairoi
Fix #2782 by computing the enabled rules by taking the override settings into consideration. Contributed by @ematipico

JavaScript APIs

Linter

New features

Add nursery/useThrowOnlyError. Contributed by @minht11
Add nursery/useImportExtensions. Contributed by @minht11

useNamingConvention now supports an option to enforce custom conventions (#1900).

For example, you can enforce the use of a prefix for private class members:

{
	"linter": {
		"rules": {
			"style": {
				"useNamingConvention": {
					"level": "error",
					"options": {
						"conventions": [
							{
								"selector": {
									"kind": "classMember",
									"modifiers": ["private"]
								},
								"match": "_(.*)",
                "formats": ["camelCase"]
							}
						]
					}
				}
			}
		}
	}
}

Please, find more details in the rule documentation.

Contributed by @Conaclos

Add [nursery/useNumberToFixedDigitsArgument](https://biomejs.dev/linter/rules/use-number-to-fixed-...

@tasshi-me

CLI

Bug fixes

The stdin-file-path option now works correctly for Astro/Svelte/Vue files (#2686)

Fix #2225 where lint output become empty for Vue files.

Contributed by @tasshi-me
biome migrate eslint now correctly resolve @scope/eslint-config (#2705). Contributed by @Conaclos

Linter

New features

Add nursery/useExplicitLengthCheck.

Bug fixes

noBlankTarget no longer hangs when applying a code fix (#2675).

Previously, the following code made Biome hangs when applying a code fix.
```
<a href="https://example.com" rel="" target="_blank"></a>
```
Contributed by @Conaclos
noRedeclare no longer panics on conditional type (#2659).

This is a regression introduced by #2394.
This regression makes noRedeclare panics on every conditional types with infer bindings.

Contributed by @Conaclos
noUnusedLabels and noConfusingLabels now ignore svelte reactive statements (#2571).

The rules now ignore reactive Svelte blocks in Svelte components.
```
<script>
$: { /* reactive block */ }
</script>
```
Contributed by @Conaclos
useExportType no longer removes leading comments (#2685).

Previously, useExportType removed leading comments when it factorized the type qualifier.
It now provides a code fix that preserves the leading comments:
```
- export {
+ export type {
    /**leading comment*/
-   type T
+   T
  }
```
Contributed by @Conaclos
useJsxKeyInIterable no longer reports false positive when iterating on non-jsx items (#2590).

The following snipet of code no longer triggers the rule:
```
<>{data.reduce((total, next) => total + next, 0)}</>
```
Contributed by @dyc3
Fix typo by renaming useConsistentBuiltinInstatiation to useConsistentBuiltinInstantiation
Contributed by @minht11

What's Changed

Other changes

feat(biome_graphql_parser): parse schema definition by @vohoanglong0107 in #2557
chore(ci): renovate pin GA to semver by @Sec-ant in #2670
build(deps): update by @Conaclos in #2669
build(deps): upgrade indexmap crate by @Conaclos in #2673
feat(biome_css_analyzer): implement noDuplicateAtImportRules by @DerTimonius in #2658
feat(biome_css_analyzer): noUnknownSelectorPseudoElement by @keita-hino in #2655
feat(biome_graphql_parser): implement NthAt for GraphqlLexer by @vohoanglong0107 in #2677
feat(biome_graphql_parser): parse scalar type definition by @vohoanglong0107 in #2663
chore: add Grit node compilers by @arendjr in #2689
chore: upgrade to rust 1.78 by @ematipico in #2691
feat: parse object type definition by @vohoanglong0107 in #2690
chore(deps): upgrade oxc_resolver by @ematipico in #2694
chore: implement Grit node bindings by @arendjr in #2697
docs: better explanation of the directive "use strict" by @ematipico in #2699
docs: add small note about process.exit by @ematipico in #2700
fix(lint/noDuplicateAtImportRules): correctly handle both single- and double quotes by @DerTimonius in #2707
feat(biome_graphql_parser): parse interface type definition by @vohoanglong0107 in #2703
feat(linter): implement NoUnmatchableAnbSelector by @togami2864 in #2706
chore(deps): update rust crate tracing to 0.1.40 by @renovate in #2554
fix(lint/useJsxKeyInIterable): handle ternaries properly by @dyc3 in #2701
fix(useExplicitLengthCheck): docs by @Sec-ant in #2735
chore(deps): update rust crate serde to 1.0.200 by @renovate in #2737
chore(deps): update github-actions by @renovate in #2740
chore(deps): update dependency prettier to v3.2.5 by @renovate in #2739
chore(deps): update pnpm to v8.15.8 by @renovate in #2733
chore(deps): update @biomejs packages by @renovate in #2732
chore(deps): update dependency eslint to v9.2.0 by @renovate in #2738

New Contributors

@dyc3 made their first contribution in #2667
@tasshi-me made their first contribution in #2686

Full Changelog: cli/v1.7.2...cli/v1.7.3

@Conaclos

Analyzer

Bug fixes

Import sorting now ignores side effect imports (#817).

A side effect import consists now in its own group.
This ensures that side effect imports are not reordered.

Here is an example of how imports are now sorted:
```
  import "z"
- import { D } from "d";
  import { C } from "c";
+ import { D } from "d";
  import "y"
  import "x"
- import { B } from "b";
  import { A } from "a";
+ import { B } from "b";
  import "w"
```
Contributed by @Conaclos
Import sorting now adds spaces where needed (#1665)
Contributed by @Conaclos

CLI

Bug fixes

biome migrate eslint now handles cyclic references.

Some plugins and configurations export objects with cyclic references.
This causes biome migrate eslint to fail or ignore them.
These edge cases are now handled correctly.

Contributed by @Conaclos

Formatter

Bug fixes

Correctly handle placement of comments inside named import clauses. #2566. Contributed by @ah-yu

Linter

New features

Add nusery/noReactSpecificProps.
Contributed by @marvin-j97
Add noUselessUndefinedInitialization.
Contributed by @lutaok
Add nusery/useArrayLiterals.
Contributed by @Kazuhiro-Mimaki
Add nusery/useConsistentBuiltinInstatiation.
Contributed by @minht11
Add nusery/useDefaultSwitchClause.
Contributed by @michellocana

Bug fixes

noDuplicateJsonKeys no longer crashes when a JSON file contains an unterminated string (#2357).
Contributed by @Conaclos
noRedeclare now reports redeclarations of parameters in a functions body (#2394).

The rule was unable to detect redeclarations of a parameter or type parameter in the function body.
The following two redeclarations are now reported:
```
function f<T>(a) {
  type T = number; // redeclaration
  const a = 0; // redeclaration
}
```
Contributed by @Conaclos
noRedeclare no longer reports overloads in object types (#2608).

The rule no longer report redeclarations in the following code:
```
type Overloads = {
  ({ a }: { a: number }): number,
  ({ a }: { a: string }): string,
};
```
Contributed by @Conaclos
noRedeclare now merge default function export declarations and types (#2372).

The following code is no longer reported as a redeclaration:
```
interface Foo {}
export default function Foo() {}
```
Contributed by @Conaclos
noUndeclaredVariables no longer reports variable-only and type-only exports (#2637).
Contributed by @Conaclos
[noUnusedVariables] no longer crash Biome when encountering a malformed conditional type (#1695).
Contributed by @Conaclos
useConst now ignores a variable that is read before its assignment.

Previously, the rule reported the following example:
```
let x;
x; // read
x = 0; // write
```
It is now correctly ignored.

Contributed by @Conaclos
useShorthandFunctionType now suggests correct code fixes when parentheses are required (#2595).

Previously, the rule didn't add parentheses when they were needed.
It now adds parentheses when the function signature is inside an array, a union, or an intersection.
```
- type Union = { (): number } | string;
+ type Union = (() => number) | string;
```
Contributed by @Conaclos
useTemplate now correctly escapes strings (#2580).

Previously, the rule didn't correctly escape characters preceded by an escaped character.

Contributed by @Conaclos
noMisplacedAssertion now allow these matchers
- expect.any()
- expect.anything()
- expect.closeTo
- expect.arrayContaining
- expect.objectContaining
- expect.stringContaining
- expect.stringMatching
- expect.extend
- expect.addEqualityTesters
- expect.addSnapshotSerializer
Contributed by @fujiyamaorange

Parser

Bug fixes

The language parsers no longer panic on unterminated strings followed by a newline and a space (#2606, #2410).

The following example is now parsed without making Biome panics:
```
"
 "
```
Contributed by @Conaclos

What's Changed

Other changes

build(xstask): remove deps fs_extra and filetime by @Conaclos in #2562
docs: Add more useImportType examples to docs by @drwpow in #2307
chore: update schema definition by @Mayandev in #2567
fix(configuration_schema): rename some fields to camelCase in the configuration_schema.json by @ah-yu in #2568
fix: rename some fileds to camelCase in the configuration_schema by @ah-yu in #2569
feat(biome_css_analyzer): noUnknownUnit by @neokidev in #2535
chore: fix some typos in comments by @hardlydearly in #2579
refactor: foundations for LSP workspaces support by @ematipico in #2589
fix(lint/noRedundantAlt): rule source by @Conaclos in #2609
feat(linter): Implement useGenericFontNames by @togami2864 in #2573
chore: remove some website leftovers by @SuperchupuDev in #2617
refactor(deserialize): don't handle Option specifically by @Conaclos in #2630
refactor: use TriviaPiece factory functions in more places by @minht11 in #2632
feat(biome_css_analyzer): noUnknownFunction by @neokidev in #2570
fix(snippet): should emit only one diagnostic by @Sec-ant in #2650
chore: add infrastructure for Grit engine by @arendjr in #2586
docs: fix typos in biome_rowan batch mutation by @vohoanglong0107 in #2653
chore: upgrade prettier and update snapshots by @ah-yu in #2502
build(deps): update by @Conaclos in #2657

New Contributors

@Mayandev made their first contribution in #2567
@neokidev made their first contribution in #2535
@hardlydearly made their first contribution in #2579
@minht11 made their first contribution in #2540
@Kazuhiro-Mimaki made their first contribution in #2541
@michellocana made their first contribution in #2605
@Shyam-Chen made their first contribution in #2598

Full Changelog: cli/v1.7.1...cli/v1.7.2

@ematipico

Editors

Bug fixes

Fix #2403 by printing the errors in the client console. Contributed by @ematipico

Formatter

Bug fixes

Add parentheses for the return expression that has leading multiline comments. #2504. Contributed by @ah-yu
Correctly format dangling comments of continue statements. #2555. Contributed by @ah-yu

Linter

Bug fixes

Fix case where jsxRuntime wasn't being respected by useImportType rule (#2473).Contributed by @arendjr
Fix #2460, where the rule noUselessFragments was crashing the linter in some cases. Now cases like these are correctly handled:
```
callFunction(<>{bar}</>)
```
Contributed by @ematipico
Fix #2366, where noDuplicateJsonKeys incorrectly computed the kes to highlight. Contributed by @ematipico

Enhancements

The rule noMisplacedAssertions now considers valid calling expect inside waitFor:

import { waitFor } from '@testing-library/react';

await waitFor(() => {
  expect(111).toBe(222);
});

Contributed by @ematipico

What's Changed

Other changes

fix(lint/noBarrelFile): rule source by @Conaclos in #2464
refactor(bench): update import statement and module handling in run.js by @chansuke in #2471
docs: fix missing punctuation and typo by @uncenter in #2477
fix: missing "--apply" option in the command example by @t-shiratori in #2479
chore: tidy up dependencies by @ematipico in #2480
chore(ci): add repository dispatch workflow by @Sec-ant in #2442
chore: fix some typos in comments by @TechVest in #2486
feat: start working on yaml support by @defnot001 in #2428
chore: prepare knope by @ematipico in #2484
ci: trigger prepare release by @ematipico in #2489
ci: trigger prepare release by @ematipico in #2490
chore: remove variables from workflows by @ematipico in #2491
chore: speed up wasm-pack profiling build by @Sec-ant in #2494
fix: reverts hashbrown, which causes issues when compiling to WASM by @ematipico in #2496
fix(linter): name of typescript-eslint by @ematipico in #2503
Handle operation parsing error GraphQL by @vohoanglong0107 in #2434
chore: remove website from monorepo by @ematipico in #2505
ci: add a workflow for linting pr titles by @unvalley in #2497
feat(rule/solidjs): add no-react-specific-props by @marvin-j97 in #2427
refactor(js_syntax): remove TsNameWithTypeArguments by @Conaclos in #2510
fix(linter): add missing fix kind for solid rule by @ematipico in #2519
feat(biome_css_analyzer): noCssEmptyBlock by @togami2864 in #2513
chore: added how to create new css lint rule by @togami2864 in #2522
refactor(css_formatter): implement FormatCssBlockLike by @denbezrukov in #2531
feat(biome_css_analyze): noDuplicateSelectorsKeyframeBlock by @isnakode in #2534
docs: fixed path to crates, updated link to translating doc by @viraxslot in #2538
fix(biome_css_analyzer): update lint error messages by @togami2864 in #2545
feat(biome_css_analyze): noImportantInKeyframe by @isnakode in #2542
chore(deps): update rust crate serde_json to 1.0.116 by @renovate in #2553
chore(deps): update rust crate proc-macro2 to 1.0.81 by @renovate in #2551
chore(deps): update github-actions by @renovate in #2549
chore: add a new bronze sponsor by @ematipico in #2556
chore(deps): update rust:1.77.2 docker digest to 6052afe by @renovate in #2550
chore(deps): update rust crate serde to 1.0.198 by @renovate in #2552
feat(biome_graphql_parser): parse fragment definition by @vohoanglong0107 in #2506
refactor(ci): add more valid PR title types by @Conaclos in #2559
docs: fix typo in biome analyze contribution document by @GunseiKPaseri in #2560
build(deps): remove 'case' dependency by @Conaclos in #2561

New Contributors

@uncenter made their first contribution in #2477
@t-shiratori made their first contribution in #2479
@TechVest made their first contribution in #2486
@defnot001 made their first contribution in #2428
@marvin-j97 made their first contribution in #2427
@viraxslot made their first contribution in #2538
@GunseiKPaseri made their first contribution in #2560

Full Changelog: cli/v1.7.0...cli/v1.7.1

@Sec-ant

Analyzer

Bug fixes

Now Biome can detect the script language in Svelte and Vue script blocks more reliably (#2245). Contributed by @Sec-ant
useExhaustiveDependencies no longer reports recursive calls as missing
dependencies (#2361).
Contributed by @arendjr
useExhaustiveDependencies correctly reports missing dependencies declared
using function declarations (#2362).
Contributed by @arendjr
Biome now can handle .svelte and .vue files with CRLF as the end-of-line sequence. Contributed by @Sec-ant
noMisplacedAssertion no longer reports method calls by describe, test, it objects (e.g. test.each([])()) (#2443). Contributed by @unvalley.

Biome now can handle .vue files with generic components (#2456).

<script generic="T extends Record<string, any>" lang="ts" setup>
//...
</script>

Contributed by @Sec-ant

Enhancements

Complete the well-known file lists for JSON-like files. Trailing commas are allowed in .jsonc files by default. Some well-known files like tsconfig.json and .babelrc don't use the .jsonc extension but still allow comments and trailing commas. While others, such as .eslintrc.json, only allow comments. Biome is able to identify these files and adjusts the json.parser.allowTrailingCommas option accordingly to ensure they are correctly parsed. Contributed by @Sec-ant
Fix dedent logic inconsistent with prettier where the indent-style is space and the indent-width is not 2. Contributed by @mdm317

CLI

New features

Add a command to migrate from ESLint

biome migrate eslint allows you to migrate an ESLint configuration to Biome.
The command supports legacy ESLint configurations and new flat ESLint configurations.
Legacy ESLint configurations using the YAML format are not supported.

When loading a legacy ESLint configuration, Biome resolves the extends field.
It resolves both shared configurations and plugin presets!
To do this, it invokes Node.js.

Biome relies on the metadata of its rules to determine the equivalent rule of an ESLint rule.
A Biome rule is either inspired or roughly identical to an ESLint rules.
By default, inspired and nursery rules are excluded from the migration.
You can use the CLI flags --include-inspired and --include-nursery to migrate them as well.

Note that this is a best-effort approach.
You are not guaranteed to get the same behavior as ESLint.

Given the following ESLint configuration:
```
{
      "ignore_patterns": ["**/*.test.js"],
      "globals": { "var2": "readonly" },
      "rules": {
          "eqeqeq": "error"
      },
      "overrides": [{
          "files": ["lib/*.js"],
          "rules": {
            "default-param-last": "off"
          }
      }]
}
```
biome migrate eslint --write changes the Biome configuration as follows:
```
{
  "linter": {
    "rules": {
      "recommended": false,
      "suspicious": {
        "noDoubleEquals": "error"
      }
    }
  },
  "javascript": { "globals": ["var2"] },
  "overrides": [{
    "include": ["lib/*.js"],
    "linter": {
      "rules": {
        "style": {
          "useDefaultParameterLast": "off"
        }
      }
    }
  }]
}
```
Also, if the working directory contains .eslintignore, then Biome migrates the glob patterns.
Nested .eslintignore in subdirectories and negated glob patterns are not supported.

If you find any issue, please don't hesitate to report them.

Contributed by @Conaclos
Added two new options to customise the emitted output of the CLI: --reporter=json and --reporter=json-pretty. With --reporter=json, the diagnostics and the
summary will be printed in the terminal in JSON format. With --reporter=json-pretty, you can print the same information, but formatted using the same options of your configuration.

NOTE: the shape of the JSON is considered experimental, and the shape of the JSON might change in the future.

Example of output when running `biome format` command
```json { "summary": { "changed": 0, "unchanged": 1, "errors": 1, "warnings": 0, "skipped": 0, "suggestedFixesSkipped": 0, "diagnosticsNotPrinted": 0 }, "diagnostics": [ { "category": "format", "severity": "error", "description": "Formatter would have printed the following content:", "message": [ { "elements": [], "content": "Formatter would have printed the following content:" } ], "advices": { "advices": [ { "diff": { "dictionary": " statement();\n", "ops": [ { "diffOp": { "delete": { "range": [0, 2] } } }, { "diffOp": { "equal": { "range": [2, 12] } } }, { "diffOp": { "delete": { "range": [0, 2] } } }, { "diffOp": { "equal": { "range": [12, 13] } } }, { "diffOp": { "delete": { "range": [0, 2] } } }, { "diffOp": { "insert": { "range": [13, 15] } } } ] } } ] }, "verboseAdvices": { "advices": [] }, "location": { "path": { "file": "format.js" }, "span": null, "sourceCode": null }, "tags": [], "source": null } ], "command": "format" } ```
Added new --staged flag to the check, format and lint subcommands.

This new option allows users to apply the command only to the files that are staged (the
ones that will be committed), which can be very useful to simplify writing git hook scripts
such as pre-commit. Contributed by @castarco

Enhancements

Improve support of .prettierignore when migrating from Prettier

Now, Biome translates most of the glob patterns in .prettierignore to the equivalent Biome ignore pattern.
Only negated glob patterns are not supported.

Contributed by @Conaclos
Support JavaScript configuration files when migrating from Prettier

biome migrate prettier is now able to migrate Prettier configuration files
ending with js, mjs, or cjs extensions.
To do this, Biome invokes Node.js.

Also, embedded Prettier configurations in package.json are now supported.

Contributed by @Conaclos
Support overrides field in Prettier configuration files when migrating from Prettier.
Contributed by @Conaclos
Support passing a file path to the --config-path flag or the BIOME_CONFIG_PATH environment variable.

Now you can pass a .json/.jsonc file path with any filename to the --config-path flag or the
BIOME_CONFIG_PATH environment variable. This will disable the configuration auto-resolution and Biome
will try to read the configuration from the said file path (#2265).
```
biome format --config-path=../biome.json ./src
```
Contributed by @Sec-ant

Bug fixes

Biome now tags the diagnostics emitted by organizeImports and formatter with correct severity levels, so they will be properly filtered by the flag --diagnostic-level (#2288). Contributed by @Sec-ant
Biome now correctly filters out files that are not present in the current directory when using the --changed flag #1996. Contributed by @castarco
Biome now skips traversing fifo or socket files (#2311). Contributed by @Sec-ant
Biome now resolves configuration files exported from external libraries in extends from the working directory (CLI) or project root (LSP). This is the documented behavior and previous resolution behavior is considered as a bug (#2231). Contributed by @Sec-ant

Configuration

Bug fixes

Now setting group level all to false can disable recommended rules from that group when top level recommended is true or unset. Contributed by @Sec-ant
Biome configuration files can correctly extends .jsonc configuration files now (#2279). Contributed by @Sec-ant
Fixed the JSON schema for React hooks configuration (#2396). Contributed by @arendjr

Enhancements

Biome now displays the location of a parsing error for its configuration file (#1627).

Previously, when Biome encountered a parsing error in its configuration file,
it didn't indicate the location of the error.
It now displays the name of the configuration file and the range where the error occurred.

Contributed by @Conaclos
options is no longer required for rules without any options (#2313).

Previously, the JSON schema required to set options to null when an object is used to set the diagnostic level of a rule without any option.
However, if options is set to null, Biome emits an error.

The schema is now fixed and it no longer requires specifying options.
This makes the following configuration valid:
```
{
  "linter": {
    "rules": {
      "styl...
```

@Sec-ant

Analyzer

Bug fixes

An operator with no spaces around in a binary expression no longer breaks the js analyzer (#2243). Contributed by @Sec-ant

CLI

Bug fixes

Fix the printed error count (#2048). Contributed by @Sec-ant

Configuration

Bug fixes

Correctly calculate enabled rules in lint rule groups. Now a specific rule belonging to a group can be enabled even if its group-level preset option recommended or all is false (#2191). Contributed by @Sec-ant

Editors

Bug fixes

Fix the unexpected code deletion and repetition when quickfix.biome is enabled and some import-related rules are applied (#2222, #688, #1015). Contributed by @Sec-ant

Linter

Bug fixes

Fix #2211. noChildrenProp should work fine when children pass as a prop in a new line. Contributed by @fireairforce
Fix #2248. lint/a11y/useButtonType should not trigger when button element with spread attribute. Contributed by @fireairforce
Fix #2216. lint/style/useNamingConvention should not ignore JSX Component name binding. Contributed by @fireairforce

Enhancements

Add support for object property members in the rule useSortedClasses. Contributed by @ematipico

Parser

The parser doesn't throw any error when the frontmatter of .astro files contains an illegal return:
```
---
const condition = true;
if (condition) {
  return "Something";
}
---
<div></div>
```
Contributed by @ematipico

What's Changed

Other changes

refactor(test): better infra for formatting by @ematipico in #2189
chore(deps): update github-actions (major) by @renovate in #2190
chore: search command infra by @arendjr in #2194
Update labeler.yml by @arendjr in #2208
feat(css_formatter): CssImportAtRule formatting by @denbezrukov in #2180
chore: derive Copy on LoggingKind and LoggingLevel by @arendjr in #2207
CSS parser parses sequence of custom idents for @font-feature-values #1743 by @denbezrukov in #2184
chore(deps): update @biomejs packages by @renovate in #2196
docs(pt-br): Update pt-br/index.mdx by @Exerea in #2139
fix(docs): improve wording of docs for global Number rules by @LucianBuzzo in #2210
feat(formatter): format @starting-style by @ematipico in #2213
Implement graphql grammar by @vohoanglong0107 in #1949
feat(lint): rule noMisplacedAssertion by @ematipico in #1935
chore: add html parser crate by @ematipico in #2163
Fixed a typo in the docs by @michaelnji in #2230
chore(deps): update @biomejs packages by @renovate in #2229
feat: css linter docs by @togami2864 in #2151
feat(parser): basic parsing for HTML parser by @ematipico in #2238
refactor(website): create a dedicated page for import sorting by @Conaclos in #2236
chore: update governance document by @ematipico in #2235
chore: fix typo in docs by @jgjgill in #2247
chore(deps): update @biomejs packages by @renovate in #2256
chore(deps): pin dependencies by @renovate in #2255
chore(deps): pin dependencies by @renovate in #2252
chore(deps): pin dependencies - autoclosed by @renovate in #2253
chore: add myself as a maintainer by @ah-yu in #2270
feat(parser): basic parsing element list with context bump by @ematipico in #2272
ci: fix release regression by @ematipico in #2280
chore: re-try release 1.6.4 by @ematipico in #2281

New Contributors

@renovate made their first contribution in #2190
@Exerea made their first contribution in #2139
@LucianBuzzo made their first contribution in #2210
@michaelnji made their first contribution in #2230
@jgjgill made their first contribution in #2247

Full Changelog: cli/v1.6.3...cli/v1.6.4

@Sec-ant

Analyzer

CLI

Bug fixes

Fix configuration resolution. Biome is now able to correctly find the biome.jsonc configuration file when --config-path is explicitly set (#2164). Contributed by @Sec-ant
JavaScript/TypeScript files of different variants (.ts, .js, .tsx, .jsx) in a single workspace now have stable formatting behaviors when running the CLI command in paths of different nested levels or in different operating systems (#2080, #2109). Contributed by @Sec-ant

Configuration

Bug fixes

Complete the documentation and overrides support for options formatter.lineEnding, [language].formatter.lineEnding, formatter.attributePosition and javascript.formatter.attributePosition. Contributed by @Sec-ant

Editors

Formatter

Bug fixes

Fix #2172 by breaking long object destructuring patterns. Contributed by @ah-yu

JavaScript APIs

Linter

New features

Add rule noEvolvingAny to disallow variables from evolving into any type through reassignments. Contributed by @fujiyamaorange

LSP

Bug fixes

Quickfix action no longer autofixes lint rule errors on save when linter is disabled (#2161). Contributed by @Sec-ant
Range formatting for Astro/Svelte/Vue doesn't place code out of place, especially when formatting on paste is enabled. Contributed by @ematipico

Parser

What's Changed

Other changes

feat(parser): GritQL parser by @arendjr in #1998
chore: reduce redundant lexer methods by @arendjr in #2165
chore(ci): update setup-rust cache strategy by @Sec-ant in #2166
chore(ci): do not cache nightly channel by @Sec-ant in #2167
chore(ci): revert wasm-pack dev mode change by @Sec-ant in #2170
fix(website): control flow by @Sec-ant in #2174
feat(css_formatter): CssPropertyAtRule formatting by @denbezrukov in #2181
feat(css_formatter): CssNamespaceAtRule formatting by @denbezrukov in #2182
docs(guides/how-biome-works): remove dangling phrase by @marcalexiei in #2179
fix(website): a small typo by @Sec-ant in #2192
fix(codegen): new lint rule generation by @unvalley in #2187
docs(website): translate integrate-biome-with-your-vcs into Japanese by @unvalley in #2176

New Contributors

@marcalexiei made their first contribution in #2179

Full Changelog: cli/v1.6.2...cli/v1.6.3

Uh oh!

Releases: biomejs/biome

CLI v1.8.1

CLI

Bug fixes

Configuration

Bug fixes

Formatter

Bug fixes

Linter

Bug fixes

Parser

New features

Bug fixes

Other changes

New Contributors

Contributors

Uh oh!

CLI v1.8.0

Analyzer

New features

Enhancements

CLI

New features

Enhancements

Bug fixes

Configuration

New features

Contributors

Uh oh!

CLI v1.7.4-nightly.125f34b

Analyzer

Enhancements

CLI

New features

Enhancements

Configuration

New features

Enhancements

Editors

New features

Bug fixes

Formatter

Bug fixes

JavaScript APIs

Linter

New features

Contributors

Uh oh!

JavaScript APIs v0.6.0-nightly.af70ac2

Analyzer

Enhancements

CLI

New features

Enhancements

Configuration

New features

Enhancements

Editors

New features

Bug fixes

Formatter

Bug fixes

JavaScript APIs

Linter

New features

Contributors

Uh oh!

CLI v1.7.3

CLI

Bug fixes

Linter

New features

Bug fixes

What's Changed

Other changes

New Contributors

Contributors

Uh oh!

CLI v1.7.2