Skip to content

chore(deps): update dependency @cloudflare/vite-plugin to v1.66.0 - #337

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/cloudflare-vite-plugin-1.x-lockfile
Open

renovate[bot] wants to merge 1 commit into
mainfrom
renovate/cloudflare-vite-plugin-1.x-lockfile

Conversation

@renovate

@renovate renovate Bot commented Nov 4, 2026 •

Copy link
Copy Markdown
Contributor

Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
@cloudflare/vite-plugin (source) 1.31.1 → 1.66.0 age confidence

Release Notes

cloudflare/workers-sdk (@​cloudflare/vite-plugin)

v1.66.0

Compare Source

Minor Changes
  • #​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.

Patch Changes
  • #​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.

v1.65.0

Compare Source

Minor Changes
  • #​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.

Patch Changes
  • #​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.

v1.64.0

Compare Source

Minor Changes
  • #​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.

Patch Changes

v1.63.2

Compare Source

Patch Changes
  • #​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]:

v1.63.1

Compare Source

Patch Changes
  • #​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]:

v1.63.0

Compare Source

Minor Changes
  • #​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.

Patch Changes

v1.62.5

Compare Source

Patch Changes

v1.62.4

Compare Source

Patch Changes

v1.62.3

Compare Source

Patch Changes

v1.62.2

Compare Source

Patch Changes

v1.62.1

Compare Source

Patch Changes

v1.62.0

Compare Source

Minor Changes
  • #​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.

Patch Changes
  • #​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]:

    • wrangler@​4.143.0

v1.61.0

Compare Source

Minor Changes
  • #​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.

Patch Changes

v1.60.2

Compare Source

Patch Changes

v1.60.1

Compare Source

Patch Changes

v1.60.0

Compare Source

Minor Changes
  • #​15648 52c0e9f Thanks @​tpmmorris! - Advertise Local Explorer scheduled invocations to headless agents

    The Vite plugin's Local Explorer hint now documents how to invoke a Worker's scheduled handler and points agents to the OpenAPI schema for the complete request contract.

Patch Changes

v1.59.0

Compare Source

Minor Changes
  • #​15817 6e77c53 Thanks @​jamesopstad! - Allow framework commands to produce Preview Build Output with the experimental config

    When cf previews deploy invokes a framework build command, Preview intent is now preserved. Function-based cloudflare.config.ts files receive isPreview: true, and generated Build Output is marked as a Preview build.

Patch Changes

v1.58.0

Compare Source

Minor Changes
  • #​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.

Patch Changes
  • #​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]:

    • wrangler@​4.137.0

v1.57.3

Compare Source

Patch Changes

v1.57.2

Compare Source

Patch Changes

v1.57.1

Compare Source

Patch Changes

v1.57.0

Compare Source

Minor Changes
  • #​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,
    	},
    });
Patch Changes

v1.56.0

Compare Source

Minor Changes
  • #​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

[!IMPORTANT]
✂ PR body was truncated to here.


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@coderabbitai

coderabbitai Bot commented Nov 4, 2026 •

Copy link
Copy Markdown
Contributor

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

Run configuration

  • Source mode: Auto
  • Repository: g-kari/tools
  • Branch: main
  • File: .coderabbit.yaml
  • Commit: d7464e1
  • Layers: Repository YAML
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: c38d750a-b971-423f-a170-06d719250e78

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • Trigger review
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

@renovate
renovate Bot force-pushed the renovate/cloudflare-vite-plugin-1.x-lockfile branch 4 times, most recently from 6f987fa to a37422f Compare November 5, 2026 07:41
@renovate renovate Bot changed the title chore(deps): update dependency @cloudflare/vite-plugin to v1.67.0 chore(deps): update dependency @cloudflare/vite-plugin to v1.64.0 Nov 5, 2026
@renovate
renovate Bot force-pushed the renovate/cloudflare-vite-plugin-1.x-lockfile branch 10 times, most recently from 9e94f3e to 1b78d48 Compare November 6, 2026 08:12
@renovate renovate Bot changed the title chore(deps): update dependency @cloudflare/vite-plugin to v1.64.0 chore(deps): update dependency @cloudflare/vite-plugin to v1.65.0 Nov 6, 2026
@renovate
renovate Bot force-pushed the renovate/cloudflare-vite-plugin-1.x-lockfile branch 5 times, most recently from ce15de0 to 8f363d9 Compare November 12, 2026 17:49
@renovate renovate Bot changed the title chore(deps): update dependency @cloudflare/vite-plugin to v1.65.0 chore(deps): update dependency @cloudflare/vite-plugin to v1.66.0 Nov 12, 2026
@renovate
renovate Bot force-pushed the renovate/cloudflare-vite-plugin-1.x-lockfile branch from 8f363d9 to 0412fa1 Compare November 13, 2026 01:49
@renovate
renovate Bot force-pushed the renovate/cloudflare-vite-plugin-1.x-lockfile branch from 0412fa1 to d346ed2 Compare November 13, 2026 01:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants