Problem

Next.js 16.2.0 introduced prefetch-hints.json, a new server manifest loaded unconditionally by NextNodeServer.getPrefetchHints(). The file exists in .next/server/ and is listed in required-server-files.json, but the glob pattern in load-manifest.ts only matches *-manifest.json and required-server-files.json — so no if/else branch is generated for it and the patched loadManifest() throws at runtime:

Unexpected loadManifest(/.next/server/prefetch-hints.json) call!

Why this is needed alongside #1151

PR #1151 adds graceful return {} fallbacks for optional manifests — ones Next.js loads with handleMissing: 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.json is different: it is a required manifest that always exists in the build output and is loaded without handleMissing: true. It simply doesn't match the *-manifest.json glob 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.

Note: This fix alone is not sufficient for full Next.js 16.2.0 support on Workers. It also requires #1151 (optional manifest fallbacks) and a fix for extensionless manifest paths — some manifests like dynamic-css-manifest and subresource-integrity-manifest are requested without the .json extension, which causes the current $PATH.endsWith(...) checks to miss them (see comment on #1151).

Fix

Add prefetch-hints to the existing glob alternation in load-manifest.ts. This follows the same pattern used when required-server-files was 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.