-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Snyk] Upgrade @biomejs/biome from 1.6.4 to 1.8.1 #2
[Snyk] Upgrade @biomejs/biome from 1.6.4 to 1.8.1 #2
Conversation
Snyk has created this PR to upgrade @biomejs/biome from 1.6.4 to 1.8.1. See this package in npm: @biomejs/biome See this project in Snyk: https://app.snyk.io/org/abdulrahman305/project/c01acaeb-ea2f-49e0-8168-1d9a94d07d11?utm_source=github&utm_medium=referral&page=upgrade-pr
👋 I'm here to help you review your pull request. When you're ready for me to perform a review, you can comment anywhere on this pull request with this command: As a reminder, here are some helpful tips on how we can collaborate together:
|
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 using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
PR summaryThis Pull Request upgrades the SuggestionEnsure that the upgrade does not introduce any breaking changes by thoroughly testing the application with the new version. Additionally, review the new features and enhancements to see if any can be leveraged to improve the project's code quality and maintainability. Disclaimer: This comment was entirely generated using AI. Be aware that the information provided may be incorrect. Current plan usage: 14.58% Have feedback or need help? |
This PR was automatically created by Snyk using the credentials of a real user.
![snyk-top-banner](https://github.com/andygongea/OWASP-Benchmark/assets/818805/c518c423-16fe-447e-b67f-ad5a49b5d123)
Snyk has created this PR to upgrade @biomejs/biome from 1.6.4 to 1.8.1.
ℹ️ 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 22 days ago.
Issues fixed by the recommended upgrade:
SNYK-JS-BRACES-6838727
SNYK-JS-MICROMATCH-6838728
Release notes
Package name: @biomejs/biome
CLI
Bug fixes
--staged
or--changed
options. Contributed by @ unvalleyConfiguration
Bug fixes
indentWidth
. Contributed by @ ematipicoFormatter
Bug fixes
Linter
Bug fixes
The
noEmptyBlock
css 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,
arg
was 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
Other changes
apply
bywrite
option by @ Jayllyz in #3071use-adjacent-overload-signature
diagnostic by @ chansuke in #3095package.json
like npm does by @ ematipico in #3155useConsistentGridAreas
by @ chansuke in #2940New Contributors
Full Changelog: cli/v1.8.0...cli/v1.8.1
Analyzer
New features
used for the lint rule
useExhaustiveDependencies
, which is now able tosuppress specific dependencies. Fixes change: rename locals to debugger (#2503) continuedev/continue#2509. Contributed by @ arendjr
Enhancements
Astro
object is always a global when processing.astro
files. Contributed by @ minht11.vue
files. (#2771) Contributed by @ dyc3CLI
New features
New
clean
command. Use this new command to clean after thebiome-logs
directory, and remove all the log files.Add two new options
--only
and--skip
to the commandbiome lint
(#58).The
--only
option allows you to run a given rule or rule group,For example, the following command runs only the
style/useNamingConvention
andstyle/noInferrableTypes
rules.If the rule is disabled in the configuration, then its severity level is set to
error
for a recommended rule orwarn
otherwise.Passing a group does not change the severity level of the rules in the group.
All the disabled rules in the group will remain disabled.
To ensure that the group is run, the
recommended
field of the group is enabled.The
nursery
group cannot be passed, as no rules are enabled by default in the nursery group.The
--skip
option allows you to skip the execution of a given group or a given rule.For example, the following command skips the
style
group and thesuspicious/noExplicitAny
rule.You can also use
--only
and--skip
together.--skip
oevrrides--only
.The following command executes only the rules from the
style
group, but thestyle/useNamingConvention
rule.These options are compatible with other options such as
--write
(previously--apply
), and--reporter
.Contributed by @ Conaclos
Add new command
biome clean
. Use this command to purge all the logs emitted by the Biome daemon. This command is really useful, because the Biome daemon tendslog many files and contents during its lifecycle. This means that if your editor is open for hours (or even days), the
biome-logs
folder could become quite heavy. Contributed by @ ematipicoAdd support for formatting and linting CSS files from the CLI. These operations are opt-in for the time being.
If you don't have a configuration file, you can enable these features with
--css-formatter-enabled
and--css-linter-enabled
:Contributed by @ ematipico
Add new CLI options to control the CSS formatting. Check the CLI reference page for more details. Contributed by @ ematipico
Add new options
--write
,--fix
(alias of--write
) and--unsafe
to the commandbiome lint
andbiome check
.Add a new option
--fix
(alias of--write
) to the commandbiome format
andbiome migrate
.The
biome <lint|check> --<write|fix>
has the same behavior asbiome <lint|check> --apply
.The
biome <lint|check> --<write|fix> --unsafe
has the same behavior asbiome <lint|check> --apply-unsafe
.The
biome format --fix
has the same behavior asbiome format --write
.The
biome migrate --fix
has the same behavior asbiome migrate --write
.This change allows these commands to write modifications in the same options.
With this change, the
--apply
and--apply-unsafe
options are deprecated.Contributed by @ unvalley
Enhancements
Biome now executes commands (lint, format, check and ci) on the working directory by default. #2266 Contributed by @ unvalley
biome migrate eslint
now tries to convert ESLint ignore patterns into Biome ignore patterns.ESLint uses gitignore patterns.
Biome now tries to convert these patterns into Biome ignore patterns.
For example, the gitignore pattern
/src
is a relative path to the file in which it appears.Biome now recognizes this and translates this pattern to
./src
.Contributed by @ Conaclos
biome migrate eslint
now supports theeslintIgnore
field inpackage.json
.ESLint allows the use of
package.json
as an ESLint configuration file.ESLint supports two fields:
eslintConfig
andeslintIgnore
.Biome only supported the former. It now supports both.
Contributed by @ Conaclos
biome migrate eslint
now propagates NodeJS errors to the user.This will help users to identify why Biome is unable to load some ESLint configurations.
Contributed by @ Conaclos
Add a new
--reporter
calledsummary
. This reporter will print diagnostics in a different way, based on the tools (formatter, linter, etc.) that are executed.Import sorting and formatter shows the name of the files that require formatting. Instead, the linter will group the number of rules triggered and the number of errors/warnings:
Formatter ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
The following files needs to be formatted:
main.ts
index.ts
Organize Imports ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
The following files needs to have their imports sorted:
main.ts
index.ts
Analyzer ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Some analyzer rules were triggered
Rule Name Diagnostics
lint/suspicious/noImplicitAnyLet 12 (12 error(s), 0 warning(s), 0 info(s))
lint/suspicious/noDoubleEquals 8 (8 error(s), 0 warning(s), 0 info(s))
lint/suspicious/noRedeclare 12 (12 error(s), 0 warning(s), 0 info(s))
lint/suspicious/noDebugger 20 (20 error(s), 0 warning(s), 0 info(s))
Contributed by @ ematipico
biome ci
now enforces printing the output using colours. If you were previously using--colors=force
, you can remove it because it's automatically set. Contributed by @ ematipicoAdd a new
--reporter
calledgithub
. This reporter will print diagnostics using GitHub workflow commands:Contributed by @ ematipico
Add a new
--reporter
calledjunit
. This reporter will print diagnostics using GitHub workflow commands:Contributed by @ ematipico
Bug fixes
biome init
would createbiome.json
even ifbiome.jsonc
already exists. Contributed by @ minht11Configuration
New features
Add an rule option
fix
to override the code fix kind of a rule (#2882).A rule can provide a safe or an unsafe code action.
You can now tune the kind of code actions thanks to the
fix
option.This rule option takes a value among:
none
: the rule no longer emits code actions.safe
: the rule emits safe code action.unsafe
: the rule emits unsafe code action.The following configuration disables the code actions of
noUnusedVariables
, makes the emitted code actions ofstyle/useConst
andstyle/useTemplate
unsafe and safe respectively.Contributed by @ Conaclos
Add option
javascript.linter.enabled
to control the linter for JavaScript (and its super languages) files. Contributed by @ ematipicoAdd option
json.linter.enabled
to control the linter for JSON (and its super languages) files. Contributed by @ ematipicoAdd option
css.linter.enabled
to control the linter for CSS (and its super languages) files. Contributed by @ ematipicoAdd option
css.formatter
, to control the formatter options for CSS (and its super languages) files. Contributed by @ ematipicoYou can now change the severity of lint rules down to
"info"
. The"info"
severity doesn't emit error codes, and it isn't affected by other options like--error-on-warnings
:Contributed by @ ematipico
Enhancements
javascript.formatter.trailingComma
option is deprecated and renamed tojavascript.formatter.trailingCommas
. The corresponding CLI option--trailing-comma
is also deprecated and renamed to--trailing-commas
. Details can be checked in #2492. Contributed by @ Sec-antBug fixes
override that did not specify the formatter section #2924. Contributed by @ dyc3
biome.json
. Contributed by @ dyc3Editors
New features
Enhancements
Formatting and linting is disabled until the configuration file is fixed. Contributed by @ ematipico
Bug fixes
Formatter
Bug fixes
JavaScript APIs
Linter
Promoted rules
New rules are incubated in the nursery group. Once stable, we promote them to a stable group. The following rules are promoted: