[niteshseram]

With output: "static", navigating to a regular page that exports prerender = false first requests a static page-data file that was never generated:

GET /_void/pages/blog/example.json → 404
GET /blog/example                 → 200 (X-VoidPages)

The page eventually loads through the server fallback, but the failed static request adds a network round trip before the server request starts. Prefetching takes the same path.

Cause

resolveStaticPageDataBuildOptions() enables static page-data fetching for the app when output === "static".

The page scanner already records explicit prerender opt-outs, but generateComponentManifest() only included island flags in the client’s routeMeta. The browser therefore had no way to distinguish a route with prerendering disabled from one eligible for static page data.

matchStaticPageId() accepted any matched, non-island page with a component. Both navigation and prefetch used that check before requesting /_void/pages/<path>.json.

Fix

Include prerender: false in the generated route metadata for pages that explicitly opt out, preserving any existing island: true flag on the same route.

matchStaticPageId() now rejects those routes before a static JSON request starts. Because navigation and prefetch share this check, both request server page data directly:

GET /blog/example → 200 (X-VoidPages)

Metadata remains sparse: explicitly enabled and unset prerender settings do not add an entry. The check uses prerender !== false, so automatic prerendering and the existing static JSON fast path continue to work.

The shared navigation config and React client config types now accept the prerender metadata.

[cpojer]

Thanks for the PR!