fix(miniflare): Fix KV bulk/get 413 error for large namespaces

[NuroDev]

Fixes #13459.

Summary

The Local Explorer's KV bulk/get endpoint was using kv.get(keys) which delegates to the KV bulk-get API. This API enforces a 25 MB aggregate size limit, causing a 413 error when browsing namespaces with large values.

Replace the single bulk-get call with individual per-key fetches via Promise.all. The number of concurrent fetches is bounded by the UI page size (50 keys), so this is safe and avoids the aggregate limit entirely.

---

• 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: ac19731

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 all the changed files thoroughly. Let me summarize my assessment:

Core fix (kv.ts:414-419): Replaces kv.get(keys) (bulk-get API) with Promise.all of individual kv.get(key) calls. This is a clean, correct fix for the 413 error. The concurrency is bounded by page size (50 keys), so it's safe.

Tests: Good regression tests at both the unit level (kv.spec.ts) and fixture level (index.test.ts). The unit test leverages the lower test-mode bulk limit (1 KiB) to avoid needing huge payloads.

Changeset: Properly formatted patch bump for miniflare.

Peer forwarding: The peer path still calls /bulk/get on the remote, but that's correct since the remote instance will also run the fixed handler.

There are no logic bugs, security issues, backward compatibility problems, or incorrect API behavior. The change is minimal, well-targeted, and properly tested.

LGTM

github run

[github-actions]

✅ All changesets look good

[workers-devprod]

Codeowners approval required for this PR:

• @cloudflare/wrangler

Show detailed file reviewers

• packages/local-explorer-ui/src/e2e/kv/kv-namespace.spec.ts: [@cloudflare/wrangler]
• packages/local-explorer-ui/src/e2e/utils.ts: [@cloudflare/wrangler]
• packages/local-explorer-ui/src/routes/kv/$namespaceId.tsx: [@cloudflare/wrangler]

[pkg-pr-new]

create-cloudflare

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

@cloudflare/kv-asset-handler

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

miniflare

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

@cloudflare/pages-shared

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

@cloudflare/unenv-preset

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

@cloudflare/vite-plugin

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

@cloudflare/vitest-pool-workers

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

@cloudflare/workers-editor-shared

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

wrangler

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

commit: ac19731

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

[petebacondarwin]

Once @emily-shen's comments are addressed, this LGTM.

[emily-shen]

Argh the HTTP API also enforces a 25MB limit - if we wanted to accurately simulate the API, the old behaviour is technically correct. What if the UI made the individual get requests instead?

[emily-shen]

Have thought about it and i think we should accurately reflect the real API, which enforces the 25MB limit too, and i think we should make the UI do the promise.all() get each key bit.

[workers-devprod]

Codeowners approval required for this PR:

• ✅ @cloudflare/wrangler

Show detailed file reviewers

[workers-devprod]

Codeowners reviews satisfied