mirror of
https://github.com/hanzoai/next.js.git
synced 2026-09-24 17:00:51 +00:00
Andrew ClarkandGitHub
3de2d1a213
Removes the "allow-runtime" prefetch config, and turns its behavior on implicitly wherever Partial Prefetching is enabled. The original motivation for "allow-runtime" was to give apps more control over server costs triggered by prefetches. Until a route explicitly opts in, prefetches would only be served from the CDN, not from the server. The problem, though, was it was very confusing to know when to add or remove this configuration. The incentive for many apps was to add it everywhere, with no clear signal for when to remove it. Our updated thinking is that Partial Prefetching itself already provides sufficient protection against runaway prefetching costs: per-link prefetches only happen on Link components that explicitly opt in with the prefetch prop. The optimizations landed earlier in this stack also make allow-runtime less necessary: on pages where all the content is statically renderable, prefetches are served from the static cache and no runtime request is ever issued; only a page that accesses non-static data is prefetched at runtime. The upshot of this decision is that runtime versus static becomes an internal optimization; the same content gets prefetched regardless of whether or how Next.js is able to optimize it.
22 lines
948 B
TypeScript
22 lines
948 B
TypeScript
import { ReactNode } from 'react'
|
|
import { NoInline } from '../../components/no-inline'
|
|
|
|
// A static layout inflated past the inlining size threshold so it stays
|
|
// OUTLINED — it gets its own standalone static response instead of being
|
|
// bundled into the page's. Without it, this route's small intermediate
|
|
// segments would be bundled into the page's static response,
|
|
// and fetching THEM statically would deliver the page's content along for
|
|
// the ride — which would make the consuming test's "the page content must
|
|
// not arrive in any static response" rejection indistinguishable from a
|
|
// genuine static prefetch attempt of the page. Keeping the page's static
|
|
// response to itself preserves what that rejection pins: with the hint
|
|
// unset, the page segment is never statically prefetched.
|
|
export default function Layout({ children }: { children: ReactNode }) {
|
|
return (
|
|
<div>
|
|
<NoInline />
|
|
{children}
|
|
</div>
|
|
)
|
|
}
|