chore(deps): update dependency @biomejs/biome to v1.9.4 #89
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.3
->1.9.4
Release Notes
biomejs/biome (@biomejs/biome)
v1.9.4
Compare Source
Analyzer
Bug fixes
Improved the message for unused suppression comments. Contributed by @dyc3
Fix #4228, where the rule
a11y/noInteractiveElementToNoninteractiveRole
incorrectly reports arole
for non-interactive elements. Contributed by @eryue0220noSuspiciousSemicolonInJsx
now catches suspicious semicolons in React fragments. Contributed by @vasucp1207CLI
Enhancements
The
--summary
reporter now reports parsing diagnostics too. Contributed by @ematipicoImproved performance of GritQL queries by roughly 25-30%. Contributed by @arendjr
Configuration
Bug fixes
Editors
Formatter
Bug fixes
JavaScript APIs
Linter
New features
Bug Fixes
Biome no longer crashes when it encounters a string that contain a multibyte character (#4181).
This fixes a regression introduced in Biome 1.9.3
The regression affected the following linter rules:
nursery/useSortedClasses
nursery/useTrimStartEnd
style/useTemplate
suspicious/noMisleadingCharacterClass
Contributed by @Conaclos
Fix #4190, where the rule
noMissingVarFunction
wrongly reported a variable as missing when used inside avar()
function that was a newline. Contributed by @ematipicoFix #4041. Now the rule
useSortedClasses
won't be triggered ifclassName
is composed only by inlined variables. Contributed by @ematipicouseImportType and useExportType now report useless inline type qualifiers (#4178).
The following fix is now proposed:
Contributed by @Conaclos
useExportType now reports ungrouped
export from
.The following fix is now proposed:
Contributed by @Conaclos
noVoidTypeReturn now accepts
void
expressions in return position (#4173).The following code is now accepted:
Contributed by @Conaclos
noUselessFragments now correctly handles fragments containing HTML escapes (e.g.
) inside expression escapes{ ... }
(#4059).The following code is no longer reported:
Contributed by @fireairforce
noUnusedFunctionParameters and noUnusedVariables no longer reports a parameter as unused when another parameter has a constructor type with the same parameter name (#4227).
In the following code, the
name
parameter is no longer reported as unused.Contributed by @Conaclos
noUndeclaredDependencies now accepts dependency names with dots. Contributed by @Conaclos
useFilenamingConvention now correctly handles renamed exports (#4254).
The rule allows the filename to be named as one of the exports of the module.
For instance, the file containing the following export can be named
Button
.The rule now correctly handles the renaming of an export.
For example, the file containing the following export can only be named
Button
.Previously the rule expected the file to be named
A
.Contributed by @Conaclos
useConsistentMemberAccessibility now ignore private class members such as
#property
(#4276). Contributed by @ConaclosnoUnknownFunction correctly handles
calc-size
function (#4212).The following code
calc-size
is no longer reported as unknown:Contributed by @fireairforce
useNamingConvention now allows configuring conventions for readonly index signatures.
Contributed by @sepruko
Previously, the rule incorrectly reported duplicates for all properties, including non-custom ones. Contributed by @togami2864
Parser
Bug Fixes
The CSS parser now accepts more emoji in identifiers (#3627).
Browsers accept more emoji than the standard allows.
Biome now accepts these additional emojis.
The following code is now correctly parsed:
Contributed by @Conaclos
Add support for parsing typescript's
resolution-mode
in Import Types(#2115)Contributed by @fireairforce
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 was generated by Mend Renovate. View the repository job log.