npm / @cloudflare/vite-plugin
@cloudflare/vite-plugin
What changed in @cloudflare/vite-plugin 1, from its official release notes, upgrade guides and advisories. Sources checked 2026-10-24.
3 breaking1 behavior and defaults4 fixes and other
See which of these apply to your code, ranked, in your agent:
npx @unstale/cli init@cloudflare/vite-plugin 18 changes
Breaking changes 3
Vite plugin v1 no longer supports this option; it supports Wrangler configuration files only. Projects using cloudflare.config.ts should upgrade to Vite plugin v2 beta.
Starting remote bindings under Bun now fails with an actionable error instead of hanging. Use Node.js or disable remote bindings to continue local development.
Worker builds now generate source maps by default. Set build.sourcemap: false or upload_source_maps: false to opt out; client builds are unchanged.
Behavior and default changes 1
Shared helpers render commands and configuration filenames for their calling CLI, preventing workflows from presenting Wrangler-branded guidance when an equivalent command exists.
Fixes and other changes 4
The local Workers runtime includes a fix for nested asset paths during local development on Windows.
Transient failures during remote preview token refresh are retried so long-running remote development sessions recover after a network outage.
The local Workflow runtime queues persistence deletion with instance recreation, preventing storage cleanup from racing reuse of the same Workflow instance ID.
The local runtime disposes Workflow step results and introspection modifiers after use, preventing undisposed RPC warnings and cancelled local Workflow requests.