wrangler@4.118.0

Summary

Minor Changes #14057 cc63aae Thanks @matingathani ! - Add --json flag to wrangler containers info for consistent JSON output with sibling commands list and instances #14944 a249591 Thanks @nickpatt ! - Enable local observability capture by default in dev wrangler dev and the Vite plugin now capture request traces and console logs into the Local Explorer's Observability tab out of the box — previously this was opt-in behind X_LOCAL_OBSERVABILITY=true . Set X_LOCAL_OBSERVABILITY=false to opt out (for example if the extra per-worker collector/streaming-tail services cause trouble in a multi-process dev-registry setup). #14919 e0bbf55 Thanks @avenceslau ! - Add additional triggers to Workflows Workers can now declaratively start a locally defined Workflow. Configure event subscriptions under triggers.events ; Wrangler validates each target and updates the script's event triggers during deployment. { "triggers" : { "events" : [ { "type" : " cf.artifacts.repo.pushed " , "filter" : { "namespace" : " my-namespace " , "repo_name" : " my-repo " }, "targets" : [ { "type" : " workflow " , "workflow_name" : " my-workflow " } ] } ] } } Patch Changes #14936 f92d1fc Thanks @petebacondarwin ! - Fix jsx_fragment being ignored when wrangler dev runs a custom build If your project uses a custom build and sets both jsx_factory and jsx_fragment , wrangler dev used your jsx_factory value for JSX fragments as well, so fragments compiled incorrectly. Your jsx_fragment value is now used. #14936 f92d1fc Thanks @petebacondarwin ! - Stop wrangler dev starting new work after you stop it or it reloads Stopping wrangler dev , or having it reload after a configuration change, could still leave it starting work for the state it had just left behind: your custom build command could run once more after dev had stopped, a change to a file in your assets directory could be reported against configuration that had already been replaced, and in some cases the process could stay alive instead of exiting. That work is now discarded, so stopping or reloading wrangler dev leaves nothing running behind it. #14936 f92d1fc Thanks @petebacondarwin ! - Stop wrangler dev from running custom builds concurrently When several watched files changed at once — for example during a git pull or a "save all" — wrangler dev started a custom build for every file that changed, so multiple copies of your build command ran at the same time and fought over the same output files. A burst of file changes now results in a single build, and a build only starts once the previous one has finished. #13746 cec9d88 Thanks @edmundhung ! - Report a clear error for account IDs that can't be used in a Cloudflare API request Account IDs are substituted straight into Cloudflare API URL paths, so a value containing non-ASCII characters previously failed deep inside the request layer with an opaque Cannot convert argument to a ByteString error that gave no hint about which setting was at fault. Account IDs read from CLOUDFLARE_ACCOUNT_ID and from the account_id configuration field are now validated up front, and an invalid value fails with a message naming both the offending value and where it came from.

News Radar provides aggregated summaries. Full content and copyright remain with the original publisher.