Fix Next.js version blocker; document Cloudflare Proxy/Workers incompatibility - #10
Merged
optymumss merged 1 commit intoJul 27, 2026
Conversation
Bump next/eslint-config-next 16.2.10 -> 16.2.12, a real published patch release that satisfies @opennextjs/cloudflare's peer range, resolving the original "Cannot find module '@opennextjs/cloudflare'" build failure. Running the actual OpenNext Cloudflare build surfaces a deeper, unresolved issue: this Next.js fork's Proxy (renamed from middleware.ts) is Node.js-runtime-only, and @opennextjs/cloudflare doesn't support Node.js middleware yet. Documented in CLOUDFLARE.md with links to the upstream issue/PRs tracking this. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01R3Q9i3afPL8DDDMmKnEpYW
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
2 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.
Summary
next/eslint-config-nextfrom16.2.10to16.2.12— a real published patch release that satisfies@opennextjs/cloudflare's peer range (>=16.2.11), resolving the original deploy failure (Cannot find module '@opennextjs/cloudflare').npm install,npx tsc --noEmit, andnext buildall pass cleanly on16.2.12.opennextjs-cloudflare build) surfaces a second, deeper, currently-unresolved blocker: this Next.js fork'ssrc/proxy.ts(renamed frommiddleware.ts) is Node.js-runtime-only, and@opennextjs/cloudflare(latest,1.20.2) has no support for Node.js middleware yet. Confirmed this is a known ecosystem-wide gap via cloudflare/workers-sdk#13755 and active, unmerged work in opennextjs-cloudflare#1309 / #1275.CLOUDFLARE.md, including what would need to change to unblock (upstream Node middleware support, or a security-relevant refactor moving auth/session logic out of Proxy into per-route server checks)..open-next/and.wrangler/to.gitignore(build artifacts produced while validating the above).This branch still does not produce a deployable Cloudflare Workers build — that's expected, per the updated
CLOUDFLARE.md. Vercel remains the live production deployment.Test plan
npm install— no peer-dependency conflictsnpx tsc --noEmit— cleannpm run build(plainnext build) — succeedsnpx opennextjs-cloudflare build— fails at the Node.js Proxy step (expected, documented)Generated by Claude Code