-
-
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
chore(deps): update dependency @biomejs/biome to v1.8.2 #95
Conversation
Review or Edit in CodeSandboxOpen the branch in Web Editor • VS Code • Insiders |
|
Important Review skippedBot user detected. To trigger a single review, invoke 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 Configration File (
|
New and removed dependencies detected. Learn more about Socket for GitHub ↗︎
🚮 Removed packages: npm/@biomejs/biome@1.8.1 |
This PR contains the following updates:
1.8.1
->1.8.2
Release Notes
biomejs/biome (@biomejs/biome)
v1.8.2
Compare Source
CLI
Bug fixes
biome migrate
and thus choke the parser. Contributed by @Sec-antEnhancement
Reword the reporter message
No fixes needed
toNo 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,
noDebugger
was disabled for theindex.js
file.The rule is now correctly enabled for the
index.js
file.Contributed by @Conaclos
Formatter
Bug fixes
JavaScript APIs
Bug fixes
v1.8.0
Linter
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
noUnmatchableAnbSelector
rule is now able to catch unmatchablean+b
selectors like0n+0
or-0n+0
. Contributed by @Sec-ant.The
useHookAtTopLevel
rule 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
useLiteralKeys
rule. (#3160)This rule now ignores the following kind of computed member name:
Contributed by @Sec-ant
The noUnknownProperty rule now ignores the
composes
property 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:
Also,
export default function
andexport default class
are considered stable now because they can only appear at the top level of a module.Contributed by @Sec-ant
Fix missing
withDefaults
macro in vue files for globals variables. Contributed by @Shyam-ChenParser
Bug fixes
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ 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 has been generated by Mend Renovate. View repository job log here.