[Snyk] Upgrade @biomejs/biome from 1.9.2 to 1.9.4 #159
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.
Snyk has created this PR to upgrade @biomejs/biome from 1.9.2 to 1.9.4.
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.
The recommended version is 3 versions ahead of your current version.
The recommended version was released on 21 days ago.
Issues fixed by the recommended upgrade:
SNYK-JS-COOKIE-8163060
SNYK-JS-ROLLUP-8073097
Release notes
Package name: @biomejs/biome
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
Formatter
Bug fixes
Linter
New features
Bug Fixes
Biome no longer crashes when it encounters a string that contains 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:
+ import type { A, B } from "";
- export type { type C, D };
+ export type { C, D };
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 ignores 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
noDuplicateCustomProperties now correctly handles custom properties and ignores non-custom properties.
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
What's Changed
Other changes
/chat
link by @ ematipico in #4171no-head-element
fromeslint-plugin-next
by @ kaioduarte in #4136noImgElement
rule by @ kaioduarte in #4155im::Vector
where we don't have to by @ arendjr in #4203noHeadImportInDocument
rule by @ kaioduarte in #4184next
branch by @ arendjr in #4250noDocumentCookie
rule by @ tunamaguro in #4255useExplicitFunctionReturnType
to `useExplicit… by @ kaykdm in #4261New Contributors
Full Changelog: js-api/v0.7.1...cli/v1.9.4
CLI
New features
GritQL queries that match functions or methods will now match async functions or methods as well.
If this is not what you want, you can capture the
async
keyword (or its absence) in a metavariable and assert its emptiness:Contributed by @ arendjr
Bug fixes
Fix #4077: Grit queries no longer need to match the statement's trailing semicolon. Contributed by @ arendjr
Fix #4102. Now the CLI command
lint
doesn't exit with an error code when using--write
/--fix
. Contributed by @ ematipicoConfiguration
Bug fixes
noLabelWithoutControl
options where incorrectly marked as mandatory. Contributed by @ ematipicoEditors
Formatter
Bug fixes
Fix #3924 where GraphQL formatter panics in block comments with empty line. Contributed by @ vohoanglong0107
Fix a case where raw values inside
url()
functions weren't properly trimmed.Contributed by @ ematipico
Fixed #4076, where a media query wasn't correctly formatted:
Contributed by @ blaze-d83
JavaScript API
Bug fixes
Linter
New features
Add noDescendingSpecificity. Contributed by @ tunamaguro
Add noNestedTernary. Contributed by @ kaykdm
Add noTemplateCurlyInString. Contributed by @ fireairforce
Add noOctalEscape. Contributed by @ fireairforce
Bug fixes
noControlCharactersInRegex no longer panics on regexes with incomplete escape sequences. Contributed by @ Conaclos
noMisleadingCharacterClass no longer reports issues outside of character classes.
The following code is no longer reported:
Contributed by @ Conaclos
noUndeclaredDependencies no longer reports Node.js builtin modules as undeclared dependencies.
The rule no longer reports the following code:
Contributed by @ Conaclos
noUnusedVariables no longer panics when suggesting the renaming of a variable at the start of a file (#4114). Contributed by @ Conaclos
noUselessEscapeInRegex no longer panics on regexes that start with an empty character class. Contributed by @ Conaclos
noUselessStringConcat no longer panics when it encounters malformed code. Contributed by @ Conaclos
noUnusedFunctionParameters no longer reports unused parameters inside an object pattern with a rest parameter.
In the following code, the rule no longer reports
a
as unused.This matches the behavior of noUnusedVariables.
Contributed by @ Conaclos
useButtonType no longer reports dynamically created button with a valid type (#4072).
The following code is no longer reported:
Contributed by @ Conaclos
useSemanticElements now ignores elements with the
img
role (#3994).MDN recommends using
role="img"
for grouping images or creating an image from other elements.The following code is no longer reported:
Contributed by @ Conaclos
useSemanticElements now ignores
alert
andalertdialog
roles (#3858). Contributed by @ ConaclosnoUselessFragments don't create invaild JSX code when Fragments children contains JSX Expression and in a LogicalExpression. Contributed by @ fireairforce
Parser
Bug fixes
What's Changed
Other changes
.prettierignore
by @ Jayllyz in #4134