fix(patches): include prefetch-hints.json in loadManifest glob for Next.js 16.2#1160
Merged
petebacondarwin merged 2 commits intoopennextjs:mainfrom Mar 23, 2026
Merged
Conversation
🦋 Changeset detectedLatest commit: 8dfcca3 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
4 tasks
commit: |
conico974
approved these changes
Mar 21, 2026
Collaborator
conico974
left a comment
There was a problem hiding this comment.
LGTM, thanks for the fix, could you just fix the prettier check please ?
HazemKhaled
added a commit
to HazemKhaled/evisa
that referenced
this pull request
Mar 21, 2026
bfef748 to
8dfcca3
Compare
Contributor
Author
|
Thanks @conico974 and @sommeeeer for the quick review! I just pushed a fix for formatting. It looks like I don't have permissions to merge this PR on my end. Y'all mind pressing "Squash & Merge" for me (or whatever merge option you prefer)? |
Merged
2 tasks
This was referenced Apr 19, 2026
ColeMurray
pushed a commit
to ColeMurray/background-agents
that referenced
this pull request
Apr 20, 2026
## Summary - bump `@opennextjs/cloudflare` from `1.17.1` to `1.19.1` and pin the version in `packages/web/package.json` - pick up the OpenNext Cloudflare fixes for the Next.js 16.2 `prefetch-hints.json` runtime crash I hit during deployment after updating to the latest version of open-inspect - keep Open-Inspect users on a known-good adapter version via the repo lockfile instead of relying on whatever version `npx` might otherwise fetch ## Why I hit a production failure after deploying the Cloudflare web app with Next `16.2.3`: ```text Error 1101 Unexpected loadManifest(/.next/server/prefetch-hints.json) call! ``` Root cause: Next 16.2 introduced `prefetch-hints.json`, but `@opennextjs/cloudflare@1.17.1` did not inline or gracefully handle that manifest in its patched `loadManifest()` runtime shim. Upstream references: - opennextjs/opennextjs-cloudflare#1157 - opennextjs/opennextjs-cloudflare#1160 - opennextjs/opennextjs-cloudflare#1151 `1.19.1` includes the manifest-handling fixes released after `1.17.1`, so this avoids the Cloudflare worker startup crash without keeping our app pinned to an older Next version. ## Validation - verified locally that the failure reproduces with `next@16.2.3` + `@opennextjs/cloudflare@1.17.1` - verified a minimal standalone repro serves successfully after upgrading the adapter to `@opennextjs/cloudflare@1.17.3+` <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Chores** * Updated development dependency version for improved build tooling compatibility. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Next.js 16.2.0 introduced
prefetch-hints.json, a new server manifest loaded unconditionally byNextNodeServer.getPrefetchHints(). The file exists in.next/server/and is listed inrequired-server-files.json, but the glob pattern inload-manifest.tsonly matches*-manifest.jsonandrequired-server-files.json— so no if/else branch is generated for it and the patchedloadManifest()throws at runtime:Why this is needed alongside #1151
PR #1151 adds graceful
return {}fallbacks for optional manifests — ones Next.js loads withhandleMissing: true(e.g.subresource-integrity-manifest.json,react-loadable-manifest.json). Those files may or may not exist at build time, and Next.js handles missing responses gracefully.prefetch-hints.jsonis different: it is a required manifest that always exists in the build output and is loaded withouthandleMissing: true. It simply doesn't match the*-manifest.jsonglob pattern because its filename doesn't end with-manifest. The correct fix is to include it in the glob so its contents are inlined at build time, not to return an empty object at runtime.Fix
Add
prefetch-hintsto the existing glob alternation inload-manifest.ts. This follows the same pattern used whenrequired-server-fileswas added to the glob. Backwards compatible with Next.js 15/16.1.x where the file doesn't exist (glob simply finds no match).Fixes #1157. Related: #1141, #1151.