NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
npm, #2609 most downloaded on npm
Cloudflare plugin for Vite
Latest stable
1.69.1
Last release 4 days ago
13 Nov 2026
Ships on a steady schedule
a new release about every 8 days
Nearly every release is documented
notes for 54 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
2 years old
915 releases · first in 2025
Drag across the ruler to compare, or tap a release to open it.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Your coding agent can read these notes before it upgrades. Set up the MCP server →
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
tailConsumers now only lists Tail Workers with a tail() handler. This is a breaking change to the experimental config API: move each entry that set st…
#16682 5966749 Thanks @ghostwriternr! - Run the Containers that cloudflare.config.ts attaches to Durable Objects
Previously, projects that load cloudflare.config.ts through the config option ran those Durable Objects without their Containers. The plugin now prepares the Containers' images and runs them, as it does for Wrangler configuration files. Dockerfile and build context paths are relative to the directory that contains cloudflare.config.ts.
cloudflare.config.ts has no setting that disables local Containers, so, as with the Vite plugin, projects with Container-backed Durable Objects need Docker to run their tests.
#16824 877b249 Thanks @jamesopstad! - Move streaming tail consumers to experimental.streamingTailConsumers in cloudflare.config.ts
Streaming Tail Workers are now declared in a separate, experimental list instead of with streaming: true on a tailConsumers entry. tailConsumers now only lists Tail Workers with a tail() handler. This is a breaking change to the experimental config API: move each entry that set streaming: true to experimental.streamingTailConsumers, without the streaming field.
export default defineConfig({
worker: {
tailConsumers: [{ worker: "tail-worker" }],
experimental: {
streamingTailConsumers: [{ worker: "streaming-tail-worker" }],
},
},
});
Fields under experimental may change or be removed without a major version bump. The wrangler-to-cf codemod now converts streaming_tail_consumers to experimental.streamingTailConsumers.
#16734 c47cca7 Thanks @matingathani! - Fix CommonJS dependencies being loaded as ES modules under Vitest 5 inline projects
A dependency with its own "type": "commonjs" package.json was treated as an ES module when an earlier .js file elsewhere in the project had been classified by the project's "type": "module" package.json. The dependency then failed at import with errors such as Cannot set properties of undefined or exports is not defined. The nearest package.json now always decides how a .js file is loaded.
Updated dependencies [877b249, 69e650c]:
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Previously, the plugin disabled Containers, so those Durable Objects ran without ctx.container. The plugin now builds or pulls the Containers' images
#15695 d437be3 Thanks @ghostwriternr! - Run the Containers that the Wrangler configuration attaches to Durable Objects
Previously, the plugin disabled Containers, so those Durable Objects ran without ctx.container. The plugin now builds or pulls the Containers' images before each project's tests run and gives the Durable Objects a real ctx.container, so these projects now need Docker. To keep running their tests without Docker, set dev.enable_containers to false in the Wrangler configuration, which disables the Containers. Cloudflare-managed registry images are not supported yet.
#16810 cdc970b Thanks @dependabot! - Update DEFAULT_COMPAT_DATE to 2026-11-10
Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.
Updated dependencies [cb9534f, 6af492e, cdc970b, cdc970b, 4e7e9f1, 267dadb, 022ee9d, 44b39b0, 325dc69]:
Set remote: false on an Artifacts binding to opt into the Miniflare simulator and persistent local repositories during development. Omitted remote con
#16186 f1d81a2 Thanks @leostera! - Support local Artifacts across Wrangler, Vite, and Workers Vitest
Set remote: false on an Artifacts binding to opt into the Miniflare simulator and persistent local repositories during development. Omitted remote continues to use the deployed resource, with a warning that changes affect real repositories; remote: true explicitly selects it. When remote bindings are disabled (wrangler dev --local, or Vite's remoteBindings: false), Artifacts bindings use the local simulator. Workers Vitest uses the local simulator when remote is omitted, so tests do not change real repositories by accident; set remote: true to test against the deployed resource. Local development does not require Cloudflare credentials, but does require Git 2.32 or newer on the host.
In Miniflare's own options, Artifacts bindings route like every other binding: only dev.remote: true with a remote proxy connection uses the deployed resource. Wrangler and Vite resolve the deployed-by-default rule, and Workers Vitest its local default, before passing options to Miniflare.
#16700 dc35efb Thanks @cjol! - Bump bundled brace-expansion to pick up security fixes
These packages bundle brace-expansion (a dependency of minimatch), and the bundled versions were affected by published advisories. The bundles now include brace-expansion 2.1.7 (from 2.0.1) and 5.0.12 (from 5.0.5). Normal glob patterns expand as before; only the pathological patterns targeted by the advisories are handled differently.
#16700 dc35efb Thanks @cjol! - Bump bundled devalue from 5.6.3 to 5.9.3 to pick up security fixes
devalue is bundled into these packages, which use it to serialise values between Node.js and workerd. Version 5.6.3 is affected by several published advisories, and 5.9.3 includes their fixes. Serialisation behaviour does not change.
#16700 dc35efb Thanks @cjol! - Bump bundled minimatch from 5.1.6 to 5.1.9 to pick up security fixes
These packages bundle minimatch, and 5.1.6 is affected by published ReDoS advisories. Version 5.1.9 includes the fixes. 5.1.8 is skipped because it broke recursive ** matching, which D1's migrations_pattern relies on.
#16695 b2061f4 Thanks @dependabot! - Update DEFAULT_COMPAT_DATE to 2026-11-04
Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.
Updated dependencies [dc35efb, dc35efb, dc35efb, dc35efb, dc35efb, dc35efb, dc35efb, b8387a5, fa3edb3, 4cde694, b2061f4, b2061f4, f1d81a2, 4bb491b, 36e64f2, 92c4b97]:
Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.
#16670 b14b9dc Thanks @dependabot! - Update DEFAULT_COMPAT_DATE to 2026-11-03
Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.
#16609 da26b7f Thanks @gpanders! - Fix tests failing to start with resolve.preserveSymlinks in isolated node_modules layouts
With resolve.preserveSymlinks: true in a pnpm project, tests failed to start with No such module ".../node_modules/vitest/dist/chai", because a package's own dependencies are linked only next to its real path. Packages linked from a store inside node_modules now load from their real paths, and other files keep their symlinked paths.
Updated dependencies [b14b9dc, 44d1ee4, b14b9dc, d2eda1c, 2750917, 34f34b3]:
#16649 199efb6 Thanks @petebacondarwin! - Suppress Version Packages CI alerts for test summaries that failed only because their dependencies were cancelled
Check the summary's test partitions or framework shards before sending an alert. Genuine failures and timeouts still alert, and alerts are retained if GitHub cannot confirm the dependency results.
…for compatibility. These exports are deprecated and now use the implementations in @cloudflare/workers-utils. Add a dependency on that package and rep…
#16424 1598fd3 Thanks @edmundhung! - Promote experimental.newConfig to a stable config option
The experimental experimental.newConfig option is now the stable config option. Pass config: true to cloudflareTest() to load your Worker's bindings, entrypoint and compatibility settings from cloudflare.config.ts in the project root, or pass the path of a cloudflare.config.ts elsewhere:
cloudflareTest({ config: true });
cloudflareTest({ config: "./worker/cloudflare.config.ts" });
config can't be combined with wrangler. miniflare options are merged over the Worker from cloudflare.config.ts, with miniflare values taking precedence. Config functions receive Vitest's mode as ctx.mode, which defaults to test and can be changed with --mode.
If you're moving from experimental.newConfig, secrets are now read from Vite's envDir instead of the directory containing cloudflare.config.ts, and remote bindings authenticate with cf instead of Wrangler.
#16642 d38cb02 Thanks @dependabot! - Update DEFAULT_COMPAT_DATE to 2026-11-02
Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.
#16623 51bbf8b Thanks @petebacondarwin! - Deprecate shared tooling helper exports from Miniflare
Miniflare continues to export getNodeCompat, NodeJSCompatMode, and getFreshSourceMapSupport for compatibility. These exports are deprecated and now use the implementations in @cloudflare/workers-utils. Add a dependency on that package and replace the Miniflare imports with:
import {
getNodeCompat,
type NodeJSCompatMode,
} from "@cloudflare/workers-utils/node-compat";
import { getFreshSourceMapSupport } from "@cloudflare/workers-utils/sourcemap";
Wrangler and the Cloudflare Vite and Vitest plugins now use the shared helpers directly. The helpers retain their behavior and can be imported without loading the Workers runtime.
The deprecated Miniflare exports will be removed in a later release, allowing downstream tools such as cf to migrate and release independently first.
Updated dependencies [d38cb02, d38cb02, 51bbf8b, e5b1798]:
Vitest's default V8 coverage provider now collects and reports coverage for tests running locally in the Workers runtime.
#15591 e3d1867 Thanks @dario-piotrowicz! - Support V8 code coverage in the Workers Vitest integration
Vitest's default V8 coverage provider now collects and reports coverage for tests running locally in the Workers runtime.
#16132 08d694c Thanks @edmundhung! - Add support for Vitest 5
#16139 2d1d563 Thanks @cpojer! - Update esbuild to 0.28.2
Align esbuild dependency with tooling using the latest 0.28 patch so package managers can share one installation instead of downloading a second native binary.
#16140 aaa6a88 Thanks @cpojer! - Update Zod to 4.6.5
Align the published Zod dependencies in Cloudflare configuration and the Vitest plugin with other tools using Zod 4.6.5 so consumers can reuse one installation.
Updated dependencies [2d1d563, 85b14e7, e6f7663, fe607f9, ad7ff45, 8de6b3c, ae29445, 757faa6, cc8e969, 417b186, 93c1069, 6947df3, 82acf3c, 9a58244]:
Updated dependencies [ 7f0734c ]:
7f0734c]:
A Workflow declared in a Worker's exports is now available on ctx.exports in wrangler dev , the Vite plugin and the Vitest plugin, with the same API a
#15856 4c2993b Thanks @Naapperas! - Support Workflows declared in exports on ctx.exports in local development
A Workflow declared in a Worker's exports is now available on ctx.exports in wrangler dev, the Vite plugin and the Vitest plugin, with the same API as a Workflow binding:
const instance = await ctx.exports.MyWorkflow.create({
params: { name: "World" },
});ctx.exports and workflows bindings with the same Workflow name share their instances, including instances created before the Workflow was declared in exports. Two Workers can't export the same Workflow name, and a binding to an exported Workflow must refer to the Worker and class that export it. getPlatformProxy() ignores Workflows declared in exports, since it doesn't run the Worker's code.
wrangler workflows commands run with --local also work with Workflows declared only in exports, without a workflows binding.
In the Vitest plugin, introspectWorkflow() and introspectWorkflowInstance() still need a Workflow binding, and now explain how to add one when passed a Workflow from ctx.exports. Instances created through ctx.exports are introspected too. A workflows binding whose script_name is the Worker's own name now resolves to the Worker itself again.
8dc53ae, 4c2993b]:
The admin API it returns is backed by RPC stubs. Its type left out Symbol.dispose and the documented example never released them, so a test that follo
#15706 f5341a4 Thanks @Om-singhaI! - Declare the adminSecretsStore() result as disposable and show using in its example
The admin API it returns is backed by RPC stubs. Its type left out Symbol.dispose and the documented example never released them, so a test that followed it made workerd warn that an RPC stub was not disposed properly. using admin = adminSecretsStore(env.MY_SECRET) now type checks and releases the stubs at the end of the scope.
Updated dependencies [1bdb96d, cd7508c, f5605f5]:
Updated dependencies [ 59267fc , 6906bf0 , 354ebdb ]:
59267fc, 6906bf0, 354ebdb]:
Updated dependencies [ ad20547 , 02c1d83 , 275184d , bd59eca ]:
ad20547, 02c1d83, 275184d, bd59eca]:
Updated dependencies [ 0ed4c54 , 703922d ]:
Experimental cloudflare.config.ts files now define settings and resources together in a default-exported defineConfig() call. Add a Worker under worke
#15713 3c75cad Thanks @jamesopstad! - Define experimental Cloudflare configuration with a single default export
Experimental cloudflare.config.ts files now define settings and resources together in a default-exported defineConfig() call. Add a Worker under worker, add Containers to the containers array, or omit both to provide settings only.
import * as entrypoint from "./src/index.ts" with { type: "cf-worker" };
export default defineConfig({
accountId: "...",
complianceRegion: "public",
worker: {
name: "my-worker",
compatibilityDate: "2026-09-18",
entrypoint,
},
});#15707 95af41d Thanks @halfstack-dev! - Support nested D1 migration layouts in readD1Migrations()
readD1Migrations() now accepts the same migrationsDir / migrationsPattern options Wrangler uses, so Vitest can apply Drizzle-style nested files such as 0001_init/migration.sql. Discovery is shared with Wrangler via @cloudflare/workers-utils, so the test path and wrangler d1 migrations apply stay aligned.
The original readD1Migrations(migrationsPath) signature still reads only top-level *.sql files in that directory.
Updated dependencies [ 412c79e , 92874f6 , fe265f8 ]:
412c79e, 92874f6, fe265f8]:
Add @cloudflare/codemod package with internal AST-based codemod utilities ( parseJs , parseTs , parseFile , transformFile , mergeObjectProperties ) bu
#13102 e200179 Thanks @dario-piotrowicz! - First release of new package
Add @cloudflare/codemod package with internal AST-based codemod utilities (parseJs, parseTs, parseFile, transformFile, mergeObjectProperties) built on recast.
#15117 f0c9c66 Thanks @edmundhung! - Support Workerd's new module registry in Workers Vitest tests
The pool now follows Workerd's V2 module fallback protocol when new_module_registry is selected while retaining the V1 path for legacy_module_registry. Tests using the new registry preserve URL-based import.meta behavior and load CommonJS dependencies as native CommonJS modules with named exports.
#15272 c921b3f Thanks @penalosa! - Add an experimental newConfig option for loading the Worker's configuration from cloudflare.config.ts
Projects that have migrated to the new TypeScript configuration format had no way to run their Vitest suite against their real bindings, since there was no Wrangler configuration file left to point wrangler.configPath at. This adds the missing option, modelled on @cloudflare/vite-plugin's experimental.newConfig:
import { cloudflareTest } from "@cloudflare/vitest-plugin";
import { defineProject } from "vitest/config";
export default defineProject({
plugins: [cloudflareTest({ experimental: { newConfig: true } })],
});newConfig: true loads cloudflare.config.ts from the project root; pass { configPath: "..." } to load it from elsewhere. Config functions are called with ctx.mode set to Vite's mode, which defaults to "test" and can be overridden with --mode. experimental.newConfig cannot be combined with wrangler.
This is experimental and may change without a major version bump. Wrangler environments, wrangler.config.ts tooling configuration, and type generation are not supported yet.
#15293 7a9b8a7 Thanks @thatsKevinJain! - Fix "Network connection lost" when multiple test files use remote bindings
Remote proxy sessions are shared across pool workers by Wrangler config path, but were disposed during each test file's teardown. Because Vitest starts the next file's worker before the previous one finishes stopping, later files reused an already-disposed session and failed with "Network connection lost". Sessions are now disposed only once the last pool worker stops.
Updated dependencies [aa54b49, 4a67a28, 2d78137, 04e8564, d1cc3af, 693ca29, 693ca29, 693ca29, daefb3c, 37ed753, f76b68e, ad89456, c809851, c66d2d5, 693ca29, 74de3ab, 0cb8690, 9fcb1c9, 22182da, a4c3458, 433fa98, d589d30, dd5148d, 82d11fc]:
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
One column per month.