biomejs/biome (@biomejs/biome)
### [`v1.7.0`](https://togithub.com/biomejs/biome/blob/HEAD/CHANGELOG.md#170-2024-04-15)
[Compare Source](https://togithub.com/biomejs/biome/compare/f6fd1ef7130e7bcd1466aa78ae7295fc5fdd5d58...2dce6af835cc9339669b09f3a758de36a90b15f7)
##### Analyzer
##### Bug fixes
- Now Biome can detect the script language in Svelte and Vue script blocks more reliably ([#2245](https://togithub.com/biomejs/biome/issues/2245)). Contributed by [@Sec-ant](https://togithub.com/Sec-ant)
- `useExhaustiveDependencies` no longer reports recursive calls as missing
dependencies ([#2361](https://togithub.com/biomejs/biome/issues/2361)).
Contributed by [@arendjr](https://togithub.com/arendjr)
- `useExhaustiveDependencies` correctly reports missing dependencies declared
using function declarations ([#2362](https://togithub.com/biomejs/biome/issues/2362)).
Contributed by [@arendjr](https://togithub.com/arendjr)
- Biome now can handle `.svelte` and `.vue` files with `CRLF` as the end-of-line sequence. Contributed by [@Sec-ant](https://togithub.com/Sec-ant)
- `noMisplacedAssertion` no longer reports method calls by `describe`, `test`, `it` objects (e.g. `test.each([])()`) ([#2443](https://togithub.com/biomejs/biome/issues/2443)). Contributed by [@unvalley](https://togithub.com/unvalley).
- Biome now can handle `.vue` files with [generic components](https://vuejs.org/api/sfc-script-setup#generics) ([#2456](https://togithub.com/biomejs/biome/issues/2456)).
```vue
```
Contributed by [@Sec-ant](https://togithub.com/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](https://togithub.com/Sec-ant)
- Fix dedent logic inconsistent with prettier where the indent-style is space and the indent-width is not 2. Contributed by [@mdm317](https://togithub.com/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](https://eslint.org/docs/latest/use/configure/configuration-files) and [new flat ESLint configurations](https://eslint.org/docs/latest/use/configure/configuration-files-new).
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](https://biomejs.dev/linter/rules-sources/).
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:
```json
{
"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:
```json
{
"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](https://togithub.com/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](https://togithub.com/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](https://togithub.com/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](https://togithub.com/Conaclos)
- Support `overrides` field in Prettier configuration files when migrating from Prettier.
Contributed by [@Conaclos](https://togithub.com/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](https://togithub.com/biomejs/biome/issues/2265)).
```shell
biome format --config-path=../biome.json ./src
```
Contributed by [@Sec-ant](https://togithub.com/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](https://togithub.com/biomejs/biome/issues/2288)). Contributed by [@Sec-ant](https://togithub.com/Sec-ant)
- Biome now correctly filters out files that are not present in the current directory when using the `--changed` flag [#1996](https://togithub.com/biomejs/biome/issues/1996). Contributed by [@castarco](https://togithub.com/castarco)
- Biome now skips traversing `fifo` or `socket` files ([#2311](https://togithub.com/biomejs/biome/issues/2311)). Contributed by [@Sec-ant](https://togithub.com/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](https://togithub.com/biomejs/biome/issues/2231)). Contributed by [@Sec-ant](https://togithub.com/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](https://togithub.com/Sec-ant)
- Biome configuration files can correctly extends `.jsonc` configuration files now ([#2279](https://togithub.com/biomejs/biome/issues/2279)). Contributed by [@Sec-ant](https://togithub.com/Sec-ant)
- Fixed the JSON schema for React hooks configuration ([#2396](https://togithub.com/biomejs/biome/issues/2396)). Contributed by [@arendjr](https://togithub.com/arendjr)
##### Enhancements
- Biome now displays the location of a parsing error for its configuration file ([#1627](https://togithub.com/biomejs/biome/issues/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](https://togithub.com/Conaclos)
- `options` is no longer required for rules without any options ([#2313](https://togithub.com/biomejs/biome/issues/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:
```json
{
"linter": {
"rules": {
"style": {
"noDefaultExport": {
"level": "off"
}
}
}
}
}
```
Contributed by [@Conaclos](https://togithub.com/Conaclos)
##### Editors
##### Bug fixes
- Biome extension is now able to parse the JSX syntax in files that associated with the `javascript` [language identifier](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocumentItem). This is an ad hoc fix, because [in the React world, `.js` files are allowed to include JSX syntax](https://togithub.com/facebook/create-react-app/issues/87#issuecomment-234627904), and these files are often associated with the `javascript` language identifier in most of the editors. Plus, [some editor extensions](https://togithub.com/michaelgmcd/vscode-language-babel/blob/8b3a472748ad07c99dc022b66795c9eb46be4ccb/package.json#L63-L80) will also associate `.jsx` files with the `javascript` language identifier. Relative links: [discussion](https://togithub.com/biomejs/biome/discussions/838#discussioncomment-9047539), [#2085](https://togithub.com/biomejs/biome/issues/2085). Contributed by [@Sec-ant](https://togithub.com/Sec-ant)
##### Formatter
##### Bug fixes
- Fix [#2291](https://togithub.com/biomejs/biome/issues/2291) by correctly handle comment placement for JSX spread attributes and JSX spread children. Contributed by [@ah-yu](https://togithub.com/ah-yu)
##### JavaScript APIs
##### Linter
##### Promoted rules
New rules are incubated in the nursery group.
Once stable, we promote them to a stable group.
The following rules are promoted:
- [complecity/noExcessiveNestedTestSuites](https://biomejs.dev/linter/rules/no-excessive-nested-test-suites)
- [complexity/noUselessTernary](https://biomejs.dev/linter/rules/no-useless-ternary)
- [correctness/useJsxKeyInIterable](https://biomejs.dev/linter/rules/use-jsx-key-in-iterable)
- [performance/noBarrelFile](https://biomejs.dev/linter/rules/no-barrel-file/)
- [performance/noReExportAll](https://biomejs.dev/linter/rules/no-re-export-all/)
- [style/noNamespaceImport](https://biomejs.dev/linter/rules/no-namespace-import/)
- [style/useNodeAssertStrict](https://biomejs.dev/linter/rules/use-node-assert-strict/)
- [suspicious/noDuplicateTestHooks](https://biomejs.dev/linter/rules/no-duplicate-test-hooks/)
- [suspicious/noExportsInTest](https://biomejs.dev/linter/rules/no-exports-in-test/)
- [suspicious/noFocusedTests](https://biomejs.dev/linter/rules/no-focused-tests/)
- [suspicious/noSkippedTests](https://biomejs.dev/linter/rules/no-skipped-tests/)
- [suspicious/noSuspiciousSemicolonInJsx](https://biomejs.dev/linter/rules/no-suspicious-semicolon-in-jsx)
##### New features
- Add a new option `jsxRuntime` to the `javascript` configuration. When set to `reactClassic`, the [noUnusedImports](https://biomejs.dev/linter/rules/no-unused-imports) and [useImportType](https://biomejs.dev/linter/rules/use-import-type) rules use this information to make exceptions for the React global that is required by the React Classic JSX transform.
This is only necessary for React users who haven't upgraded to the [new JSX transform](https://legacy.reactjs.org/blog/2020/09/22/introducing-the-new-jsx-transform.html).
Contributed by [@Conaclos](https://togithub.com/Conaclos) and [@arendjr](https://togithub.com/arendjr)
- Implement [#2043](https://togithub.com/biomejs/biome/issues/2043): The React rule [`useExhaustiveDependencies`](https://biomejs.dev/linter/rules/use-exhaustive-dependencies/) is now also compatible with Preact hooks imported from `preact/hooks` or `preact/compat`. Contributed by [@arendjr](https://togithub.com/arendjr)
- Add rule [noFlatMapIdentity](https://biomejs.dev/linter/rules/no-flat-map-identity) to disallow unnecessary callback use on `flatMap`. Contributed by [@isnakode](https://togithub.com/isnakode)
- Add rule [noConstantMathMinMaxClamp](https://biomejs.dev/linter/rules/no-constant-math-min-max-clamp), which disallows using `Math.min` and `Math.max` to clamp a value where the result itself is constant. Contributed by [@mgomulak](https://togithub.com/mgomulak)
##### Enhancements
- [style/useFilenamingConvention](https://biomejs.dev/linter/rules/use-filenaming-convention/) now allows prefixing a filename with `+` ([#2341](https://togithub.com/biomejs/biome/issues/2341)).
This is a convention used by [Sveltekit](https://kit.svelte.dev/docs/routing#page) and [Vike](https://vike.dev/route).
Contributed by [@Conaclos](https://togithub.com/Conaclos)
- [style/useNamingConvention](https://biomejs.dev/linter/rules/use-naming-convention/) now accepts `PascalCase` for local and top-level variables.
This allows supporting local variables that hold a component or a regular class.
The following code is now accepted:
```tsx
function loadComponent() {
const Component = getComponent();
return ;
}
```
Contributed by [@Conaclos](https://togithub.com/Conaclos)
- [complexity/useLiteralKeys](https://biomejs.dev/linter/rules/use-literal-keys/) no longer report computed properties named `__proto__` ([#2430](https://togithub.com/biomejs/biome/issues/2430)).
In JavaScript, `{["__proto__"]: null}` and `{__proto__: null}` have not the same semantic.
The first code set a regular property to `null`.
The second one set the prototype of the object to `null`.
See the [MDN Docs](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Object/proto) for more details.
The rule now ignores computed properties named `__proto__`.
Contributed by [@Conaclos](https://togithub.com/Conaclos)
##### Bug fixes
- Lint rules `useNodejsImportProtocol`, `useNodeAssertStrict`, `noRestrictedImports`, `noNodejsModules` will no longer check `declare module` statements anymore. Contributed by [@Sec-ant](https://togithub.com/Sec-ant)
- [style/useNamingConvention](https://biomejs.dev/linter/rules/use-naming-convention/) now accepts any case for variables from object destructuring ([#2332](https://togithub.com/biomejs/biome/issues/2332)).
The following name is now ignored:
```js
const { Strange_Style } = obj;
```
Previously, the rule renamed this variable. This led to a runtime error.
Contributed by [@Conaclos](https://togithub.com/Conaclos)
##### Parser
##### Bug fixes
- Fixed an issue when Unicode surrogate pairs were encoded in JavaScript strings
using an escape sequence ([#2384](https://togithub.com/biomejs/biome/issues/2384)).
Contributed by [@arendjr](https://togithub.com/arendjr)
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
[ ] If you want to rebase/retry this PR, check this box
This PR has been generated by Mend Renovate. View repository job log here.
This PR contains the following updates:
1.6.4->1.7.0Release Notes
biomejs/biome (@biomejs/biome)
### [`v1.7.0`](https://togithub.com/biomejs/biome/blob/HEAD/CHANGELOG.md#170-2024-04-15) [Compare Source](https://togithub.com/biomejs/biome/compare/f6fd1ef7130e7bcd1466aa78ae7295fc5fdd5d58...2dce6af835cc9339669b09f3a758de36a90b15f7) ##### Analyzer ##### Bug fixes - Now Biome can detect the script language in Svelte and Vue script blocks more reliably ([#2245](https://togithub.com/biomejs/biome/issues/2245)). Contributed by [@Sec-ant](https://togithub.com/Sec-ant) - `useExhaustiveDependencies` no longer reports recursive calls as missing dependencies ([#2361](https://togithub.com/biomejs/biome/issues/2361)). Contributed by [@arendjr](https://togithub.com/arendjr) - `useExhaustiveDependencies` correctly reports missing dependencies declared using function declarations ([#2362](https://togithub.com/biomejs/biome/issues/2362)). Contributed by [@arendjr](https://togithub.com/arendjr) - Biome now can handle `.svelte` and `.vue` files with `CRLF` as the end-of-line sequence. Contributed by [@Sec-ant](https://togithub.com/Sec-ant) - `noMisplacedAssertion` no longer reports method calls by `describe`, `test`, `it` objects (e.g. `test.each([])()`) ([#2443](https://togithub.com/biomejs/biome/issues/2443)). Contributed by [@unvalley](https://togithub.com/unvalley). - Biome now can handle `.vue` files with [generic components](https://vuejs.org/api/sfc-script-setup#generics) ([#2456](https://togithub.com/biomejs/biome/issues/2456)). ```vue ``` Contributed by [@Sec-ant](https://togithub.com/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](https://togithub.com/Sec-ant) - Fix dedent logic inconsistent with prettier where the indent-style is space and the indent-width is not 2. Contributed by [@mdm317](https://togithub.com/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](https://eslint.org/docs/latest/use/configure/configuration-files) and [new flat ESLint configurations](https://eslint.org/docs/latest/use/configure/configuration-files-new). 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](https://biomejs.dev/linter/rules-sources/). 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: ```json { "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: ```json { "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](https://togithub.com/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" } ```Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.