docs: navigation interrupts after streaming has started (notFound, forbidden,…
docs: navigation interrupts after streaming has started (notFound, forbidden, unauthorized) (#95851) Adds a "Calling `x()` after streaming has started" example to the `notFound`, `forbidden`, and `unauthorized` references. - The check lives in the data-access function that loads the data, inside a `<Suspense>` boundary, so the page shell keeps streaming (blog post 404, account 401, admin projects 403). - Documents the status-code trade-off: the interrupt fires after headers are sent, so the response is a `200`; a `loading.tsx` is part of the stream, not a way around it; `instant = false` opts the route out of the shell for a real status code. - Links the authentication guide's DAL section instead of re-teaching it, plus a good-to-know on floating promises never rendering the UI. Docs-only.
Showing
Please
register
or
sign in
to comment