[Snyk] Upgrade @biomejs/biome from 1.7.1 to 1.8.3 #3
Conversation
Snyk has created this PR to upgrade @biomejs/biome from 1.7.1 to 1.8.3. See this package in npm: @biomejs/biome See this project in Snyk: https://app.snyk.io/org/ramzimalhas/project/aef67e1b-a09f-4098-8364-02e634969906?utm_source=github&utm_medium=referral&page=upgrade-pr
|
|
Important Review skippedIgnore keyword(s) in the title. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting 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 Configuration File (
|
|
Changes made by this pull request: package-lock.json package.json |
Snyk has created this PR to upgrade @biomejs/biome from 1.7.1 to 1.8.3.
ℹ️ 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 9 versions ahead of your current version.
The recommended version was released on 2 months ago.
Release notes
Package name: @biomejs/biome
CLI
Bug fixes
Fix #3104 by suppressing node warnings when using
biome migrate. Contributed by @ SuperchupuDevForce colors to be off when using the GitHub reporter to properly create annotations in GitHub actions (#3148). Contributed by @ Sec-ant
Parser
Bug fixes
Formatter
Bug fixes
Linter
New features
nursery/useDeprecatedReasonrule. Contributed by @ vohoanglong0107.Bug fixes
useConsistentArrayTypeanduseShorthandArrayTypenow ignoreArrayin theextendsandimplementsclauses. Fix #3247. Contributed by @ Conaclospackage.json. Contributed by @ ematipicouseArrowFunctionrule now preserves a trailing comma when there is only a single type parameter in the arrow function and JSX is enabled. Fixes #3292. Contributed by @ Sec-antEnhancements
Enhance tailwind sorting lint rule #1274 with variant support.
Every preconfigured variant is assigned a
weightthat concurs on establishing the output sorting order.Since nesting variants on the same utility class is possible, the resulting
weightis the Bitwise XOR of all the variants weight for that class.Dynamic variants (e.g.
has-[.custom-class],group-[:checked]) are also supported and they take theweightof their base variant name the custom value attached (e.g.has-[.custom-class]takeshasweight).Arbitrary variants (e.g.
[&nth-child(2)]) don't have a weight assigned and they are placed after every known variant.Classes with the same amount of arbitrary variants follow lexicographical order. The class that has the highest number of nested arbitrary variants is placed last.
Screen variants (e.g.
sm:,max-md:,min-lg:) are not supported yet.Contributed by @ lutaok
What's Changed
Other changes
pull_diagnosticsfor graphql by @ ematipico in #3248noUnknownPropertyby @ togami2864 in #3252biome_graphql_analyzeby @ ematipico in #3276JsonParserSettingstoOptionby @ dyc3 in #3272CssParserSettingstoOptionby @ dyc3 in #3273New Contributors
Full Changelog: cli/v1.8.2...cli/v1.8.3
CLI
Bug fixes
biome migrateand thus choke the parser. Contributed by @ Sec-antEnhancement
Reword the reporter message
No fixes neededtoNo fixes applied.The former message is misleading when there're still errors or warnings in the files that should be taken care of manually. For example:
The new message suits better in these cases.
Contributed by @ Sec-ant
Configuration
Bug fixes
Don't conceal previous overrides (#3176).
Previously, each override inherited the unset configuration of the base configuration.
This means that setting a configuration in an override can be concealed by a subsequent override that inherits of the value from the base configuration.
For example, in the next example,
noDebuggerwas disabled for theindex.jsfile.{ "linter": { "rules": { "suspicious": { "noDebugger": "off" } } }, "overrides": [ { "include": ["index.js"], "linter": { "rules": { "suspicious": { "noDebugger": "warn" } } } }, { "include": ["index.js"], "linter": { "rules": { "suspicious": { "noDoubleEquals": "off" } } } } ] }The rule is now correctly enabled for the
index.jsfile.Contributed by @ Conaclos
Formatter
Bug fixes
JavaScript APIs
Bug fixes
v1.8.0Linter
New features
Bug fixes
Add nursery/noShorthandPropertyOverrides. #2958 Contributed by @ neokidev
Fix [#3084] false positive by correctly recognize parenthesized return statement. Contributed by @ unvalley
useImportExtensions now suggests a correct fix for
import '.'andimport './.'. Contributed by @ minht11Fix useDateNow false positive when new Date object has arguments
new Date(0).getTime(). Contributed by @ minht11.The
noUnmatchableAnbSelectorrule is now able to catch unmatchablean+bselectors like0n+0or-0n+0. Contributed by @ Sec-ant.The
useHookAtTopLevelrule now recognizes properties named as hooks likefoo.useFoo(). Contributed by @ ksnyder9801Fix #3092, prevent warning for
Custom properties (--*). Contributed by @ chansukeFix a false positive in the
useLiteralKeysrule. (#3160)This rule now ignores the following kind of computed member name:
Contributed by @ Sec-ant
The noUnknownProperty rule now ignores the
composesproperty often used in css modules. #3000 Contributed by @ chansukeFix false positives of the useExhaustiveDependencies rule.
The component itself is considered stable when it is used recursively inside a hook closure defined inside of it:
function MyRecursiveComponent() {
// MyRecursiveComponent is stable, we don't need to add it to the dependencies list.
const children = useMemo(() => <MyRecursiveComponent />, []);
return <div>{children}</div>;
}
Also,
export default functionandexport default classare considered stable now because they can only appear at the top level of a module.Contributed by @ Sec-ant
Fix missing
withDefaultsmacro in vue files for globals variables. Contributed by @ Shyam-ChenParser
Bug fixes
What's Changed
Other changes
jscode blocks containing JSX elements tojsxby @ Sec-ant in #3168noSubstrby @ chansuke in #3125useSortedKeysfor JSON objects by @ ematipico in #2412--compactflag forpkg.pr.newby @ Sec-ant in #3180--compactflag by @ Sec-ant in #3181chansuketo maintainers list by @ chansuke in #3206enumflags2by @ ematipico in #3230New Contributors
Full Changelog: cli/v1.8.1...cli/v1.8.2
CLI
Bug fixes
--stagedor--changedoptions. Contributed by @ unvalleyConfiguration
Bug fixes
indentWidth. Contributed by @ ematipicoFormatter
Bug fixes
Linter
Bug fixes
The
noEmptyBlockcss lint rule now treats empty blocks containing comments as valid ones. Contributed by @ Sec-antuseLiteralKeys no longer reports quoted member names (#3085).
Previously useLiteralKeys reported quoted member names that can be unquoted.
For example, the rule suggested the following fix:
This conflicted with the option quoteProperties of our formatter.
The rule now ignores quoted member names.
Contributed by @ Conaclos
noEmptyInterface now ignores empty interfaces in ambient modules (#3110). Contributed by @ Conaclos
noUnusedVariables and noUnusedFunctionParameters no longer report the parameters of a constructor type (#3135).
Previously,
argwas reported as unused in a constructor type like:Contributed by @ Conaclos
noStringCaseMismatch now ignores escape sequences (#3134).
The following code is no longer reported by the rule:
Contributed by @ Conaclos
Parser
New features
Bug fixes