Strip query strings from module names when writing to disk

[jamesopstad]

Fixes #11535.

Strip query strings from module names before writing to disk

When bundling modules with query string suffixes (e.g. .wasm?module), the ? character was included in the output filename. Since ? is not a valid filename character on Windows, this caused an ENOENT error during wrangler dev. This was particularly visible when using Prisma Client with the D1 adapter, which imports .wasm?module files.

The fix strips query strings from module names before writing them to disk, while preserving correct module resolution.

---

• 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: bug fix

A picture of a cute animal (not mandatory, but encouraged)

---

[changeset-bot]

🦋 Changeset detected

Latest commit: beacef5

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

[workers-devprod]

Codeowners approval required for this PR:

• ✅ @cloudflare/wrangler

Show detailed file reviewers

[github-actions]

✅ All changesets look good

[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 4 additional findings.

[pkg-pr-new]

create-cloudflare

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

@cloudflare/kv-asset-handler

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

miniflare

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

@cloudflare/pages-shared

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

@cloudflare/unenv-preset

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

@cloudflare/vite-plugin

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

@cloudflare/vitest-pool-workers

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

@cloudflare/workers-editor-shared

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

wrangler

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

commit: 695561a

[petebacondarwin]

LGTM - one question... there appears to be more than 2 possible code paths covered by these changes but only two tests. Are we missing tests for some scenarios?

[jamesopstad]

LGTM - one question... there appears to be more than 2 possible code paths covered by these changes but only two tests. Are we missing tests for some scenarios?

The change is only needed in the path that is being tested. It felt more consistent to use the cleanedPath in the other locations but the functionality shouldn't change there. I think the existing coverage is enough for these i.e. the bug is fixed and the use of cleanedPath elsewhere hasn't broken the existing tests.