chore(deps): update dependency @biomejs/biome to v1.9.1 #2121
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}
|
|
Important Review skippedBot user detected. To trigger a single review, invoke the You can disable this status message by setting the 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 using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
|
Here's the code health analysis summary for commits Analysis Summary
|
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
✅ All tests successful. No failed tests found. Additional details and impacted files@@ Coverage Diff @@
## dev #2121 +/- ##
=======================================
Coverage 29.03% 29.03%
=======================================
Files 223 223
Lines 12545 12545
Branches 511 528 +17
=======================================
Hits 3642 3642
Misses 8903 8903
☔ View full report in Codecov by Sentry. |
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.9.0->1.9.1Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
biomejs/biome (@biomejs/biome)
v1.9.1Compare Source
Analyzer
CLI
Bug fixes
useEditorConfignow loads the editorconfig when runningbiome ci#3864. Contributed by @dyc3Revert #3731 to fix broken quick fixes and code actions. Contributed by @nhedger
Configuration
Editors
Formatter
JavaScript APIs
Linter
New Features
Bug fixes
useSemanticElements now ignores
alertandalertdialogroles (3858). Contributed by @ConaclosnoUndeclaredDependencies now ignores
@/imports and recognizes type imports from Definitely Typed andbunimports. Contributed by @ConaclosParser
v1.9.0Compare Source
Analyzer
CLI
New features
Add
--graphql-linter-enabledoption, to control whether the linter should be enabled or not for GraphQL files. Contributed by @ematipicoNew EXPERIMENTAL
searchcommand. The search command allows you to search a Biome project using GritQL syntax.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
searchcommand is explicitly marked as EXPERIMENTAL, since many bugs remain. Keep this in mind when you try it out, and please let us know 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.
Contributed by @arendjr and @BackupMiles
The option
--max-diagnosticsnow accept anonevalue, which lifts the limit of diagnostics shown. Contributed by @ematipicoAdd a new reporter
--reporter=gitlab, that emits diagnostics for using the GitLab Code Quality report.[ { "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
Add new options to the
lsp-proxyandstartcommands:--log-path: a directory where to store the daemon logs. The commands also accepts the environment variableBIOME_LOG_PATH.--log-prefix-name: a prefix that's added to the file name of the logs. It defaults toserver.log. The commands also accepts the environment variableBIOME_LOG_PREFIX_NAME.@Contributed by @ematipico
Enhancements
When a
--reporteris provided, and it's different from the default one, the value provided by via--max-diagnosticsis ignored and the limit is lifted. Contributed by @ematipicobiome initnow 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
The
--verboseflag 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.
Contributed by @ematipico
Allow passing
nurseryto the--onlyand--skipfilters.The
--onlyoption allows you to run a given rule or rule group.The
--skipoption 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
The CLI now returns an error code when calling a command in
stdinmode, and the contents of the files aren't fixed. For example, the following example will result in an error code of1because thelintcommand triggers some lint rules:Contributed by @ematipico
Bug fixes
biome lint --writenow takes--onlyand--skipinto account (#3470). Contributed by @ConaclosFix #3368, now the reporter
githubtracks the diagnostics that belong to formatting and organize imports. Contributed by @ematipicoFix #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
Migrating from Prettier or ESLint no longer overwrite the
overridesfield from the configuration (#3544). Contributed by @ConaclosFix JSX expressions for
noAriaHiddenOnFocusable(#3708). Contributed by @anthonyshewFix edge case for
<canvas>elements that userole="img"(#3728). Contributed by @anthonyshewFix #3633, where diagnostics where incorrectly printed if the code has errors. Contributed by @ematipico
Allow
aria-labelon heading to preventuseHeadingContentdiagnostic (#3767). Contributed by @anthonyshewFix edge case #3791 for rule
noFocusedTestsbeing used with non-string-like expressions (#3793). Contributed by @h-a-n-aFix optional ARIA properties for
role="separator"inuseAriaPropsForRole(#3856). Contributed by @anthonyshewConfiguration
Add support for loading configuration from
.editorconfigfiles (#1724).Configuration supplied in
.editorconfigwill be overridden by the configuration inbiome.json. Support is disabled by default and can be enabled by adding the following to your formatter configuration inbiome.json:{ "formatter": { "useEditorconfig": true } }Contributed by @dyc3
overridesfrom an extended configuration is now merged with theoverridesof the extension.Given the following shared configuration
biome.shared.json:and the following configuration:
Previously, the
overridesfrombiome.shared.jsonwas overwritten.It is now merged and results in the following configuration:
Contributed by @Conaclos
Editors
Fix #3577, where the update of the configuration file was resulting in the creation of a new internal project. Contributed by @ematipico
Fix #3696, where
biome.jsoncwas incorrectly parsed with incorrect options. Contributed by @ematipicoFormatter
The CSS formatter is enabled by default. Which means that you don't need to opt-in anymore using the configuration file
biome.json:{ - "css": { - "formatter": { - "enabled": true - } - } }Contributed by @ematipico
Add parentheses for nullcoalescing in ternaries.
This change aligns on Prettier 3.3.3.
This adds clarity to operator precedence.
Contributed by @Conaclos
Keep the parentheses around
infer ... extendsdeclarations in type unions and type intersections (#3419). Contributed by @ConaclosKeep parentheses around a
yieldexpression inside a type assertion.Previously, Biome removed parentheses around some expressions that require them inside a type assertion.
For example, in the following code, Biome now preserves the parentheses.
Contributed by @Conaclos
Remove parentheses around expressions that don't need them inside a decorator.
Biome now matches Prettier in the following cases:
class { - @​(decorator) + @​decorator method() {} }, class { - @​(decorator()) + @​decorator() method() {} }, class { @​(decorator?.()) method() {} },Contributed by @Conaclos
Keep parentheses around objects preceded with a
@satisfiescomment.In the following example, parentheses are no longer removed.
Contributed by @Conaclos
Linter
Promoted rules
New rules are incubated in the nursery group.
Once stable, we promote them to a stable group.
The following CSS rules are promoted:
The following JavaScript rules are promoted:
Deprecated rules
correctness/noInvalidNewBuiltinis deprecated. Use correctness/noInvalidBuiltinInstantiation instead.style/useSingleCaseStatementis deprecated. Use correctness/noSwitchDeclarations instead.suspicious/noConsoleLogis deprecated. Use suspicious/noConsole instead.New features
Implement css suppression action. Contributed by @togami2864
Add support for GraphQL linting. Contributed by @ematipico
Add nursery/noCommonJs. Contributed by @minht11
Add nursery/noDuplicateCustomProperties. Contributed by @chansuke
Add nursery/noEnum. Contributed by @nickfla1
Add nursery/noDynamicNamespaceImportAccess. Contributed by @minht11
Add nursery/noIrregularWhitespace. Contributed by @michellocana
Add nursery/noRestrictedTypes. Contributed by @minht11
Add nursery/noSecrets. Contributed by @SaadBazaz
Add nursery/noUselessEscapeInRegex. Contributed by @Conaclos
Add nursery/noValueAtRule. Contributed by @rishabh3112
Add nursery/useAriaPropsSupportedByRole. Contributed by @ryo-ebata
Add nursery/useConsistentMemberAccessibility. Contributed by @seitarof
Add nursery/useStrictMode. Contributed by @ematipico
Add nursery/useTrimStartEnd. Contributed by @chansuke
Add nursery/noIrreguluarWhitespace. Contributed by @DerTimonius
Enhancements
Rename
nursery/noUnknownSelectorPseudoElementtonursery/noUnknownPseudoElement. Contributed by @togami2864The CSS linter is now enabled by default. Which means that you don't need to opt-in anymore using the configuration file
biome.json:{ - "css": { - "linter": { - "enabled": true - } - } }Contributed by @ematipico
The JavaScript linter recognizes TypeScript 5.5 and 5.6 globals. Contributed by @Conaclos
noBlankTarget now supports an array of allowed domains.
The following configuration allows
example.comandexample.orgas blank targets.Contributed by @Jayllyz
noConsole now accepts an option that specifies some allowed calls on
console. Contributed by @ConaclosAdd an
ignoreNulloption for noDoubleEquals.By default the rule allows loose comparisons against
null.The option
ignoreNullcan be set tofalsefor reporting loose comparison againstnull.Contributed by @peaBerberian.
noDuplicateObjectKeys now works for JSON and JSONC files. Contributed by @ematipico
noInvalidUseBeforeDeclaration now reports direct use of an enum member before its declaration.
In the following code,
Ais reported as use before its declaration.Contributed by @Conaclos
noNodejsModules now ignores imports of a package which has the same name as a Node.js module. Contributed by @Conaclos
noNodejsModules now ignores type-only imports (#1674).
The rule no longer reports type-only imports such as:
Contributed by @Conaclos
noRedundantUseStrict no longer reports
"use strict"directives when thepackage.jsonmarks explicitly the file as a script using the field"type": "commonjs". Contributed by @ematipiconoStaticOnlyClass no longer reports a class that extends another class (#3612). Contributed by @errmayank
noUndeclaredVariables no longer reports a direct reference to an enum member (#2974).
In the following code, the
Areference is no longer reported as an undeclared variable.Contributed by @Conaclos
noUndeclaredVariables recognized Svelte 5 runes in Svelte components and svelte files.
Svelte 5 introduced runes.
The rule now recognizes Svelte 5 runes in files ending with the
.svelte,.svelte.jsor.svelte.tsextensions.Contributed by @Conaclos
noUnusedVariables now checks TypeScript declaration files.
This allows to report a type that is unused because it isn't exported.
Global declarations files (declarations files without exports and imports) are still ignored.
Contributed by @Conaclos
useFilenamingConvention now supports unicase letters.
unicase letters have a single case: they are neither uppercase nor lowercase.
Biome now accepts filenames in unicase.
For example, the filename
안녕하세요is now accepted.We still reject a name that mixes unicase characters with lowercase or uppercase characters.
For example, the filename
A안녕하세요is rejected.This change also fixes #3353.
Filenames consisting only of numbers are now accepted.
Contributed by @Conaclos
useFilenamingConvention now supports Next.js/Nuxt/Astro dynamic routes (#3465).
Next.js, SolidStart, Nuxt, and Astro support dynamic routes such as
[...slug].jsand[[...slug]].js.Biome now recognizes this syntax.
slugmust contain only alphanumeric characters.Contributed by @Conaclos
useExportType no longer reports empty
export(#3535).An empty
export {}allows you to force TypeScript to consider a file with no imports and exports as an EcmaScript module.While
export type {}is valid, it is more common to useexport {}.Users may find it confusing that the linter asks them to convert it to
export type {}.Also, a bundler should be able to remove
export {}as well asexport type {}.So it is not so useful to report
export {}.Contributed by @Conaclos
Bug fixes
noControlCharactersInRegex now corretcly handle
\uescapes in unicode-aware regexes.Previously, the rule didn't consider regex with the
vflags as unicode-aware regexes.Moreover,
\uhhhhwas not handled in unicode-aware regexes.Contributed by @Conaclos
noControlCharactersInRegex now reports control characters and escape sequence of control characters in string regexes. Contributed by @Conaclos
noExcessiveNestedTestSuites: fix an edge case where the rule would alert on heavily nested zod schemas. Contributed by @dyc3noExtraNonNullAssertionno longer reports a single non-null assertion enclosed in parentheses (#3352). Contributed by @ConaclosnoMultipleSpacesInRegularExpressionLiterals now correctly provides a code fix when Unicode characters are used. Contributed by @Conaclos
noRedeclare no longer report redeclartions for lexically scoped function declarations #3664.
In JavaScript strict mode, function declarations are lexically scoped:
they cannot be accessed outside the block where they are declared.
In non-strict mode, function declarations are hoisted to the top of the enclosing function or global scope.
Previously Biome always hoisted function declarations.
It now takes into account whether the code is in strict or non strict mode.
Contributed by @Conaclos
noUndeclaredDependencies now ignores self package imports.
Given teh following
package.json:{ "name": "my-package", "main": "index.js" }The following import is no longer reported by the rule:
Contributed by @Conaclos
Fix [#3149] crashes that occurred when applying the
noUselessFragmentsunsafe fixes in certain scenarios. Contributed by @unvalleynoRedeclare no longer reports a variable named as the function expression where it is declared. Contributed by @Conaclos
useAdjacentOverloadSignaturesno longer reports a#privateclass member and a public class member that share the same name (#3309).The following code is no longer reported:
Contributed by @Conaclos
useAltText n olonger requests alt text for elements hidden from assistive technologies (#3316). Contributed by @robintown
useNamingConvention now accepts applying custom convention on abstract classes. Contributed by @Conaclos
useNamingConvention no longer suggests an empty fix when a name doesn't match strict Pascal case (#3561).
Previously the following code led
useNamingConventionto suggest an empty fix.The rule no longer provides a fix for this case.
Contributed by @Conaclos
useNamingConvention no longer provides fixes for global TypeScript declaration files.
Global TypeScript declaration files have no epxorts and no imports.
All the declared types are available in all files of the project.
Thus, it is not safe to propose renaming only in the declaration file.
Contributed by @Conaclos
useSortedClasses lint error with Template literals (#3394). Contributed by @hangaoke1
useValidAriaValues now correctly check property types (3748).
Properties that expect a string now accept arbitrary text.
An identifiers can now be made up of any characters except ASCII whitespace.
An identifier list can now be separated by any ASCII whitespace.
Contributed by @Conaclos
Parser
Enhancements
The JSON parser now allows comments in
turbo.jsonandjest.config.json. Contributed by @Netail and @ConaclosThe JSON parser now allows comments in files with the
.jsonextension under the.vscodeand.zeddirectories.Biome recognizes are well known JSON files that allows comments and/or trailing commas.
Previously, Biome did not recognize JSON files under the
.vscodeand the.zeddirectories as JSON files that allow comments.You had to configure Biome to recognize them:
{ "overrides": [ { "include": ["**/.vscode/*.json", "**/.zed/*.json"], "json": { "parser": { "allowComments": true } } } ] }This override is no longer needed!
Note that JSON files under the
.vscodeand the.zeddirectories don't accept trailing commas.Contributed by @Conaclos
Bug fixes
The CSS parser now accepts emoji in identifiers (3627).
The following code is now correctly parsed:
Contributed by @Conaclos
Fix #3287 nested selectors with pseudo-classes. Contributed by @denbezrukov
Fix #3349 allow CSS multiple ampersand support. Contributed by @denbezrukov
Fix #3410 by correctly parsing break statements containing keywords.
Contributed by @ah-yu
Fix #3464 by enabling JSX in
.vuefiles that use thelang='jsx'orlang='tsx'attribute. Contributed by @ematipicoConfiguration
📅 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.