Describe the bug
Next.js canary (16.4.0-canary.3) moved preview props out of prerender-manifest.json into a new standalone .next/server/preview-props.json (PREVIEW_PROPS_MANIFEST). NextNodeServer.getPreviewProps() loads it from the Server constructor, so every dynamic route 500s:
Error: Unexpected loadManifest(/.next/server/preview-props.json) call!
at loadManifest (.open-next/server-functions/default/handler.mjs)
at NextNodeServer.getPreviewProps
at new Server
at new NextNodeServer
The file is present in the build output, but doesn't match the glob in load-manifest.ts:
**/{*-manifest,required-server-files,prefetch-hints}.json
Steps to reproduce
- Build any Next.js app on next@16.4.0-canary.3 with @opennextjs/cloudflare@1.20.2 (opennextjs-cloudflare build)
- opennextjs-cloudflare preview
- Request any non-prerendered route → 500
Expected behavior
The route renders, as it does on next@16.2.3. Same shape as #1157 / #1160 (prefetch-hints.json) — adding preview-props to the glob fixes it, verified locally.
@opennextjs/cloudflare version
1.20.2
Wrangler version
4.125.0
next info output
Additional context
No response
Describe the bug
Next.js canary (
16.4.0-canary.3) moved preview props out ofprerender-manifest.jsoninto a new standalone.next/server/preview-props.json(PREVIEW_PROPS_MANIFEST).NextNodeServer.getPreviewProps()loads it from the Server constructor, so every dynamic route 500s:The file is present in the build output, but doesn't match the glob in
load-manifest.ts:**/{*-manifest,required-server-files,prefetch-hints}.jsonSteps to reproduce
Expected behavior
The route renders, as it does on
next@16.2.3. Same shape as #1157 / #1160 (prefetch-hints.json) — adding preview-props to the glob fixes it, verified locally.@opennextjs/cloudflare version
1.20.2
Wrangler version
4.125.0
next info output
Additional context
No response