Repository navigation
fix: release 0.4.2 with owned deferred fallbacks and literal-dot routes - #21
Merged
Merged
Conversation
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.
Smolter 0.4.2
Fix abandoned deferred content through the integrated
Await fallbackAPI and support literal dots in file routes. Preserve deployment recovery ownership across page/fetcher mutations and watcher replacement; bound initial deferred promises with a validated total deadline.Deferred ownership and migration
Use
<Await resolve={promise} fallback={pending}>…</Await>for early-hydrated deferred fields, including persistent root sections. Ordinary fallback HTML remains component-owned; streamed data settles only the current mounted owner. No renderer patch, DOM scanning/cleanup, route wrapper, polling, extra request or separate public entrypoint is introduced. Non-early SSR retains resolved HTML streaming.This is not a repair of native Preact streamed Suspense. Consumers must replace the surrounding native Suspense on these fields. The known-failing native matrix is preserved as an explicit standalone diagnostic under
tests/reproductions/playwright.config.ts. The supported thirteen-case matrix remains blocking in CI using exactly the same ownership assertion harness, including absence of stale fallback/resolved content and persistence of root state/focus. Early deferred results require JavaScript. No Vibes files or external repositories are modified.File routes
robots[.]txt.tsorrobots[.]txt/route.tsmaps to/robots.txt. Unescaped dots still separate segments. Generated eager/SSR/lazy routes rejectidandroutePathexports rather than relying on overrides; rename files and remove those exports. Generated paths target route revalidation, while root usesroot. Explicit identity remains supported in manual route arrays.Validation and size
Detailed consumer instructions, inline reproduction and per-entrypoint measurements:
tests/reproductions/0.4.2-handover.md. JSR-before-npm publication ordering is unchanged. Release only after required CI passes.