Improve Next16 support

[vicb]

Next 16 support was released in @opennextjs/cloudflare@1.15.0.

We still need to implement (remaining from #972)

• SWR with revalidateTag(tag, "max") - [BUG] Next.js 16.1.0 / Next.js 16.0.10 - revalidateTag with profile "max" / stale-while-revalidate does not work #1058

[service-paradis]

I'm trying to migrate to Cloudflare Pages using @opennextjs/cloudflare with Next.js 16.1.4, but I'm hitting a blocker related to proxy.ts support.

Details

The Issue:

• Next.js 16's new proxy.ts file defaults to Node.js runtime and cannot be configured to use Edge runtime
• @opennextjs/cloudflare only supports Edge middleware and errors on Node.js middleware since v1.11.1
• Build fails with: ERROR Node.js middleware is not currently supported. Consider switching to Edge Middleware. when running opennextjs-cloudflare build && opennextjs-cloudflare preview

My Observations:

1. This issue (Improve Next16 support #1082) have no mentions of proxy.ts needing to be implemented
2. However, Issue #972 still has the "proxy" checkbox unchecked
3. Issue #962 about proxy.ts was closed pointing to Next16 support #972, but no clear resolution

My Questions:

1. Is proxy.ts support actually implemented in v1.15.0? The unchecked checkbox in Next16 support #972 suggests it's incomplete
2. If not implemented, is there a workaround for using Next.js 16 proxy with @opennextjs/cloudflare today?
3. What's the recommended approach?

My Setup:

• Next.js: 16.1.4
• @opennextjs/cloudflare: 1.15.0
• wrangler: 4.59.3
• proxy.ts uses only Web APIs (Request, Response, NextRequest) - already Edge-compatible from API perspective

Thanks for your work!

[vicb]

I'm trying to migrate to Cloudflare Pages using @opennextjs/cloudflare with Next.js 16.1.4, but I'm hitting a blocker related to proxy.ts support.

Details

#972

It will take a few weeks before the Adapters API impl is here

[grabmateusz]

@vicb is there a ticket to track for Adapters API implementation? Also is there high level ETA for #1058 (just to know what to expect)?

[vicb]

I am planning to work on 1058 this week.
There is a roadmap (project) for the adapters API. No concrete date for now but we are actively working on that and will have a clearer view as we make some progress

[AssisrMatheus]

I'm trying to migrate to Cloudflare Pages using @opennextjs/cloudflare with Next.js 16.1.4, but I'm hitting a blocker related to proxy.ts support.
Details

#972

It will take a few weeks before the Adapters API impl is here

proxy.js isn't supported due to waiting on the adapters api but would middleware.js still be supported? Even if deprecated

[vicb]

proxy.js isn't supported due to waiting on the adapters api but would middleware.js still be supported? Even if deprecated

Yes, we plan on releasing the Adapter API based adapter with Next 16 support so it'll be there

[grabmateusz]

I am planning to work on 1058 this week. There is a roadmap (project) for the adapters API. No concrete date for now but we are actively working on that and will have a clearer view as we make some progress

Hi @vicb , just checking if there is any progress with 1058? Thank you in advance for your reply.

[tristanbes]

Hello, @vicb seems like you forget to report back to this issue the "proxy" middleware support. Only the SWR cache thing is tracked there:
It's dangerous because issue #972 is closed;

It's already creating some confusion in other repositories (getsentry/sentry-javascript#18928)

Thanks.

[conico974]

"proxy" middleware is not just a name change, it is the node middleware which is not supported here. It will not be supported before the adapter API.
You can still use the old middleware file if you want to use a middleware.

[tristanbes]

I know, my point being: you stopped tracking this topic since the issue #972 is closed. I'm not saying it's easy or you should do this tomorrow.

[conico974]

Adapter apis work is in another repo, it's not tracked here and we are well aware of the issue. I just created it where it belongs opennextjs/adapters-api#20

[vicb]

We have https://github.com/orgs/opennextjs/projects/3 too, that should be enough tracking?