fix(deps): update workers-sdk derived test and fixture dependencies

[ant-release-bot]

This PR contains the following updates:

Package	Change	Age	Confidence
@cloudflare/vite-plugin (source)	2.0.0-beta.v.2 → 2.0.0-beta.v.3
wrangler (source)	4.151.2 → 4.151.3

---

Warning

Some dependencies could not be looked up. Check the warning logs for more information.

---

Release Notes

cloudflare/workers-sdk (@​cloudflare/vite-plugin)

v2.0.0-beta.v.3

Compare Source

Patch Changes

• #​15846 a88cac4 Thanks @​oddharsh! - Fail with an error instead of hanging when local dev requests can't work under Bun

  Bun's fetch() ignores the undici dispatcher that Miniflare routes requests through (oven-sh/bun#39247). Under Bun, createTestHarness()'s server.fetch() and server.getWorker()'s fetch(), email() and scheduled() now throw a UserError, requests to the dev server URL get a 503 naming the cause, and starting remote bindings throws a UserError. Each of these used to hang with no error. server.getWorker().getEnv() and getExport() keep working under Bun.

• #​16318 ff1f971 Thanks @​jamesopstad! - Prevent legacy Wrangler configuration files from being silently ignored

  The Vite plugin now stops with an actionable error when wrangler.json, wrangler.jsonc, or wrangler.toml is present without cloudflare.config.ts. Run npx cf migrate --bundler vite to migrate the project before building.

• Updated dependencies [3464abc]:

  • miniflare@5.20261019.1-beta
  • @​cloudflare/runtime-types@0.1.14
  • @​cloudflare/build-output-utils@0.9.3
  • @​cloudflare/config@0.27.0

cloudflare/workers-sdk (wrangler)

v4.151.3

Compare Source

Patch Changes

• #​15611 4508172 Thanks @​taylorlee! - Allow wrangler dev to start module Workers without a default export

  Previously, wrangler dev failed to start module Workers that exported only named entrypoints, such as RPC services, unless an unused default export was added. These Workers now start normally in local development without that workaround.

• #​16370 61fc739 Thanks @​WalshyDev! - Fetch the remote config diff from the configured compliance region

  When a Worker was last deployed from the dashboard, wrangler deploy and wrangler versions upload download its remote configuration to compare with the local one. These requests ignored the compliance_region field in the Wrangler configuration file and only honoured the CLOUDFLARE_COMPLIANCE_REGION environment variable. A FedRAMP High Worker configured through the config file would send them to api.cloudflare.com instead of api.fed.cloudflare.com, and the deploy would fail with authentication errors. They now use the same compliance region as the rest of the deploy.

• #​15846 a88cac4 Thanks @​oddharsh! - Fail with an error instead of hanging when local dev requests can't work under Bun

  Bun's fetch() ignores the undici dispatcher that Miniflare routes requests through (oven-sh/bun#39247). Under Bun, createTestHarness()'s server.fetch() and server.getWorker()'s fetch(), email() and scheduled() now throw a UserError, requests to the dev server URL get a 503 naming the cause, and starting remote bindings throws a UserError. Each of these used to hang with no error. server.getWorker().getEnv() and getExport() keep working under Bun.

• #​16359 262021d Thanks @​tw4! - Stop --strict deploys and version uploads from aborting when the API omits optional binding fields

  Previously, wrangler deploy --strict and wrangler versions upload --strict could report a destructive change for an unchanged configuration, for example an R2 bucket in the default jurisdiction, because a field the API left out was compared as removed. Missing and unset optional fields are now treated as equal, so these commands proceed when the local configuration matches the deployed Worker.

• Updated dependencies [3464abc]:

  • miniflare@5.20261019.1-beta

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate CLI.

[ask-bonk]

LGTM

github run

[pkg-pr-new]

npm i https://pkg.pr.new/cf@371

commit: a832ead

[github-actions]

cf --help startup

	mean	stddev	min	max
PR	274.7 ms	6.2 ms	268.4 ms	294.2 ms
base	273.9 ms	3.9 ms	268.1 ms	281.8 ms

Δ (PR vs base): — +0.9 ms (+0.3%)

Measured with hyperfine on ubuntu-latest (3 warmup runs, 20 timed runs). CI numbers carry ±a few ms of runner jitter; treat small deltas as noise.

[clanky-the-clanker]

💬 Approved with comments — A routine patch-level bump of @​cloudflare/vite-plugin and wrangler in three test fixtures, with no code changes. The one finding is a non-blocking note about fixture READMEs that already listed old versions before this pull request.

Findings: 1 info

_{The decision is advisory: this comment never approves, blocks or requests changes on the pull request.}

🔧 Fix with your agent

Paste the following into your coding agent to investigate and fix these issues.

Fix the following code review issues found in pull request #371.

Before making changes, review each issue and present a brief summary table:
- For each finding, state whether you agree, disagree, or need clarification
- If you disagree (e.g., the fix would require disproportionate changes
  for minimal ROI, or the finding is factually incorrect), explain why
- If you need to clarify something before deciding, ask those questions
- Then share your plan for which issues to tackle and in what order

## INFO (1)

### [Documentation] Fixture READMEs (`fixtures/vite-plugin-project/README.md:26-27`, `fixtures/wrangler-bundler-project/README.md:19`) list Wrangler/vite-plugin versions that were already out of date before this bump. Consider giving only the minimum supported version so automated updates do not leave them stale.
- **File:** fixtures/vite-plugin-project/README.md:27

---

📝 Documentation: 💬 1 info

Fixture READMEs list old dependency versions. They were already out of date before this pull request.

Recommendation: 💬 Optional Nits

• [INFO] Fixture READMEs (fixtures/vite-plugin-project/README.md:26-27, fixtures/wrangler-bundler-project/README.md:19) list Wrangler/vite-plugin versions that were already out of date before this bump. Consider giving only the minimum supported version so automated updates do not leave them stale. (fixtures/vite-plugin-project/README.md:27)

View full review

Two fixture READMEs list dependency versions that no longer match the manifests:

• fixtures/vite-plugin-project/README.md:24-28 describes "the current lockfile" as resolving @cloudflare/vite-plugin 2.0.0-beta.sha-ad79608dd and Wrangler 4.145.0.
• fixtures/wrangler-bundler-project/README.md:19 says the committed Wrangler dependency is 4.136.1.

Before this pull request the manifests already pinned Wrangler 4.151.2 and vite-plugin 2.0.0-beta.v.2, so this bump did not cause the mismatch. Either update the READMEs in a follow-up, or reword them to give only the minimum supported version (as README.md:21 already does with "4.136.0 or newer"). That would stop them going out of date on every automated bump.

---

✅ All other checks passed

📋 Code Quality: ✅ LGTM

The three fixture package.json files now pin @cloudflare/vite-plugin to 2.0.0-beta.v.3 and wrangler to 4.151.3, and all three are updated the same way. No JSON, YAML or TS file still references 4.151.2 or 2.0.0-beta.v.2. The release notes list only patch-level changes. This review did not cover pnpm-lock.yaml.

---

_{Reviewed commit: a832eade}