NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
npm
npm, #2609 most downloaded on npm
Cloudflare plugin for Vite
Latest stable
1.69.1
Last release 9 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.
Behavior change: Artifacts bindings now default to the local simulator during development, like KV, R2 and D1. Previously, an omitted remote in Wrangl
#16735 f005593 Thanks @leostera! - Use the local simulator for Artifacts bindings that omit remote
Behavior change: Artifacts bindings now default to the local simulator during development, like KV, R2 and D1. Previously, an omitted remote in Wrangler and the Vite plugin used the deployed Artifacts resource. If you want deployed repos in wrangler dev or vite dev, set "remote": true on the binding (dev: { remote: true } in cloudflare.config.ts). Artifacts is in beta, so this ships as a minor release.
While remote is omitted, wrangler dev, getPlatformProxy() and the Vite plugin warn when remote bindings are enabled, once for each binding rather than on every config reload: "Artifacts binding REPOS uses the local simulator by default. Set remote: true to use deployed repos, or remote: false to silence this warning." Workers Vitest and wrangler dev --local already used the simulator, so they don't warn. Local Artifacts needs no Cloudflare credentials, but requires Git 2.32 or newer on the host.
#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 [f005593, 61eacca, 856842e, 856842e, 3cea40b, 63eb6da, 3cea40b, 63eb6da]:
Your coding agent can read these notes before it upgrades. Set up the MCP server →
When remote bindings could not authenticate, the error told you to run wrangler whoami, wrangler logout and wrangler login. It now names cf auth whoam
#16833 5f539b5 Thanks @jamesopstad! - Name cf commands and settings in remote bindings errors
When remote bindings could not authenticate, the error told you to run wrangler whoami, wrangler logout and wrangler login. It now names cf auth whoami, cf auth logout and cf auth login. When a Flagship binding without an id needed to run remotely, the error named Wrangler's app_id setting and suggested wrangler flagship apps create. It now names id and suggests cf flagship apps create.
For the Vitest plugin, this applies to projects that load cloudflare.config.ts. Projects that use a Wrangler configuration file still see the Wrangler commands.
Updated dependencies [dc47e6d]:
The client output now includes assets imported by the dedicated prerender Worker and by built child environments of the production entry or prerender
#16761 4d157fb Thanks @jamesopstad! - Serve assets imported by prerender Workers and child environments
The client output now includes assets imported by the dedicated prerender Worker and by built child environments of the production entry or prerender Workers.
#16761 4d157fb Thanks @jamesopstad! - Avoid rebuilding environments already built in a pre buildApp hook
When another plugin builds a Worker or client environment in a buildApp hook with order: "pre", the Cloudflare plugin now skips rebuilding that environment.
When using a custom builder.buildApp, the plugin now completes any required client build and makes assets imported by the entry Worker available to serve. Previously, custom builders skipped these steps.
#16761 4d157fb Thanks @jamesopstad! - Stop emitting Vite manifests for Worker environments by default
Enable build.manifest explicitly if your tooling requires these manifests.
#16830 88c774b Thanks @jamesopstad! - Always name cf in actionable messages
Vite plugin v2 is only compatible with cf, so messages that tell you which CLI or command to use now always name cf. Previously they named Wrangler unless Vite was started by cf.
#16682 5966749 Thanks @ghostwriternr! - Stop suggesting settings that do not exist when Docker is unavailable
When Docker could not be reached, the error suggested setting dev.enable_containers to false in cloudflare.config.ts or passing --enable-containers=false. cloudflare.config.ts has no such setting and the Vite plugin has no such flag, so the error no longer suggests them.
Updated dependencies [877b249, 69e650c]:
Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.
#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 [cdc970b, cdc970b, d87fdfe, 4e7e9f1, 267dadb, 44b39b0]:
Cloudflare tooling can pass a selected profile to child processes through CLOUDFLARE_AUTH_PROFILE. Explicit profile arguments take precedence over the
#16599 dee7a1d Thanks @petebacondarwin! - Support CLOUDFLARE_AUTH_PROFILE for shared authentication profile selection
Cloudflare tooling can pass a selected profile to child processes through CLOUDFLARE_AUTH_PROFILE. Explicit profile arguments take precedence over the variable, followed by directory bindings and the default profile. The cf-wrangler development delegate also initializes cf authentication so it reads the selected cf credentials.
Experimental cf development delegates inherit the selected profile without additional command-line flags. Vite refreshes remote authentication when the resolved profile changes, and cf-wrangler keeps its authentication scoped to the delegate invocation.
#16608 0d9cf4e Thanks @petebacondarwin! - Preserve the server origin when constructing Worker request URLs
HTTP requests, WebSocket upgrades, and static routing now consistently treat incoming paths as paths on the selected server origin in dev and preview. Encoded paths and query strings are preserved, and non-origin-form request targets are rejected.
#16683 6f29f97 Thanks @jamesopstad! - Stop persisting account selections made by cf and the Cloudflare Vite and Vitest plugins
Profiles continue to select credentials rather than accounts. If the active credentials can access one account, it is selected automatically. If they can access multiple accounts, cf and the Vite and Vitest plugins reuse the selection while running but ask again the next time they start. Configure accountId in cloudflare.config.ts or set the CLOUDFLARE_ACCOUNT_ID environment variable to avoid repeated prompts.
Wrangler's existing persistent account selection remains unchanged.
#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.
#16413 3ef2afd Thanks @ghostwriternr! - Remove Container networking sidecars and snapshot clone volumes in local development
Wrangler and the Vite plugin removed only the application containers of Container-enabled Durable Objects, found by image tag, and left behind the networking sidecars and snapshot clone volumes that workerd also creates. They now leave cleanup to Miniflare, which removes all of these when the Container configuration changes, such as after a rebuild, when local development stops, and when the process exits.
#16736 245d09f Thanks @edmundhung! - Set the Build Output directories before other plugins read the resolved config
Plugins that read an environment's build.outDir in their configResolved hook now see the Build Output directory, instead of the directory from before the Cloudflare plugin moved it.
Updated dependencies [fea323a, 56459a5, abf924e, de10016, abf924e, de10016, 66bc0d6, c64fdfb]:
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 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.
#16698 0b942ba Thanks @matingathani! - Respect the user's build.cssTarget in Worker environments
The plugin set build.cssTarget to es2024 for every Worker environment. Vite merges array-valued build options by appending, so the user's targets ended up combined with es2024, and Lightning CSS took the lowest version per browser. A project that pinned build.cssTarget to browsers with native light-dark() support would get the prefers-color-scheme polyfill in its Worker CSS anyway.
The plugin now only applies its es2024 default when neither build.cssTarget nor the Worker environment's own build.cssTarget is set.
Updated dependencies [dc35efb, dc35efb, dc35efb, dc35efb, dc35efb, b8387a5, 4cde694, b2061f4, b2061f4, f1d81a2, 4bb491b, 36e64f2, 92c4b97]:
The previous name, ParsedInputConfigWithWorker, remains exported as a deprecated alias for compatibility. The configuration shape and required entry W…
#16656 b447229 Thanks @petebacondarwin! - Expose CloudflareConfig and deprecate ParsedInputConfigWithWorker in the beta Vite plugin
Import CloudflareConfig from @cloudflare/vite-plugin to annotate configuration customizers. The previous name, ParsedInputConfigWithWorker, remains exported as a deprecated alias for compatibility. The configuration shape and required entry Worker remain unchanged.
#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 [b14b9dc, b14b9dc, d2eda1c, 2750917]:
…for compatibility. These exports are deprecated and now use the implementations in @cloudflare/workers-utils. Add a dependency on that package and rep…
#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 [1598fd3, d38cb02, d38cb02, 51bbf8b]:
This is a breaking change to the beta API: object overrides and callbacks that mutate or return partial Worker configurations must return a complete c…
#16573 91f0e03 Thanks @petebacondarwin! - Customize the full parsed Cloudflare configuration through the beta Vite plugin's config callback
The config option now accepts (loadedConfig: ParsedInputConfigWithWorker) => ParsedInputConfigWithWorker, allowing frameworks to customize account settings and Containers alongside the entry Worker. Both the loaded and returned configurations include a Worker, and ParsedInputConfigWithWorker is exported for framework authors. The returned configuration is revalidated, including resource relationships, before being used for development and recorded in the build output for preview and deployment.
This is a breaking change to the beta API: object overrides and callbacks that mutate or return partial Worker configurations must return a complete configuration instead. Copy the loaded configuration and any nested fields to preserve, for example config: (loadedConfig) => ({ ...loadedConfig, worker: { ...loadedConfig.worker, name: "my-worker", compatibilityDate: "2026-10-01" } }). Fields and arrays are replaced rather than deep-merged.
#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 [91f0e03, effe4ed, 76e18a8, 76e18a8, 009ca6e]:
Durable Object bindings that explicitly name the Worker itself now resolve to the test runner in @cloudflare/vitest-plugin, for both cloudflare.config
#16013 8b64bec Thanks @swalker326! - Fix Durable Object self-references in tests and container validation
Durable Object bindings that explicitly name the Worker itself now resolve to the test runner in @cloudflare/vitest-plugin, for both cloudflare.config.ts and Wrangler configuration files. Named Wrangler environments use their effective Worker name, keeping bindings to the base Worker external. Container validation also accepts these self-references, using the effective deployment name to distinguish local and external bindings.
Explicit binding targets remain intact during configuration conversion, so deploying with --name or a CI name override preserves the intended Durable Object target.
Updated dependencies [15fbaed, d8899ac]:
Setting remote: true on an Analytics Engine dataset now sends writeDataPoint() calls from wrangler dev and the Vite plugin to the real dataset. Withou
#16536 a95d647 Thanks @WalshyDev! - Support remote Analytics Engine bindings in local development
Setting remote: true on an Analytics Engine dataset now sends writeDataPoint() calls from wrangler dev and the Vite plugin to the real dataset. Without it, writes are still dropped locally.
{
"analytics_engine_datasets": [
{
"binding": "EVENTS",
"dataset": "my-dataset",
"remote": true
}
]
}
#15290 6e3924d Thanks @edmundhung! - Close Vite HMR WebSocket upgrades when Vite WebSockets are disabled
Previously, server.ws: false left the browser's raw upgrade socket pending because no Vite handler claimed it. Worker and Sandbox WebSocket forwarding remains unchanged.
Updated dependencies [a95d647, c7a3373, c7a3373, c7a3373]:
In Miniflare v5 beta, resolve the registry from CLOUDFLARE_DEV_REGISTRY_PATH, then the unsafeDevRegistryPath constructor option, then /dev-registry/v5
#16494 0968b08 Thanks @petebacondarwin! - Enable Miniflare's development registry by default and centralize path resolution
In Miniflare v5 beta, resolve the registry from CLOUDFLARE_DEV_REGISTRY_PATH, then the unsafeDevRegistryPath constructor option, then <Cloudflare config directory>/dev-registry/v5. The default is independent of legacy Wrangler directories and is scoped to the Miniflare major version. The Vite v2 beta plugin follows this new default, while current Wrangler and getPlatformProxy() retain Wrangler's legacy default for compatibility with existing Wrangler sessions. Vite v2 and Wrangler therefore require the same CLOUDFLARE_DEV_REGISTRY_PATH to discover each other; set it for both processes when mixing these tools.
Add enableDevRegistry: false to disable registration and discovery explicitly. Shared storage now uses the resolved default without requiring an explicit path. As before, shared storage requires an enabled registry to elect a storage owner, so combining unsafeEnableSharedStorage: true with enableDevRegistry: false is rejected. Miniflare no longer reads MINIFLARE_REGISTRY_PATH; use CLOUDFLARE_DEV_REGISTRY_PATH instead. Expose resolveDevRegistryPath() for integrations that also read registry files. Wrangler uses the effective path for its runtime configuration, initial bindings display, and Flagship active-session check, so the canonical override cannot bypass that check. An explicitly disabled Wrangler registry remains disabled.
#15659 8d98a15 Thanks @dedsec-terminal! - Fix Vite DevTools WebSocket connections closing unexpectedly
Leave upgrades at /__devtools/__ws to Vite DevTools instead of forwarding them to the Worker. Sandbox preview requests continue to reach the Worker.
Updated dependencies [0968b08, f3c13b3]:
Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.
#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.
#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.
#16452 c4a3f9d Thanks @apeacock1991! - Treat cloudflare:durable-objects as a built-in runtime module
Workers can import retryable() from cloudflare:durable-objects to mark Durable Object methods as safe to retry. The plugin now leaves that import for the runtime to resolve, as it does for cloudflare:workers, instead of trying to resolve it as a package.
#16453 18fe656 Thanks @james-elicx! - Preserve a Worker response's statusText in Vite dev and preview
Responses such as new Response(body, { status: 231, statusText: "Custom" }) now reach the browser as 231 Custom instead of 231 unknown. Empty status text is also preserved over HTTP/1.x.
#16428 7684ef4 Thanks @edmundhung! - Use cf credentials for remote bindings in vite dev and vite preview
Remote bindings previously used cf credentials only when Vite was started by cf dev. If remote bindings report that you aren't authenticated, run cf auth login or set CLOUDFLARE_API_TOKEN.
#16486 f09d7c9 Thanks @petebacondarwin! - Preserve separate Set-Cookie request headers in Vite dev and preview
Workers now receive each incoming Set-Cookie value separately for HTTP requests and WebSocket upgrades, including values with commas in an Expires date. Previously, multiple values could be combined into one header.
#16457 ab5c335 Thanks @Eshan05! - Fix a dev server failing to start when an earlier dev server in the same process had different Worker exports
The Vite plugin now clears the Worker export types it detected when a dev server closes. A dev server created afterwards in the same process derives them from its own config again, so it no longer fails with Class extends value undefined for a Durable Object the earlier server's Worker did not export.
Updated dependencies [9e05ade, 5f82a56, e651d7c, 5f82a56, e651d7c, 8a30d8e, bcd618d]:
Nothing published for this version
Bun's fetch() ignores the undici dispatcher that Miniflare routes requests through (oven-sh/bun#39247). Under Bun, createTestHarness()'s server.fetch(
#15846 a88cac4 Thanks @oddharsh! - Fail with an error instead of hanging when local dev requests can't work under Bun
Bun's fetch() ignores the undici dispatcher that Miniflare routes requests through (oven-sh/bun#39247). Under Bun, createTestHarness()'s server.fetch() and server.getWorker()'s fetch(), email() and scheduled() now throw a UserError, requests to the dev server URL get a 503 naming the cause, and starting remote bindings throws a UserError. Each of these used to hang with no error. server.getWorker().getEnv() and getExport() keep working under Bun.
#16318 ff1f971 Thanks @jamesopstad! - Prevent legacy Wrangler configuration files from being silently ignored
The Vite plugin now stops with an actionable error when wrangler.json, wrangler.jsonc, or wrangler.toml is present without cloudflare.config.ts. Run npx cf migrate --bundler vite to migrate the project before building.
Updated dependencies [3464abc]:
Shared deployment and Container helpers now receive only the command paths and configuration syntax required by each operation. Wrangler reuses the pa
#16225 fc51b96 Thanks @dario-piotrowicz! - Decouple shared deployment guidance from Wrangler
Shared deployment and Container helpers now receive only the command paths and configuration syntax required by each operation. Wrangler reuses the paths that register its command tree, while other consumers can supply their own values without global presentation state or Wrangler-specific fallbacks.
Updated dependencies [37ab91c, 0ae7926]:
Domain objects accept hostname, production, and previews to serve production traffic, Preview traffic, or both. String domains continue to serve produ
#16266 68f86a3 Thanks @GregBrimble! - Add custom domain traffic settings to experimental programmatic Worker configuration
Domain objects accept hostname, production, and previews to serve production traffic, Preview traffic, or both. String domains continue to serve production traffic only. Apply hosting settings with a parent Worker or trigger deployment.
The deprecated WRANGLER_HYPERDRIVE_LOCAL_CONNECTION_STRING_ environment variable is no longer supported. Rename Hyperdrive overrides to CLOUDFLARE_HYP…
#16262 fe8ce54 Thanks @jamesopstad! - Load local Worker secrets with Vite-compatible file resolution
The plugin now uses Vite's resolved mode and envDir when locating files that provide declared Worker secrets.
CLOUDFLARE_ENV is no longer used to select mode-specific .dev.vars and .env files. Projects that relied on it should use Vite's --mode option instead. For preview, set the mode during vite build; vite preview uses the mode recorded in the Build Output.
The deprecated WRANGLER_HYPERDRIVE_LOCAL_CONNECTION_STRING_<BINDING_NAME> environment variable is no longer supported. Rename Hyperdrive overrides to CLOUDFLARE_HYPERDRIVE_LOCAL_CONNECTION_STRING_<BINDING_NAME>.
#16262 fe8ce54 Thanks @jamesopstad! - Remove legacy local testing endpoint rewrites
The plugin no longer rewrites legacy local testing endpoints to their canonical /cdn-cgi/local/* and /__cf_local/* equivalents. Local-development scripts, tests, or integrations that call the legacy endpoints directly must update them as follows:
/cdn-cgi/handler/scheduled and /cdn-cgi/mf/scheduled → /cdn-cgi/local/scheduled/cdn-cgi/handler/email → /cdn-cgi/local/email/cdn-cgi/mf/stream/* → /__cf_local/stream/*/cdn-cgi/mf/imagedelivery/* → /__cf_local/imagedelivery/*/cdn-cgi/explorer/* → /cdn-cgi/local/explorer/*#16262 fe8ce54 Thanks @jamesopstad! - Use native Cloudflare configuration and Build Output in Vite plugin v2
Wrangler cannot deploy apps built with Vite plugin v2. Deploy with cf deploy instead.
The plugin now loads Worker configuration from cloudflare.config.ts and no longer loads Wrangler configuration files. The configPath and experimental.newConfig options have been removed. Worker configuration supplied through the config, auxiliaryWorkers, and prerenderWorker plugin options now uses the native camelCase configuration format, and the exported WorkerConfig type has been updated to match.
Projects using a Wrangler configuration file must move their Worker configuration to cloudflare.config.ts.
Builds now always emit a structured Build Output in .cloudflare/output. When Containers are configured, vite build builds any Dockerfile-backed Container images and records them in the output. vite preview then reuses those images rather than rebuilding them when the preview server starts.
Wrangler is no longer a runtime or peer dependency of the plugin.
#16262 fe8ce54 Thanks @jamesopstad! - Drop support for Vite 6
The minimum supported Vite version is now Vite 7. Projects using Vite 6 must upgrade to Vite 7 or later before updating @cloudflare/vite-plugin to this release.
#16262 fe8ce54 Thanks @jamesopstad! - Default the entry Worker to the ssr Vite environment
The entry Worker's Vite environment now defaults to ssr instead of deriving its name from the Worker name. Projects whose Vite configuration or plugins target the entry environment by its previous Worker-derived name must target environments.ssr, or preserve the previous name by setting viteEnvironment.name explicitly.
#16262 fe8ce54 Thanks @jamesopstad! - Generate Worker types from cloudflare.config.ts
The plugin now generates .cloudflare/types/index.d.ts during development and builds. Generated declarations infer bindings from cloudflare.config.ts and include runtime types for the configured compatibility date and flags by default. Use the top-level types option to disable generation or omit runtime types.
Include the configuration and generated declarations in the TypeScript configuration for your Worker:
{
"include": ["src", "cloudflare.config.ts", ".cloudflare/types"]
}
The experimental.newConfig option, including experimental.newConfig.types, has been removed.
#16262 fe8ce54 Thanks @jamesopstad! - Stabilize the prerenderWorker plugin option
Configure a dedicated prerender Worker with the top-level prerenderWorker option instead of experimental.prerenderWorker.
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
Frameworks such as Waku start a Vite preview server with the same plugin instances to generate static files during vite build. Since 1.69.0 this made
#16841 3eaeb02 Thanks @edmundhung! - Fix builds failing with Expected "assets-only" or "workers" plugin config when a framework starts a preview server during the build
Frameworks such as Waku start a Vite preview server with the same plugin instances to generate static files during vite build. Since 1.69.0 this made the build fail after static generation; builds now complete again, as they did in 1.68.0.
The runtime includes session-scoped cleanup of local Container resources and security fixes for bundled dependencies. Node.js 22.12.0 or later is requ…
#16757 110539e Thanks @petebacondarwin! - Support auth profile selection for experimental cf-authenticated remote bindings
Remote binding sessions can select an authentication profile with CLOUDFLARE_AUTH_PROFILE. Experimental cf authentication keeps account choices within the session instead of persisting them across invocations. Wrangler authentication retains its existing account persistence.
#16801 a1f9218 Thanks @petebacondarwin! - Support custom Cloudflare API headers in Vite development
Use CLOUDFLARE_API_HEADERS to supply additional headers for remote-binding preview uploads, experimental authentication, and Container API requests. Upgrade Wrangler and the shared API helpers together; request diagnostics redact sensitive headers even when log sanitization is disabled.
#16730 9792d4f Thanks @petebacondarwin! - Support local Artifacts bindings in Vite plugin v1
Set remote: false on an Artifacts binding in Wrangler configuration to use local repositories. With remoteBindings: false, Artifacts also uses the local simulator. Omitted remote continues to use deployed repositories when remote bindings are enabled. Local Artifacts requires Git 2.32 or newer.
#16730 9792d4f Thanks @petebacondarwin! - Preserve the server origin when constructing Worker request URLs
HTTP requests, WebSocket upgrades, and static routing now consistently treat incoming paths as paths on the selected server origin in dev and preview. Encoded paths and query strings are preserved, and non-origin-form request targets are rejected.
#16801 a1f9218 Thanks @petebacondarwin! - Update Miniflare to protect local Browser Rendering and Artifacts credentials
Local Browser Rendering receives browser configuration and a usable home directory without unrelated host credentials. Local Artifacts Git forwarding also strips X-Auth-Key before passing requests to the repository.
#16817 cdde2c8 Thanks @petebacondarwin! - Complete v1 builds without rebuilding environments or relying on Vite manifests
Preserve assets imported by entry, child, and prerender Workers when framework plugins build environments first or delete their Vite manifests. Keep the Vite 6 builder callback and Wrangler output configuration used by v1.
#16770 7bb9993 Thanks @petebacondarwin! - Delegate local Container cleanup to Miniflare
Local development and preview now let Miniflare remove application containers, networking sidecars and snapshot clone volumes. Dispose the runtime when a dev-server restart removes the Cloudflare plugin, including overlapping restarts.
#16704 73e4659 Thanks @petebacondarwin! - Update the v1 local runtime and remote binding authentication
Use the November 4 runtime and default compatibility date. Local D1 reads outside sessions no longer write bookmarks, local static assets are read-only during preview, and local Secrets Store persistence is restricted to its owner. Remote binding Access login redirects produce an actionable authentication error while responses returned by bindings are preserved. New opt-in cf OAuth logins request the corrected PlanetScale setup scope.
#16757 110539e Thanks @petebacondarwin! - Update the local development runtime to the November 9 release
Update Miniflare and the coupled Wrangler and shared dependencies, keeping the Workers types aligned with the runtime. Remote binding preview uploads avoid materializing unused multipart request bodies, reducing memory use during session creation.
The runtime includes session-scoped cleanup of local Container resources and security fixes for bundled dependencies. Node.js 22.12.0 or later is required by the updated runtime.
Load the Node.js compatibility helper from workers-utils so v1 continues to build and run after Miniflare removes its deprecated export.
#16677 42151ba Thanks @petebacondarwin! - Support opting into zstd compression for local Container image builds in v1
Update the container build helper so WRANGLER_CONTAINER_IMAGE_COMPRESSION=zstd applies when the Vite plugin prepares Dockerfile-based Container images. Docker must use the containerd image store; the default build behavior is unchanged.
#16676 90cdb9d Thanks @petebacondarwin! - Update the v1 development runtime to Miniflare 5.20261103.0-beta
Use the November 3 workerd runtime with matching Wrangler 4.157.0 and default compatibility date. Local rate-limit bindings now support weighted calls using delta. Load the Node.js compatibility helper from workers-utils so v1 continues to build and run after Miniflare removes its deprecated export.
#16580 0ba4ded Thanks @petebacondarwin! - Fix signed Accept-Encoding headers on the experimental local R2 S3 endpoint
Preserve the original S3 request header in the Vite request adapter so clients that sign Accept-Encoding: identity can use the endpoint exposed by Vite development and preview without SignatureDoesNotMatch errors. The runtime verifies the exact value signed by the client.
#16601 d338c29 Thanks @petebacondarwin! - Validate OAuth callbacks during remote binding login in Vite development
Unrelated browser callbacks no longer interrupt remote binding login, and provider error messages no longer print terminal control characters.
#16703 3272ca5 Thanks @petebacondarwin! - Respect the user's build.cssTarget in Worker environments
Only apply the es2024 CSS default when neither the top-level nor the Worker environment's build.cssTarget is set. This prevents Vite's array merging from lowering explicit browser targets and adding unwanted CSS polyfills.
Upgrade Miniflare to 5.20261023.2-beta and Wrangler to 4.155.0. Builds and asset manifest generation now reject .assetsignore files with invalid UTF-8
#16543 0489cda Thanks @petebacondarwin! - Validate asset ignore files and update local Flagship support
Upgrade Miniflare to 5.20261023.2-beta and Wrangler to 4.155.0. Builds and asset manifest generation now reject .assetsignore files with invalid UTF-8 or null characters instead of silently ignoring their patterns. The Local Explorer also supports Flagship management by app ID, and local flag evaluations retain metadata.
Miniflare also waits for temporary file cleanup before disposal completes, so closing or restarting a Vite dev server finishes cleanup before returning.
#16579 e696113 Thanks @petebacondarwin! - Support remote Analytics Engine bindings in Vite plugin v1
Set remote: true on an analytics_engine_datasets entry in wrangler.jsonc to send writeDataPoint() calls from local development and preview to the real dataset.
#16578 2eae147 Thanks @petebacondarwin! - Close Vite HMR WebSocket upgrades when Vite WebSockets are disabled
Previously, server.ws: false left the browser's raw upgrade socket pending because no Vite handler claimed it. Worker and Sandbox WebSocket forwarding remains unchanged.
#16639 a6f98d0 Thanks @petebacondarwin! - Update the v1 local runtime to workerd 1.20261101.1
Upgrade Miniflare to 5.20261101.0-beta with matching Wrangler and shared SDK dependencies. Local development and preview use the November 1 runtime, and Workers without an explicit compatibility date default to 2026-11-01. Update Workers types to match the runtime.
Upgrade Miniflare to 5.20261023.1-beta and Wrangler to 4.154.0. Vite plugin v1 now uses CLOUDFLARE_DEV_REGISTRY_PATH or /dev-registry/v5 for Worker di
#16539 046db08 Thanks @petebacondarwin! - Update the development registry to use the canonical Cloudflare path
Upgrade Miniflare to 5.20261023.1-beta and Wrangler to 4.154.0. Vite plugin v1 now uses CLOUDFLARE_DEV_REGISTRY_PATH or <Cloudflare config directory>/dev-registry/v5 for Worker discovery. MINIFLARE_REGISTRY_PATH is no longer read. When mixing Vite and Wrangler development sessions, set the same CLOUDFLARE_DEV_REGISTRY_PATH for both because Wrangler retains its legacy default.
#16407 9ec1101 Thanks @petebacondarwin! - Support remote Hyperdrive bindings in Vite plugin v1 development and preview
Set remote: true on a Hyperdrive binding in wrangler.jsonc to connect to its deployed configuration without a local database connection string. The retained remote proxy exposes the binding's connection string and socket streams, and remote session cleanup preserves startup errors and shares one disposal attempt.
#16542 ef573d4 Thanks @petebacondarwin! - Preserve machine-readable error properties from remote bindings
Enable enhanced error serialization on the remote proxy Worker used by Vite plugin v1. Combined with Miniflare 5.20261023.1-beta, remote binding errors retain properties such as code and numericCode so Worker code can handle them without parsing error messages.
#16480 ccaa34a Thanks @petebacondarwin! - Prevent malformed token-exchange responses from crashing remote binding startup
Update the Undici dependency bundled from the retained remote-bindings package to 7.30.1. Responses with excessive content encodings now reject without a later unhandled stream error when the server closes the connection early.
#16502 6f2eda1 Thanks @petebacondarwin! - Update the retained asset configuration validator to Zod 4.6.6
The Vite plugin validates _headers and _redirects through its private workers-shared package. Update that bundled copy to address excessive memory consumption when validating oversized collections.
#16444 79678c4 Thanks @petebacondarwin! - Update Vite plugin v1 to the October 23 Workers runtime
Use Miniflare 5.20261023.0-beta and the matching Wrangler release for local development and preview. Align bundled helpers and Workers types with this runtime, and use 2026-10-23 as the fallback compatibility date when none is configured. The runtime and helper updates also prevent malformed HTTP responses with excessive content encodings from causing unhandled stream errors. The published helpers also update their bundled Zod validator and fix Windows keyring setup for remote-binding credentials when the configuration path contains spaces.
#16479 1d5354b Thanks @petebacondarwin! - Treat cloudflare:durable-objects as a built-in runtime module
Workers can import retryable() from cloudflare:durable-objects to mark Durable Object methods as safe to retry. The plugin now leaves that import for the runtime to resolve, as it does for cloudflare:workers, instead of trying to resolve it as a package.
#16493 4ce6176 Thanks @petebacondarwin! - Preserve a Worker response's statusText in Vite dev and preview
Responses such as new Response(body, { status: 231, statusText: "Custom" }) now reach the browser as 231 Custom instead of 231 unknown. Empty status text is also preserved over HTTP/1.x.
#16501 109844e Thanks @petebacondarwin! - Preserve separate Set-Cookie request headers in Vite dev and preview
Workers now receive each incoming Set-Cookie value separately for HTTP requests and WebSocket upgrades, including values with commas in an Expires date. Previously, multiple values could be combined into one header.
#16503 ca116f9 Thanks @petebacondarwin! - Fix a dev server failing to start when an earlier dev server in the same process had different Worker exports
The Vite plugin now clears the Worker export types it detected when a dev server closes. A dev server created afterwards in the same process derives them from its own config again, so it no longer fails with Class extends value undefined for a Durable Object the earlier server's Worker did not export.
#16504 436fa9a Thanks @petebacondarwin! - Fix Vite DevTools WebSocket connections closing unexpectedly
Leave upgrades at /__devtools/__ws to Vite DevTools instead of forwarding them to the Worker. Sandbox preview requests continue to reach the Worker.
Vite plugin v1 now supports Wrangler configuration files only. Projects using cloudflare.config.ts for configuration should upgrade to Vite plugin v2
#16363 d3240f2 Thanks @jamesopstad! - Remove the experimental.newConfig option from Vite plugin v1
Vite plugin v1 now supports Wrangler configuration files only. Projects using cloudflare.config.ts for configuration should upgrade to Vite plugin v2 beta.
#16373 8cc5f87 Thanks @petebacondarwin! - Report unsupported remote bindings under Bun instead of hanging
Starting remote bindings now fails with an actionable error explaining Bun's unsupported request routing. Use Node.js or disable remote bindings to continue local development.
#16334 9cecd09 Thanks @petebacondarwin! - Fix Container setup guidance in Vite development and preview
Container registry instructions now show the Wrangler command and the configuration location, including Wrangler files and inline Vite configuration.
#16333 68d6eec Thanks @petebacondarwin! - Update the local Workers runtime to the October 19 release
Include the fix for nested asset paths during local development on Windows, together with the compatible Wrangler release.
The runtime update also disposes Workflow step results and introspection modifiers after use, preventing undisposed RPC warnings and cancelled local Workflow requests.
#16379 160e655 Thanks @petebacondarwin! - Update the local Workflow runtime to use native storage cleanup
Consume the Miniflare fix that queues Workflow persistence deletion with instance recreation, including deletion through the local Explorer. This prevents storage cleanup from racing reuse of the same Workflow instance ID.
#16289 bbe822f Thanks @petebacondarwin! - Retry remote preview token refreshes after transient failures
Backport the retry fix to the private remote-bindings workspace package and require wrangler@4.151.1 so long-running remote development sessions recover after a network outage.
#16291 0262f7d Thanks @petebacondarwin! - Use published SDK dependencies for Vite plugin v1 maintenance
Pin the plugin's published SDK dependencies to their deployed npm versions. Keep private shared packages as workspace dependencies so their implementation and build tools remain available on the v1 maintenance branch.
Worker builds now emit source maps unless Vite's build.sourcemap or the Worker's upload_source_maps is set, so deployed Workers get stack traces that
#16245 d6b1c82 Thanks @WalshyDev! - Generate source maps for Worker environments by default
Worker builds now emit source maps unless Vite's build.sourcemap or the Worker's upload_source_maps is set, so deployed Workers get stack traces that point at the original source. The source maps are written next to the Worker bundle and included in Build Output; the client environment is unchanged, so no source maps are added to public assets. Set build.sourcemap: false for the Worker environment, or upload_source_maps: false in the Worker config, to opt out.
cf build looks for Container images left behind by earlier builds so it can remove them. This lookup is best effort, but when Docker could not be reac
#16025 61e07fd Thanks @kohjunhao! - Fix optional Docker lookups printing Docker CLI errors during successful builds
cf build looks for Container images left behind by earlier builds so it can remove them. This lookup is best effort, but when Docker could not be reached it still printed errors such as Cannot connect to the Docker daemon, even when the build succeeded and no image needed Docker. Docker commands whose output Wrangler reads no longer forward the Docker CLI's error output to the terminal. If one of these commands fails in a way that stops the command, the error message still includes the Docker CLI's output.
#16038 dc3e4df Thanks @dario-piotrowicz! - Use consumer-specific CLI names and commands in shared user-facing messages
Shared deployment, container, configuration, and authentication helpers can now render commands and configuration filenames for their calling CLI while preserving Wrangler-compatible defaults. This prevents cf workflows from presenting Wrangler-branded guidance when an equivalent cf command exists.
Updated dependencies [fcf625d, 091e5ec, 5152bf8, 9f87de8, daae435, 18f061c, 9be5ec7, 61e07fd, cafd3f9, ea64ec4, d232454]:
…latest on npm, even after that version had been deprecated for shipping a bug. Deprecated versions are now never recommended: if the latest release ha…
#15617 93c1069 Thanks @jpatel3! - Stop the update check from recommending deprecated versions
Previously, the "update available" notice shown by wrangler and @cloudflare/vite-plugin always pointed at whichever version was tagged latest on npm, even after that version had been deprecated for shipping a bug. Deprecated versions are now never recommended: if the latest release has been deprecated, the newest non-deprecated stable release below it is suggested instead, or nothing at all if you are already on it.
The check now reads the npm registry directly instead of going through the update-check package, which discarded the deprecation information. The on-disk cache location and one-hour refresh interval are unchanged.
#16003 6947df3 Thanks @oddharsh! - Ship using and await using declarations to the runtime as written
Worker builds no longer lower explicit resource management into helper code, so Workers that use it ship about 1.7 KB less. workerd supports the syntax natively. On Vite 8 the plugin builds Workers at an es2026 target, so Oxc leaves the syntax alone. On Vite 6 and 7, where esbuild has no es2026 target, the Worker environments tell esbuild that using is supported instead. Client builds keep their own targets: the plugin changes only the Worker environments.
#16145 e820406 Thanks @cpojer! - Honor the source-map setting in release builds
Omit the plugin's JavaScript and declaration source maps when building with SOURCEMAPS=false, reducing the installed package size. Normal development builds keep source maps, and application source-map settings are unchanged.
Updated dependencies [2d1d563, 85b14e7, e6f7663, fe607f9, ad7ff45, 8de6b3c, ae29445, 757faa6, cc8e969, 417b186, 93c1069, 6947df3, 82acf3c, 9a58244]:
Set tunnel.allowedMail to a list of email addresses or domain patterns to require email authentication when exposing a Vite development or preview ser
#16030 aa2f9b7 Thanks @edmundhung! - Add email-protected Quick Tunnels to the Cloudflare Vite plugin
Set tunnel.allowedMail to a list of email addresses or domain patterns to require email authentication when exposing a Vite development or preview server through a Quick Tunnel.
Updated dependencies [ 7f700ef , 90e6a1b , 7f57b1c , 6a4b0fe ]:
7f700ef, 90e6a1b, 7f57b1c, 6a4b0fe]:
Updated dependencies [ b8e7cc3 , b00ef4f , 9d7b08e , 464a582 , aee2842 , efd67e6 ]:
Updated dependencies [ b9f1cdc , ddaa558 , 8468487 , a0712e5 , a0712e5 ]:
Updated dependencies [ 91a3606 , 2a15ae2 ]:
91a3606, 2a15ae2]:
Undici 7.29.1 fixes GHSA-3wwx-pv8p-q78v . Update the shared dependency catalog and matching types used by Miniflare and Wrangler so downstream install
#15938 62fd03a Thanks @dieub! - Resolve the affected Undici dependency in new Wrangler and Vite plugin installs
Undici 7.29.1 fixes GHSA-3wwx-pv8p-q78v. Update the shared dependency catalog and matching types used by Miniflare and Wrangler so downstream installs can resolve the patched runtime without an application-level override. A published release is still required for consumers; this changeset does not alter already published package metadata.
Updated dependencies [7bb6eae, 60ccdbd, 62fd03a, 06ed9c8, 86211fe, c2bb4c8, eb1efe0, 485cfb3]:
Experimental cloudflare.config.ts projects must now import defineConfig , bindings, triggers, and related helpers from cf/config . Generated declarati
#15914 7f0734c Thanks @jamesopstad! - Use cf/config for cloudflare.config.ts authoring
Experimental cloudflare.config.ts projects must now import defineConfig, bindings, triggers, and related helpers from cf/config. Generated declarations from Wrangler and the Vite plugin also reference this package, so projects using the experimental configuration flow must add cf as a dependency.
The Vite plugin no longer exports @cloudflare/vite-plugin/experimental-config. wrangler/experimental-config remains available for defineWranglerConfig, but no longer re-exports Cloudflare configuration helpers.
#15878 e7915c1 Thanks @dawNotPoi! - Keep dependency optimization caches stable on the first Vite dev server restart.
The first dev server restart no longer re-optimizes unchanged dependencies, including in projects without Containers. Container images are still cleaned up when the server closes, even after a config reload removes the Cloudflare plugin.
Updated dependencies [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]:
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
When Wrangler's --experimental-new-config flag or Vite's experimental.newConfig option is enabled, inferred configuration and runtime declarations are
#15778 cd7508c Thanks @jamesopstad! - Generate types during development and supported builds with Vite's experimental.newConfig option or Wrangler's --experimental-new-config flag (and --experimental-cf-build-output for builds)
When Wrangler's --experimental-new-config flag or Vite's experimental.newConfig option is enabled, inferred configuration and runtime declarations are now kept in .cloudflare/types/index.d.ts. Vite refreshes them during development and production builds. Wrangler refreshes them during development and when building with both --experimental-new-config and --experimental-cf-build-output. In the experimental wrangler.config.ts format, the types option is now top-level because it applies to both commands.
#15765 1bdb96d Thanks @th0m! - Prepare the required egress sidecar for local Containers without configured images
Wrangler dev and Vite dev/preview now pull the required sidecar for Durable Object-managed Containers that select their application image at start time. Previously, these Containers failed to start unless the sidecar image was already cached in Docker.
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 , 14d946d ]:
The root remains config.json , Worker configs are now worker.config.json , and Container configs are now container.config.json . Resource configs no l
#15713 3c75cad Thanks @jamesopstad! - Identify experimental Build Output resource configs by filename and location
The root remains config.json, Worker configs are now worker.config.json, and Container configs are now container.config.json. Resource configs no longer contain top-level type discriminators, while settings and build context are stored together in the root config.
#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,
},
});#15711 91e2f86 Thanks @ghostwriternr! - Allow local Container images without exposed ports
Wrangler and the Cloudflare Vite plugin no longer reject images that omit Docker EXPOSE metadata. Local Containers can run command-only workloads or serve traffic through workerd without declaring an unused image port.
Updated dependencies [3c75cad, 3c75cad, 91e2f86, c5913a6, 35668d7, 3c75cad, 45b3b81, 8235e6a, 0751490, 43b1f85, 731a2ee]:
Wrangler and the Cloudflare Vite plugin now build Dockerfile-backed Container images when experimental Build Output is enabled. Container configs are
#15609 1f070c8 Thanks @emily-shen! - Build Containers when emitting experimental Build Output
Wrangler and the Cloudflare Vite plugin now build Dockerfile-backed Container images when experimental Build Output is enabled. Container configs are emitted under .cloudflare/output/v0/containers with local image references, while existing registry references pass through unchanged.
#15329 c4c9b75 Thanks @akshitsinha! - Evaluate Flagship flags locally during development
Flagship bindings now use the local Miniflare store by default in Wrangler and the Vite plugin, keeping development offline and isolated from production flags. Set remote: true on a binding to continue using its remote app.
Use wrangler flagship flags pull <APP_ID> to seed the store from a remote app. Flag management commands also accept --local to read and update the local store directly.
#15701 643e5cc Thanks @WillTaylorDev! - Pass Preview intent to defineWorker and upload its resolved configuration
Preview builds now evaluate programmatic Worker configuration with ctx.isPreview set to true and record that intent in Build Output. The shared Preview uploader deploys the resolved bindings and settings while preserving configured Preview base values when it creates a Preview.
The Vite plugin builds or pulls named images from Wrangler configuration and exposes their local tags through ctx.container.images . Pass one of those
#15674 a939a6c Thanks @ghostwriternr! - Support explicit named Container image selection in local development
The Vite plugin builds or pulls named images from Wrangler configuration and exposes their local tags through ctx.container.images. Pass one of those references to ctx.container.start({ image }) to select the image.
This extends the experimental Durable Object-managed Containers interface.
Updated dependencies [ 71b6f10 , ad23e6e , bac0c6a , be2437a , bac0c6a , 6f3d7b5 ]:
The Local Explorer endpoint list is now consistent across the three places it appears: the AGENTS.md template in create-cloudflare , the runtime agent
#14775 1be7b97 Thanks @dario-piotrowicz! - Sync Local Explorer endpoint lists across agent hints
The Local Explorer endpoint list is now consistent across the three places it appears: the AGENTS.md template in create-cloudflare, the runtime agent hint in wrangler dev, and the Vite plugin agent hint. All three now include the observability/clear endpoint, use the canonical /cdn-cgi/local/explorer path, and have cross-reference comments pointing to each other.
#15399 982b806 Thanks @tpmmorris! - Improve over-limit run_worker_first errors when duplicate rules are present
The error now reports distinct and duplicate-entry counts and lists duplicated rules, making it clear when removing redundant entries can bring the configuration within the limit.
Too many `run_worker_first` rules were provided; 105 rules provided (99 distinct, 6 duplicate entries) exceeds max of 100. Note: duplicate entries count towards the route limit. Ensure that no duplicate rules are present in your `run_worker_first` configuration.
The duplicated rules found are:
- "/rule/0"
- "/rule/1"
- "/rule/2"
- "/rule/3"
- "/rule/4"
...and 1 more duplicated rule.
Updated dependencies [1be7b97, b149147, 7db596c, 76c0ce6, a83d7ac, a0856da, e35c4a1, d3565a5, a83d7ac, cb0955f, fa79b26, 16d1310, ca71205, 1015cfb, 982b806, ffabe74, 7db596c, e03822a, a83d7ac, 641df47, c4a6279]:
Miniflare stores local D1, KV, R2, and observability state under .wrangler/state . Those writes were watched as source changes on Linux and Windows, w
#15574 164e4fb Thanks @RealBhupesh! - Ignore .wrangler persistence writes in Vite's file watcher
Miniflare stores local D1, KV, R2, and observability state under .wrangler/state. Those writes were watched as source changes on Linux and Windows, which fired every plugin hotUpdate hook and could make page loads take seconds. The plugin now ignores **/.wrangler/** while preserving any server.watch.ignored patterns already set by the user.
Updated dependencies [8997652]:
One column per month.