[Snyk] Upgrade @biomejs/biome from 1.8.3 to 2.1.4 #372
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.8.3 to 2.1.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 35 versions ahead of your current version.
The recommended version was released 25 days ago.
Release notes
Package name: @biomejs/biome
2.1.4
Patch Changes
#7121
b9642ab
Thanks @ arendjr! - Fixed #7111: Imported symbols using aliases are now correctly recognised.#7103
80515ec
Thanks @ omasakun! - Fixed #6933 and #6994.When the values of private member assignment expressions, increment expressions, etc. are used, those private members are no longer marked as unused.
#6887
0cc38f5
Thanks @ ptkagori! - Added thenoQwikUseVisibleTask
rule to Qwik.This rule is intended for use in Qwik applications to warn about the use of
useVisibleTask$()
functions which require careful consideration before use.Invalid:
Valid:
#7084
50ca155
Thanks @ ematipico! - Added the new nursery rulenoUnnecessararyConditions
, which detects whenever some conditions don'tchange during the life cycle of the program, and truthy or false, hence deemed redundant.
For example, the following snippets will trigger the rule:
#6887
0cc38f5
Thanks @ ptkagori! - Added theuseImageSize
rule to Biome.The
useImageSize
rule enforces the use of width and height attributes on<img>
elements for performance reasons. This rule is intended to prevent layout shifts and improve Core Web Vitals by ensuring images have explicit dimensions.Invalid:
Valid:
#6887
0cc38f5
Thanks @ ptkagori! - Added theuseAnchorHref
rule to Biome.The
useAnchorHref
rule enforces the presence of anhref
attribute on<a>
elements in JSX. This rule is intended to ensure that anchor elements are always valid and accessible.Invalid:
Valid:
#7100
29fcb05
Thanks @ Jayllyz! - Added the rulenoNonNullAssertedOptionalChain
.This rule prevents the use of non-null assertions (
!
) immediately after optional chaining expressions (?.
). Optional chaining is designed to safely handle nullable values by returningundefined
when the chain encountersnull
orundefined
. Using a non-null assertion defeats this purpose and can lead to runtime errors.obj?.prop!;
obj?.method()!;
obj?.[key]!;
obj?.prop!;
// Valid - proper optional chaining usage
obj?.prop;
obj?.method();
obj?.prop ?? defaultValue;
obj!.prop?.method();
#7129
9f4538a
Thanks @ drwpow! - Removed option, combobox, listbox roles from useSemanticElements suggestions#7106
236deaa
Thanks @ arendjr! - Fixed #6985: Inference of return types no longer mistakenly picks up return types of nested functions.#7102
d3118c6
Thanks @ omasakun! - Fixed #7101:noUnusedPrivateClassMembers
now handles members declared as part of constructor arguments:private
modifier and makes it a plain method argument.noUnusedFunctionParameter
.#7104
5395297
Thanks @ harxki! - Reverting to prevent regressions around ref handling#7143
1a6933a
Thanks @ siketyan! - Fixed #6799: ThenoImportCycles
rule now ignores type-only imports if the newignoreTypes
option is enabled (enabled by default).#7099
6cc84cb
Thanks @ arendjr! - Fixed #7062: Biome now correctly considers extended configs when determining the mode for the scanner.#6887
0cc38f5
Thanks @ ptkagori! - Added theuseQwikClasslist
rule to Biome.This rule is intended for use in Qwik applications to encourage the use of the built-in
class
prop (which accepts a string, object, or array) instead of theclassnames
utility library.Invalid:
Valid:
#7019
57c15e6
Thanks @ fireairforce! - Added support in the JS parser forimport source
(a stage3 proposal). The syntax looks like:#7053
655049e
Thanks @ jakeleventhal! - Added theuseConsistentTypeDefinitions
rule.This rule enforces consistent usage of either
interface
ortype
for object type definitions in TypeScript.The rule accepts an option to specify the preferred style:
interface
(default): Prefer usinginterface
for object type definitionstype
: Prefer usingtype
for object type definitionsExamples:
// ❌ Invalid
type Point = { x: number; y: number };
// ✅ Valid
interface Point {
x: number;
y: number;
}
// With option { style: "type" }
// ❌ Invalid
interface Point {
x: number;
y: number;
}
// ✅ Valid
type Point = { x: number; y: number };
The rule will automatically fix simple cases where conversion is straightforward.
What's Changed
@ typescript-eslint/consistent-type-definitions
by @ jakeleventhal in #7053noNonNullAssertedOptionalChain
rule by @ Jayllyz in #7100noUnnecessaryConditions
by @ ematipico in #7084New Contributors
Full Changelog: https://github.com/biomejs/biome/compare/@ biomejs/[email protected]...@ biomejs/[email protected]
2.1.3
Patch Changes
#7057
634a667
Thanks @ mdevils! - Added the rulenoVueReservedKeys
, which prevents the use of reserved Vue keys.It prevents the use of Vue reserved keys such as those starting with
# @ biomejs/biome (like
$el,
$data,
$props) and keys starting with
_` in data properties, which can cause conflicts and unexpected behavior in Vue components.Invalid example
Valid examples
#6941
734d708
Thanks @ JamBalaya56562! - Added@ eslint-react/no-nested-component-definitions
as a rule source fornoNestedComponentDefinitions
. Now it will get picked up bybiome migrate --eslint
.#6463
0a16d54
Thanks @ JamBalaya56562! - Fixed a website link for theuseComponentExportOnlyModules
linter rule to point to the correct URL.#6944
e53f2fe
Thanks @ sterliakov! - Fixed #6910: Biome now ignores type casts and assertions when evaluating numbers fornoMagicNumbers
rule.#6991
476cd55
Thanks @ denbezrukov! - Fixed #6973: Add support for parsing the :active-view-transition-type() pseudo-class#6992
0b1e194
Thanks @ ematipico! - Added a new JSON rule callednoQuickfixBiome
, which disallow the use of code actionquickfix.biome
inside code editor settings.#6943
249306d
Thanks @ JamBalaya56562! - Fixed@ vitest/eslint-plugin
source url.#6947
4c7ed0f
Thanks @ JamBalaya56562! - Fixed ESLint migration for the ruleprefer-for
fromeslint-plugin-solid
to Biome'suseForComponent
.#6976
72ebadc
Thanks @ siketyan! - Fixed #6692: The rulesnoUnusedVariables
andnoUnusedFunctionParameters
no longer cause an infinite loop when the suggested name is not applicable (e.g. the suggested name is already declared in the scope).#6990
333f5d0
Thanks @ rvanlaarhoven! - Fixed the documentation URL forlint/correctness/noUnknownPseudoClass
#7000
4021165
Thanks @ harxki! - Fixed #6795:noUnassignedVariables
now correctly recognizes variables used in JSXref
attributes.#7044
b091ddf
Thanks @ ematipico! - Fixed #6622, now the ruleuseSemanticElements
works for JSX self-closing elements too.#7014
c4864e8
Thanks @ siketyan! - Fixed #6516: Thebiome migrate
command no longer break the member list with trailing comments.#6979
29cb6da
Thanks @ unvalley! - Fixed #6767:useSortedClasses
now correctly removes leading and trailing whitespace in className.Previously, trailing spaces in className were not fully removed.
<div <span class="pl...