Skip to content

fix(deps): update all dependencies - #1678

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/all-dependencies
Open

renovate[bot] wants to merge 1 commit into
mainfrom
renovate/all-dependencies

Conversation

@renovate

@renovate renovate Bot commented Oct 29, 2026 •

Copy link
Copy Markdown
Contributor

Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
@kobalte/core (source) 0.13.12 → 0.13.14 age confidence
@kobalte/solidbase ^0.6.13 → ^3.0.0 age confidence
@solid-primitives/context (source) ^0.3.2 → ^2.0.0 age confidence
@solid-primitives/event-listener (source) ^2.4.6 → ^3.0.0 age confidence
@solid-primitives/marker (source) ^0.2.2 → ^2.0.0 age confidence
@solid-primitives/platform (source) ^0.2.1 → ^1.0.0 age confidence
@solidjs/meta ^0.29.4 → ^2.0.0 age confidence
@solidjs/router ^1.0.0 → ^2.0.0 age confidence
@solidjs/router ^1.0.0 → ^2.0.0 age confidence
@solidjs/router 1.0.0 → 2.0.0 age confidence
@solidjs/start (source) 2.0.0 → 2.2.3 age confidence
@tailwindcss/vite (source) 4.3.3 → 4.3.5 age confidence
@types/node (source) ^25.9.5 → ^26.0.0 age confidence
@typescript-eslint/eslint-plugin (source) 8.65.0 → 8.73.0 age confidence
@typescript-eslint/parser (source) 8.65.0 → 8.73.0 age confidence
dotenv ^17.4.2 → ^18.0.0 age confidence
eslint (source) 10.7.0 → 10.15.0 age confidence
eslint-plugin-solid ^0.14.5 → ^0.20.0 age confidence
globals 17.7.0 → 17.14.0 age confidence
pnpm (source) 11.20.0 → 12.21.0 age confidence
prettier (source) 3.9.6 → 3.10.1 age confidence
resolve 1.22.12 → 1.22.14 age confidence
solid-js (source) 1.9.14 → 2.0.0 age confidence
solid-js (source) ^1.9.14 → ^2.0.0 age confidence
tailwindcss (source) 4.3.3 → 4.3.5 age confidence
typescript-eslint (source) 8.65.0 → 8.73.0 age confidence
vite (source) 8.2.4 → 8.3.8 age confidence

Release Notes

kobaltedev/kobalte (@​kobalte/core)

v0.13.14

Compare Source

