miniflare
4.20260730.0 · 30 Jul 2026MIT57.5M / weekRepositoryHomepagenpmAtom feed
4.20260730.0 is the newest release of 4.x.
In short
2 new1 fixed1 internal
Release note
Minor Changes
Rename the
web_searchbinding kind towebsearchPre-launch rename of the public binding type from
web_searchtowebsearchso the on-the-wire shape matches the product name (Web Search). The wrangler config key, the binding-type string sent to the Cloudflare API, and the miniflare option key all move fromweb_search/webSearchtowebsearch.Update your wrangler config:
- "web_search": { "binding": "WEBSEARCH" } + "websearch": { "binding": "WEBSEARCH" }The runtime
WebSearchtype exposed onenv.WEBSEARCHis unchanged.Support cross-worker workflow bindings via the dev registry
When a workflow binding has a
scriptNamethat refers to a worker registered in another Miniflare instance (viaunsafeDevRegistryPath), miniflare now reroutes the engine'sUSER_WORKFLOWbinding through the dev-registry-proxy worker — the same mechanism Durable Objects already use for cross-workerscriptNamebindings.Previously the workflow engine was bound directly to a local service
core:user:<scriptName>, so workerd refused to start when that script lived in a different process.This unblocks
getPlatformProxy()(and any other split-Miniflare setup) for users whose workflow class is defined in a separate worker — for example SvelteKit/Remix on Cloudflare, whereadapter-cloudflare's dev integration runs the user's worker in a sidecar.See #7459.
Patch Changes
Detect early workerd exit instead of hanging indefinitely
When
workerdexits during startup before writing all expected listen events to the control file descriptor (e.g. due to an IPv6 bind failure, permission error, or missing library), Miniflare'swaitForPorts()would block forever. This causedwrangler devto stall at "Starting local server..." with no error and no timeout.The fix races
waitForPorts()against the child process exit event so that any unexpectedworkerdtermination is detected immediately. Whenworkerdexits early, Miniflare now throwsERR_RUNTIME_FAILUREwith the runtime's stderr output included in the error message, making the root cause diagnosable without external tools.
A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.