wrangler@4.87.0
Breaking Changes📦 cloudflare-workersView on GitHub →
⚠ 2 breaking✨ 2 features🐛 2 fixes🔧 4 symbols
Summary
This release enforces Node.js 22 as the minimum required version and introduces an experimental programmatic API for generating Worker types. It also fixes deployment logic when using explicit configuration flags and improves asset directory handling for development proxies.
⚠️ Breaking Changes
- Wrangler now requires Node.js version 22.0.0 or higher. Node.js 20.x is no longer supported.
- The behavior of `wrangler deploy` has changed: auto-config detection and OpenNext delegation are now skipped if the `--config` flag is explicitly provided, preventing accidental deployment of the wrong Worker.
Migration Steps
- Ensure your Node.js environment is running version 22.0.0 or newer.
- If you rely on `wrangler deploy` automatically delegating to OpenNext when an OpenNext project is present, ensure you do not pass the `--config` flag unless you intend to override the default configuration.
✨ New Features
- Introduced an experimental programmatic API, `experimental_generateTypes()`, available from the package root, to generate Worker types with options for including env/runtime toggles.
- Wrangler now emits `markdownDescription` in `config-schema.json` to improve hover text rendering in editors supporting rich JSON Schema hovers.
🐛 Bug Fixes
- Fixed an issue where `wrangler deploy` would ignore the explicit `--config` flag and delegate to OpenNext if an OpenNext project was detected, leading to incorrect deployments.
- Refactored `getPlatformProxy` and `unstable_getMiniflareWorkerOptions` to skip the check for the existence of the assets directory, allowing them to start even if the directory is not yet created (common during development/build phases). Note that `wrangler dev`, `wrangler deploy`, etc., still require the assets directory if specified.