wrangler@4.114.0
📦 cloudflare-workersView on GitHub →
✨ 1 features🐛 5 fixes🔧 4 symbols
Summary
This release introduces local-dev observability for `wrangler dev` and the Vite plugin, capturing detailed traces of Worker invocations. It also includes several bug fixes, such as improved D1 error messages and a fix for the dev proxy hanging on network errors.
Migration Steps
- Enable local-dev observability by setting `X_LOCAL_OBSERVABILITY=true` if you wish to use it before the public release.
- If you encounter errors related to the `legacy_env` field in `.wrangler/deploy/config.json`, ensure it is removed from user-authored configurations.
✨ New Features
- Local-dev observability: `wrangler dev` and the Vite plugin now capture a trace for every local Worker invocation, including spans, logs, and `console.*` output, and requests crossing worker or Durable Object boundaries. This data can be explored via a new Observability tab in the Local Explorer (Traces and Events views) or a read-only SQL endpoint at `/cdn-cgi/explorer/api/local/observability/query`. This feature is off by default and can be enabled by setting `X_LOCAL_OBSERVABILITY=true`.
🐛 Bug Fixes
- Improved the D1 database-limit error message to provide clearer next steps for users hitting their database limit.
- Fixed grammar in the container image-too-large error message.
- Ignored the removed `legacy_env` field when reading a redirected configuration to prevent errors from older tool-generated configurations.
- Fixed the dev proxy from silently hanging or returning a misleading 503 on network errors for non-root-path requests during `wrangler dev`. Errors are now reported immediately.
- Added explanation on how to provision Flagship bindings if `app_id` is missing in remote development, guiding users to create the binding first with `wrangler flagship apps create`.