build(deps): update dependency @biomejs/biome to v1.7.0 #220
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
Important Auto Review SkippedBot user detected. To trigger a single review, invoke the Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (invoked as PR comments)
Additionally, you can add CodeRabbit Configration File (
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
1.6.4->1.7.0Release Notes
biomejs/biome (@biomejs/biome)
v1.7.0Compare Source
Analyzer
Bug fixes
Now Biome can detect the script language in Svelte and Vue script blocks more reliably (#2245). Contributed by @Sec-ant
useExhaustiveDependenciesno longer reports recursive calls as missingdependencies (#2361).
Contributed by @arendjr
useExhaustiveDependenciescorrectly reports missing dependencies declaredusing function declarations (#2362).
Contributed by @arendjr
Biome now can handle
.svelteand.vuefiles withCRLFas the end-of-line sequence. Contributed by @Sec-antnoMisplacedAssertionno longer reports method calls bydescribe,test,itobjects (e.g.test.each([])()) (#2443). Contributed by @unvalley.Biome now can handle
.vuefiles with generic components (#2456).Contributed by @Sec-ant
Enhancements
Complete the well-known file lists for JSON-like files. Trailing commas are allowed in
.jsoncfiles by default. Some well-known files liketsconfig.jsonand.babelrcdon't use the.jsoncextension 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 thejson.parser.allowTrailingCommasoption accordingly to ensure they are correctly parsed. Contributed by @Sec-antFix 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 eslintallows 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
extendsfield.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-inspiredand--include-nurseryto 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 --writechanges 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
.eslintignorein 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=jsonand--reporter=json-pretty. With--reporter=json, the diagnostics and thesummary 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
--stagedflag to thecheck,formatandlintsubcommands.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 @castarcoEnhancements
Improve support of
.prettierignorewhen migrating from PrettierNow, Biome translates most of the glob patterns in
.prettierignoreto 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 prettieris now able to migrate Prettier configuration filesending with
js,mjs, orcjsextensions.To do this, Biome invokes Node.js.
Also, embedded Prettier configurations in
package.jsonare now supported.Contributed by @Conaclos
Support
overridesfield in Prettier configuration files when migrating from Prettier.Contributed by @Conaclos
Support passing a file path to the
--config-pathflag or theBIOME_CONFIG_PATHenvironment variable.Now you can pass a
.json/.jsoncfile path with any filename to the--config-pathflag or theBIOME_CONFIG_PATHenvironment variable. This will disable the configuration auto-resolution and Biomewill try to read the configuration from the said file path (#2265).
Contributed by @Sec-ant
Bug fixes
Biome now tags the diagnostics emitted by
organizeImportsandformatterwith correct severity levels, so they will be properly filtered by the flag--diagnostic-level(#2288). Contributed by @Sec-antBiome now correctly filters out files that are not present in the current directory when using the
--changedflag #1996. Contributed by @castarcoBiome now skips traversing
fifoorsocketfiles (#2311). Contributed by @Sec-antBiome now resolves configuration files exported from external libraries in
extendsfrom 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-antConfiguration
Bug fixes
Now setting group level
alltofalsecan disable recommended rules from that group when top levelrecommendedistrueor unset. Contributed by @Sec-antBiome configuration files can correctly extends
.jsoncconfiguration files now (#2279). Contributed by @Sec-antFixed 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
optionsis no longer required for rules without any options (#2313).Previously, the JSON schema required to set
optionstonullwhen an object is used to set the diagnostic level of a rule without any option.However, if
optionsis set tonull, Biome emits an error.The schema is now fixed and it no longer requires specifying
options.This makes the following configuration valid:
{ "linter": { "rules": { "style": { "noDefaultExport": { "level": "off" } } } } }Contributed by @Conaclos
Editors
Bug fixes
javascriptlanguage identifier. This is an ad hoc fix, because in the React world,.jsfiles are allowed to include JSX syntax, and these files are often associated with thejavascriptlanguage identifier in most of the editors. Plus, some editor extensions will also associate.jsxfiles with thejavascriptlanguage identifier. Relative links: discussion, #2085. Contributed by @Sec-antFormatter
Bug fixes
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:
New features
Add a new option
jsxRuntimeto thejavascriptconfiguration. When set toreactClassic, the noUnusedImports and useImportType 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.
Contributed by @Conaclos and @arendjr
Implement #2043: The React rule
useExhaustiveDependenciesis now also compatible with Preact hooks imported frompreact/hooksorpreact/compat. Contributed by @arendjrAdd rule noFlatMapIdentity to disallow unnecessary callback use on
flatMap. Contributed by @isnakodeAdd rule noConstantMathMinMaxClamp, which disallows using
Math.minandMath.maxto clamp a value where the result itself is constant. Contributed by @mgomulakEnhancements
style/useFilenamingConvention now allows prefixing a filename with
+(#2341).This is a convention used by Sveltekit and Vike.
Contributed by @Conaclos
style/useNamingConvention now accepts
PascalCasefor local and top-level variables.This allows supporting local variables that hold a component or a regular class.
The following code is now accepted:
Contributed by @Conaclos
complexity/useLiteralKeys no longer report computed properties named
__proto__(#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 for more details.
The rule now ignores computed properties named
__proto__.Contributed by @Conaclos
Bug fixes
Lint rules
useNodejsImportProtocol,useNodeAssertStrict,noRestrictedImports,noNodejsModuleswill no longer checkdeclare modulestatements anymore. Contributed by @Sec-antstyle/useNamingConvention now accepts any case for variables from object destructuring (#2332).
The following name is now ignored:
Previously, the rule renamed this variable. This led to a runtime error.
Contributed by @Conaclos
Parser
Bug fixes
using an escape sequence (#2384).
Contributed by @arendjr
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 has been generated by Mend Renovate. View repository job log here.