Skip to content

Improve support for Next 16.1#1071

Merged
vicb merged 8 commits intomainfrom
vicb/n16.1
Jan 20, 2026
Merged

Improve support for Next 16.1#1071
vicb merged 8 commits intomainfrom
vicb/n16.1

Conversation

@vicb
Copy link
Copy Markdown
Contributor

@vicb vicb commented Jan 16, 2026

There was a bug in Next preventing 16.1+ to run well on Cloudflare.
The Next team fixed that in vercel/next.js#88733 (released in 16.1.4)

We have a patch for 16.1.0-16.1.3.
The patch has been improved in aws and we should merge the next release (3.9.10) before merging this PR.

@changeset-bot
Copy link
Copy Markdown

changeset-bot Bot commented Jan 16, 2026

🦋 Changeset detected

Latest commit: dfccd72

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
@opennextjs/cloudflare Patch

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

@pkg-pr-new
Copy link
Copy Markdown

pkg-pr-new Bot commented Jan 16, 2026

Open in StackBlitz

npm i https://pkg.pr.new/@opennextjs/cloudflare@1071

commit: dfccd72

@vicb vicb changed the title [WIP] Next 16.1 Improve support for Next 16.1 Jan 20, 2026
@vicb vicb changed the title Improve support for Next 16.1 [BLOCKED on aws 3.9.10] Improve support for Next 16.1 Jan 20, 2026
@vicb vicb changed the title [BLOCKED on aws 3.9.10] Improve support for Next 16.1 Improve support for Next 16.1 Jan 20, 2026
@vicb
Copy link
Copy Markdown
Contributor Author

vicb commented Jan 20, 2026

Thanks for the review Magnus.
I'll merge and release if the CI gets green.
Then we only need to look at the build size before we can say 16.x is supported 🚀

@vicb vicb merged commit 886c742 into main Jan 20, 2026
7 checks passed
@vicb vicb deleted the vicb/n16.1 branch January 20, 2026 11:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants