Skip to content

[BUG] Unexpected loadManifest(/.next/server/preview-props.json) call on Next.js 16.4 canary #1355

Description

@chargome

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

  1. Build any Next.js app on next@16.4.0-canary.3 with @opennextjs/cloudflare@1.20.2 (opennextjs-cloudflare build)
  2. opennextjs-cloudflare preview
  3. 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

Activity

  1. chargome commented on Aug 24, 2026

    @chargome
    Author

    Opened a PR that fixes this, please feel free to take this over/close/merge 🙏

  2. valleywood commented on Oct 8, 2026

    @valleywood

    How come there is no action on this (reviews on the PR) since 24/8 ? 🤔

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingtriage

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions