-
-
Notifications
You must be signed in to change notification settings - Fork 31
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 all minor update of dev dependencies #825
Open
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/all-minor-dependencies
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
renovate
bot
force-pushed
the
renovate/all-minor-dependencies
branch
from
February 15, 2024 17:22
ad9a19c
to
ccd1ea9
Compare
renovate
bot
changed the title
chore(deps): update dependency sponsorkit to v0.9.1
chore(deps): update all minor update of dev dependencies
Feb 15, 2024
renovate
bot
force-pushed
the
renovate/all-minor-dependencies
branch
2 times, most recently
from
February 23, 2024 21:13
592051b
to
9c21a3d
Compare
renovate
bot
force-pushed
the
renovate/all-minor-dependencies
branch
3 times, most recently
from
February 28, 2024 15:55
43b9e4a
to
3c05693
Compare
renovate
bot
force-pushed
the
renovate/all-minor-dependencies
branch
3 times, most recently
from
March 12, 2024 14:27
5b2cb50
to
85e5ba8
Compare
renovate
bot
force-pushed
the
renovate/all-minor-dependencies
branch
6 times, most recently
from
March 25, 2024 19:28
3fa55d9
to
5aedd65
Compare
renovate
bot
force-pushed
the
renovate/all-minor-dependencies
branch
2 times, most recently
from
April 4, 2024 20:14
3fa7215
to
3069599
Compare
renovate
bot
force-pushed
the
renovate/all-minor-dependencies
branch
2 times, most recently
from
April 15, 2024 14:57
47eea5c
to
6264312
Compare
renovate
bot
force-pushed
the
renovate/all-minor-dependencies
branch
from
April 22, 2024 19:26
6264312
to
e779e9a
Compare
renovate
bot
force-pushed
the
renovate/all-minor-dependencies
branch
6 times, most recently
from
May 7, 2024 00:14
bb899ef
to
6f63f24
Compare
renovate
bot
force-pushed
the
renovate/all-minor-dependencies
branch
4 times, most recently
from
June 25, 2024 09:09
d1061a6
to
2f67fd4
Compare
renovate
bot
force-pushed
the
renovate/all-minor-dependencies
branch
2 times, most recently
from
July 1, 2024 20:11
d0371b1
to
042f32e
Compare
renovate
bot
force-pushed
the
renovate/all-minor-dependencies
branch
4 times, most recently
from
July 11, 2024 20:00
f1a8fb8
to
bec1595
Compare
renovate
bot
force-pushed
the
renovate/all-minor-dependencies
branch
5 times, most recently
from
July 18, 2024 16:39
59213a2
to
d7af7da
Compare
renovate
bot
force-pushed
the
renovate/all-minor-dependencies
branch
2 times, most recently
from
July 27, 2024 10:29
e4328b8
to
e1f6f1b
Compare
renovate
bot
force-pushed
the
renovate/all-minor-dependencies
branch
from
August 1, 2024 11:11
e1f6f1b
to
87e9207
Compare
renovate
bot
force-pushed
the
renovate/all-minor-dependencies
branch
from
August 10, 2024 17:24
87e9207
to
28a2d61
Compare
renovate
bot
force-pushed
the
renovate/all-minor-dependencies
branch
3 times, most recently
from
August 23, 2024 20:01
b5479d4
to
8948aed
Compare
renovate
bot
force-pushed
the
renovate/all-minor-dependencies
branch
5 times, most recently
from
September 12, 2024 18:52
f4a0231
to
68bc6d5
Compare
renovate
bot
force-pushed
the
renovate/all-minor-dependencies
branch
from
September 15, 2024 19:35
68bc6d5
to
5798671
Compare
renovate
bot
force-pushed
the
renovate/all-minor-dependencies
branch
from
September 19, 2024 17:20
5798671
to
e71b254
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR contains the following updates:
1.5.3
->1.9.2
10.0.6
->10.0.8
4.3.4
->4.3.7
8.0.1
->8.1.0
0.8.5
->0.15.5
29.1.2
->29.2.5
5.3.3
->5.6.2
Release Notes
biomejs/biome (@biomejs/biome)
v1.9.2
Compare Source
CLI
New features
Added support for custom GritQL definitions, including:
Contributed by @arendjr
Bug fixes
contains
queries to report false positives when the matchednode appeared inside a sibling node. Contributed by @arendjr
Editors
Bug fixes
Fix #3923. Now the
.editorconfig
is correctly parsed by the LSP, and the options are correctly applied to files when formatting is triggered.Plus, the Biome LSP now watches for any change to the
.editorconfig
, and updates the formatting settings.Reduced the number of log files generated by the LSP server. Now the maximum number of logs saved on disk is seven. Contributed by @ematipico
Fix the code actions capabilities available in the LSP Biome server. Before, the LSP was using the default capabilities, which resulted in pulling code actions even when they were disabled by the editor.
This means that the code actions are pulled by the client only when the editor enables
quickfix.biome
,source.organizeImports.biome
andsource.fixAll.biome
.Now, if you enable
organizeImports.enabled: true
in thebiome.json
, and then you configure your editor with the following code actionsource.organizeImports.biome: false
, the editor won't sort the imports.Contributed by @ematipico
Linter
New features
Bug fixes
noLabelWithoutControl now accept JSX expression as label value (#3875). Contributed by @Conaclos
useFilenamingConvention no longer suggests names with a disallowed case (#3952). Contributed by @Conaclos
useFilenamingConvention now recognizes file names starting with ASCII digits as lowercase (#3952).
Thus,
2024-09-17-filename
,2024_09_17_filename
and20240917FileName
are inkebab-case
,snake_case
, andcamelCase
respectively.Contributed by @Conaclos
useFilenamingConvention now applies the configured formats to the file extensions (#3650). Contributed by @Conaclos
Parser
Bug fixes
useStrictMode now reports Script files with some directives, but without the
use strict
directive. Contributed by @ConaclosThe CSS parser now accepts the characters U+FFDCF and U+FFFD in identifiers. Contributed by @Conaclos
v1.9.1
Compare Source
Analyzer
CLI
Bug fixes
useEditorConfig
now loads the editorconfig when runningbiome ci
#3864. Contributed by @dyc3Revert #3731 to fix broken quick fixes and code actions. Contributed by @nhedger
Configuration
Editors
Formatter
JavaScript APIs
Linter
New Features
Bug fixes
useSemanticElements now ignores
alert
andalertdialog
roles (3858). Contributed by @ConaclosnoUndeclaredDependencies now ignores
@/
imports and recognizes type imports from Definitely Typed andbun
imports. Contributed by @ConaclosParser
v1.9.0
Compare Source
Analyzer
CLI
New features
Add
--graphql-linter-enabled
option, to control whether the linter should be enabled or not for GraphQL files. Contributed by @ematipicoNew EXPERIMENTAL
search
command. The search command allows you to search a Biome project using GritQL syntax.GritQL is a powerful language that lets you do structural searches on your codebase. This means that trivia such as whitespace or even the type of strings quotes used will be ignored in your search query. It also has many features for querying the structure of your code, making it much more elegant for searching code than regular expressions.
While we believe this command may already be useful to users in some situations (especially when integrated in the IDE extensions!), we also had an ulterior motive for adding this command: We intend to utilize GritQL for our plugin efforts, and by allowing our users to try it out in a first iteration, we hope to gain insight in the type of queries you want to do, as well as the bugs we need to focus on.
For now, the
search
command is explicitly marked as EXPERIMENTAL, since many bugs remain. Keep this in mind when you try it out, and please let us know your issues!Note: GritQL escapes code snippets using backticks, but most shells interpret backticks as command invocations. To avoid this, it's best to put single quotes around your Grit queries.
Contributed by @arendjr and @BackupMiles
The option
--max-diagnostics
now accept anone
value, which lifts the limit of diagnostics shown. Contributed by @ematipicoAdd a new reporter
--reporter=gitlab
, that emits diagnostics for using the GitLab Code Quality report.Contributed by @NiclasvanEyk
Add new options to the
lsp-proxy
andstart
commands:--log-path
: a directory where to store the daemon logs. The commands also accepts the environment variableBIOME_LOG_PATH
.--log-prefix-name
: a prefix that's added to the file name of the logs. It defaults toserver.log
. The commands also accepts the environment variableBIOME_LOG_PREFIX_NAME
.@Contributed by @ematipico
Enhancements
When a
--reporter
is provided, and it's different from the default one, the value provided by via--max-diagnostics
is ignored and the limit is lifted. Contributed by @ematipicobiome init
now generates a new config file with more options set.This change intends to improve discoverability of the options and to set the more commonly used options to their default values.
Contributed by @Conaclos
The
--verbose
flag now reports the list of files that were evaluated, and the list of files that were fixed.The evaluated files are the those files that can be handled by Biome, files that are ignored, don't have an extension or have an extension that Biome can't evaluate are excluded by this list.
The fixed files are those files that were handled by Biome and changed. Files that stays the same after the process are excluded from this list.
Contributed by @ematipico
Allow passing
nursery
to the--only
and--skip
filters.The
--only
option allows you to run a given rule or rule group.The
--skip
option allows you to skip the execution of a given group or a given rule.Previously, it was not possible to pass
nursery
.This restriction is now removed, as it may make sense to skip the nursery rules that a project has enabled.
Contributed by @Conaclos
The CLI now returns an error code when calling a command in
stdin
mode, and the contents of the files aren't fixed. For example, the following example will result in an error code of1
because thelint
command triggers some lint rules:Contributed by @ematipico
Bug fixes
biome lint --write
now takes--only
and--skip
into account (#3470). Contributed by @ConaclosFix #3368, now the reporter
github
tracks the diagnostics that belong to formatting and organize imports. Contributed by @ematipicoFix #3545, display a warning, 'Avoid using unnecessary Fragment,' when a Fragment contains only one child element that is placed on a new line. Contributed by @satojin219
Migrating from Prettier or ESLint no longer overwrite the
overrides
field from the configuration (#3544). Contributed by @ConaclosFix JSX expressions for
noAriaHiddenOnFocusable
(#3708). Contributed by @anthonyshewFix edge case for
<canvas>
elements that userole="img"
(#3728). Contributed by @anthonyshewFix #3633, where diagnostics where incorrectly printed if the code has errors. Contributed by @ematipico
Allow
aria-label
on heading to preventuseHeadingContent
diagnostic (#3767). Contributed by @anthonyshewFix edge case #3791 for rule
noFocusedTests
being used with non-string-like expressions (#3793). Contributed by @h-a-n-aFix optional ARIA properties for
role="separator"
inuseAriaPropsForRole
(#3856). Contributed by @anthonyshewConfiguration
Add support for loading configuration from
.editorconfig
files (#1724).Configuration supplied in
.editorconfig
will be overridden by the configuration inbiome.json
. Support is disabled by default and can be enabled by adding the following to your formatter configuration inbiome.json
:Contributed by @dyc3
overrides
from an extended configuration is now merged with theoverrides
of the extension.Given the following shared configuration
biome.shared.json
:and the following configuration:
Previously, the
overrides
frombiome.shared.json
was overwritten.It is now merged and results in the following configuration:
Contributed by @Conaclos
Editors
Fix #3577, where the update of the configuration file was resulting in the creation of a new internal project. Contributed by @ematipico
Fix #3696, where
biome.jsonc
was incorrectly parsed with incorrect options. Contributed by @ematipicoFormatter
The CSS formatter is enabled by default. Which means that you don't need to opt-in anymore using the configuration file
biome.json
:Contributed by @ematipico
Add parentheses for nullcoalescing in ternaries.
This change aligns on Prettier 3.3.3.
This adds clarity to operator precedence.
Contributed by @Conaclos
Keep the parentheses around
infer ... extends
declarations in type unions and type intersections (#3419). Contributed by @ConaclosKeep parentheses around a
yield
expression inside a type assertion.Previously, Biome removed parentheses around some expressions that require them inside a type assertion.
For example, in the following code, Biome now preserves the parentheses.
Contributed by @Conaclos
Remove parentheses around expressions that don't need them inside a decorator.
Biome now matches Prettier in the following cases:
Contributed by @Conaclos
Keep parentheses around objects preceded with a
@satisfies
comment.In the following example, parentheses are no longer removed.
Contributed by @Conaclos
Linter
Promoted rules
New rules are incubated in the nursery group.
Once stable, we promote them to a stable group.
The following CSS rules are promoted:
The following JavaScript rules are promoted:
Deprecated rules
correctness/noInvalidNewBuiltin
is deprecated. Use correctness/noInvalidBuiltinInstantiation instead.style/useSingleCaseStatement
is deprecated. Use correctness/noSwitchDeclarations instead.suspicious/noConsoleLog
is deprecated. Use suspicious/noConsole instead.New features
Implement css suppression action. Contributed by @togami2864
Add support for GraphQL linting. Contributed by @ematipico
Add nursery/noCommonJs. Contributed by @minht11
Add nursery/noDuplicateCustomProperties. Contributed by @chansuke
Add nursery/noEnum. Contributed by @nickfla1
Add nursery/noDynamicNamespaceImportAccess. Contributed by @minht11
Add nursery/noIrregularWhitespace. Contributed by @michellocana
Add nursery/noRestrictedTypes. Contributed by @minht11
Add nursery/noSecrets. Contributed by @SaadBazaz
Add nursery/noUselessEscapeInRegex. Contributed by @Conaclos
Add nursery/noValueAtRule. Contributed by @rishabh3112
Add nursery/useAriaPropsSupportedByRole. Contributed by @ryo-ebata
Add nursery/useConsistentMemberAccessibility. Contributed by @seitarof
Add nursery/useStrictMode. Contributed by @ematipico
Add nursery/useTrimStartEnd. Contributed by @chansuke
Add nursery/noIrreguluarWhitespace. Contributed by @DerTimonius
Enhancements
Rename
nursery/noUnknownSelectorPseudoElement
tonursery/noUnknownPseudoElement
. Contributed by @togami2864The CSS linter is now enabled by default. Which means that you don't need to opt-in anymore using the configuration file
biome.json
:Contributed by @ematipico
The JavaScript linter recognizes TypeScript 5.5 and 5.6 globals. Contributed by @Conaclos
noBlankTarget now supports an array of allowed domains.
The following configuration allows
example.com
andexample.org
as blank targets.Contributed by @Jayllyz
noConsole now accepts an option that specifies some allowed calls on
console
. Contributed by @ConaclosAdd an
ignoreNull
option for noDoubleEquals.By default the rule allows loose comparisons against
null
.The option
ignoreNull
can be set tofalse
for reporting loose comparison againstnull
.Contributed by @peaBerberian.
noDuplicateObjectKeys now works for JSON and JSONC files. Contributed by @ematipico
noInvalidUseBeforeDeclaration now reports direct use of an enum member before its declaration.
In the following code,
A
is reported as use before its declaration.Contributed by @Conaclos
noNodejsModules now ignores imports of a package which has the same name as a Node.js module. Contributed by @Conaclos
noNodejsModules now ignores type-only imports (#1674).
The rule no longer reports type-only imports such as:
Contributed by @Conaclos
noRedundantUseStrict no longer reports
"use strict"
directives when thepackage.json
marks explicitly the file as a script using the field"type": "commonjs"
. Contributed by @ematipiconoStaticOnlyClass no longer reports a class that extends another class (#3612). Contributed by @errmayank
noUndeclaredVariables no longer reports a direct reference to an enum member (#2974).
In the following code, the
A
reference is no longer reported as an undeclared variable.Contributed by @Conaclos
noUndeclaredVariables recognized Svelte 5 runes in Svelte components and svelte files.
Svelte 5 introduced runes.
The rule now recognizes Svelte 5 runes in files ending with the
.svelte
,.svelte.js
or.svelte.ts
extensions.Contributed by @Conaclos
noUnusedVariables now checks TypeScript declaration files.
This allows to report a type that is unused because it isn't exported.
Global declarations files (declarations files without exports and imports) are still ignored.
Contributed by @Conaclos
useFilenamingConvention now supports unicase letters.
unicase letters have a single case: they are neither uppercase nor lowercase.
Biome now accepts filenames in unicase.
For example, the filename
안녕하세요
is now accepted.We still reject a name that mixes unicase characters with lowercase or uppercase characters.
For example, the filename
A안녕하세요
is rejected.This change also fixes #3353.
Filenames consisting only of numbers are now accepted.
Contributed by @Conaclos
useFilenamingConvention now supports Next.js/Nuxt/Astro dynamic routes (#3465).
Next.js, SolidStart, Nuxt, and Astro support dynamic routes such as
[...slug].js
and[[...slug]].js
.Biome now recognizes this syntax.
slug
must contain only alphanumeric characters.Contributed by @Conaclos
useExportType no longer reports empty
export
(#3535).An empty
export {}
allows you to force TypeScript to consider a file with no imports and exports as an EcmaScript module.While
export type {}
is valid, it is more common to useexport {}
.Users may find it confusing that the linter asks them to convert it to
export type {}
.Also, a bundler should be able to remove
export {}
as well asexport type {}
.So it is not so useful to report
export {}
.Contributed by @Conaclos
Bug fixes
noControlCharactersInRegex now corretcly handle
\u
escapes in unicode-aware regexes.Previously, the rule didn't consider regex with the
v
flags as unicode-aware regexes.Moreover,
\uhhhh
was not handled in unicode-aware regexes.Contributed by @Conaclos
noControlCharactersInRegex now reports control characters and escape sequence of control characters in string regexes. Contributed by @Conaclos
noExcessiveNestedTestSuites
: fix an edge case where the rule would alert on heavily nested zod schemas. Contributed by @dyc3noExtraNonNullAssertion
no longer reports a single non-null assertion enclosed in parentheses (#3352). Contributed by @ConaclosnoMultipleSpacesInRegularExpressionLiterals now correctly provides a code fix when Unicode characters are used. Contributed by @Conaclos
noRedeclare no longer report redeclartions for lexically scoped function declarations #3664.
In JavaScript strict mode, function declarations are lexically scoped:
they cannot be accessed outside the block where they are declared.
In non-strict mode, function declarations are hoisted to the top of the enclosing function or global scope.
Previously Biome always hoisted function declarations.
It now takes into account whether the code is in strict or non strict mode.
Contributed by @Conaclos
noUndeclaredDependencies now ignores self package imports.
Given teh following
package.json
:The following import is no longer reported by the rule:
Contributed by @Conaclos
Fix [#3149] crashes that occurred when applying the
noUselessFragments
unsafe fixes in certain scenarios. Contributed by @unvalleynoRedeclare no longer reports a variable named as the function expression where it is declared. Contributed by @Conaclos
useAdjacentOverloadSignatures
no longer reports a#private
class member and a public class member that share the same name (#3309).The following code is no longer reported:
Contributed by @Conaclos
useAltText n olonger requests alt text for elements hidden from assistive technologies (#3316). Contributed by @robintown
useNamingConvention now accepts applying custom convention on abstract classes. Contributed by @Conaclos
useNamingConvention no longer suggests an empty fix when a name doesn't match strict Pascal case (#3561).
Previously the following code led
useNamingConvention
to suggest an empty fix.The rule no longer provides a fix for this case.
Contributed by @Conaclos
useNamingConvention no longer provides fixes for global TypeScript declaration files.
Global TypeScript declaration files have no epxorts and no imports.
All the declared types are available in all files of the project.
Thus, it is not safe to propose renaming only in the declaration file.
Contributed by @Conaclos
useSortedClasses lint error with Template literals (#3394). Contributed by @hangaoke1
useValidAriaValues now correctly check property types (3748).
Properties that expect a string now accept arbitrary text.
An identifiers can now be made up of any characters except ASCII whitespace.
An identifier list can now be separated by any ASCII whitespace.
Contributed by @Conaclos
Parser
Enhancements
The JSON parser now allows comments in
turbo.json
andjest.config.json
. Contributed by @Netail and @ConaclosThe JSON parser now allows comments in files with the
.json
extension under the.vscode
and.zed
directories.Biome recognizes are well known JSON files that allows comments and/or trailing commas.
Previously, Biome did not recognize JSON files under the
.vscode
and the.zed
directories as JSON files that allow comments.You had to configure Biome to recognize them:
This override is no longer needed!
Note that JSON files under the
.vscode
and the.zed
directories don't accept trailing commas.Contributed by @Conaclos
Bug fixes
The CSS parser now accepts emoji in identifiers (3627).
The following code is now correctly parsed:
Contributed by @Conaclos
Fix #3287 nested selectors with pseudo-classes. Contributed by @denbezrukov
Fix #3349 allow CSS multiple ampersand support. Contributed by @denbezrukov
Fix #3410 by correctly parsing break statements containing keywords.
Contributed by @ah-yu
Fix #3464 by enabling JSX in
.vue
files that use thelang='jsx'
orlang='tsx'
attribute. Contributed by @ematipicov1.8.3
Compare Source
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/useDeprecatedReason
rule. Contributed by @vohoanglong0107.Bug fixes
useConsistentArrayType
anduseShorthandArrayType
now ignoreArray
in theextends
andimplements
clauses. Fix #3247. Contributed by @Conaclospackage.json
. Contributed by @ematipicouseArrowFunction
rule 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
weight
that concurs on establishing the output sorting order.Since nesting variants on the same utility class is possible, the resulting
weight
is 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 theweight
of their base variant name the custom value attached (e.g.has-[.custom-class]
takeshas
weight).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
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
v1.8.1
Compare Source
Analyzer
CLI
Bug fixes
--staged
or--changed
options. Contributed by @unvalleyConfiguration
Bug fixes
indentWidth
. Contributed by @ematipicoEditors
Formatter
Bug fixes
JavaScript APIs
Linter
Bug fixes
The
noEmptyBlock
css lint rule now treats empty blocks containing comments as valid ones. Contributed by @Sec-antConfiguration
📅 Schedule: Branch creation - "every weekend" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.