-
-
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 dependencies (non-major) #147
Conversation
|
9887c0f
to
f14f8d7
Compare
@aria-ui/collection
@aria-ui/combobox
@aria-ui/core
@aria-ui/listbox
@aria-ui/menu
@aria-ui/overlay
@aria-ui/popover
@aria-ui/tooltip
@aria-ui/presence
@aria-ui/select
commit: |
f14f8d7
to
402c4cd
Compare
402c4cd
to
8c66466
Compare
8c66466
to
6cb1c4d
Compare
6cb1c4d
to
e9698b8
Compare
e9698b8
to
be70065
Compare
be70065
to
fae0974
Compare
fae0974
to
a41600d
Compare
a41600d
to
08553ab
Compare
08553ab
to
8931c10
Compare
8931c10
to
d98a6d3
Compare
d98a6d3
to
419b3c3
Compare
419b3c3
to
ee2f207
Compare
ee2f207
to
7e3be05
Compare
d411957
to
305e08b
Compare
305e08b
to
1758e92
Compare
1758e92
to
302bfef
Compare
302bfef
to
14654b2
Compare
14654b2
to
a80b41d
Compare
a80b41d
to
d7af2cb
Compare
d7af2cb
to
6aa2151
Compare
6aa2151
to
16f5ec1
Compare
16f5ec1
to
78d89ba
Compare
78d89ba
to
b93488a
Compare
b93488a
to
00dc7c2
Compare
00dc7c2
to
a837f82
Compare
a837f82
to
9c7483a
Compare
This PR contains the following updates:
^0.9.3
->^0.9.4
1.8.3
->1.9.3
2.27.7
->2.27.9
^1.6.10
->^1.6.11
^2.6.0
->^2.8.1
^1.1.8
->^1.1.10
^2.0.5
->^2.1.2
^0.65.1
->^0.73.1
^0.65.1
->^0.73.1
^4.15.1
->^4.15.11
^0.4.2
->^0.4.4
^9.9.1
->^9.12.0
1.7.15
->1.7.18
^0.0.24
->^0.0.29
^1.46.1
->^1.47.2
9.9.0
->9.12.0
^8.2.4
->^8.3.0
2.1.1
->2.1.3
0.26.7
->0.26.8
^5.5.4
->^5.6.2
^2.0.5
->^2.1.2
Release Notes
withastro/language-tools (@astrojs/check)
v0.9.4
Compare Source
Patch Changes
6e62aaa
: Upgrades chokidar to v45a44072
: Fixes formatting not working by default in certain circumstances5a44072
]3a836de
]biomejs/biome (@biomejs/biome)
v1.9.3
Compare Source
CLI
New features
GritQL queries that match functions or methods will now match async functions or methods as well.
If this is not what you want, you can capture the
async
keyword (or its absence) in a metavariable and assert its emptiness:Contributed by @arendjr
Bug fixes
Fix #4077: Grit queries no longer need to match the statement's trailing semicolon. Contributed by @arendjr
Fix #4102. Now the CLI command
lint
doesn't exit with an error code when using--write
/--fix
. Contributed by @ematipicoConfiguration
Bug fixes
noLabelWithoutControl
options where incorrectly marked as mandatory. Contributed by @ematipicoEditors
Formatter
Bug fixes
Fix #3924 where GraphQL formatter panics in block comments with empty line. Contributed by @vohoanglong0107
Fix a case where raw values inside
url()
functions weren't properly trimmed.Contributed by @ematipico
Fixed #4076, where a media query wasn't correctly formatted:
Contributed by @blaze-d83
JavaScript API
Bug fixes
Linter
New features
Add noDescendingSpecificity. Contributed by @tunamaguro
Add noNestedTernary. Contributed by @kaykdm
Add noTemplateCurlyInString. Contributed by @fireairforce
Add noOctalEscape. Contributed by @fireairforce
Bug fixes
noControlCharactersInRegex no longer panics on regexes with incomplete escape sequences. Contributed by @Conaclos
noMisleadingCharacterClass no longer reports issues outside of character classes.
The following code is no longer reported:
Contributed by @Conaclos
noUndeclaredDependencies no longer reports Node.js builtin modules as undeclared dependencies.
The rule no longer reports the following code:
Contributed by @Conaclos
noUnusedVariables no longer panics when suggesting the renaming of a variable at the start of a file (#4114). Contributed by @Conaclos
noUselessEscapeInRegex no longer panics on regexes that start with an empty character class. Contributed by @Conaclos
noUselessStringConcat no longer panics when it encounters malformed code. Contributed by @Conaclos
noUnusedFunctionParameters no longer reports unused parameters inside an object pattern with a rest parameter.
In the following code, the rule no longer reports
a
as unused.This matches the behavior of noUnusedVariables.
Contributed by @Conaclos
useButtonType no longer reports dynamically created button with a valid type (#4072).
The following code is no longer reported:
Contributed by @Conaclos
useSemanticElements now ignores elements with the
img
role (#3994).MDN recommends using
role="img"
for grouping images or creating an image from other elements.The following code is no longer reported:
Contributed by @Conaclos
useSemanticElements now ignores
alert
andalertdialog
roles (#3858). Contributed by @ConaclosnoUselessFragments don't create invaild JSX code when Fragments children contains JSX Expression and in a LogicalExpression. Contributed by @fireairforce
Parser
Bug fixes
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](https://www.biomejs.dev/linter/rules/no-control-characte
Configuration
📅 Schedule: Branch creation - "before 4am on the first day of the month" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, 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.