Repository navigation
[vite-plugin] Version v1 maintenance release - #16544
Conversation
commit: |
|
✅ Approved — This is a routine release pull request: the minor version bump and the changelog entries match the changesets it consumes, and no issues were found. The decision is advisory: this comment never approves, blocks or requests changes on the pull request. ✅ All checks passed🚀 Release: ✅ LGTMRisk: Low. This is a standard Changesets version bump with a matching changelog. 🔒 Security: ✅ LGTMThis pull request only changes release metadata. There are no security concerns. 📖 AGENTS.md: ✅ LGTMNo AGENTS.md concerns. 📋 Code Quality: ✅ LGTMThe version bump from 1.65.0 to 1.66.0 in ⚡ Performance: ✅ LGTMThis pull request has no runtime code changes. 📝 Documentation: ✅ LGTMThe CHANGELOG entries for 1.66.0 match the changeset files this pull request removes. Reviewed commit: |
94f848f to
3525d70
Compare
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to vite-plugin-v1, this PR will be updated.
Releases
@cloudflare/vite-plugin@1.66.0
Minor Changes
#16539
046db08Thanks @petebacondarwin! - Update the development registry to use the canonical Cloudflare pathUpgrade Miniflare to 5.20261023.1-beta and Wrangler to 4.154.0. Vite plugin v1 now uses
CLOUDFLARE_DEV_REGISTRY_PATHor<Cloudflare config directory>/dev-registry/v5for Worker discovery.MINIFLARE_REGISTRY_PATHis no longer read. When mixing Vite and Wrangler development sessions, set the sameCLOUDFLARE_DEV_REGISTRY_PATHfor both because Wrangler retains its legacy default.#16407
9ec1101Thanks @petebacondarwin! - Support remote Hyperdrive bindings in Vite plugin v1 development and previewSet
remote: trueon a Hyperdrive binding inwrangler.jsoncto 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.Patch Changes
#16542
ef573d4Thanks @petebacondarwin! - Preserve machine-readable error properties from remote bindingsEnable 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
codeandnumericCodeso Worker code can handle them without parsing error messages.#16480
ccaa34aThanks @petebacondarwin! - Prevent malformed token-exchange responses from crashing remote binding startupUpdate 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
6f2eda1Thanks @petebacondarwin! - Update the retained asset configuration validator to Zod 4.6.6The Vite plugin validates
_headersand_redirectsthrough its private workers-shared package. Update that bundled copy to address excessive memory consumption when validating oversized collections.#16444
79678c4Thanks @petebacondarwin! - Update Vite plugin v1 to the October 23 Workers runtimeUse Miniflare
5.20261023.0-betaand the matching Wrangler release for local development and preview. Align bundled helpers and Workers types with this runtime, and use2026-10-23as 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
1d5354bThanks @petebacondarwin! - Treatcloudflare:durable-objectsas a built-in runtime moduleWorkers can import
retryable()fromcloudflare:durable-objectsto mark Durable Object methods as safe to retry. The plugin now leaves that import for the runtime to resolve, as it does forcloudflare:workers, instead of trying to resolve it as a package.#16493
4ce6176Thanks @petebacondarwin! - Preserve a Worker response'sstatusTextin Vite dev and previewResponses such as
new Response(body, { status: 231, statusText: "Custom" })now reach the browser as231 Custominstead of231 unknown. Empty status text is also preserved over HTTP/1.x.#16501
109844eThanks @petebacondarwin! - Preserve separateSet-Cookierequest headers in Vite dev and previewWorkers now receive each incoming
Set-Cookievalue separately for HTTP requests and WebSocket upgrades, including values with commas in anExpiresdate. Previously, multiple values could be combined into one header.#16503
ca116f9Thanks @petebacondarwin! - Fix a dev server failing to start when an earlier dev server in the same process had different Worker exportsThe 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 undefinedfor a Durable Object the earlier server's Worker did not export.#16504
436fa9aThanks @petebacondarwin! - Fix Vite DevTools WebSocket connections closing unexpectedlyLeave upgrades at
/__devtools/__wsto Vite DevTools instead of forwarding them to the Worker. Sandbox preview requests continue to reach the Worker.