@cloudflare/vite-plugin@1.53.0
Breaking Changes📦 cloudflare-workersView on GitHub →
⚠ 1 breaking✨ 2 features🐛 5 fixes🔧 8 symbols
Summary
This release introduces the ability to link containers to Durable Objects from the export side and fixes several bugs related to compatibility dates, Node.js compatibility, and FedRAMP region targeting.
⚠️ Breaking Changes
- Previously, two containers could be attached to the same Durable Object, which would silently fail. This is now an error. If you have two containers for one `class_name`, give each its own Durable Object class.
Migration Steps
- If you previously attached multiple containers to a single Durable Object, update your configuration to assign each container to its own Durable Object class.
✨ New Features
- Containers can now be attached to a Durable Object from its `exports` entry using a new `container` field. This makes `containers[].class_name` optional.
- Wrangler now reports errors for various invalid container/Durable Object configurations, including missing container references, conflicting claims, and duplicate container names.
🐛 Bug Fixes
- The `@cloudflare/vite-plugin` now honors `access.dev`, ensuring `ctx.access.getIdentity()` returns the configured identity.
- Worker-side request body cancellation is now handled without surfacing stream controller errors in local development.
- A fixed default compatibility date is now used instead of the current date to prevent local development failures due to runtime version mismatches.
- Date-enabled Node.js compatibility no longer adds conflicting globals to generated runtime types; Node.js globals are now sourced from `@types/node`.
- Wrangler now uses the FedRAMP High managed container registry when targeting the FedRAMP High compliance region for container builds, pushes, deployments, image commands, and local development.