chore: cloudflare nodejs_compat_v2
example
#639
Merged
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.
Reviving #630
For now, we don't integrate it out-of-the-box. Let's use it as an example.It loos likenodejs_compat_v2
is becoming the default soon, so let's get on it.https://developers.cloudflare.com/workers/configuration/compatibility-dates/#nodejs-compatibility-flag
Also
experiment:...
is not needed anymore since wrangler 3.73Side note: Nitro/unenv is probably relying on the convention of
globalThis.__env__
to be exposed asprocess.env
. If we also useunenv
'sinject
then we could get on that convention as well: