[wrangler] Include default module rules in generated types

[xgame92]

Fixes #8893

Summary

wrangler types now includes the built-in Text, Data, and CompiledWasm module declarations in generated declaration files, using the same effective rule resolution and fallthrough semantics as deployment.

Configured rules remain the only module declarations shown in console output. Effective rules are deduplicated after glob normalization, generated-file hashes include the effective declarations, and silent API/check paths do not emit rule warnings.

---

• Tests
  • Tests included/updated
  • Automated tests not possible - manual testing has been completed as follows:
  • Additional testing not necessary because:
• Public documentation
  • Cloudflare docs PR(s):
  • Documentation not necessary because: This fixes generated output to match existing deployment behavior.

Note

This is a contribution from an AI agent: OpenAI Codex.

---

[changeset-bot]

🦋 Changeset detected

Latest commit: 6ee341c

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

This PR includes changesets to release 3 packages

Name	Type
wrangler	Patch
@cloudflare/vite-plugin	Patch
@cloudflare/vitest-plugin	Patch

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

[workers-devprod]

Codeowners approval required for this PR:

• @cloudflare/wrangler

Show detailed file reviewers

• .changeset/gentle-files-type.md: [@cloudflare/wrangler]
• packages/wrangler/e2e/types.test.ts: [@cloudflare/wrangler]
• packages/wrangler/src/tests/type-generation.test.ts: [@cloudflare/wrangler]
• packages/wrangler/src/deployment-bundle/rules.ts: [@cloudflare/wrangler]
• packages/wrangler/src/type-generation/index.ts: [@cloudflare/wrangler]

[pkg-pr-new]

@cloudflare/autoconfig

npm i https://pkg.pr.new/@cloudflare/autoconfig@15573

@cloudflare/build-output-utils

npm i https://pkg.pr.new/@cloudflare/build-output-utils@15573

@cloudflare/codemods

npm i https://pkg.pr.new/@cloudflare/codemods@15573

@cloudflare/config

npm i https://pkg.pr.new/@cloudflare/config@15573

create-cloudflare

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

@cloudflare/deploy-helpers

npm i https://pkg.pr.new/@cloudflare/deploy-helpers@15573

@cloudflare/kv-asset-handler

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

miniflare

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

@cloudflare/pages-functions

npm i https://pkg.pr.new/@cloudflare/pages-functions@15573

@cloudflare/pages-shared

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

@cloudflare/unenv-preset

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

@cloudflare/vite-plugin

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

@cloudflare/vitest-plugin

npm i https://pkg.pr.new/@cloudflare/vitest-plugin@15573

@cloudflare/workers-auth

npm i https://pkg.pr.new/@cloudflare/workers-auth@15573

@cloudflare/workers-editor-shared

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

@cloudflare/workers-utils

npm i https://pkg.pr.new/@cloudflare/workers-utils@15573

wrangler

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

commit: 6ee341c

[xgame92]

@petebacondarwin The latest CI run is green except for Vite Plugin Playground (windows-latest, vite-8). That job completed 93 test files successfully and then two unrelated suites timed out in the shared beforeAll hook after 50 seconds (assets/no-client-entry and worker-♫/log-level-error). The Wrangler-specific and cross-platform checks passed. I do not have repository permission to rerun the failed job; could a maintainer please rerun it when convenient? The PR is otherwise ready for codeowner review.

[dario-piotrowicz]

Thanks for the f ix @xgame92 🙂

This PR generally looks ok to me, but I left a couple of small questions

[dario-piotrowicz]

mh... this change seems unrelated to this PR 🤔

why are you changing the variable used here?

[xgame92]

This change is related to the service-worker part of the PR. generatePerEnvTypeStrings() now deliberately returns different console and file representations: the console keeps the existing export {}; declare global preview, while the written declaration must remain a script so wildcard ambient modules are valid. The header hash is what wrangler types --check compares for staleness, so it needs to hash the actual fileContent returned as envTypes; hashing consoleOutput would miss changes in effective/default declarations. The same change is applied in the single-environment path, and includes effective module rules in the generated types hash covers it.

[dario-piotrowicz]

Should this be a Set?

[xgame92]

The Map is intentional here. A Set<ModuleTypeRuleSet> would compare object identity, so separately created top-level/named-environment objects with identical contents would not be deduplicated. JSON.stringify(ruleSet) provides the structural key, while the map value preserves the original typed object and first-seen order; using a Set<string> would require parsing or casting the values back.