wrangler@4.116.0
📦 cloudflare-workersView on GitHub →
✨ 4 features🐛 2 fixes🔧 3 symbols
Summary
Wrangler now automatically derives Worker names in agent-driven deploys and the `wrangler check startup` command has graduated from alpha with enhanced reporting. This release also introduces support for dispatching email handlers in the test harness and fixes an issue with interrupting authorization flows.
✨ New Features
- Wrangler now derives the Worker name from the project and automatically registers the same project-derived workers.dev account subdomain on a first deploy when running in a detected agent environment.
- The experimental build output directory now includes the Worker's configuration at `.cloudflare/output/v0/workers/default/config.json` instead of `.cloudflare/output/v0/workers/<worker-name>/worker.config.json`.
- `wrangler check startup` is now out of alpha and shows bundle size and a local timing summary. It reports local profile window, sampled active, garbage collection, and idle time alongside raw and compressed bundle sizes.
- Added support for dispatching email handlers with `createTestHarness`. You can now call `server.getWorker().email({ from, to, raw })` to dispatch directly to a Worker's `email()` handler and inspect its outcome, rejection reason, forwarded messages, and replies.
🐛 Bug Fixes
- Fixed ctrl+c not being able to interrupt wrangler while waiting for Cloudflare Access authorization. `cloudflared` is now spawned asynchronously, keeping wrangler responsive while it waits.
- Fixed `wrangler triggers deploy` to use Vite-generated redirected configuration. The command now reads `.wrangler/deploy/config.json`, matching `wrangler deploy` and `wrangler versions upload`, so generated Worker names and trigger settings are applied.