Patch Changes
  • 3d32663: ## v0.13.14 (September 7, 2026)

    Bug fixes

    • Preserve aria-hidden during modal handoff (#​721)
    • Resolve interact-outside targets across shadow boundaries (#​722)
    • Combobox: Prevent filter reset on blur (#​731)

v0.13.13

Patch Changes
  • cb89022: ## v0.13.13 (August 10, 2026)

    New features

    Bug fixes

    • Defer aria-hidden in ariaHideOutside to avoid focus warning (#​700)
    • Tabs: Skip indicator animation on initial render (#​704)
    • Prevent default in selection escape handler only when empy disallowEmptySelection (#​708)
    • Tooltip: button type (#​708)
    • Combobox: clear input on blur (#​708)
    • Select: call onChange only when changed (#​708)
    • Set form control label for attribute during ssr (#​708)
kobaltedev/solidbase (@​kobalte/solidbase)

v3.0.0

Compare Source

v2.0.0

Compare Source

solidjs-community/solid-primitives (@​solid-primitives/context)

v2.0.0

Compare Source

Major Changes
  • 637f383: BREAKING: Rework the API.

    Please refer to the README for the new API.

solidjs/solid-meta (@​solidjs/meta)

v2.0.0

Compare Source

Major Changes
  • 37caba2: Solid Meta 1.0: rebuilt as a thin layer over Solid 2.0's useHead primitive.

    • Provider-less: the head registry is ambient. MetaProvider and
      MetaContext are gone — remove the wrapper and the tags={[]} SSR
      plumbing; on the server, head tags are spliced into <head> automatically
      by renderToString/renderToStream (or collected via the onHead render
      option).
    • New components: <Head> groups its child tags into one replacement
      set (several og:images that override as a unit and restore on disposal);
      <Script> covers JSON-LD and other head scripts.
    • New semantics from the core registry: identity-based deduplication
      with last-committed-wins and restore-on-disposal, key to override
      identity, streaming-correct SSR patches that ride suspense reveals, and
      flicker-free hydration adoption.
    • Removed: the legacy useHead(TagDescription) shim (the core
      useHead(HeadTag | HeadTag[] | () => HeadTag[]) in @solidjs/web
      replaces it),
      escape prop (everything is escaped; text is applied via textContent),
      ref/event handlers on head tags, and client-dynamic <Base> /
      <Meta charset> (shell-only on the server, ignored with a dev warning on
      the client).
    • Peer dependencies: requires solid-js >=2.0.0-beta.30 and
      @solidjs/web >=2.0.0-beta.31 (the first beta with reactive useHead
      groups, media-qualified meta identity, and replaceable icons). For Solid
      1.x stay on @solidjs/meta 0.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 match solid-js, @solidjs/web and @solidjs/router: the 1.0.0-next.* prereleases were this same line, and there is no stable 1.x. For Solid 1.x stay on @solidjs/meta 0.29.x.

    Peer dependencies are now solid-js / @solidjs/web ^2.0.0.

Patch Changes
  • 36a5a18: Drop the useHead / HeadTag re-exports. The primitive belongs to
    @solidjs/web (a required peer) — import it from there. Keeping a second
    import path for the identical function only invited confusion about whether
    they differ.

  • 8a74994: Fix hydration id drift from dynamic Title/Style/Script bodies

    Compiled JSX children (e.g. <Title>Page {site()}</Title>) can allocate a
    computation 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 Loading boundary).

    headTag now pins the body in a memo created at registration, under the
    component, 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 a solid export condition so @solidjs/vite-plugin (through vitefu) bundles @solidjs/meta in SSR instead of leaving it external. Left external, Node loaded it against the production solid-js server build while the app ran on the dev build, and the two owner stacks threw NoOwnerError in dev SSR (#​74).

  • 70014b4: Update solid-js / @solidjs/web to 2.0.0-rc.0 and move the peer ranges from >=2.0.0-beta.30 <2.0.0 / >=2.0.0-beta.31 <2.0.0 to ^2.0.0-rc.0. The old ranges admitted the hazardous 2.0.0-experimental.* publishes (which sort between beta and rc) and excluded stable 2.0.0; the caret floors above the experimentals and auto-graduates to stable 2.x.

v0.29.8

Patch Changes
  • 917b81e: Cap the solid-js peer range to ^1.8.4 so this 1.x line doesn't install against Solid 2.0. Solid 2 support lives on the next tag (@solidjs/meta@next).
solidjs/solid-router (@​solidjs/router)

v2.0.0

Compare Source

Major Changes
  • 9b66caf: Remove the legacy component API. The createRouter factory (routes as config
    objects, 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 anchor
    integration — are the only link primitive.

    Removed:

    • <Router>, <HashRouter>, <MemoryRouter>, <StaticRouter> and the
      createRouterComponent integration wrapper. Use
      createRouter({ routes, history }) with the browserHistory (default),
      hashHistory, or memoryHistory adapters; on the server the request URL
      drives a static integration automatically.
    • JSX <Route> (and its RouteProps type). Routes are config objects —
      the single source of truth the typed path proxy infers from.
      createFlightDataCollector likewise no longer accepts JSX trees; hand it
      config objects, an array, a thunk, or a router instance.
    • <A> and Navigate. Anchors are plain <a href> elements: the claims
      integration applies aria-current="page", data-active, and
      data-pending automatically, and useLinkState remains the escape hatch
      for custom client links. For Navigate-style declarative redirects, call
      useNavigate() in the route component or redirect from a preload.
    • The create hook on RouterIntegration (only the legacy components
      called it).

    Renamed:

    • useCurrentMatches is now useRouteMatches — same behavior, an accessor
      of the router's resolved matches for the current location, outermost
      first. The name draws the line against useMatch: one reflects the route
      tree, the other tests a path pattern you supply.
    • usePreloadRoute keeps its name and now also accepts typed path nodes
      (paths.users(2).settings) alongside strings and URLs.

    hashParser moved to src/routers/history.ts (exported for integrations);
    createMemoryHistory is replaced by the memoryHistory(initialPath) adapter,
    which carries go/back/forward/listen for tests and tools.

  • 0a1101a: Renumber the Solid 2 prerelease line from 1.0.0-next.* to 2.0.0-next.*. The 0.16 line has been declared stable as 1.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.12 is the successor to 1.0.0-next.11. If you track the next tag with a ^1.0.0-next.* range, update it to 2.0.0-next.* or a stable 1.x will 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 a createRouter factory, 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 the root prop and receives the matched content as props.children. The factory's preload option replaces rootPreload.
    • Router.paths is 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 from matchFilters (new int filter types params as numbers) and search types from an optional per-route Standard Schema search validator. Every node coerces via toString, and navigate()/useParams() accept paths nodes.
    • Router.match(url) matches arbitrary URLs against the instance with no rendering or request context — for middleware, sitemaps, and tests.
    • History adapters are imported values (hashHistory(), memoryHistory(initialUrl?), browserHistory()) passed as config.history, so unused adapters never enter the bundle; the default is browser history on the client and the request URL on the server.
    • BREAKING: the low-level createRouter integration 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.
    • Fixes rootPreload's return value being dropped: the root section's data prop now receives the preload result.
Minor Changes
  • dff457e: Plain <a> elements now carry link state automatically — no <A> wrapper needed. The Solid compiler claims every a[href] at creation and re-claims when a dynamic href changes; the router consumes those claims (for routers created through createRouter) and maintains:

    • aria-current="page" — the location matches the link exactly
    • data-active — exact or prefix match (root / matches exactly only)
    • data-pending — the link is the target of an in-flight navigation

    State 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, and rel="external" links are left alone; with explicitLinks only anchors with the link attribute participate; base-path scoping matches click delegation. Style with CSS attribute selectors:

    nav a[aria-current="page"] {
      font-weight: 600;
    }
    nav a[data-active] {
      color: var(--accent);
    }
    a[data-pending] {
      opacity: 0.6;
    }

    Typed path nodes are now valid href values directly (<a href={paths.users(2)}>): TypedPath carries the JSX serializable-attribute brand and SSR stringifies the node into markup.

    useLinkState's (and claimed anchors') pending now 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: false in the createRouter config. Custom history adapters own their session and are not wrapped implicitly; pass scrollRestoration: true to thread restoration through one.

  • 2abd13b: Add defineRoutes, an identity helper with a const type parameter that
    preserves route literal types for extracted route trees. Inline arrays passed
    to createRouter already infer literally; defineRoutes removes the need
    for as const on the common pattern of exporting the tree as a separate
    value — and makes the silent type degradation of forgetting it impossible.

  • c55d6bf: Forms submitted through delegation are marked aria-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. Programmatic useAction calls have no form and set nothing. Style with CSS:

    form[aria-busy] button {
      pointer-events: none;
      opacity: 0.6;
    }
  • 0e06170: Add the @solidjs/router/fs emission adapter: fileRoutes(entries) converts a neutral filesystem-routing manifest into RouteDefinitions, wiring lazy() components (with moduleUrl for route assets) and spreading route config, while preserving literal types so RoutePaths keeps working for typed navigation.

  • 08d35de: Lazy route subtrees: children accepts 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 into paths and 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's default or routes export (or a direct array) is used.

  • ff75957: Add useLinkState — reactive active/current/pending state 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, end for exact-only). Accepts typed paths nodes as well as strings.

    createFlightDataCollector also accepts a createRouter instance directly: its routes, base, and preload are 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 to useSearchParams(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-arg useSearchParams() keeps today's raw string-valued behavior. Async schema validation throws.

Patch Changes
  • c9f8c25: Adopt the core server-function protocol from @solidjs/web (requires the
    solid release shipping the server-functions subpath). The router's
    redirect/reload/json response helpers are removed — import redirect,
    reload, and respond from @solidjs/web instead. Actions and queries now
    consume ResponseEnvelope values (what respond() returns) directly in
    memory, and decode transport pass-through responses (redirects, revalidation,
    single-flight payloads) themselves via decodeResponse from
    @solidjs/web/server-functions — the customBody expando and the
    CustomResponse type are gone (NarrowResponse now narrows through
    ResponseEnvelope).

  • 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. createNoJSHandler is 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 Location or referrer, origin-checked), X-Revalidate keys, and post-mutation cookie headers — so createFlightDataCollector consumes outcome.targetUrl/revalidateKeys/foldedHeaders and keeps only the router's own policy: matching the target against the route tree and running its preloads. createSingleFlightHeaders is deleted from @solidjs/router/server (the folding lives in the runtime's foldSetCookies and arrives pre-applied), and manually opted-in single-flight responses are unwrapped via the runtime's decodeResponsePayload instead 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's parseServerFunctionUrl instead of parsing ?id= by hand, so the router no longer hard-codes the addressing scheme. Requires @solidjs/web 2.0.0-rc.4; the peer floor is raised to ^2.0.0-rc.4.

  • f3b5f56: Put state, noscroll, replace, and preload back on JSX.AnchorHTMLAttributes by augmenting @solidjs/web/jsx-runtime. preload also accepts "viewport" and "eager". link stays 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=active is current and a link to / is not; previously every link to / with any query was current. data-active and data-pending still compare the path only.

  • 8edac15: Require the async flash decoder (solidjs/solid#3239): the flash cookie is now encrypted, so the runtime's decodeFlashCookie returns a Promise and the provideFlashDecoder slot 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/web 2.0.0-rc.7 (the release that ships the async, encrypted codec and records the unbound function base as the flash url, so a .with()-bound no-JS post matches its useSubmission again); the solid-js / @solidjs/web peer 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 /apple or /application/x is 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: A base with a trailing slash, such as Vite's import.meta.env.BASE_URL ("/app/"), no longer produces double slashes. Router.paths hrefs and navigate("/about") now give /app/about instead 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 of
    re-parsing both per anchor, roughly halving the URL constructions link
    state 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 the transparent node 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"): between set(x) and the flush that carries it, latest(x) answers the pre-write value and isPending(x) is false. The router composed its next location write by reading its own unflushed one back — setSearchParams merged onto pendingTarget (latest(source)), and navigateFromRoute's "already heading there" check compared against it — so under rc.9 the first of two synchronous setSearchParams calls was lost, a call issued behind a navigate() 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 a LocationWrite, whose value may be a function of headed — the location the router is heading to, an unflushed write of this tick included — and the no-op rule (same value and state) 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's isPending/latest probes 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 and onSettled instead of isPending/latest. No behavior change. RouterIntegration.inflight is replaced by settled.

  • 1db62b1: Observe tier: the router declares the route the document arrived on, with the same OBSERVE.attribution.withOrigin call it makes for every navigation — around the work that builds its context (initial: true on the ref), on both sides. On the client this is the first "navigation" record (initial: true, at the 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/:id rather than one name per user) had this for every navigation but the first; now it has the first too. Nothing in production builds: OBSERVE is undefined there and the declaration folds out. Needs solid-js / @solidjs/web 2.0.0-rc.12 or later (NavigationRef.initial, RenderEvent.route), already inside the ^2.0.0-rc.13 peer range.

  • 9cf2230: Route params are decoded (#​670). useParams(), props.params and Router.match() return each dynamic segment decoded after matching, so /item/%E7%8C%AB gives id: "猫" and paths.item("猫") round-trips. matchFilters see the decoded value, so { k: ["猫"] } now matches. An encoded slash stays inside its param (/a%2Fb/view gives name: "a/b" for /:name/view), splat params are decoded segment by segment, and a malformed escape is left raw. match.path and location.pathname keep the URL's encoding.

    Breaking: code that already calls decodeURIComponent on params decodes twice; drop the extra decode. Encode a param (or use paths) 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 first action() 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: Add defineRoute for definition-site param typing: wrapping a single route types props.params/args.params in its component and preload from the route's own path pattern — :id is string, :tab? is string | undefined — instead of the open Params record, closing the gap where required params still read as possibly undefined. It is an identity function at runtime, and path, children, matchFilters, and search still flow literally into paths and the typed hooks. For components declared away from their route, the new RouteProps<Path, Data?> type (and its component-type form RouteComponent<Path, Data?>, which types props contextually) takes a path witness — a paths node or the pattern string — and RouteParams<S> spells a pattern's param record standalone. File-system route files get the same treatment through defineFileRoute(pattern, config) in @solidjs/router/fs, which types the route export's preload and validates its matchFilters from a pattern witness (the manifest still provides the runtime path); the config carries the pattern as a phantom brand, so RouteProps<typeof route> types the file's component — params from the pattern, data inferred from the preload — with one witness per file. RouteSectionProps, RouteSectionComponent, and RoutePreloadFunc(Args) gain an optional params type parameter (defaulting to Params, non-breaking).

  • c22e671: Developer diagnostics (the nested-router warning, the relative-routing-unsupported warning, the invalid-path error log) are now gated behind solid's DEV flag, so app bundlers fold them out of production bundles.

  • 2c444ef: Drop the router-side leaving-section gate; require solid 2.0.0-beta.30

    Solid'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.leaving internals and
    the read-time gate in query that worked around it are removed.

  • b222250: Restore scroll with a single scroll once routing settles, dropping the ResizeObserver that 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 equivalent MutationObserver sits 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 no ResizeObserver, 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 explicit undefined on every optional RouteDefinition property (and on the optional properties of defineRoute, defineFileRoute, and their returned config types), so route trees produced under exactOptionalPropertyTypes — notably fileRoutes() applied to filesystem-routing's generated manifest types, whose leaves carry children: undefined — type-check. The runtime already treated absent and undefined alike; the one presence check (hasOwnProperty("path")) now treats an explicit path: undefined as 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 to createServerReference, and the transport re-addresses its own calls — so this updates the wire-shape expectations in tests and the synthesis doc comment. Requires @solidjs/web 2.0.0-rc.5 (the

[!IMPORTANT]
✂ PR body was truncated to here.


Configuration

📅 Schedule: (UTC)

  • 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 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.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate

renovate Bot commented Oct 29, 2026 •

Copy link
Copy Markdown
Contributor Author

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: pnpm-lock.yaml
Error: ERR_PNPM_NO_MATURE_MATCHING_VERSION

  × installing dependencies
  ╰─▶ 7 versions do not meet the minimumReleaseAge constraint:
        @solid-primitives/context@2.0.0 was published at 2026-11-
      17T17:13:20.475Z, within the minimumReleaseAge cutoff (2026-11-
      10T18:40:37.041Z)
        @solid-primitives/event-listener@3.0.0 was published at 2026-11-
      17T17:12:59.050Z, within the minimumReleaseAge cutoff (2026-11-
      10T18:40:37.041Z)
        @solid-primitives/marker@2.0.0 was published at 2026-11-
      17T17:14:47.385Z, within the minimumReleaseAge cutoff (2026-11-
      10T18:40:37.041Z)
        @solid-primitives/platform@1.0.0 was published at 2026-11-
      17T17:16:57.345Z, within the minimumReleaseAge cutoff (2026-11-
      10T18:40:37.041Z)
        @solid-primitives/utils@7.0.0 was published at 2026-11-
      17T17:14:54.314Z, within the minimumReleaseAge cutoff (2026-11-
      10T18:40:37.041Z)
        eslint-plugin-solid@0.20.0 was published at 2026-11-17T18:14:19.168Z,
      within the minimumReleaseAge cutoff (2026-11-10T18:40:37.041Z)
        prettier@3.10.1 was published at 2026-11-12T07:06:22.298Z, within the
      minimumReleaseAge cutoff (2026-11-10T18:40:37.041Z)
  help: Run the install interactively to approve these picks, add them to
        minimumReleaseAgeExclude in pnpm-workspace.yaml, or wait for the
        packages to mature.


@bolt-new-by-stackblitz

Copy link
Copy Markdown

Review PR in StackBlitz Codeflow Run & review this pull request in StackBlitz Codeflow.

@netlify

netlify Bot commented Oct 29, 2026 •

Copy link
Copy Markdown

❌ Deploy Preview for solid-docs failed. Why did it fail? →

Name Link
🔨 Latest commit 6595d92
🔍 Latest deploy log https://app.netlify.com/projects/solid-docs/deploys/6afc9fb526d2f1e7af8cb3c3

@renovate
renovate Bot force-pushed the renovate/all-dependencies branch 5 times, most recently from 4ac2c68 to 6130937 Compare November 5, 2026 06:45
@renovate
renovate Bot force-pushed the renovate/all-dependencies branch 9 times, most recently from 7cf0358 to 2cf6356 Compare November 12, 2026 08:58
@renovate
renovate Bot force-pushed the renovate/all-dependencies branch 2 times, most recently from 75636ce to 4e7ac4b Compare November 15, 2026 09:18
@brenelz brenelz added the 1.x label Nov 16, 2026
@renovate
renovate Bot force-pushed the renovate/all-dependencies branch 4 times, most recently from 61f7d4a to c19c05f Compare November 17, 2026 17:55
@renovate
renovate Bot force-pushed the renovate/all-dependencies branch from c19c05f to 6595d92 Compare November 17, 2026 18:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant