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 7 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
The package has been renamed from @cloudflare/vitest-pool-workers to @cloudflare/vitest-plugin to be clearer about it's usage.
#15074 bfcc442 Thanks @penalosa! - Rename @cloudflare/vitest-pool-workers to @cloudflare/vitest-plugin for the v1 release
The package has been renamed from @cloudflare/vitest-pool-workers to @cloudflare/vitest-plugin to be clearer about it's usage.
To migrate, run the codemod from the root of your project:
npx @cloudflare/codemods vitest:pool-workers-to-vitest-pluginThis handles the whole rename for you:
package.json, moving plain version ranges to ^1.0.0 while preserving workspace:/catalog:/link:/file: protocol references, along with any overrides, resolutions and pnpm.overrides entries.import { cloudflareTest } from "@cloudflare/vitest-pool-workers" to import { cloudflareTest } from "@cloudflare/vitest-plugin", preserving any subpaths.types entry in your test tsconfig.json from @cloudflare/vitest-pool-workers/types to @cloudflare/vitest-plugin/types.Pass --dry-run to preview the changes first, or --files <glob> to restrict which files are considered.
If you would rather migrate by hand, the only changes needed are the dependency name in package.json, the package specifier in any import/require of the plugin, and the types entry in your test tsconfig.json.
#14690 d81fae7 Thanks @penalosa! - Add a central CLI for Cloudflare codemods
Run a codemod by name, e.g. npx @cloudflare/codemods vitest:v3-to-v4. The initial migrations cover Vitest v3 to v4 configuration (vitest:v3-to-v4) and the @cloudflare/vitest-pool-workers to @cloudflare/vitest-plugin v1 rename (vitest:pool-workers-to-vitest-plugin). The existing Vitest transform now lives in this dedicated package.
Your coding agent can read these notes before it upgrades. Set up the MCP server →
Updated dependencies [`8cf78c8`, `6946da1`]:
Updated dependencies [`b5c083b`]:
b5c083b]:
#16594 effe4ed Thanks @jaeminbird! - Fix wrangler types --check reporting CRLF types files as out of date
When worker-configuration.d.ts was checked out with CRLF line endings (for example with Git's core.autocrlf=true, the default on Windows), the runtime header kept a trailing \r and never matched the expected header. wrangler types --check then always failed, wrangler dev always warned that the types might be out of date, and cached runtime types were never reused. Generated types files are now read with either line ending.
#16635 76e18a8 Thanks @dependabot! - Update DEFAULT_COMPAT_DATE to 2026-11-01
Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.
Updated dependencies [76e18a8, 76e18a8, 009ca6e]:
Updated dependencies [`5a56dda`]:
5a56dda]:
Updated dependencies [`5e6556a`]:
5e6556a]:
Updated dependencies [`552bcfc`]:
552bcfc]:
Updated dependencies [`2b390d7`, `a6c214f`]:
#16403 5f82a56 Thanks @dependabot! - Update DEFAULT_COMPAT_DATE to 2026-10-22
Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.
#16437 e651d7c Thanks @dependabot! - Update DEFAULT_COMPAT_DATE to 2026-10-23
Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.
Updated dependencies [9e05ade, 5f82a56, e651d7c, 5f82a56, e651d7c, 8a30d8e, bcd618d]:
C3 resolves the invoking package manager with which-pm-runs, which already returns nub, but detectPackageManager had no nub case in its switch, so it
#14499 8cd805d Thanks @colinhacks! - Detect the nub package manager
C3 resolves the invoking package manager with which-pm-runs, which already returns nub, but detectPackageManager had no nub case in its switch, so it fell through to the npm default and produced npm commands. detectPackageManager now maps nub to its nub/nubx executables, and @cloudflare/cli-shared-helpers's package-install helpers accept nub as a package manager.
Updated dependencies []:
Updated dependencies [`42df9bb`]:
42df9bb]:
3464abc]:
Updated dependencies [`0283a1f`]:
0283a1f]:
Updated dependencies [`aad35b7`, `1ac96a1`, `1ca8d8f`]:
e1d1b77]:
Updated dependencies [`aa5d580`]:
aa5d580]:
Updated dependencies [`cfd6205`, `cfd6205`]:
Updated dependencies [`673b09e`, `5dfb788`]:
#16148 57f2a71 Thanks @sx4im! - Use a reserved .invalid domain for runtime type generation
wrangler types dispatched runtime type generation to http://dummy.com/..., which is a real, publicly registered domain. A misrouted request could download arbitrary web content into the generated .d.ts. The dispatch URL now uses dummy.invalid (RFC 2606), which can never resolve, so such requests fail closed instead.
Updated dependencies [2d1d563, e6f7663, fe607f9, 8de6b3c, ae29445, cc8e969, 417b186]:
#16849 3cea40b Thanks @dependabot! - Update DEFAULT_COMPAT_DATE to 2026-11-12
Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.
#16886 63eb6da Thanks @dependabot! - Update DEFAULT_COMPAT_DATE to 2026-11-13
Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.
Updated dependencies [`ecfdd5a`]:
ecfdd5a]:
#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 [ b00ef4f , 9d7b08e , 464a582 ]:
#16746 abf924e Thanks @dependabot! - Update DEFAULT_COMPAT_DATE to 2026-11-06
Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.
#16792 de10016 Thanks @dependabot! - Update DEFAULT_COMPAT_DATE to 2026-11-09
Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.
Updated dependencies [`8cd805d`]:
8cd805d]:
#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 [`42df9bb`]:
42df9bb]:
#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.
Updated dependencies [`0283a1f`]:
0283a1f]:
#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.
vite+ installs @voidzero-dev/vite-plus-core under the vite npm alias, so the resolved node_modules/vite/package.json reports the wrapper's own version
#14548 383e679 Thanks @petebacondarwin! - Fix Vite version detection for vite+ projects during autoconfiguration
vite+ installs @voidzero-dev/vite-plus-core under the vite npm alias, so the resolved node_modules/vite/package.json reports the wrapper's own version (e.g. 0.2.2) rather than the underlying Vite version it bundles. This caused autoconfiguration to fail with an error claiming the Vite version was too old to be configured automatically. Autoconfiguration now detects the correct underlying Vite version for these projects.
Updated dependencies [aad35b7, 1ac96a1, 1ca8d8f]:
#16635 76e18a8 Thanks @dependabot! - Update DEFAULT_COMPAT_DATE to 2026-11-01
Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.
#16603 2667a9f Thanks @petebacondarwin! - Fix repeated slashes in URL paths bypassing Pages Functions middleware
Pages Functions now collapse repeated slashes when looking up middleware, so requests such as //secure/one run the same middleware as /secure/one. The original request URL and function-route matching are preserved. Middleware receives a functionPath prefix from the original URL so imported assets can still resolve their relative paths.
Updated dependencies [`6529f0c`]:
6529f0c]:
aa5d580]:
#16403 5f82a56 Thanks @dependabot! - Update DEFAULT_COMPAT_DATE to 2026-10-22
Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.
#16437 e651d7c Thanks @dependabot! - Update DEFAULT_COMPAT_DATE to 2026-10-23
Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.
Updated dependencies [`2194f88`]:
2194f88]:
Provides both a programmatic API and a CLI (pages-functions build) for converting a Cloudflare Pages functions/ directory into a Cloudflare Workers bu
#14785 5e6556a Thanks @dario-piotrowicz! - Publish helpers for compiling Pages Functions directories into Workers bundle
Provides both a programmatic API and a CLI (pages-functions build) for converting a Cloudflare Pages functions/ directory into a Cloudflare Workers bundle:
npx @cloudflare/pages-functions build ./functions --outdir ./dist
The package compiles the Worker and its auxiliary modules, but does not deploy them or generate deployment configuration. Consumers must provide the appropriate Wrangler configuration, including the selected fallback service binding (ASSETS by default) when applicable.
#14928 f05a0de Thanks @dario-piotrowicz! - Improve asset directory error messages in Pages Functions builds
Previously, when an imported asset directory was invalid, a single error message was shown: '<path>' does not exist or is not a directory. This has been split into two distinct, actionable messages:
'<path>' does not exist. Please create the directory or check the path and try again.'<path>' is not a directory. Please provide a path to a valid directory.b21eac2 Thanks @jamesopstad! - Move build output utils to new @cloudflare/build-output-utils packageb21eac2]:
#15789 1c96111 Thanks @jamesopstad! - Publish @cloudflare/runtime-types as a standalone package
Consumers can now share the runtime type generator used by Wrangler and the Cloudflare Vite and Vitest integrations.
This package is not yet stable enough for external use — APIs may change without notice.
Updated dependencies [`b4f0c97`, `8cf78c8`, `a60ff4d`, `6946da1`, `99eb50c`]:
Updated dependencies [`b5c083b`, `9c74538`, `a88d169`, `a88d169`, `daf65f2`, `a9e5abb`]:
Updated dependencies [`cec9d88`]:
cec9d88]:
#16490 bcd618d Thanks @petebacondarwin! - Update Zod to 4.6.6 to address GHSA-mrhx-c7xc-m3w5
The updated shared dependency fixes excessive memory consumption when validating oversized collections. This updates both the published Zod dependencies and the copies bundled into development tools and Workers.
Updated dependencies [`5a56dda`, `5a56dda`, `5a56dda`, `5a56dda`, `5a56dda`, `5a56dda`, `5a56dda`, `5a56dda`, `5a56dda`, `5a56dda`, `5a56dda`, `5a56dd
5a56dda, 5a56dda, 5a56dda, 5a56dda, 5a56dda, 5a56dda, 5a56dda, 5a56dda, 5a56dda, 5a56dda, 5a56dda, 5a56dda, 5a56dda, 5a56dda, 5a56dda, 5a56dda, 5a56dda]:
Updated dependencies [`01d7020`, `48f0c6c`, `8049ca4`, `d7f38c3`, `5c25cfe`, `5e6556a`, `1f61001`]:
Updated dependencies [`773ead4`, `773ead4`, `1035f74`, `e426cb9`, `3a22ae5`, `465c0fb`, `552bcfc`, `6e0bf6e`]:
Updated dependencies [`fe3ae91`, `246ce92`, `c38a2c3`, `c079ba3`, `95b026e`, `c4bacec`, `3203b5d`]:
Updated dependencies [`42af66d`, `a0a091b`, `f03b108`, `4815711`, `2b390d7`, `a6c214f`, `34430b3`]:
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
Nothing published for this version
Nothing published for this version
Nothing published for this version
One column per month.