chore(deps): update dependency @cloudflare/vite-plugin to v1.33.2#8548
Open
renovate[bot] wants to merge 1 commit intolatestfrom
Open
chore(deps): update dependency @cloudflare/vite-plugin to v1.33.2#8548renovate[bot] wants to merge 1 commit intolatestfrom
renovate[bot] wants to merge 1 commit intolatestfrom
Conversation
4dcacb9 to
1dacacb
Compare
1dacacb to
724bb7d
Compare
724bb7d to
fcd45dc
Compare
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.29.1→1.33.2Release Notes
cloudflare/workers-sdk (@cloudflare/vite-plugin)
v1.33.2Patch Changes
#13636
1d54fb7Thanks @edmundhung! - Stop denyingvite.config.*files from Vite dev server accessThis allows projects to access
vite.config.*files during development when needed.#13653
48c61b6Thanks @jamesopstad! - Use the date that the plugin is built as the default compatibility date.When no compatibility date was set by the user, the plugin was falling back to the current date. This meant that the date could get ahead of the latest date supported by the installed version of workerd. We now populate the default compatibility date when the plugin is built. This means that it is updated with each release but then stays fixed.
#13634
f3cb2b2Thanks @jamesopstad! - Simplify/cdn-cgi/handlingWe now only add special handling for
/cdn-cgi/handler/*routes, so that trigger handlers are invoked on the User Worker.#13611
6e99febThanks @smaldd14! - Support Cloudflare-managed registry images in Vite plugin local devPreviously, using a
registry.cloudflare.comimage in acontainersbinding would crashvite devwith an unsupported error. The Vite plugin now configures the Cloudflare API client usingCLOUDFLARE_API_TOKENandCLOUDFLARE_ACCOUNT_IDbefore pulling container images, matching the behavior ofwrangler dev.Updated dependencies [
5a2968a,5680287,3494842,7d728fb,df9319d,d5e3c57,3ceeec3,7567ef7,0a95061,2831b54,7fc50c1,377715d]:v1.33.1Compare Source
Patch Changes
8fec8b8,2f3d7b9,a610749]:v1.33.0Compare Source
Minor Changes
50bf819Thanks @penalosa! - Useworkerd's debug port to power cross-process service bindings, Durable Objects, and tail workers via the dev registry. This enables Durable Object RPC via the dev registry, and is an overall stability improvement.Patch Changes
#13587
fdb32caThanks @vimtor! - Allow internal Wrangler config path overrides via env@cloudflare/vite-pluginnow checksCLOUDFLARE_VITE_WRANGLER_CONFIG_PATHwhenconfigPathis not set explicitly. This lets integrators provide generated Wrangler configs outside the project root without requiring users to threadconfigPaththrough framework config.Updated dependencies [
05f4443,4a9ba90,d8c895a,b35617b,7dc0433,8ca78bb,b6e1351,d8314c6,b35617b,7f50300,4fda685,be5e6a0,e456952,59eec63,50bf819,cc1413a,d0a9d1c,4eb1da9,8ca78bb,266c418,6d887db,5716d69]:v1.32.3Compare Source
Patch Changes
#13427
c4deb1dThanks @edmundhung! - Harden file serving for Vite devThe Vite plugin now includes Wrangler config files, Vite config files, and
.wranglerstate files inserver.fs.denyso they cannot be fetched directly from the Vite dev server.Updated dependencies [
854d66c,6f63eaa,aef9825,eaaa728,58292f6,5e5bbc1,d5ff5a4,07a918c,89c7829,60565dd,6cbcdeb,90aee27]:v1.32.2Compare Source
Patch Changes
9b2b6ba]:v1.32.1Compare Source
Patch Changes
6b11b07,dd4e888]:v1.32.0Compare Source
Minor Changes
#13137
1313275Thanks @emily-shen! - Addehotkey to open local explorer during devPress
eduringvite devto open the local explorer UI at/cdn-cgi/explorer, which allows you to inspect the state of your D1, R2, KV, DO and Workflow bindings.Patch Changes
5338bb6,79fd529,28bc2be,4fd138b,bafb96b,c50cb5b,2589395,525a46b,5eff8c1,1313275]:v1.31.2Compare Source
Patch Changes
42c7ef0,c510494,8b71eca,a42e0e8,7ca6f6e]:v1.31.1Compare Source
Patch Changes
a3e3b57,7d318e1,fa6d84f,96ee5d4,7d318e1,7a60d4b,78cbe37,6fa5dfd]:v1.31.0Compare Source
Minor Changes
#13011
b9b7e9dThanks @ruifigueira! - Add experimental headful browser rendering support for local developmentWhen developing locally with the Browser Rendering API, you can enable headful (visible) mode via the
X_BROWSER_HEADFULenvironment variable to see the browser while debugging:Note: when using
@cloudflare/playwright, two Chrome windows may appear — the initial blank page and the one created bybrowser.newPage(). This is expected behavior due to how Playwright handles browser contexts via CDP.#13051
d5bffdeThanks @dario-piotrowicz! - UpdategetLocalWorkerdCompatibilityDateto return today's dateThe re-exported
getLocalWorkerdCompatibilityDatefunction from@cloudflare/vite-pluginpreviously resolved the workerd compatibility date by traversing the localminiflareinstallation, which was unreliable in some package manager setups. It now simply returns today's date. The function is also marked as deprecated — callers should just use today's date instead, for example like so:new Date().toISOString().slice(0, 10)Patch Changes
#13125
f76652cThanks @kayluhb! - Fix SyntaxError when SSR-transformed module ends with a single-line commentWhen module code ends with a
//comment (e.g.//# sourceMappingURL=...preserved by vite-plus), the closing}of the async wrapper inrunInlinedModulewas absorbed into the comment, causingSyntaxError: Unexpected end of input. Adding a newline before the closing brace prevents this.#13188
110002cThanks @shulaoda! - Normalize the return value ofgetAssetsDirectory()withvite.normalizePath()to ensureassets.directoryin the outputwrangler.jsonalways uses forward slashesUpdated dependencies [
9c4035b,5d29055,fb67a18,d5bffde,ab44870,48d83ca,b2f53ea,b9b7e9d,14e72eb,4dc94fd,b2f53ea,d5bffde,48d83ca]:v1.30.3Compare Source
Patch Changes
#13111
f214760Thanks @dependabot! - Add missingconnectkey toWorkerEntrypointandDurableObjectkey lists in the runner workerThe
connectmethod was added to theWorkerEntrypointandDurableObjecttypes in workerd 1.20260329.1 but was missing from theWORKER_ENTRYPOINT_KEYSandDURABLE_OBJECT_KEYSarrays used for RPC property access in the Vite plugin runner worker. This caused the compile-time exhaustiveness check to fail with the updated workers-types.Updated dependencies [
ffbc268,9eff028,ed20a9b,f214760,746858a,9aad27f,1fc5518,b539dc7,9282493,a532eea,cd0e971,d4c6158,2565b1d]:v1.30.2Compare Source
Patch Changes
#12953
80b093eThanks @jamesopstad! - FixCannot perform I/O on behalf of a different requesterrors for deferred dynamic importsConcurrent requests that loaded the same dynamic import were previously sharing the same promise to resolve it in a Worker context. We now ensure that all imports execute within a Durable Object's IoContext before the result is returned to the Worker.
Updated dependencies [
eeaa473,9fcdfca,bc24ec8,1faff35,0b4c21a,535582d,992f9a3,f4ea4ac,91b7f73,f6cdab2,53ed15a,ce65246,7a5be20,6b50bfa,0386553,9c5ebf5,53ed15a,53ed15a]:v1.30.1Compare Source
Patch Changes
#12851
86a40f0Thanks @jamesopstad! - Fix a bug that prevented using subpath imports for additional module typesYou can now use subpath imports for additional module types (
.html,.txt,.sql,.bin,.wasm) by defining them in yourpackage.jsonimportsfield:Updated dependencies [
593c4db,b8f3309,451dae3,5aaaab2,5aaaab2,f8516dd,9c9fe30,379f2a2,c2e9163,6a6449e,9a1cf29,875da60]:v1.30.0Compare Source
Minor Changes
#12848
ce48b77Thanks @emily-shen! - Enable local explorer by defaultThis ungates the local explorer, a UI that lets you inspect the state of D1, DO and KV resources locally by visiting
/cdn-cgi/explorerduring local development.Note: this feature is still experimental, and can be disabled by setting the env var
X_LOCAL_EXPLORER=false.Patch Changes
#12942
4f7fd79Thanks @jamesopstad! - Avoid splicing into the middleware stack for Vite versions other than v6Previously, the plugin spliced its pre-middleware into the Vite middleware stack relative to
viteCachedTransformMiddleware. In Vite 8, this middleware can be omitted in some scenarios, which would cause the splice to fail. The plugin now registers pre-middleware usingserver.middlewares.use()directly, which places it in the correct position for Vite 7+. For Vite 6, the middleware is moved to the correct position in a post hook.Updated dependencies [
782df44,3c988e2,62545c9,d028ffb,cb71403,71ab981,3a1c149,7c3c6c6,ce48b77,8729f3d]:Configuration
📅 Schedule: (UTC)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, 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.