wrangler@4.103.0
Minor Changes
-
#14295
cfd6205Thanks @dario-piotrowicz! - Moveunstable_getWorkerNameFromProjectfrom wrangler to@cloudflare/workers-utilsThe
unstable_getWorkerNameFromProjectexport has been removed from thewranglerpackage. This function is now available asgetWorkerNameFromProject(without theunstable_prefix) from@cloudflare/workers-utils. If you were importing this function fromwrangler, update your import to use@cloudflare/workers-utilsinstead. -
#14295
cfd6205Thanks @dario-piotrowicz! - Remove experimental autoconfig exportsThe experimental autoconfig exports (
experimental_getDetailsForAutoConfig,experimental_runAutoConfig,experimental_AutoConfigFramework) have been removed. This logic has been moved to the@cloudflare/autoconfigpackage (without theexperimental_prefixes since the package itself is pre-v1).
Patch Changes
-
#14366
c6579d3Thanks @jamesopstad! - Resolve relativecf-workerentrypoint imports relative to the importing moduleWhen loading the experimental
cloudflare.config.ts, a relative entrypoint imported withimport ... with { type: "cf-worker" }(e.g../src/index.ts) is now anchored to the module where the import is written, rather than being passed through verbatim and later resolved against the top-level config file. This fixes incorrect resolution when the import lives in a file other than the entry config — for example a config that re-exports from a nested file.Bare specifiers (such as
@scope/pkg) and virtual modules (such asvirtual:foo) are still left unresolved so that consumers can apply their own resolution. -
#14316
444b75eThanks @matingathani! - Preventwrangler devcrash when source-mapping a truncated error chunkWhen a worker logs many errors in quick succession, the stderr chunks received by
wrangler devcan be truncated mid-stack-frame, leaving a call site with an invalid column number. The source map library throws in that case, which was crashing the wrangler process entirely. The error is now caught and the original (un-source-mapped) text is returned instead. -
#14118
b38823fThanks @aicayzer! - FixUint8Arraystep outputs in local Workflows being persisted with the full backingArrayBufferA
Uint8Arrayreturned from a Workflows step underwrangler devwas serialised together with its full underlyingArrayBuffer, causing a rawSQLITE_TOOBIGerror at view sizes well below the documented 1MiB step-output limit. For example, a 200KB view sliced from an 800KB buffer (a common pattern fromcrypto.getRandomValuesorarr.slice(...)on a larger pool) would fail. The view's bytes are now copied to a tight buffer before persistence, bringing local behaviour in line with production. Fixes #14101. -
Updated dependencies [
b38823f]:- miniflare@4.20260617.1