deps: update dependency @cloudflare/vite-plugin to v1.12.1 - autoclosed#96
Closed
renovate[bot] wants to merge 1 commit intomainfrom
Closed
deps: update dependency @cloudflare/vite-plugin to v1.12.1 - autoclosed#96renovate[bot] wants to merge 1 commit intomainfrom
renovate[bot] wants to merge 1 commit intomainfrom
Conversation
Contributor
Author
|
|
الوو السلام عليك ورحمة الله وبركاته **** |
|
الوو السلام عليك ورحمة الله وبركاته |
d3ee696 to
bf44982
Compare
auto-merge was automatically disabled
October 11, 2025 21:08
Pull request was closed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
1.0.12->1.12.1Release Notes
cloudflare/workers-sdk (@cloudflare/vite-plugin)
v1.12.1Compare Source
Patch Changes
#10482
aec77ccThanks @jamesopstad! - Pass thecompatibility_dateandcompatibility_flagsto theunenvpreset. This enables support for thenode:httpandnode:httpsmodules.Updated dependencies [
76d9aa2,85be2b6,452ad0b,7c339ae]:v1.12.0Compare Source
Minor Changes
7b05c8eThanks @CarmenPopoviciu! - Add support for testing Cron Triggers and Email Workers invite devandvite preview.Patch Changes
#10422
88fd2f9Thanks @jamesopstad! - Statically replace the value ofprocess.env.NODE_ENVin development when thenodejs_compatcompatibility flag is enabled.Previously, this was replaced at build time when
nodejs_compatwas enabled and at dev and build time whennodejs_compatwas not enabled.#10065
3024ec1Thanks @MichaelDeBoey! - Update@mjackson/node-fetch-serverto@remix-run/node-fetch-serverUpdated dependencies [
c4fd176,19e2aab,c4fd176,e81c2cf]:v1.11.7Compare Source
Patch Changes
718fffcThanks @jamesopstad! - Exclude Cloudflare built-ins from client dependency optimization.Some frameworks allow users to mix client and server code in the same file and then extract the server code.
As the dependency optimization may happen before the server code is extracted, we now exclude Cloudflare built-ins from client optimization.
d304055,f534c0d,da40571,0a96e69,f9f7519,4728c68]:v1.11.6Compare Source
Patch Changes
565c3a3,ddadb93,9b09751,cadf19a,20520fa,875197a]:v1.11.5Compare Source
Patch Changes
76a6701,d54d8b7,979984b,80e964c,a5a1426,ae0c806,0c04da9,b524a6f,eb32a3a,4288a61]:v1.11.4Compare Source
Patch Changes
5020694]:v1.11.3Compare Source
Patch Changes
e7cae16,3b6ab8a,c58a05c,42aafa3,70bd966,d391076,422ae22,1479fd0,80960b9,05c5b28,5d5ecd5,e3d9703,bd8223d,e7cae16,d481901,9aad334,28494f4,8cf47f9]:v1.11.2Compare Source
Patch Changes
773cca3,773cca3,2e8eb24,93c4c26,48853a6,2e8eb24]:v1.11.1Compare Source
Patch Changes
#9993
9901788Thanks @jamesopstad! - Fix issue that resulted inA hanging Promise was cancelederrors when developing large applications.We now handle requests for modules in a Durable Object so that they can be shared across invocations.
Additionally, using
import.meta.hot.sendwithin the context of a request is now supported.#9556
8ba7736Thanks @edmundhung! - fix: cross-process service bindings no longer skip static asset serving#10099
360004dThanks @emily-shen! - fix: move local dev container cleanup to process exit hook. This should ensure containers are cleaned up even when Wrangler is shut down programatically.#10173
4e62cd8Thanks @jamesopstad! - Ensure that headers set viaserver.headersin the Vite config are added to HTML asset responses in development.Updated dependencies [
6b9cd5b,b4d1373,631f26d,d6ecd05,b4d1373,360004d,e82aa19,dae1377,8ba7736,1655bec,354a001,5c3b83f,502a8e0,07c8611,7e204a9,3f83ac1]:v1.11.0Compare Source
Minor Changes
#9914
a24c9d8Thanks @petebacondarwin! - Add support for loading local dev vars from .env filesIf there are no
.dev.varsor.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>.localfiles.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
.envfiles in order to configure themselves as a tool.Further details:
vite buildthe local vars will be computed and stored in a.dev.varsfile next to the compiled Worker code, so thatvite previewcan use them.wrangler typescommand will similarly read the.envfiles (if no.dev.varsfiles) in order to generate theEnvinterface.CLOUDFLARE_LOAD_DEV_VARS_FROM_DOT_ENVenvironment variable is"false"then local dev variables will not be loaded from.envfiles.CLOUDFLARE_INCLUDE_PROCESS_ENVenvironment variable is"true"then all the environment variables found onprocess.envwill be included as local dev vars.--env-file=<path/to/dotenv/file>global CLI option. This affects both loading.envto configure Wrangler the tool as well as loading local dev vars.Patch Changes
#10071
4a4049cThanks @CarmenPopoviciu! - feat(vite-plugin): Add Containers-related info logsAdd 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]:v1.10.2Compare Source
Patch Changes
#10048
dbdbb8cThanks @vicb! - pass the compatibility date and flags to the unenv preset#10096
687655fThanks @vicb! - bump unenv to 2.0.0-rc.19#10040
26ffa05Thanks @CarmenPopoviciu! - feat(vite-plugin): Add containers support invite previewAdds 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 aDockerfile. Support for registry links will be added in a later version.#10054
bc910f9Thanks @eltigerchino! - Addworkerto the default conditions for resolving packagesThis makes it consistent with the conditions used when bundling Worker code with Wrangler.
#10061
f8a80a8Thanks @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]:v1.10.1Compare Source
Patch Changes
#10031
823cba8Thanks @vicb! - wrangler and vite-plugin now depend upon the latest version of unenv-presetUpdated dependencies [
c5b291d,3d4f946,7245101,823cba8,19794bf,154acf7,19794bf,7fb0bfd,059a39e]:v1.10.0Compare Source
Minor Changes
#10001
5796ca9Thanks @jamesopstad! - We now automatically inject the following HMR code into your Worker entry file:This prevents file changes from invalidating the full module graph and improves HMR performance in development.
Patch Changes
#10038
a355327Thanks @emily-shen! - Resolvecontainers.image(if it is a path to a Dockerfile) to an absolute path in the deploy config.#9891
dd416e9Thanks @hi-ogawa! - setbuild.rollupOptions.platform: "neutral"on rolldown-vite to prevent Rolldown'snode:modulebasedrequirepolyfill from breaking the build.#9819
0c4008cThanks @CarmenPopoviciu! - feat(vite-plugin): Add containers support invite devAdds support for Cloudflare Containers in
vite dev. Please note that at the time of this PR a container image can only specify the path to aDockerfile. Support for registry links will be added in a later version, as will containers support invite preview.Updated dependencies [
189fe23,c02b067,7e5585d,b0217f9,e87198a,ad02ad3,0c4008c]:v1.9.6Compare Source
Patch Changes
6cc24c0,9f0c175]:v1.9.5Compare Source
Patch Changes
#9847
14ce577Thanks @penalosa! - Upgrade UndiciUpdated dependencies [
ac08e68,4ba9f25,17b1e5a,3bb69fa,274a826,77d1cb2,d6a1b9b,e2672c5,a5d7b35,5b0fc9e,bf4c9ab,14ce577,f73da0d]:v1.9.4Compare Source
Patch Changes
c01c4ee,3743896]:v1.9.3Compare Source
Patch Changes
80cc834]:v1.9.2Compare Source
Patch Changes
05adc61,bb09e50,25dbe54,3bdec6b]:v1.9.1Compare Source
Patch Changes
#9856
8bf60a7Thanks @jamesopstad! - Set the Wrangler peer dependency to the same version as the direct dependency. This fixes an issue where older versions of Wrangler could override the version used by the plugin.Updated dependencies [
1b3a2b7,dbfa4ef,ba69586,1a75f85,395f36d,6f344bf,fc29c31,45497ab,a447d67,7c55f9e,49c85c5,0bb619a,a1181bf,a727db3,1358034,1a58bc3,7e3aa1b]:v1.9.0Compare Source
Minor Changes
#9535
56dc5c4Thanks @penalosa! - In 2023 we announced breakpoint debugging support for Workers, which meant that you could easily debug your Worker code in Wrangler's built-in devtools (accessible via the[d]hotkey) as well as multiple other devtools clients, including VSCode. For most developers, breakpoint debugging via VSCode is the most natural flow, but until now it's required manually configuring alaunch.jsonfile, runningwrangler dev, and connecting via VSCode's built-in debugger.Now, using VSCode's built-in JavaScript Debug Terminals, there are just two steps: open a JS debug terminal and run
vite devorvite preview. VSCode will automatically connect to your running Worker (even if you're running multiple Workers at once!) and start a debugging session.#9803
df04528Thanks @penalosa! - Support Workers Analytics Engine & Rate Limiting bindingsPatch Changes
56dc5c4,8acaf43,4309bb3,d11288a]:v1.8.0Compare Source
Minor Changes
#9773
45e97e8Thanks @jamesopstad! - Vite 7 is now supported and included as a peer dependency. We continue to also support Vite 6.#9753
67130b3Thanks @jamesopstad! - AllowoptimizeDeps.excludeto be specified for Worker environments. This enables other plugins to exclude dependencies from optimization that require access to virtual modules. Note that excluded dependencies must be ESM.v1.7.5Compare Source
Patch Changes
9c938c2,fb83341,b137a6f,29e911a,f3c5791]:v1.7.4Compare Source
Patch Changes
086e29d,d5edf52,bfb791e,24b2c66,3f478af,5162c51]:v1.7.3Compare Source
Patch Changes
#9647
6c6afbdThanks @jamesopstad! - In Vite 7, theapplyToEnvironmenthook is called in preview mode. This is now accounted for to ensure compatibility.Updated dependencies [
ffa742f,8a60fe7,c489a44,8a60fe7,17d23d8]:v1.7.2Compare Source
Patch Changes
#9586
d1d34feThanks @penalosa! - Remove the Mixed Mode naming in favour of "remote bindings"/"remote proxy"Updated dependencies [
08be3ed,d1d34fe]:v1.7.1Compare Source
Patch Changes
828b7df,b1c9139,92f12f4,2671e77]:v1.7.0Compare Source
Minor Changes
#9575
5601fc3Thanks @jamesopstad! - Supportrun_worker_first.run_worker_firsthas been expanded to accept an array of routes that should go directly to your Worker. Additionally, routes can be omitted by adding a!prefix. These negative routes will be treated as assets.This is a new way to define routing explicitly and, when provided, overrides the implicit routing behavior.
{ "assets": { "not_found_handling": "single-page-application", "run_worker_first": [ "/api/*", // These routes go directly to the Worker "!/api/docs/*", // These routes are still treated as assets ], }, }The previous behavior of setting
"run_worker_first": trueto always invoke your Worker is also now supported.Patch Changes
#9583
70ba9fbThanks @edmundhung! - fix: avoid crashing on unknown service bindings at startupWith Dev Registry support, the plugin no longer throws an assertion error during startup when a service binding references a named entrypoint from an unknown worker. Instead, an appropriate runtime error will be returned if the worker cannot be resolved.
#9548
0174e39Thanks @jamesopstad! - Enable HTML handling for HTML files in the public directory.It is generally encouraged to use HTML files as entry points in Vite so that their dependencies are bundled. However, if you have plain HTML files that should simply be copied to the root of the output directory as-is, you can place these in the public directory and they will now work as expected in dev.
#9566
521eeb9Thanks @vicb! - Bump@cloudflare/unenv-presetto 2.3.3#9581
6bc0a2fThanks @petebacondarwin! - fix: ensure that globals are polyfilled before every import#9536
3b61c41Thanks @dario-piotrowicz! - performance improvement: restart a mixed mode session only if the worker's remote bindings have changedUpdated dependencies [
3b61c41,bd528d5,2177fb4,1d3293f,04f9164,36113c2,49f5ac7,cf33417,521eeb9,02e2c1e,02e2c1e,3b61c41,e16fcc7,c117904,fae8c02]:v1.6.0Compare Source
Minor Changes
#9510
590d69bThanks @jamesopstad! - Enhanced build support for Workers with assets.Assets that are imported in the entry Worker are now automatically moved to the client build output. This enables importing assets in your Worker and accessing them via the assets binding. See Static Asset Handling to find out about all the ways you can import assets in Vite.
Additionally, a broader range of build scenarios are now supported. These are:
publicdirectory assetspublicdirectory assetsPatch Changes
#9513
0e50072Thanks @jamesopstad! - Ensure that .dev.vars files cannot be accessed via the dev server or preview server.Updated dependencies [
1914b87,931f467,95eb47d,80b8bd9,95eb47d,9e4cd16,92305af,0b2ba45]:v1.5.1Compare Source
Patch Changes
4ab5a40,485cd08,66edd2f,d1a1787,e3b3ef5,1f84092,3261957]:v1.5.0Compare Source
Minor Changes
2cef3abThanks @jamesopstad! - Support loading all asset types via assets binding. Previously only HTML assets could be loaded via the assets binding. The binding now integrates with Vite's internal middleware to load all asset types.Patch Changes
db2cdc6]:v1.4.0Compare Source
Minor Changes
#9173
fac2f9dThanks @edmundhung! - Enable cross-process Service bindings and Tail workers with the Dev RegistryYou can now run workers in separate dev sessions—whether
vite devorwrangler dev—and they’ll automatically discover and connect to each other:Worker A
Worker B
Then run both workers in separate terminals:
v1.3.1Compare Source
Patch Changes
#9387
e39a45fThanks @jamesopstad! - Prevent leaking Miniflare server logs. Logs that were previously filtered were leaking as they were changed to include colors. We now override the new MiniflareLog.logReadymethod with a noop rather than filtering the logs.#9308 [
d3a6eb3](https://redirect.githConfiguration
📅 Schedule: Branch creation - "after 10:00 before 18:00 every weekday" in timezone Asia/Tokyo, Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Never, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.