fix: enable using workerd process v2

[vicb]

fixes #899

node:process has a new implementation in workerd ("v2" enabled by default on 2025-09-15).
v2 supports process.chdir() so it now errors when a non existent directory is passed (the cloudflare adapter passes "").
(The unenv implementation used before was a no-op).

[changeset-bot]

🦋 Changeset detected

Latest commit: a5cb01d

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]

Open in StackBlitz

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

commit: a5cb01d

[sommeeeer]

LGTM, good job on the fast fix

[conico974]

It does work, but I don't think this is the right fix. We should not patch things in aws here, at least not like that.
We should use this plugin https://github.com/opennextjs/opennextjs-aws/blob/main/packages/open-next/src/plugins/replacement.ts and just add an #override around it in aws

[vicb]

It does work, but I don't think this is the right fix. We should not patch things in aws here, at least not like that. We should use this plugin https://github.com/opennextjs/opennextjs-aws/blob/main/packages/open-next/src/plugins/replacement.ts and just add an #override around it in aws

I agree it's not ideal and we should improve this.
One way would be to pass additionalCodePatches to createServerBundle and use the replacement plugin.
But:

• cloudflare already has its own version of createServerBundle
• having AWS specific code in the "common" code base is not the best thing either

So let's merge this PR as is for now and think about a better way to support "common" + variants when we work on the adapters API.

WDYT?

[conico974]

So let's merge this PR as is for now and think about a better way to support "common" + variants when we work on the adapters API.
WDYT?

That's fine by me, but I still prefer the #override solution with the additionalCodePatches

What i really don't like about this one is that there is no way to know from the aws repo that we are modifying this function somewhere else. Very easy to forget about it and break a release this way

[vicb]

So let's merge this PR as is for now and think about a better way to support "common" + variants when we work on the adapters API.
WDYT?

That's fine by me, but I still prefer the #override solution with the additionalCodePatches

What i really don't like about this one is that there is no way to know from the aws repo that we are modifying this function somewhere else. Very easy to forget about it and break a release this way

Agreed.

Hopefully we don't add more than what the setNextjsServerWorkingDirectory name says in this function. Also this is e2e tested in playground15.

I have create this issue to improve the current PR but let's merge this now to avoid new projects fail build for now.

[vicb]

Thanks all for the review and feedback.

As the comments say, we should improve the current implementation but I'll merge this to avoid breaking new projects.