@cloudflare/vitest-pool-workers@0.18.0
📦 cloudflare-workersView on GitHub →
✨ 5 features🔧 9 symbols
Summary
This release introduces declarative Durable Object exports via `wrangler.json` for managing DO lifecycles (creation, deletion, renaming, transfer). This new flow is integrated across deployment, local development, testing, and type generation.
Migration Steps
- When defining Durable Object lifecycle changes, use the declarative `exports` map in `wrangler.json` instead of the legacy `migrations` array.
- If a Worker declares DO class bindings but no lifecycle configuration, `wrangler` will now suggest an `exports` entry instead of a legacy `migrations` block.
✨ New Features
- Added support for declarative Durable Object exports via an `exports` map in `wrangler.json` as an alternative to the legacy `migrations` array.
- The deployment response now surfaces the server's reconciliation result, including created namespaces, applied tombstones, and structured per-scenario info.
- Local development (`wrangler dev`, `vite dev`, `unstable_startWorker`) now reads Durable Object SQLite storage settings from the new `exports` field.
- `@cloudflare/vitest-pool-workers` now reads Durable Object configuration from `exports` for correct local SQLite storage and unbound DO class access via `ctx.exports.X`.
- `wrangler types` is now aware of `exports`, adding live entries (including `expecting-transfer`) to `Cloudflare.GlobalProps.durableNamespaces` to type `ctx.exports.X` for unbound DOs.