Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: upgrade to unenv v2 #3072

Merged
merged 2 commits into from
Feb 6, 2025
Merged

feat: upgrade to unenv v2 #3072

merged 2 commits into from
Feb 6, 2025

Conversation

pi0
Copy link
Member

@pi0 pi0 commented Feb 6, 2025

unenv provides Node.js API compatibility for deployment presets without Node.js support.

This PR migrated unenv to v2 with a lot of improvements:

  • All polyfills have ESM-compatible exports
  • Polyfill support surface improved with less blink mocks

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:

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 🙏🏼

@pi0 pi0 marked this pull request as draft February 6, 2025 20:14
@pi0 pi0 marked this pull request as ready for review February 6, 2025 20:41
@pi0 pi0 merged commit ac78f21 into v2 Feb 6, 2025
4 checks passed
@pi0 pi0 deleted the feat/unenv-v2 branch February 6, 2025 20:45
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.

1 participant