refactor(unenv-preset): sync directory structure with unenv

[vicb]

Sync the directory structure with unjs/unenv#392

---

edit Jan 28:

This PR is expected to fail until [email protected] is released (or whatever rc changes the unenv file structure, see unjs/unenv#392)

It can be test locally in the unenv-preset folder via:

pnpm link /path/to/[email protected]
pnpm test:ci

---

/cc @pi0 @petebacondarwin

Todo:

• update unenv version (for now file:...) when it is released
• fix the build

---

• 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:
• Public documentation
  • TODO (before merge)
  • Cloudflare docs PR(s):
  • Documentation not necessary because: no user facing change

[changeset-bot]

⚠️ No Changeset found

Latest commit: cb92141

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

[pi0]

Really not sure about effect of this on resolution but it won't be same as normal installations in node_modules.

We should adopt it with next rc (or nightly if you have it still working here)

[vicb]

Yep, that was just pushing the changes that I have for (p)review.
This PR is in draft mode, I should have been more clear in the description.

[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

[petebacondarwin]

What's happening here?

[vicb]

pnpm link to test the dev version as the new structure has not been released to npm.
Will need to be updated after the release and then remove draft from the PR

[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/13301360645/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/13301360645/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/13301360645/npm-package-cloudflare-workers-bindings-extension-7915 -O ./cloudflare-workers-bindings-extension.0.0.0-vf735271e1.vsix && code --install-extension ./cloudflare-workers-bindings-extension.0.0.0-vf735271e1.vsix

create-cloudflare:

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

@cloudflare/kv-asset-handler:

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

miniflare:

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

@cloudflare/pages-shared:

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

@cloudflare/unenv-preset:

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

@cloudflare/vite-plugin:

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

@cloudflare/vitest-pool-workers:

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

@cloudflare/workers-editor-shared:

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

@cloudflare/workers-shared:

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

@cloudflare/workflows-shared:

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

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

---

[email protected] includes the following runtime dependencies:

Package	Constraint	Resolved
miniflare	workspace:*	3.20250204.0
workerd	1.20250204.0	1.20250204.0
workerd --version	1.20250204.0	2025-02-04

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!