Sync unenv-preset with unenv@2.0.0-rc.8

[vicb]

Sync @cloudflare/unenv-preset with unenv@2.0.0-rc.8

Changelog:

• The preset is now esm only
• Polyfill perf_hooks (fixes 🚀 Feature Request: [unenv-preset] implement globalThis.performance in nodejs_compat mode #8111)

Notes:

The ESBuild plugin needs to be updated because

• The preset now only publish ESM
• To support the polyfill property of the preset Environment

You can check the WIP/test-preset branch that includes the updates and test the preset.

I have deliberately not include included a changelog because this package should not be released before 2.0 is ready

• Tests
  • TODO (before merge)
  • Tests included
  • Tests not necessary because: already tested
• E2E Tests CI Job required? (Use "e2e" label or ask maintainer to run separately)
  • I don't know
  • Required
  • Not required because: the preset is not used yet in wrangler
• Public documentation
  • TODO (before merge)
  • Cloudflare docs PR(s):
  • Documentation not necessary because: no user facing change

---

This is part 1 of 2 in a stack made with GitButler:

•  2  Use @cloudflare/unenv-preset in wrangler #8300
•  1  Sync unenv-preset with unenv@2.0.0-rc.8 #7915 👈

[changeset-bot]

⚠️ No Changeset found

Latest commit: 36d0036

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[anonrig]

@vicb Can you rebase?

[vicb]

@vicb Can you rebase?

I will, probably tomorrow. For now this is only a preview syncing with the next version of unenv

edit Jan 28: rebased and tested locally using pnpm link - added details in the description

[vicb]

Drop timers + rebased

[github-actions]

A wrangler prerelease is available for testing. You can install this latest build in your project with:

npm install --save-dev https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/13585800010/npm-package-wrangler-7915

You can reference the automatically updated head of this PR with:

npm install --save-dev https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/prs/7915/npm-package-wrangler-7915

Or you can use npx with this latest build directly:

npx https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/13585800010/npm-package-wrangler-7915 dev path/to/script.js

Additional artifacts:

cloudflare-workers-bindings-extension:

wget https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/13585800010/npm-package-cloudflare-workers-bindings-extension-7915 -O ./cloudflare-workers-bindings-extension.0.0.0-vac7291578.vsix && code --install-extension ./cloudflare-workers-bindings-extension.0.0.0-vac7291578.vsix

create-cloudflare:

npx https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/13585800010/npm-package-create-cloudflare-7915 --no-auto-update

@cloudflare/kv-asset-handler:

npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/13585800010/npm-package-cloudflare-kv-asset-handler-7915

miniflare:

npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/13585800010/npm-package-miniflare-7915

@cloudflare/pages-shared:

npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/13585800010/npm-package-cloudflare-pages-shared-7915

@cloudflare/unenv-preset:

npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/13585800010/npm-package-cloudflare-unenv-preset-7915

@cloudflare/vite-plugin:

npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/13585800010/npm-package-cloudflare-vite-plugin-7915

@cloudflare/vitest-pool-workers:

npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/13585800010/npm-package-cloudflare-vitest-pool-workers-7915

@cloudflare/workers-editor-shared:

npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/13585800010/npm-package-cloudflare-workers-editor-shared-7915

@cloudflare/workers-shared:

npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/13585800010/npm-package-cloudflare-workers-shared-7915

@cloudflare/workflows-shared:

npm install https://prerelease-registry.devprod.cloudflare.dev/workers-sdk/runs/13585800010/npm-package-cloudflare-workflows-shared-7915

Note that these links will no longer work once the GitHub Actions artifact expires.

---

wrangler@3.111.0 includes the following runtime dependencies:

Package	Constraint	Resolved
miniflare	workspace:*	3.20250214.1
workerd	1.20250214.0	1.20250214.0
workerd --version	1.20250214.0	2025-02-14

Please ensure constraints are pinned, and miniflare/workerd minor versions match.

[vicb]

@petebacondarwin I have started to sync with unenv - there are still a few changes to sync. I also have 2 PRs on unenv that are pendings.

This PR also needs to be tested with a version of wrangler actually using the preset - currently wrangler (then also pnpm -F @cloudflare/unenv-preset test:ci) is using unjs/unenv.

I hope to be done with that later today so that we can release @cloudflare/unenv-preset@2 this week. This would be a prerequisite before switching wrangler back to the preset.

[vicb]

@petebacondarwin we need to fix performance (see #8111, it was broken before but with the changes to unenv we have to fix this now and it's a good time anyway) but the rest should be ~ready.

The PR should be ready by tomorrow but feel free to take a look before.

Thanks!

[petebacondarwin]

Nice work! Got there finally!
As well as updating Wrangler, we'll need to update Vite plugin.

[petebacondarwin]

Out of curiosity, why do we create all these identity aliases? It seems a bit pointless?
Shouldn't we only add aliases for things that need to be mapped to polyfills?
(I could understand creating ${p} -> node:${p} perhaps?)

[vicb]

I have added this comment:

		// `nodeCompatModules` are implemented in workerd.
		// Create aliases to override polyfills defined in based environments.

Does it help?

[petebacondarwin]

Is it worth adding a changeset now?

[vicb]

Is it worth adding a changeset now?

I'll first merge the PR, test the PR releases and if that looks good we can add a changeset

[pi0]

(might be worth to add a test if you can o make sure it will exist in dist -- had a tough time to investigate issue in unenv when we changed bundler)