Sourced from @​cloudflare/vite-plugin's releases.

@​cloudflare/vite-plugin@​1.11.0

Minor Changes

• #9914 a24c9d8 Thanks @​petebacondarwin! - Add support for loading local dev vars from .env files

  If there are no .dev.vars or .dev.vars.<environment> files, when running Wrangler or the Vite plugin in local development mode, they will now try to load additional local dev vars from .env, .env.local, .env.<environment> and .env.<environment>.local files.

  These loaded vars are only for local development and have no effect in production to the vars in a deployed Worker. Wrangler and Vite will continue to load .env files in order to configure themselves as a tool.

  Further details:

  • In vite build the local vars will be computed and stored in a .dev.vars file next to the compiled Worker code, so that vite preview can use them.
  • The wrangler types command will similarly read the .env files (if no .dev.vars files) in order to generate the Env interface.
  • If the CLOUDFLARE_LOAD_DEV_VARS_FROM_DOT_ENV environment variable is "false" then local dev variables will not be loaded from .env files.
  • If the CLOUDFLARE_INCLUDE_PROCESS_ENV environment variable is "true" then all the environment variables found on process.env will be included as local dev vars.
  • Wrangler (but not Vite plugin) also now supports the --env-file=<path/to/dotenv/file> global CLI option. This affects both loading .env to configure Wrangler the tool as well as loading local dev vars.

Patch Changes

• #10071 4a4049c Thanks @​CarmenPopoviciu! - feat(vite-plugin): Add Containers-related info logs

  Add logs, when a Worker has Containers configured, providing information about container build status, and how to rebuild containers during local development.

• Updated dependencies [9b61f44, 0f7820e, a24c9d8, e9bb8d3]:

  • miniflare@4.20250730.0
  • wrangler@4.27.0

@​cloudflare/vite-plugin@​1.10.2

Patch Changes

• #10048 dbdbb8c Thanks @​vicb! - pass the compatibility date and flags to the unenv preset

• #10096 687655f Thanks @​vicb! - bump unenv to 2.0.0-rc.19

• #10040 26ffa05 Thanks @​CarmenPopoviciu! - feat(vite-plugin): Add containers support in vite preview

  Adds support for Cloudflare Containers in vite preview. Please note that at the time of this PR a container image can only specify the path to a Dockerfile. Support for registry links will be added in a later version.

• #10054 bc910f9 Thanks @​eltigerchino! - Add worker to the default conditions for resolving packages

  This makes it consistent with the conditions used when bundling Worker code with Wrangler.

• #10061 f8a80a8 Thanks @​emily-shen! - fix: properly set the socket path that the container engine is listening on.

  Previously, this was only picking up the value set in Wrangler config under dev.containerEngine, but this value can also be set from env vars or automatically read from the current docker context.

• Updated dependencies [82a5b2e, f8f7352, 2df1d06, f8a80a8, dbdbb8c, 5991a9c, 687655f, 755a249]:

  • miniflare@4.20250726.0

... (truncated)

Sourced from @​cloudflare/vite-plugin's changelog.

1.11.0

Minor Changes

• #9914 a24c9d8 Thanks @​petebacondarwin! - Add support for loading local dev vars from .env files

  If there are no .dev.vars or .dev.vars.<environment> files, when running Wrangler or the Vite plugin in local development mode, they will now try to load additional local dev vars from .env, .env.local, .env.<environment> and .env.<environment>.local files.

  These loaded vars are only for local development and have no effect in production to the vars in a deployed Worker. Wrangler and Vite will continue to load .env files in order to configure themselves as a tool.

  Further details:

  • In vite build the local vars will be computed and stored in a .dev.vars file next to the compiled Worker code, so that vite preview can use them.
  • The wrangler types command will similarly read the .env files (if no .dev.vars files) in order to generate the Env interface.
  • If the CLOUDFLARE_LOAD_DEV_VARS_FROM_DOT_ENV environment variable is "false" then local dev variables will not be loaded from .env files.
  • If the CLOUDFLARE_INCLUDE_PROCESS_ENV environment variable is "true" then all the environment variables found on process.env will be included as local dev vars.
  • Wrangler (but not Vite plugin) also now supports the --env-file=<path/to/dotenv/file> global CLI option. This affects both loading .env to configure Wrangler the tool as well as loading local dev vars.

Patch Changes

• #10071 4a4049c Thanks @​CarmenPopoviciu! - feat(vite-plugin): Add Containers-related info logs

  Add logs, when a Worker has Containers configured, providing information about container build status, and how to rebuild containers during local development.

• Updated dependencies [9b61f44, 0f7820e, a24c9d8, e9bb8d3]:

  • miniflare@4.20250730.0
  • wrangler@4.27.0

1.10.2

Patch Changes

• #10048 dbdbb8c Thanks @​vicb! - pass the compatibility date and flags to the unenv preset

• #10096 687655f Thanks @​vicb! - bump unenv to 2.0.0-rc.19

• #10040 26ffa05 Thanks @​CarmenPopoviciu! - feat(vite-plugin): Add containers support in vite preview

  Adds support for Cloudflare Containers in vite preview. Please note that at the time of this PR a container image can only specify the path to a Dockerfile. Support for registry links will be added in a later version.

• #10054 bc910f9 Thanks @​eltigerchino! - Add worker to the default conditions for resolving packages

  This makes it consistent with the conditions used when bundling Worker code with Wrangler.

• #10061 f8a80a8 Thanks @​emily-shen! - fix: properly set the socket path that the container engine is listening on.

  Previously, this was only picking up the value set in Wrangler config under dev.containerEngine, but this value can also be set from env vars or automatically read from the current docker context.

... (truncated)

• 463bfd2 Version Packages (#10116)
• c307b08 refactor: remove redundant watcher.close() from vite-plugin (#10138)
• 4c5f9c5 refactor: remove abort controller from vite-plugin (#10137)
• cbaaccd refactor: remove unnecessary miniflare.ready awaits (#10135)
• a24c9d8 Add support for reading .env files as runtime vars in local development (#9...
• 9b61f44 Bump the workerd-and-workers-types group with 2 updates (#10129)
• 4a4049c feat(vite-plugin): Add Containers-related info logs (#10071)
• c070c77 Version Packages (#10059)
• 687655f bump unenv to 2.0.0-rc.19 (#10096)
• 2df1d06 Bump the workerd-and-workers-types group with 2 updates (#9968)
• Additional commits viewable in compare view

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)