miniflare
4.20260730.0 · 30 Jul 2026MIT57.5M / weekRepositoryHomepagenpmAtom feed
4.20260730.0 is the newest release of 4.x.
In short
2 new5 fixed
Release note
Patch Changes
Added the following improvements to local Browser Rendering binding in Miniflare:
Local Chrome version upgraded to 126.0.6478.182
Reciprocate browser websocket close events
Allow mixed
d1Databasesrecords containing both string and object entriesPreviously, passing a
d1Databasesconfig that mixed plain string values and object entries (e.g.{ MY_DB: "db-name", OTHER_DB: { id: "...", remoteProxyConnectionString: ... } }) would cause Miniflare to throw an error. Both forms are now accepted and normalised correctly.Allow mixed
kvNamespacesrecords containing both string and object entriesPreviously, passing a
kvNamespacesconfig that mixed plain string values and object entries (e.g.{ MY_NS: "ns-name", OTHER_NS: { id: "...", remoteProxyConnectionString: ... } }) would cause Miniflare to throw an error. Both forms are now accepted and normalised correctly.Allow mixed
pipelinesrecords containing both string and object entriesPreviously, passing a
pipelinesconfig that mixed plain string values and object entries (e.g.{ MY_PIPELINE: "pipeline-name", OTHER_PIPELINE: { pipeline: "...", remoteProxyConnectionString: ... } }) would cause Miniflare to throw an error. Both forms are now accepted and normalised correctly.Allow mixed
r2Bucketsrecords containing both string and object entriesPreviously, passing an
r2Bucketsconfig that mixed plain string values and object entries (e.g.{ MY_BUCKET: "bucket-name", OTHER_BUCKET: { ... } }) would cause Miniflare to throw an error. Both forms are now accepted and normalised correctly.Disable undici Pool request timeouts for local dev
Miniflare's undici
Poolinstances were using the defaultheadersTimeoutandbodyTimeoutof 300 seconds (5 minutes). Any request taking longer than that — streaming responses, large uploads, long-polling, or compute-heavy Workers — would be silently killed with a "request failed" error.Setting both timeouts to
0disables them entirely, which is the correct behaviour for a local development tool where there is no reason to enforce request timeouts.
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.