fix(deps): update dependency @solidjs/router to v0.16.3 - #8619
Open
renovate[bot] wants to merge 1 commit into
Open
fix(deps): update dependency @solidjs/router to v0.16.3#8619renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
renovate
Bot
force-pushed
the
renovate/solidjs-router-0.x
branch
from
September 7, 2026 16:42
90eb88d to
06deba0
Compare
This file contains hidden or 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
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:
0.16.1→0.16.3Release Notes
solidjs/solid-router (@solidjs/router)
v0.16.3Compare Source
Patch Changes
31501fd: Add opt-in explicit scroll restoration for back/forward navigation:<Router scrollRestoration>(#577). The browser's native same-document heuristic loses the saved offset when the destination route forces a layout while the document is still short — any component that measures itself on mount is enough to trigger it. When enabled the router setshistory.scrollRestoration = "manual", captures positions continuously keyed by the history entry depth it already tracks, persists them across reloads, and restores after the navigation settles — retrying as the document grows if the target offset isn't reachable yet, cancelled by the first user scroll. Off by default on 0.x; no behavior changes unless enabled.v0.16.2Patch Changes
676db85: fix #451 - dispose per-route roots when the route tree unmounts; leaked roots stayed subscribed to route matches and crashed withTypeError: ... (evaluating 'match().path')on a later navigation (e.g. when a<Show>in the root component hid the outlet during login/logout flows)cae1d15: Fix a batch of long-standing bugs:useSubmission().retrywas always a no-op due to an operator-precedence bug (#504)useBeforeLeavelisteners now observedefaultPreventedset by other listeners (#530)<A>active state now ignores trailing slashes onhref(#532)useCurrentMatchesreturns a copy so user mutation can't corrupt router state (#516)+,@,:,$,&,,,;,=), so routes like/+fooor/@usermatch the browser's raw pathname (#559, #509)setSearchParamscalls now compose: the merge applies to the in-flight navigation target instead of the stale committed location (#547)e9acd69: fix #454 - defaultRouteDefinition's data generic toanyso typed components and preload functions are assignable in annotated configs likeconst routes: RouteDefinition[], where no inference site for the generic exists9d80d4e: Paths with empty interior segments (doubled slashes, e.g.//dashor/foo//bar) no longer match routes and now render the not-found state instead of silently matching their collapsed form (#567). A single trailing slash is still tolerated. Doubled leading slashes are also no longer normalized away by the browser integration and parse correctly instead of being treated as protocol-relative URLs.b308c21: fix #497 -revalidatenow forces the cache miss synchronously instead of deferring it into the transition microtask, so a same-tickrefetch()after an un-awaitedrevalidate()refetches fresh datae9acd69: fix #347 - acceptVoidComponentpages as route components;componentnow takes aRouteSectionComponentunion so components that don't declarechildrentype-check, while components requiring props the router doesn't pass are still rejectedConfiguration
📅 Schedule: (UTC)
🚦 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 was generated by Mend Renovate. View the repository job log.