wrangler@4.107.1
📦 cloudflare-workersView on GitHub →
🐛 5 fixes🔧 6 symbols
Summary
This patch release focuses on bug fixes, including correct handling of `.dev.vars` overrides and improved secret deployment error messages. It also updates internal dependencies and refactors path resolution to improve ESM compatibility.
Migration Steps
- If you rely on global config or cache directory resolution that previously used `xdg-app-paths`, note that this dependency was replaced by a vendored pure-ESM implementation in `@cloudflare/workers-utils`. If you are consuming node-only entry points from `@cloudflare/workers-utils`, use `@cloudflare/workers-utils/fs-helpers` or `@cloudflare/workers-utils/global-wrangler-config-path` as appropriate.
🐛 Bug Fixes
- Fixed an issue where `wrangler dev` would not override config `vars` with values from `.dev.vars` during local development when the `secrets` field was defined in the configuration file.
- Improved error guidance when deploying a new Worker with `secrets.required` by directing users to use `wrangler deploy --secrets-file <path>` instead of suggesting the non-functional `wrangler secret put <NAME>`.
- Fixed a potential crash when displaying certain CLI output that contained no content lines.
- Rate limit counters in `wrangler dev` and Miniflare are now keyed by `namespace_id` instead of binding name, ensuring bindings referencing the same namespace share a limit, which also re-enables rate limit bindings in multiworker `wrangler dev` sessions.
- Watch-mode rebuild failures in `unstable_startWorker` now emit an error event (`buildFailed`) allowing programmatic consumers to observe them, matching the behavior of initial build failures.