You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(types): boundary primitives return a typed Accessor<T | U> at every layer
createErrorBoundary/createLoadingBoundary previously returned () => unknown
(or leaked SourceAccessor<unknown>), so reading a boundary's value required
casts and surfaced as TS warnings in every rollup build. The external
signature is now identical across @solidjs/signals core, solid-js client
hydration, and the server runtime: pass content and fallback functions, get
back Accessor<T | U>. The SSR loading boundary's template plumbing moves to a
private ssrLoadingBoundary cast at a single point, since its accessor yields
resolved fragments rather than T/U.
Co-authored-by: Cursor <cursoragent@cursor.com>
`createErrorBoundary` and `createLoadingBoundary` now return a properly typed `Accessor<T | U>` (content union fallback) instead of `() => unknown`, with the same external signature across the core, client hydration, and server layers.
0 commit comments