[vitest-pool-workers] Bump RTTI compat date

[penalosa]

The RTTI query used to build workerdBuiltinModules was hardcoded to compat date "2023-12-01", meaning any Node.js modules added to workerd in the last 2+ years weren't recognized as builtins. This caused the module fallback service to reject them with "Not found" instead of routing to workerd's native implementation.

This PR replaces the hardcoded date with today's date at build time, so workerdBuiltinModules automatically stays in sync with the bundled workerd version on each rebuild.

---

• Tests
  • Tests included/updated
  • Automated tests not possible - manual testing has been completed as follows:
  • Additional testing not necessary because: this only affects the build-time RTTI query — the set of builtin modules recognized by the fallback service and module runner interceptor now matches what workerd actually provides
• Public documentation
  • Cloudflare docs PR(s):
  • Documentation not necessary because: internal build plumbing change

---

[changeset-bot]

🦋 Changeset detected

Latest commit: 3632bc6

The changes in this PR will be included in the next version bump.

Not sure what this means? Click here to learn what changesets are.

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

[ask-bonk]

I've reviewed the full PR thoroughly. Here's my analysis:

1. query.mjs change (RTTI compat date): The script property is a JS template literal (backtick string), so ${supportedCompatibilityDate} is interpolated at the Node.js level when the Miniflare options are constructed. This is correct - the compat date string will be embedded into the worker script that gets passed to workerd. The supportedCompatibilityDate is properly exported from miniflare via export * from "./runtime" in miniflare's index.ts.

2. pool/index.ts change (ensureFeature for child_process): The nodejs_child_process_module flag follows the exact same pattern as the other flags (nodejs_tty_module, nodejs_fs_module, etc.). The ensureFeature function at line 778 constructs enable_nodejs_child_process_module / disable_nodejs_child_process_module flag names, both of which are confirmed to exist in the codebase (used in unenv-preset and wrangler e2e tests).

3. This is a build-time script: getBuiltinModules() is called during the tsdown build (line 61 of tsdown.config.ts) and the result is embedded as a define constant. The compat date interpolation happens at build time, which is the right time to capture it.

Both changes are straightforward, correct, and well-scoped. No logic bugs, no security concerns, no backward compatibility issues.

LGTM

github run

[pkg-pr-new]

create-cloudflare

npm i https://pkg.pr.new/create-cloudflare@13091

@cloudflare/kv-asset-handler

npm i https://pkg.pr.new/@cloudflare/kv-asset-handler@13091

miniflare

npm i https://pkg.pr.new/miniflare@13091

@cloudflare/pages-shared

npm i https://pkg.pr.new/@cloudflare/pages-shared@13091

@cloudflare/unenv-preset

npm i https://pkg.pr.new/@cloudflare/unenv-preset@13091

@cloudflare/vite-plugin

npm i https://pkg.pr.new/@cloudflare/vite-plugin@13091

@cloudflare/vitest-pool-workers

npm i https://pkg.pr.new/@cloudflare/vitest-pool-workers@13091

@cloudflare/workers-editor-shared

npm i https://pkg.pr.new/@cloudflare/workers-editor-shared@13091

wrangler

npm i https://pkg.pr.new/wrangler@13091

commit: 3632bc6

[workers-devprod]

Codeowners approval required for this PR:

• ✅ @cloudflare/wrangler

Show detailed file reviewers

[devin-ai-integration]

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no potential bugs to report.

View in Devin Review to see 2 additional findings.

[github-actions]

✅ All changesets look good