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.
unenv provides Node.js API compatibility for deployment presets without Node.js support.
This PR migrated unenv to v2 with a lot of improvements:
Cloudflare team had been collaborating on v2 and initially adopted unenv v2 for
wrangler
tooling (announcement) however due to incompatibility of polyfills and alignments needed to make sure we can safely enable node.js compatibility for all Nitro users (see #2949 and #3064 for some context) it took a long time until we could migrate.TODO before merge:
node-mock-http
migration (context: Rollup config breaks some third-party libraries #3071)Note
More tests will be done on nightly channel before final nitro
2.11
release. If you have relatively big projects deployed to cloudflare (without prerendering) testing before release would be so much helpful to make sure there are no major regressions 🙏🏼