fix(deps): update all non-major dependencies #75
+1,721
−1,282
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:
^0.4.10
->^0.4.15
^0.9.3
->^0.9.4
^3.1.5
->^3.1.9
^8.3.3
->^8.3.4
^3.6.2
->^3.6.3
^5.1.0
->^5.1.5
1.8.3
->1.9.4
1.8.3
->1.9.4
^19.4.1
->^19.7.1
^19.4.1
->^19.7.1
^5.0.20
->^5.1.1
^1.2.0
->^1.2.3
^2.1.1
->^2.1.6
^1.1.0
->^1.1.2
^18.3.5
->^18.3.18
^18.3.0
->^18.3.5
^4.15.2
->^4.16.18
^2.3.1
->^2.3.6
^2.2.0
->^2.2.1
^0.7.0
->^0.7.1
^3.0.0
->^3.0.1
^9.1.5
->^9.1.7
^15.2.10
->^15.4.3
^0.438.0
->^0.473.0
^0.438.0
->^0.475.0
^17.5.1
->^17.6.0
^2.5.2
->^2.6.0
^3.4.10
->^3.4.17
^5.5.4
->^5.7.3
Release Notes
ariakit/ariakit (@ariakit/react)
v0.4.15
Compare Source
onSubmit
andonValidate
.@ariakit/[email protected]
v0.4.14
Compare Source
Improved performance on composite widgets
Composite item components such as
ComboboxItem
andSelectItem
now render 20-30% faster compared to Ariakit v0.4.13.This enhancement should decrease the time needed to render large collections of items in composite widgets and improve the Interaction to Next Paint (INP) metric. We're working on further optimizations to make composite widgets even faster in future releases.
Combobox auto-scroll
The
Combobox
component now scrolls the list to the top while typing when theautoSelect
prop is disabled.The behavior is now consistent with the
autoSelect
prop, except the first item won't be automatically focused.Other updates
item
method to prevent it from returning items that have been removed from the collection store.item
method when keeping different menu stores in sync.id
prop to composite stores.SelectValue
to display thefallback
when the value is an empty array or string.@ariakit/[email protected]
v0.4.13
Compare Source
Accessible composite widgets with invalid
activeId
We've improved the logic for composite widgets such as Tabs and Toolbar when the
activeId
state points to an element that is disabled or missing from the DOM. This can happen if an item is dynamically removed, disabled, or lazily rendered, potentially making the composite widget inaccessible to keyboard users.Now, when the
activeId
state is invalid, all composite items will remain tabbable, enabling users to Tab into the composite widget. Once a composite item receives focus or the element referenced by theactiveId
state becomes available, the roving tabindex behavior is restored.Other updates
focusShift
.onChange
from triggering on radios that are already checked.DisclosureContent
setting an incorrectanimating
state value during enter animations.@ariakit/[email protected]
v0.4.12
Compare Source
Tab panels with scroll restoration
Ariakit now supports scroll restoration for the
TabPanel
component. This allows you to control whether and how the scroll position is restored when switching tabs.To enable scroll restoration, use the new
scrollRestoration
prop:By default, the scroll position is restored when switching tabs. You can set it to
"reset"
to return the scroll position to the top of the tab panel when changing tabs. Use thescrollElement
prop to specify a different scrollable element:Full height dialogs and on-screen virtual keyboards
A new
--dialog-viewport-height
CSS variable has been added to the Dialog component. This variable exposes the height of the visual viewport, considering the space taken by virtual keyboards on mobile devices. Use this CSS variable when you have input fields in your dialog to ensure it always fits within the visual viewport:Overriding composite state for specific methods
The
next
,previous
,up
, anddown
methods of the composite store now accept an object as the first argument to override the composite state for that specific method. For example, you can pass a differentactiveId
value to thenext
method so it returns the next item based on that value rather than the current active item in the composite store:It's important to note that the composite state is not modified when using this feature. The state passed to these methods is used solely for that specific method call.
Other updates
Tab
to pass therowId
prop when used with other composite widgets.@ariakit/[email protected]
v0.4.11
Compare Source
Tabs inside animated Combobox or Select
When rendering Tab inside Combobox or Select, it now waits for the closing animation to finish before restoring the tab with the selected item. This should prevent an inconsistent UI where the tab is restored immediately while the content is still animating out. See Select with Combobox and Tabs.
Other updates
activeId
upon closing the popover.data-focus-visible
attribute.MenuButton
hiding the menu on Safari.@ariakit/[email protected]
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
]withastro/astro (@astrojs/mdx)
v3.1.9
Compare Source
Patch Changes
1d4f6a4
Thanks @bmenant! - Addcomponents
property to MDXInstance type definition (RenderResult and module import)v3.1.8
Compare Source
Patch Changes
710a1a1
]:v3.1.7
Compare Source
Patch Changes
40e7a1b
Thanks @bluwy! - Initializes the MDX processor only when there's.mdx
filesv3.1.6
Compare Source
Patch Changes
c9ae7b1
Thanks @bluwy! - Handles nested root hast node when optimizing MDXwithastro/adapters (@astrojs/node)
v8.3.4
Patch Changes
0cf7e91
Thanks @bluwy! - Updatessend
dependency to 0.19.0withastro/astro (@astrojs/react)
v3.6.3
Compare Source
Patch Changes
8a46e80
Thanks @marbrex! - Resolvevite
peer dependency problem for strict package managers like Yarn in PnP mode.withastro/astro (@astrojs/tailwind)
v5.1.5
Compare Source
Patch Changes
cf30880
Thanks @ascorbic! - Upgrades Vitev5.1.4
Compare Source
Patch Changes
739dbfb
Thanks @ascorbic! - Upgrades Vite to pin esbuildv5.1.3
Compare Source
Patch Changes
4f2fd0a
Thanks @Princesseuh! - Fixes compatibility with Astro 5v5.1.2
Compare Source
Patch Changes
8e500f2
Thanks @delucis! - Adds keywords topackage.json
to improve categorization in the Astro integrations catalogv5.1.1
Compare Source
Patch Changes
dcd1158
Thanks @matthewp! - Make @astrojs/tailwind compat with Astro 5biomejs/biome (@biomejs/biome)
v1.9.4
Compare Source
Analyzer
Bug fixes
Implement GraphQL suppression action. Contributed by @vohoanglong0107
Improved the message for unused suppression comments. Contributed by @dyc3
Fix #4228, where the rule
a11y/noInteractiveElementToNoninteractiveRole
incorrectly reports arole
for non-interactive elements. Contributed by @eryue0220noSuspiciousSemicolonInJsx
now catches suspicious semicolons in React fragments. Contributed by @vasucp1207CLI
Enhancements
The
--summary
reporter now reports parsing diagnostics too. Contributed by @ematipicoImproved performance of GritQL queries by roughly 25-30%. Contributed by @arendjr
Configuration
Bug fixes
Editors
Formatter
Bug fixes
JavaScript APIs
Linter
New features
Bug Fixes
Biome no longer crashes when it encounters a string that contain a multibyte character (#4181).
This fixes a regression introduced in Biome 1.9.3
The regression affected the following linter rules:
nursery/useSortedClasses
nursery/useTrimStartEnd
style/useTemplate
suspicious/noMisleadingCharacterClass
Contributed by @Conaclos
Fix #4190, where the rule
noMissingVarFunction
wrongly reported a variable as missing when used inside avar()
function that was a newline. Contributed by @ematipicoFix #4041. Now the rule
useSortedClasses
won't be triggered ifclassName
is composed only by inlined variables. Contributed by @ematipicouseImportType and useExportType now report useless inline type qualifiers (#4178).
The following fix is now proposed:
Contributed by @Conaclos
useExportType now reports ungrouped
export from
.The following fix is now proposed:
Contributed by @Conaclos
noVoidTypeReturn now accepts
void
expressions in return position (#4173).The following code is now accepted:
Contributed by @Conaclos
noUselessFragments now correctly handles fragments containing HTML escapes (e.g.
) inside expression escapes{ ... }
(#4059).The following code is no longer reported:
Contributed by @fireairforce
noUnusedFunctionParameters and noUnusedVariables no longer reports a parameter as unused when another parameter has a constructor type with the same parameter name (#4227).
In the following code, the
name
parameter is no longer reported as unused.Contributed by @Conaclos
noUndeclaredDependencies now accepts dependency names with dots. Contributed by @Conaclos
useFilenamingConvention now correctly handles renamed exports (#4254).
The rule allows the filename to be named as one of the exports of the module.
For instance, the file containing the following export can be named
Button
.The rule now correctly handles the renaming of an export.
For example, the file containing the following export can only be named
Button
.Previously the rule expected the file to be named
A
.Contributed by @Conaclos
useConsistentMemberAccessibility now ignore private class members such as
#property
(#4276). Contributed by @ConaclosnoUnknownFunction correctly handles
calc-size
function (#4212).The following code
calc-size
is no longer reported as unknown:Contributed by @fireairforce
useNamingConvention now allows configuring conventions for readonly index signatures.
Contributed by @sepruko
Previously, the rule incorrectly reported duplicates for all properties, including non-custom ones. Contributed by @togami2864
Parser
Bug Fixes
The CSS parser now accepts more emoji in identifiers (#3627).
Browsers accept more emoji than the standard allows.
Biome now accepts these additional emojis.
The following code is now correctly parsed:
Contributed by @Conaclos
Add support for parsing typescript's
resolution-mode
in Import Types(#2115)Contributed by @fireairforce
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
Enhancements
Add an option
reportUnnecessaryDependencies
to useExhaustiveDependencies.Defaults to true. When set to false, errors will be suppressed for React hooks that declare dependencies but do not use them.
Contributed by @simon-paris
Add an option
reportMissingDependenciesArray
to useExhaustiveDependencies. Contributed by @simon-parisBug 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 [@&fix(deps): update react monorepo to v19 (major) #82Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), 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.