chore: update node versions in various places

[emily-shen]

• update engines, volta.node field in package.jsons
• update c3 tests to use a slightly more recent release of node 20, since the angular cli dependabot bump needed > 20.19

---

• Tests
  • TODO (before merge)
  • Tests included
  • Tests not necessary because: should just make sure existing tests don't fail
• Wrangler / Vite E2E Tests CI Job required? (Use "e2e" label or ask maintainer to run separately)
  • I don't know
  • Required
  • Not required because: should just make sure existing tests don't fail
• Public documentation
  • TODO (before merge)
  • Cloudflare docs PR(s):
  • Documentation not necessary because: internal chore
• Wrangler V3 Backport
  • TODO (before merge)
  • Wrangler PR:
  • Not necessary because: v3 doesn't follow same node version policy

[changeset-bot]

⚠️ No Changeset found

Latest commit: 7a66624

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

[windsurf-bot]

Looks good to me 🤙

[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/15442207081/npm-package-wrangler-9451

Prereleases for other packages:

cloudflare-workers-bindings-extension:

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

create-cloudflare:

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

@cloudflare/kv-asset-handler:

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

miniflare:

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

@cloudflare/pages-shared:

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

@cloudflare/unenv-preset:

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

@cloudflare/vite-plugin:

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

@cloudflare/vitest-pool-workers:

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

@cloudflare/workers-editor-shared:

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

@cloudflare/workers-shared:

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

@cloudflare/workflows-shared:

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

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

[edmundhung]

Should we make this 20 so that it picks up the latest version all the time?

[edmundhung]

I think this will make users running Wrangler on node 18 a hard failure?

[emily-shen]

we already hard fail on node 18 right? i'm not sure if i've misunderstood

[edmundhung]

True. I think the difference might be the error message that show up as node (or npm?) will fails it before Wrangler runs, so users might find the error less helpful, which might be fine?

[edmundhung]

I was wrong. Just give it a test with node 18 and it looks good 👍🏼

npm warn EBADENGINE Unsupported engine {
npm warn EBADENGINE   package: '[email protected]',
npm warn EBADENGINE   required: { node: '>=20.0.0' },
npm warn EBADENGINE   current: { node: 'v18.20.4', npm: '10.7.0' }
npm warn EBADENGINE }
npm warn EBADENGINE Unsupported engine {
npm warn EBADENGINE   package: '@cloudflare/[email protected]',
npm warn EBADENGINE   required: { node: '>=20.0.0' },
npm warn EBADENGINE   current: { node: 'v18.20.4', npm: '10.7.0' }
npm warn EBADENGINE }
npm warn EBADENGINE Unsupported engine {
npm warn EBADENGINE   package: '[email protected]',
npm warn EBADENGINE   required: { node: '>=20.0.0' },
npm warn EBADENGINE   current: { node: 'v18.20.4', npm: '10.7.0' }
npm warn EBADENGINE }
Wrangler requires at least Node.js v20.0.0. You are using v18.20.4. Please update your version of Node.js.

Consider using a Node.js version manager such as https://volta.sh/ or https://github.com/nvm-sh/nvm.