Repository navigation
test(nextjs): Raise @opennextjs/cloudflare floor for nextjs-16 - #25682
Merged
Merged
Conversation
Contributor
size-limit report 📦Compared: 837f086 (PR test merge using develop at 3cb76b2) Against: 3cb76b2 (develop) · base run #63878 ✅ Baseline matches: this diff contains only this PR's changes.
|
Contributor
Optional E2E testsAll optional checks were successful. 6 successful. See the run. Successful checks
|
mydea
force-pushed
the
test/nextjs-16-cf-canary-variant
branch
2 times, most recently
from
October 27, 2026 08:38
37b2faa to
4adfdbf
Compare
mydea
changed the title
opennextjs/opennextjs-cloudflare#1356 shipped in @opennextjs/cloudflare 1.20.12, so restore the canary variant on the Cloudflare runtime and unpin the latest variant from Next.js 16.3. Fixes #23541 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
OpenNext's Turbopack runtime patch breaks on Next.js 16.5 canary. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
mydea
force-pushed
the
test/nextjs-16-cf-canary-variant
branch
from
October 28, 2026 08:31
34d1032 to
8d9cf52
Compare
mydea
marked this pull request as ready for review
October 28, 2026 08:49
nicohrubec
approved these changes
Oct 28, 2026
chargome
approved these changes
Oct 28, 2026
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
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.
This raises the
@opennextjs/cloudflarefloor of thenextjs-16app to^1.20.12. That release contains the fix for opennextjs/opennextjs-cloudflare#1356, which is why the Cloudflare variants were pinned to 16.3 before instead or latest.Note that the canary variant is still not re-enabled, because there seems to be a bug in
@opennextjs/cloudflare. See below for details on what may be happening there.Canary is still failing (follow up work needed):
This PR originally also restored the
nextjs-16 (cloudflare, canary)variant, but that variant currently fails nearly every test with a 500, so it is not re-added yet.Workerd can't
requiredynamic paths, so OpenNext rewrites the Turbopack runtime'srequire(resolved)chunk loads into a call to afunction requireChunk(chunkPath)it appends to[turbopack]_runtime.js. Next.js 16.5 canary (seen with16.5.0-canary.28and@opennextjs/cloudflare@1.20.13) now declares its ownfunction requireChunk(chunkPath, sourceModuleId)in that file. It is used for async chunk loads and also installs the chunk's module factories. Both declarations live in the same scope, so OpenNext's wins. Async chunk loads then onlyrequirethe chunk without registering its modules. Ourinstrumentation.tsloadssentry.server.configwith a dynamicimport(), so every request fails withAn error occurred while loading instrumentation hook: Module … was instantiated … but the module factory is not available, which OpenNext turns into a generic 500. Renaming OpenNext's injected helper fixes it: with that change, the wholenextjs-16Cloudflare suite passes locally on canary. Next.js 16.4 has norequireChunkof its own, which is why thelatestvariant passes.The canary variant can come back once OpenNext ships a fix for this.
Ref #23541