wrangler@4.104.0
📦 cloudflare-workersView on GitHub →
✨ 1 features🐛 3 fixes🔧 3 symbols
Summary
This release introduces the ability to access the full environment object in test harnesses and resolves several bugs related to module rule processing and container egress on arm64.
Migration Steps
- If you rely on build failures when files match inactive module rules, note that these files will now be silently skipped during filesystem discovery; direct imports matching inactive rules still cause hard errors.
✨ New Features
- Added `getEnv()` to `createTestHarness()` Worker handles, allowing tests to access the full `env` object including vars, secrets, and bindings via `await server.getWorker<Env>().getEnv()`.
🐛 Bug Fixes
- Fixed an issue where Wrangler would error during build if `find_additional_modules` discovered a file that only matched an inactive module rule (where `fallthrough: false` was set in a rule). Discovered files matching only inactive rules are now silently skipped (logged at debug level).
- Fixed container egress interception on arm64 Docker runtimes by no longer forcing the `proxy-everything` sidecar image to pull as `linux/amd64`, allowing Docker to select the native image.
- In `wrangler containers registries configure`, the private credential is no longer required when reusing an existing Secrets Store secret, as the existing secret is referenced instead of created.