biomejs/biome (@biomejs/biome)
### [`v1.9.0`](https://redirect.github.com/biomejs/biome/blob/HEAD/CHANGELOG.md#v190-2024-09-12)
[Compare Source](https://redirect.github.com/biomejs/biome/compare/c28d5978c1440b3ae184d1cc354233711abf8a8e...b260d5b0e6b2e8e0093128ca2bf1f66c8e5d35da)
##### Analyzer
- Implement the [semantic model for CSS](https://redirect.github.com/biomejs/biome/pull/3546). Contributed by [@togami2864](https://redirect.github.com/togami2864)
##### CLI
##### New features
- Add `--graphql-linter-enabled` option, to control whether the linter should be enabled or not for GraphQL files. Contributed by [@ematipico](https://redirect.github.com/ematipico)
- New EXPERIMENTAL `search` command. The search command allows you to search a Biome project using [GritQL syntax](https://biomejs.dev/reference/gritql).
GritQL is a powerful language that lets you do *structural* searches on your codebase. This means that trivia such as whitespace or even the type of strings quotes used will be ignored in your search query. It also has many features for querying the structure of your code, making it much more elegant for searching code than regular expressions.
While we believe this command may already be useful to users in some situations (especially when integrated in the IDE extensions!), we also had an ulterior motive for adding this command: We intend to utilize GritQL for our plugin efforts, and by allowing our users to try it out in a first iteration, we hope to gain insight in the type of queries you want to do, as well as the bugs we need to focus on.
For now, the `search` command is explicitly marked as EXPERIMENTAL, since many bugs remain. Keep this in mind when you try it out, and please [let us know](https://redirect.github.com/biomejs/biome/issues) your issues!
Note: GritQL escapes code snippets using backticks, but most shells interpret backticks as command invocations. To avoid this, it's best to put *single quotes* around your Grit queries.
```shell
biome search '`console.log($message)`' # find all `console.log` invocations
```
Contributed by [@arendjr](https://redirect.github.com/arendjr) and [@BackupMiles](https://redirect.github.com/BackupMiles)
- The option `--max-diagnostics` now accept a `none` value, which lifts the limit of diagnostics shown. Contributed by [@ematipico](https://redirect.github.com/ematipico)
- Add a new reporter `--reporter=gitlab`, that emits diagnostics for using the [GitLab Code Quality report](https://docs.gitlab.com/ee/ci/testing/code_quality.html#implement-a-custom-tool).
```json
[
{
"description": "Use === instead of ==. == is only allowed when comparing against `null`",
"check_name": "lint/suspicious/noDoubleEquals",
"fingerprint": "6143155163249580709",
"severity": "critical",
"location": {
"path": "main.ts",
"lines": {
"begin": 4
}
}
}
]
```
Contributed by [@NiclasvanEyk](https://redirect.github.com/NiclasvanEyk)
- Add new options to the `lsp-proxy` and `start` commands:
- `--log-path`: a directory where to store the daemon logs. The commands also accepts the environment variable `BIOME_LOG_PATH`.
- `--log-prefix-name`: a prefix that's added to the file name of the logs. It defaults to `server.log`. The commands also accepts the environment variable `BIOME_LOG_PREFIX_NAME`.
[@Contributed](https://redirect.github.com/Contributed) by [@ematipico](https://redirect.github.com/ematipico)
##### Enhancements
- When a `--reporter` is provided, and it's different from the default one, the value provided by via `--max-diagnostics` is ignored and **the limit is lifted**. Contributed by [@ematipico](https://redirect.github.com/ematipico)
- `biome init` now generates a new config file with more options set.
This change intends to improve discoverability of the options and to set the more commonly used options to their default values.
Contributed by [@Conaclos](https://redirect.github.com/Conaclos)
- The `--verbose` flag now reports the list of files that were evaluated, and the list of files that were fixed.
The **evaluated** files are the those files that can be handled by Biome, files that are ignored, don't have an extension or have an extension that Biome can't evaluate are excluded by this list.
The **fixed** files are those files that were handled by Biome and *changed*. Files that stays the same after the process are excluded from this list.
```shell
VERBOSE ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
ℹ Files processed:
- biome/biome.json
- biome/packages/@biomejs/cli-win32-arm64/package.json
- biome/packages/tailwindcss-config-analyzer/package.json
VERBOSE ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
ℹ Files fixed:
- biome/biome/packages/tailwindcss-config-analyzer/src/generate-tailwind-preset.ts
```
Contributed by [@ematipico](https://redirect.github.com/ematipico)
- Allow passing `nursery` to the `--only` and `--skip` filters.
The `--only` option allows you to run a given rule or rule group.
The `--skip` option allows you to skip the execution of a given group or a given rule.
Previously, it was not possible to pass `nursery`.
This restriction is now removed, as it may make sense to skip the nursery rules that a project has enabled.
Contributed by [@Conaclos](https://redirect.github.com/Conaclos)
- The CLI now returns an error code when calling a command in `stdin` mode, and the contents of the files aren't fixed. For example, the following example will result in an error code of `1` because the `lint` command triggers some lint rules:
```shell
echo "let x = 1" | biome lint --stdin-file-path=stdin.js
```
Contributed by [@ematipico](https://redirect.github.com/ematipico)
##### Bug fixes
- `biome lint --write` now takes `--only` and `--skip` into account ([#3470](https://redirect.github.com/biomejs/biome/issues/3470)). Contributed by [@Conaclos](https://redirect.github.com/Conaclos)
- Fix [#3368](https://redirect.github.com/biomejs/biome/issues/3368), now the reporter `github` tracks the diagnostics that belong to formatting and organize imports. Contributed by [@ematipico](https://redirect.github.com/ematipico)
- Fix [#3545](https://redirect.github.com/biomejs/biome/issues/3545), display a warning, 'Avoid using unnecessary Fragment,' when a Fragment contains only one child element that is placed on a new line. Contributed by [@satojin219](https://redirect.github.com/satojin219)
- Migrating from Prettier or ESLint no longer overwrite the `overrides` field from the configuration ([#3544](https://redirect.github.com/biomejs/biome/issues/3544)). Contributed by [@Conaclos](https://redirect.github.com/Conaclos)
- Fix JSX expressions for `noAriaHiddenOnFocusable` ([#3708](https://redirect.github.com/biomejs/biome/pull/3708)). Contributed by [@anthonyshew](https://redirect.github.com/anthonyshew)
- Fix edge case for `
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), 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.
[ ] If you want to rebase/retry this PR, check this box
This PR contains the following updates:
1.8.3->1.9.0Release Notes
biomejs/biome (@biomejs/biome)
### [`v1.9.0`](https://redirect.github.com/biomejs/biome/blob/HEAD/CHANGELOG.md#v190-2024-09-12) [Compare Source](https://redirect.github.com/biomejs/biome/compare/c28d5978c1440b3ae184d1cc354233711abf8a8e...b260d5b0e6b2e8e0093128ca2bf1f66c8e5d35da) ##### Analyzer - Implement the [semantic model for CSS](https://redirect.github.com/biomejs/biome/pull/3546). Contributed by [@togami2864](https://redirect.github.com/togami2864) ##### CLI ##### New features - Add `--graphql-linter-enabled` option, to control whether the linter should be enabled or not for GraphQL files. Contributed by [@ematipico](https://redirect.github.com/ematipico) - New EXPERIMENTAL `search` command. The search command allows you to search a Biome project using [GritQL syntax](https://biomejs.dev/reference/gritql). GritQL is a powerful language that lets you do *structural* searches on your codebase. This means that trivia such as whitespace or even the type of strings quotes used will be ignored in your search query. It also has many features for querying the structure of your code, making it much more elegant for searching code than regular expressions. While we believe this command may already be useful to users in some situations (especially when integrated in the IDE extensions!), we also had an ulterior motive for adding this command: We intend to utilize GritQL for our plugin efforts, and by allowing our users to try it out in a first iteration, we hope to gain insight in the type of queries you want to do, as well as the bugs we need to focus on. For now, the `search` command is explicitly marked as EXPERIMENTAL, since many bugs remain. Keep this in mind when you try it out, and please [let us know](https://redirect.github.com/biomejs/biome/issues) your issues! Note: GritQL escapes code snippets using backticks, but most shells interpret backticks as command invocations. To avoid this, it's best to put *single quotes* around your Grit queries. ```shell biome search '`console.log($message)`' # find all `console.log` invocations ``` Contributed by [@arendjr](https://redirect.github.com/arendjr) and [@BackupMiles](https://redirect.github.com/BackupMiles) - The option `--max-diagnostics` now accept a `none` value, which lifts the limit of diagnostics shown. Contributed by [@ematipico](https://redirect.github.com/ematipico) - Add a new reporter `--reporter=gitlab`, that emits diagnostics for using the [GitLab Code Quality report](https://docs.gitlab.com/ee/ci/testing/code_quality.html#implement-a-custom-tool). ```json [ { "description": "Use === instead of ==. == is only allowed when comparing against `null`", "check_name": "lint/suspicious/noDoubleEquals", "fingerprint": "6143155163249580709", "severity": "critical", "location": { "path": "main.ts", "lines": { "begin": 4 } } } ] ``` Contributed by [@NiclasvanEyk](https://redirect.github.com/NiclasvanEyk) - Add new options to the `lsp-proxy` and `start` commands: - `--log-path`: a directory where to store the daemon logs. The commands also accepts the environment variable `BIOME_LOG_PATH`. - `--log-prefix-name`: a prefix that's added to the file name of the logs. It defaults to `server.log`. The commands also accepts the environment variable `BIOME_LOG_PREFIX_NAME`. [@Contributed](https://redirect.github.com/Contributed) by [@ematipico](https://redirect.github.com/ematipico) ##### Enhancements - When a `--reporter` is provided, and it's different from the default one, the value provided by via `--max-diagnostics` is ignored and **the limit is lifted**. Contributed by [@ematipico](https://redirect.github.com/ematipico) - `biome init` now generates a new config file with more options set. This change intends to improve discoverability of the options and to set the more commonly used options to their default values. Contributed by [@Conaclos](https://redirect.github.com/Conaclos) - The `--verbose` flag now reports the list of files that were evaluated, and the list of files that were fixed. The **evaluated** files are the those files that can be handled by Biome, files that are ignored, don't have an extension or have an extension that Biome can't evaluate are excluded by this list. The **fixed** files are those files that were handled by Biome and *changed*. Files that stays the same after the process are excluded from this list. ```shell VERBOSE ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ ℹ Files processed: - biome/biome.json - biome/packages/@biomejs/cli-win32-arm64/package.json - biome/packages/tailwindcss-config-analyzer/package.json VERBOSE ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ ℹ Files fixed: - biome/biome/packages/tailwindcss-config-analyzer/src/generate-tailwind-preset.ts ``` Contributed by [@ematipico](https://redirect.github.com/ematipico) - Allow passing `nursery` to the `--only` and `--skip` filters. The `--only` option allows you to run a given rule or rule group. The `--skip` option allows you to skip the execution of a given group or a given rule. Previously, it was not possible to pass `nursery`. This restriction is now removed, as it may make sense to skip the nursery rules that a project has enabled. Contributed by [@Conaclos](https://redirect.github.com/Conaclos) - The CLI now returns an error code when calling a command in `stdin` mode, and the contents of the files aren't fixed. For example, the following example will result in an error code of `1` because the `lint` command triggers some lint rules: ```shell echo "let x = 1" | biome lint --stdin-file-path=stdin.js ``` Contributed by [@ematipico](https://redirect.github.com/ematipico) ##### Bug fixes - `biome lint --write` now takes `--only` and `--skip` into account ([#3470](https://redirect.github.com/biomejs/biome/issues/3470)). Contributed by [@Conaclos](https://redirect.github.com/Conaclos) - Fix [#3368](https://redirect.github.com/biomejs/biome/issues/3368), now the reporter `github` tracks the diagnostics that belong to formatting and organize imports. Contributed by [@ematipico](https://redirect.github.com/ematipico) - Fix [#3545](https://redirect.github.com/biomejs/biome/issues/3545), display a warning, 'Avoid using unnecessary Fragment,' when a Fragment contains only one child element that is placed on a new line. Contributed by [@satojin219](https://redirect.github.com/satojin219) - Migrating from Prettier or ESLint no longer overwrite the `overrides` field from the configuration ([#3544](https://redirect.github.com/biomejs/biome/issues/3544)). Contributed by [@Conaclos](https://redirect.github.com/Conaclos) - Fix JSX expressions for `noAriaHiddenOnFocusable` ([#3708](https://redirect.github.com/biomejs/biome/pull/3708)). Contributed by [@anthonyshew](https://redirect.github.com/anthonyshew) - Fix edge case for `Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), 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.
This PR was generated by Mend Renovate. View the repository job log.