Repository navigation
fix(deps): update all dependencies - #1678
Open
renovate[bot] wants to merge 1 commit into
Open
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
Contributor
Author
|
|
|
❌ Deploy Preview for solid-docs failed. Why did it fail? →
|
renovate
Bot
force-pushed
the
renovate/all-dependencies
branch
5 times, most recently
from
November 5, 2026 06:45
4ac2c68 to
6130937
Compare
renovate
Bot
force-pushed
the
renovate/all-dependencies
branch
9 times, most recently
from
November 12, 2026 08:58
7cf0358 to
2cf6356
Compare
renovate
Bot
force-pushed
the
renovate/all-dependencies
branch
2 times, most recently
from
November 15, 2026 09:18
75636ce to
4e7ac4b
Compare
renovate
Bot
force-pushed
the
renovate/all-dependencies
branch
4 times, most recently
from
November 17, 2026 17:55
61f7d4a to
c19c05f
Compare
renovate
Bot
force-pushed
the
renovate/all-dependencies
branch
from
November 17, 2026 18:40
c19c05f to
6595d92
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.
Note
This PR body was truncated due to platform limits.
This PR contains the following updates:
0.13.12→0.13.14^0.6.13→^3.0.0^0.3.2→^2.0.0^2.4.6→^3.0.0^0.2.2→^2.0.0^0.2.1→^1.0.0^0.29.4→^2.0.0^1.0.0→^2.0.0^1.0.0→^2.0.01.0.0→2.0.02.0.0→2.2.34.3.3→4.3.5^25.9.5→^26.0.08.65.0→8.73.08.65.0→8.73.0^17.4.2→^18.0.010.7.0→10.15.0^0.14.5→^0.20.017.7.0→17.14.011.20.0→12.21.03.9.6→3.10.11.22.12→1.22.141.9.14→2.0.0^1.9.14→^2.0.04.3.3→4.3.58.65.0→8.73.08.2.4→8.3.8Release Notes
kobaltedev/kobalte (@kobalte/core)
v0.13.14Compare Source
Patch Changes
3d32663: ## v0.13.14 (September 7, 2026)Bug fixes
v0.13.13Patch Changes
cb89022: ## v0.13.13 (August 10, 2026)New features
Bug fixes
kobaltedev/solidbase (@kobalte/solidbase)
v3.0.0Compare Source
v2.0.0Compare Source
solidjs-community/solid-primitives (@solid-primitives/context)
v2.0.0Compare Source
Major Changes
637f383: BREAKING: Rework the API.Please refer to the README for the new API.
solidjs/solid-meta (@solidjs/meta)
v2.0.0Compare Source
Major Changes
37caba2: Solid Meta 1.0: rebuilt as a thin layer over Solid 2.0'suseHeadprimitive.MetaProviderandMetaContextare gone — remove the wrapper and thetags={[]}SSRplumbing; on the server, head tags are spliced into
<head>automaticallyby
renderToString/renderToStream(or collected via theonHeadrenderoption).
<Head>groups its child tags into one replacementset (several
og:images that override as a unit and restore on disposal);<Script>covers JSON-LD and other head scripts.with last-committed-wins and restore-on-disposal,
keyto overrideidentity, streaming-correct SSR patches that ride suspense reveals, and
flicker-free hydration adoption.
useHead(TagDescription)shim (the coreuseHead(HeadTag | HeadTag[] | () => HeadTag[])in@solidjs/webreplaces it),
escapeprop (everything is escaped; text is applied viatextContent),ref/event handlers on head tags, and client-dynamic<Base>/<Meta charset>(shell-only on the server, ignored with a dev warning onthe client).
solid-js>=2.0.0-beta.30and@solidjs/web>=2.0.0-beta.31(the first beta with reactiveuseHeadgroups, media-qualified meta identity, and replaceable icons). For Solid
1.x stay on
@solidjs/meta0.29.x; for Solid 0.x, 0.26.x.See the README migration guide for a 0.x → 1.0 walkthrough.
f9e874f: Solid Meta 2.0.0, the stable release for Solid 2.0. The version jumps to 2.0.0 to matchsolid-js,@solidjs/weband@solidjs/router: the1.0.0-next.*prereleases were this same line, and there is no stable 1.x. For Solid 1.x stay on@solidjs/meta0.29.x.Peer dependencies are now
solid-js/@solidjs/web^2.0.0.Patch Changes
36a5a18: Drop theuseHead/HeadTagre-exports. The primitive belongs to@solidjs/web(a required peer) — import it from there. Keeping a secondimport path for the identical function only invited confusion about whether
they differ.
8a74994: Fix hydration id drift from dynamic Title/Style/Script bodiesCompiled JSX children (e.g.
<Title>Page {site()}</Title>) can allocate acomputation when read. The head registry evaluates descriptor getters at
runtime-dependent points — the registry effect on the client, stream flush on
the server — so that allocation landed under different owners on each runtime
and drifted every hydration id assigned after it, breaking claims for content
rendered after the tag (most visibly under a streamed
Loadingboundary).headTagnow pins the body in a memo created at registration, under thecomponent, at the same point on both runtimes; the descriptor getter is a pure
read. Adds an SSR -> hydrate parity harness covering sync, root-async, and
boundary-async Title bodies.
f9e874f:<Head>no longer writes a signal during server render, so dev SSR stops logging[SERVER_WRITE]for every page that uses it (#80). The server reads the group's tags when its boundary flushes, so the write did nothing there.f9e874f: Add asolidexport condition so@solidjs/vite-plugin(through vitefu) bundles@solidjs/metain SSR instead of leaving it external. Left external, Node loaded it against the productionsolid-jsserver build while the app ran on the dev build, and the two owner stacks threwNoOwnerErrorin dev SSR (#74).70014b4: Updatesolid-js/@solidjs/webto2.0.0-rc.0and move the peer ranges from>=2.0.0-beta.30 <2.0.0/>=2.0.0-beta.31 <2.0.0to^2.0.0-rc.0. The old ranges admitted the hazardous2.0.0-experimental.*publishes (which sort between beta and rc) and excluded stable2.0.0; the caret floors above the experimentals and auto-graduates to stable 2.x.v0.29.8Patch Changes
917b81e: Cap thesolid-jspeer range to^1.8.4so this 1.x line doesn't install against Solid 2.0. Solid 2 support lives on thenexttag (@solidjs/meta@next).solidjs/solid-router (@solidjs/router)
v2.0.0Compare Source
Major Changes
9b66caf: Remove the legacy component API. ThecreateRouterfactory (routes as configobjects, the instance as the provider component) is now the only way to set up
the router, and plain
<a>elements — managed by the compiler-claimed anchorintegration — are the only link primitive.
Removed:
<Router>,<HashRouter>,<MemoryRouter>,<StaticRouter>and thecreateRouterComponentintegration wrapper. UsecreateRouter({ routes, history })with thebrowserHistory(default),hashHistory, ormemoryHistoryadapters; on the server the request URLdrives a static integration automatically.
<Route>(and itsRoutePropstype). Routes are config objects —the single source of truth the typed path proxy infers from.
createFlightDataCollectorlikewise no longer accepts JSX trees; hand itconfig objects, an array, a thunk, or a router instance.
<A>andNavigate. Anchors are plain<a href>elements: the claimsintegration applies
aria-current="page",data-active, anddata-pendingautomatically, anduseLinkStateremains the escape hatchfor custom client links. For
Navigate-style declarative redirects, calluseNavigate()in the route component or redirect from a preload.createhook onRouterIntegration(only the legacy componentscalled it).
Renamed:
useCurrentMatchesis nowuseRouteMatches— same behavior, an accessorof the router's resolved matches for the current location, outermost
first. The name draws the line against
useMatch: one reflects the routetree, the other tests a path pattern you supply.
usePreloadRoutekeeps its name and now also accepts typed path nodes(
paths.users(2).settings) alongside strings and URLs.hashParsermoved tosrc/routers/history.ts(exported for integrations);createMemoryHistoryis replaced by thememoryHistory(initialPath)adapter,which carries
go/back/forward/listenfor tests and tools.0a1101a: Renumber the Solid 2 prerelease line from1.0.0-next.*to2.0.0-next.*. The 0.16 line has been declared stable as1.0.0, so the 1.x majors now belong to the Solid 1 router; this line continues unchanged under 2.x, matching Solid 2's major. No code changes —2.0.0-next.12is the successor to1.0.0-next.11. If you track thenexttag with a^1.0.0-next.*range, update it to2.0.0-next.*or a stable1.xwill eventually satisfy it and hand you the Solid 1 router.d642c49: Begin the 1.0 API redesign: routes become config objects created outside JSX through acreateRouterfactory, and the route tree becomes the single source of truth for matching and types.createRouter({ routes, ... })returns an instance that is itself the provider component (<Router>{props => ...}</Router>); the render-prop child replaces therootprop and receives the matched content asprops.children. The factory'spreloadoption replacesrootPreload.Router.pathsis a typed path proxy derived from the route tree: property access descends static segments, calls bind params (paths.users(id).settings), and zero-arg or search-object calls terminate to a string (paths.search({ q, page })). Param types flow frommatchFilters(newintfilter types params as numbers) and search types from an optional per-route Standard Schemasearchvalidator. Every node coerces viatoString, andnavigate()/useParams()accept paths nodes.Router.match(url)matches arbitrary URLs against the instance with no rendering or request context — for middleware, sitemaps, and tests.hashHistory(),memoryHistory(initialUrl?),browserHistory()) passed asconfig.history, so unused adapters never enter the bundle; the default is browser history on the client and the request URL on the server.createRouterintegration factory export is replaced by the new factory (custom integrations become history adapters). The JSX<Router>/<HashRouter>/<MemoryRouter>/<StaticRouter>components and<Route>remain for now and will be removed later in the 1.0 line.rootPreload's return value being dropped: the root section'sdataprop now receives the preload result.Minor Changes
dff457e: Plain<a>elements now carry link state automatically — no<A>wrapper needed. The Solid compiler claims everya[href]at creation and re-claims when a dynamichrefchanges; the router consumes those claims (for routers created throughcreateRouter) and maintains:aria-current="page"— the location matches the link exactlydata-active— exact or prefix match (root/matches exactly only)data-pending— the link is the target of an in-flight navigationState is correct at creation, so late mounts (
<Show>,<For>, portals) are never stale, and it stays live per element with automatic disposal. External,targeted,download, andrel="external"links are left alone; withexplicitLinksonly anchors with thelinkattribute participate; base-path scoping matches click delegation. Style with CSS attribute selectors:Typed path nodes are now valid
hrefvalues directly (<a href={paths.users(2)}>):TypedPathcarries the JSX serializable-attribute brand and SSR stringifies the node into markup.useLinkState's (and claimed anchors')pendingnow matches the in-flight navigation target explicitly instead of "active while routing", so it reads consistently from both pure computations and effects — effects observe the committed location during a transition and previously could never see the pending state.Requires the element-claim runtime from
@solidjs/web(dom-expressions 0.50.0-next.25+).Explicit scroll restoration for back/forward navigation is on by default (#577). Positions are captured per history entry (persisted across reloads) and restored once the navigation settles, retrying as the document grows when content commits late — replacing the browser heuristic that loses the saved offset whenever the destination route forces a layout while the document is still short. Opt out with
scrollRestoration: falsein thecreateRouterconfig. Customhistoryadapters own their session and are not wrapped implicitly; passscrollRestoration: trueto thread restoration through one.2abd13b: AdddefineRoutes, an identity helper with aconsttype parameter thatpreserves route literal types for extracted route trees. Inline arrays passed
to
createRouteralready infer literally;defineRoutesremoves the needfor
as conston the common pattern of exporting the tree as a separatevalue — and makes the silent type degradation of forgetting it impossible.
c55d6bf: Forms submitted through delegation are markedaria-busy="true"while their action is in flight — the form half of the attribute vocabulary links get (data-active/data-pending). The attribute covers the mutation and its response handling (revalidation included), survives overlapping submissions of the same form via a counter, and always clears, error or not. ProgrammaticuseActioncalls have no form and set nothing. Style with CSS:0e06170: Add the@solidjs/router/fsemission adapter:fileRoutes(entries)converts a neutralfilesystem-routingmanifest intoRouteDefinitions, wiringlazy()components (withmoduleUrlfor route assets) and spreadingrouteconfig, while preserving literal types soRoutePathskeeps working for typed navigation.08d35de: Lazy route subtrees:childrenaccepts a thunk (children: () => import("./feature/routes")) so a section's route table loads on demand while staying part of the one typed tree. Types flow through the import's promise type intopathsand the typed hooks; hover-intent preloading kicks the table load and cascades into inner route preloads when it lands; navigation into an unresolved subtree folds the load into the transition (old screen holds); SSR and the single-flight collector resolve matched boundaries server-side. Resolution is cached per thunk and append-only. Async boundaries require the streaming render entry points (renderToStream/renderToStringAsync); the module'sdefaultorroutesexport (or a direct array) is used.ff75957: AdduseLinkState— reactiveactive/current/pendingstate for custom link components, the programmatic counterpart of the attribute vocabulary plain anchors will receive (aria-current,data-active,data-pending).<A>now derives its active/current state from it, so both share one semantics (trailing-slash and case handling,endfor exact-only). Accepts typed paths nodes as well as strings.createFlightDataCollectoralso accepts acreateRouterinstance directly: its routes, base, andpreloadare read off the instance config, so server wiring stays a one-liner (createFlightDataCollector(Router)).afc50c5: Update the router for the Solid 2 beta runtime and align its data APIs with the new async and action model.This release removes deprecated async wrappers, updates action and submission behavior around Solid 2 actions, refreshes the documented optimistic patterns, and includes the related router/runtime compatibility changes needed for the beta branch.
6655835: Typed, parsed search params. Passing a paths node touseSearchParams(paths.search)opts into Standard Schema parsing: the schemas of the currently matched routes run root→leaf over the raw query and their outputs merge over it, so reads return the schema's output type (defaults applied, values coerced) and the setter is typed by the schema's input. A schema that reports issues is skipped, leaving raw values — search strings are user input, so defaults belong in the schema. Zero-arguseSearchParams()keeps today's raw string-valued behavior. Async schema validation throws.Patch Changes
c9f8c25: Adopt the core server-function protocol from@solidjs/web(requires thesolid release shipping the
server-functionssubpath). The router'sredirect/reload/jsonresponse helpers are removed — importredirect,reload, andrespondfrom@solidjs/webinstead. Actions and queries nowconsume
ResponseEnvelopevalues (whatrespond()returns) directly inmemory, and decode transport pass-through responses (redirects, revalidation,
single-flight payloads) themselves via
decodeResponsefrom@solidjs/web/server-functions— thecustomBodyexpando and theCustomResponsetype are gone (NarrowResponsenow narrows throughResponseEnvelope).6cff38b: Adopt the wire protocols the server function runtime absorbed from the router. The flash cookie (name/detect/clear and the codec) and the no-JS form convention now live in@solidjs/web/server-functions; the router's copies and shims are deleted.createNoJSHandleris no longer exported from@solidjs/router/server— the runtime applies the convention to browser form posts by default, and apps that need to configure it (e.g. a base path) import it from@solidjs/web/server-functions/server. SSR still seeds the decoded flash cookie into submission state — with the decoder now installed only on the server, so client bundles tree-shake the codec they never ran.The generic halves of single-flight collection moved upstream too. The runtime now pre-digests the mutation outcome — target URL (redirect
Locationor referrer, origin-checked),X-Revalidatekeys, and post-mutation cookie headers — socreateFlightDataCollectorconsumesoutcome.targetUrl/revalidateKeys/foldedHeadersand keeps only the router's own policy: matching the target against the route tree and running its preloads.createSingleFlightHeadersis deleted from@solidjs/router/server(the folding lives in the runtime'sfoldSetCookiesand arrives pre-applied), and manually opted-in single-flight responses are unwrapped via the runtime'sdecodeResponsePayloadinstead of router-side envelope parsing. Requires@solidjs/web>= 2.0.0-beta.28.31ea11b: Adopt path-based server function addressing (solidjs/solid#3076). Action urls are now<endpoint>/<id>[?args=...]— the id in the path, bound arguments staying in the query. The generic form-action fallback reads the id back through the runtime'sparseServerFunctionUrlinstead of parsing?id=by hand, so the router no longer hard-codes the addressing scheme. Requires@solidjs/web2.0.0-rc.4; the peer floor is raised to^2.0.0-rc.4.f3b5f56: Putstate,noscroll,replace, andpreloadback onJSX.AnchorHTMLAttributesby augmenting@solidjs/web/jsx-runtime.preloadalso accepts"viewport"and"eager".linkstays owned by core. Pairs with the core change that removes those four props from the anchor type.5da9bb5:aria-current="page"now requires the query to match as well as the path, ignoring parameter order. On/?filter=active, a link to/?filter=activeis current and a link to/is not; previously every link to/with any query was current.data-activeanddata-pendingstill compare the path only.8edac15: Require the async flash decoder (solidjs/solid#3239): the flash cookie is now encrypted, so the runtime'sdecodeFlashCookiereturns a Promise and theprovideFlashDecoderslot takes only that shape. The submissions seed carries the in-flight decode through the not-ready protocol from a lazy, hydration-transparent memo — a request that never reads submissions never decodes, the decode runs at most once, and the server-only memo consumes no hydration-id slot.Requires
@solidjs/web2.0.0-rc.7 (the release that ships the async, encrypted codec and records the unbound function base as the flashurl, so a.with()-bound no-JS post matches itsuseSubmissionagain); thesolid-js/@solidjs/webpeer floor is raised to^2.0.0-rc.7.0159537: Respect a path-segment boundary when deciding whether a link is under the router's base path. Under base/app, a link to/appleor/application/xis no longer claimed for link state (data-active,aria-current,data-pending) or intercepted on click;/app,/app/and/app/...still are. Without a base, behavior is unchanged.7872c96: Abasewith a trailing slash, such as Vite'simport.meta.env.BASE_URL("/app/"), no longer produces double slashes.Router.pathshrefs andnavigate("/about")now give/app/aboutinstead of/app//about, which matched no route.9ba0fca: A chained.with()(action.with(a).with(b)) now puts every bound argument in its url (?args=[a,b]). Previously the url carried only the last call's arguments, so a server-rendered or no-JavaScript submission ran with arguments missing, and two chains ending in the same argument shared one url and overwrote each other's client registration.5bf9f13: Rework link-claim state to a single render effect that sweeps a registry of claimed anchors, replacing the per-anchor render effect. Behavior is unchanged — every anchor still depends on the same location sources, so nothing was gained from per-element granularity — but each claimed anchor now costs a registry entry and a cleanup hook instead of a full reactive node with dependency links, cutting per-anchor memory roughly 6x and making claim/unclaim on link-heavy pages cheaper.457ac72: Claimed anchors share one parse of the location and base path instead ofre-parsing both per anchor, roughly halving the
URLconstructions linkstate does at load and on every navigation sweep.
47b5e47: Make the link-claims sweep effect hydration-transparent. The sweep is created in the router's client-only branch, so the server never allocates a hydration id for it; when the client-side render effect consumed a child id during hydration, every subsequent id shifted by one slot relative to the server — lazy-route hydration lookups missed ("was not preloaded before hydration") and hydration finished with unclaimed server-rendered nodes. The effect now opts out of the id scheme with thetransparentnode option, the same mechanism component owners use.6cb1818: Clear settled submissions on navigation again, as 1.x did. The 2.0 rewrite dropped the clear along with pending submissions, so a page's errors and results outlived unmounting and reappeared when you came back. Every client location write (navigate, redirect hop, back/forward) now clears them, committing with that navigation, so the old page keeps showing them while the navigation is pending. An action that navigates still shows its own outcome on the page it lands on.e1e531c: Follow solid 2.0.0-rc.9's A28 rule (solidjs/solid#3473, "a write becomes visible at flush — to every channel"): betweenset(x)and the flush that carries it,latest(x)answers the pre-write value andisPending(x)is false. The router composed its next location write by reading its own unflushed one back —setSearchParamsmerged ontopendingTarget(latest(source)), andnavigateFromRoute's "already heading there" check compared against it — so under rc.9 the first of two synchronoussetSearchParamscalls was lost, a call issued behind anavigate()applied to the old route, and a navigation to the committed location issued behind another write in the same tick was dropped as a no-op. Location writes now compose through the writer's own channel, the integration's functional updater:RouterIntegration.signal's setter takes aLocationWrite, whosevaluemay be a function ofheaded— the location the router is heading to, an unflushed write of this tick included — and the no-op rule (samevalueandstate) is decided there too, for every integration.pendingTarget,isRouting()and redirect-hop detection keep reading the flushed world, which is where A28 puts them.Also:
query()reads the navigation intent untracked. Tracked, every consumer memo depended on the location'sisPending/latestprobes and re-ran as each navigation started and landed; under a redirect that leaves a route section, rc.9 runs that leaving memo (a lane-dirtied zombie, solidjs/solid#3444) and it refetched the entry the redirect had just invalidated.a5aba8e: Navigation coordination — query/preload intent, redirect hops, inherited replace/scroll and the leave-guard destination — reads the router's own location writes andonSettledinstead ofisPending/latest. No behavior change.RouterIntegration.inflightis replaced bysettled.1db62b1: Observe tier: the router declares the route the document arrived on, with the sameOBSERVE.attribution.withOrigincall it makes for every navigation — around the work that builds its context (initial: trueon the ref), on both sides. On the client this is the first"navigation"record (initial: true,atthe document's navigation start, no write to wait for); on the server the same declaration names the request's"render"record (RenderEvent.route: the matched pattern, the path, the params). A consumer naming page loads and requests by route (/users/:idrather than one name per user) had this for every navigation but the first; now it has the first too. Nothing in production builds:OBSERVEis undefined there and the declaration folds out. Needssolid-js/@solidjs/web2.0.0-rc.12or later (NavigationRef.initial,RenderEvent.route), already inside the^2.0.0-rc.13peer range.9cf2230: Route params are decoded (#670).useParams(),props.paramsandRouter.match()return each dynamic segment decoded after matching, so/item/%E7%8C%ABgivesid: "猫"andpaths.item("猫")round-trips.matchFilterssee the decoded value, so{ k: ["猫"] }now matches. An encoded slash stays inside its param (/a%2Fb/viewgivesname: "a/b"for/:name/view), splat params are decoded segment by segment, and a malformed escape is left raw.match.pathandlocation.pathnamekeep the URL's encoding.Breaking: code that already calls
decodeURIComponenton params decodes twice; drop the extra decode. Encode a param (or usepaths) when interpolating it into a URL by hand.366e130: Decouple the data layer from the router core so Router-only apps tree-shake query/action/flash entirely. The coupling inverts across three seams, each a slot the action side fills on firstaction()creation: form submits consult a handler slot in events.ts instead of importing the actions map; single-flight registration becomes a rendezvous in routing.ts (the Router registers, the action side provides the consumer — either order works, so lazily loaded action modules attach to an already-mounted router, and a router-only app never subscribes so the server is never asked to collect); and the submissions signal allocates lazily with the flash codec provided from the action side (the one-shot cookie clear stays eager per request via the new tiny flashCookie.ts half, so Set-Cookie still precedes streaming flushes and unread outcomes cannot haunt later renders). No behavior changes; bundle checks confirm a Router-only entry excludes action.ts, query.ts, the flash codec, and the @solidjs/web/server-functions import.6ecf770: AdddefineRoutefor definition-site param typing: wrapping a single route typesprops.params/args.paramsin itscomponentandpreloadfrom the route's ownpathpattern —:idisstring,:tab?isstring | undefined— instead of the openParamsrecord, closing the gap where required params still read as possiblyundefined. It is an identity function at runtime, andpath,children,matchFilters, andsearchstill flow literally intopathsand the typed hooks. For components declared away from their route, the newRouteProps<Path, Data?>type (and its component-type formRouteComponent<Path, Data?>, which typespropscontextually) takes a path witness — apathsnode or the pattern string — andRouteParams<S>spells a pattern's param record standalone. File-system route files get the same treatment throughdefineFileRoute(pattern, config)in@solidjs/router/fs, which types therouteexport'spreloadand validates itsmatchFiltersfrom a pattern witness (the manifest still provides the runtime path); the config carries the pattern as a phantom brand, soRouteProps<typeof route>types the file's component —paramsfrom the pattern,datainferred from thepreload— with one witness per file.RouteSectionProps,RouteSectionComponent, andRoutePreloadFunc(Args)gain an optional params type parameter (defaulting toParams, non-breaking).c22e671: Developer diagnostics (the nested-router warning, the relative-routing-unsupported warning, the invalid-path error log) are now gated behind solid'sDEVflag, so app bundlers fold them out of production bundles.2c444ef: Drop the router-side leaving-section gate; require solid 2.0.0-beta.30Solid's scheduler now cancels recomputes that a parking transition's own
writes queued on nodes the same navigation orphans, so a redirect's
revalidation sweep no longer re-runs query memos in outgoing route sections
at all — the phantom second request on single-flight mutations is prevented
in core. The
RouteContext.retained/RouterContext.leavinginternals andthe read-time gate in
querythat worked around it are removed.b222250: Restore scroll with a single scroll once routing settles, dropping theResizeObserverthat re-asserted the offset while the document was still growing. Settling after the transition commits is what makes the offset reachable, and it is the strategy every peer router ships (SvelteKit, TanStack Router, React Router, Next); TanStack's equivalentMutationObserversits commented out in their source. The chase carried real downside for a case none of them try to cover: with no bound, a target that is never reachable (a list that is genuinely shorter now) left the observer connected for the life of the page, re-clamping the viewport to the bottom on every subsequent resize, and scroll-induced layout changes can feed it back into itself. It was also untestable in jsdom, which has noResizeObserver, so the branch had no coverage. Content committing after the transition settles — an image without reserved space, a boundary below the fold — now keeps whatever offset the document can hold. Saves ~110 bytes gzipped.12a2500: Accept an explicitundefinedon every optionalRouteDefinitionproperty (and on the optional properties ofdefineRoute,defineFileRoute, and their returned config types), so route trees produced underexactOptionalPropertyTypes— notablyfileRoutes()applied tofilesystem-routing's generated manifest types, whose leaves carrychildren: undefined— type-check. The runtime already treated absent andundefinedalike; the one presence check (hasOwnProperty("path")) now treats an explicitpath: undefinedas a pathless route too (#598).7ff74bf: Track the server-function data address (solidjs/solid#3094). Scripted calls now go to<endpoint>/data/<id>while rendered action urls stay at the bare<endpoint>/<id>; the router needed no functional change — synthesized form actions already hand the rendered url tocreateServerReference, and the transport re-addresses its own calls — so this updates the wire-shape expectations in tests and the synthesis doc comment. Requires@solidjs/web2.0.0-rc.5 (theConfiguration
📅 Schedule: (UTC)
🚦 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.