Skip to content

fix(deps): update all non-major dependencies#1173

Merged
hi-ogawa merged 2 commits intomainfrom
renovate/all-minor-patch
Apr 6, 2026
Merged

fix(deps): update all non-major dependencies#1173
hi-ogawa merged 2 commits intomainfrom
renovate/all-minor-patch

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate bot commented Apr 6, 2026

This PR contains the following updates:

Package Change Age Confidence
@cloudflare/vite-plugin (source) ^1.30.3 → ^1.31.0 age confidence
@playwright/test (source) ^1.59.0 → ^1.59.1 age confidence
@rolldown/pluginutils (source) 1.0.0-rc.12 → 1.0.0-rc.13 age confidence
@types/node (source) ^24.12.0 → ^24.12.2 age confidence
playwright-chromium (source) ^1.59.0 → ^1.59.1 age confidence
react-router (source) 7.13.2 → 7.14.0 age confidence
rolldown (source) 1.0.0-rc.12 → 1.0.0-rc.13 age confidence
srvx (source) ^0.11.13 → ^0.11.15 age confidence
vitefu ^1.1.2 → ^1.1.3 age confidence
wrangler (source) ^4.79.0 → ^4.80.0 age confidence

Release Notes

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

v1.31.0

Compare Source

Minor Changes

  • #​13011 b9b7e9d Thanks @​ruifigueira! - Add experimental headful browser rendering support for local development

    Experimental: This feature may be removed or changed without notice.

    When developing locally with the Browser Rendering API, you can enable headful (visible) mode via the X_BROWSER_HEADFUL environment variable to see the browser while debugging:

    X_BROWSER_HEADFUL=true wrangler dev
X_BROWSER_HEADFUL=true vite dev

    Note: when using @cloudflare/playwright, two Chrome windows may appear — the initial blank page and the one created by browser.newPage(). This is expected behavior due to how Playwright handles browser contexts via CDP.

  • #​13051 d5bffde Thanks @​dario-piotrowicz! - Update getLocalWorkerdCompatibilityDate to return today's date

    The re-exported getLocalWorkerdCompatibilityDate function from @cloudflare/vite-plugin previously resolved the workerd compatibility date by traversing the local miniflare installation, 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 f76652c Thanks @​kayluhb! - Fix SyntaxError when SSR-transformed module ends with a single-line comment

    When module code ends with a // comment (e.g. //# sourceMappingURL=... preserved by vite-plus), the closing } of the async wrapper in runInlinedModule was absorbed into the comment, causing SyntaxError: Unexpected end of input. Adding a newline before the closing brace prevents this.

  • #​13188 110002c Thanks @​shulaoda! - Normalize the return value of getAssetsDirectory() with vite.normalizePath() to ensure assets.directory in the output wrangler.json always uses forward slashes

  • Updated dependencies [9c4035b, 5d29055, fb67a18, d5bffde, ab44870, 48d83ca, b2f53ea, b9b7e9d, 14e72eb, 4dc94fd, b2f53ea, d5bffde, 48d83ca]:

    • wrangler@​4.80.0
    • miniflare@​4.20260401.0
microsoft/playwright (@​playwright/test)

v1.59.1

Compare Source

rolldown/rolldown (@​rolldown/pluginutils)

v1.0.0-rc.13

Compare Source

🚀 Features
🐛 Bug Fixes
🚜 Refactor
📚 Documentation
🧪 Testing
⚙️ Miscellaneous Tasks
❤️ New Contributors
remix-run/react-router (react-router)

v7.14.0

Compare Source

Patch Changes

  • UNSTABLE RSC FRAMEWORK MODE BREAKING CHANGE - Existing route module exports remain unchanged from stable v7 non-RSC mode, but new exports are added for RSC mode. If you want to use RSC features, you will need to update your route modules to export the new annotations. (#​14901)

    If you are using RSC framework mode currently, you will need to update your route modules to the new conventions. The following route module components have their own mutually exclusive server component counterparts:

    Server Component Export Client Component
    ServerComponent default
    ServerErrorBoundary ErrorBoundary
    ServerLayout Layout
    ServerHydrateFallback HydrateFallback

    If you were previously exporting a ServerComponent, your ErrorBoundary, Layout, and HydrateFallback were also server components. If you want to keep those as server components, you can rename them and prefix them with Server. If you were previously importing the implementations of those components from a client module, you can simply inline them.

    Example:

    Before

    import { ErrorBoundary as ClientErrorBoundary } from "./client";

export function ServerComponent() {
  // ...
}

export function ErrorBoundary() {
  return <ClientErrorBoundary />;
}

export function Layout() {
  // ...
}

export function HydrateFallback() {
  // ...
}

    After

    export function ServerComponent() {
  // ...
}

export function ErrorBoundary() {
  // previous implementation of ClientErrorBoundary, this is now a client component
}

export function ServerLayout() {
  // rename previous Layout export to ServerLayout to make it a server component
}

export function ServerHydrateFallback() {
  // rename previous HydrateFallback export to ServerHydrateFallback to make it a server component
}

  • rsc Link prefetch (#​14902)

  • Remove recursion from turbo-stream v2 allowing for encoding / decoding of massive payloads. (#​14838)

  • encodeViaTurboStream leaked memory via unremoved AbortSignal listener (#​14900)

h3js/srvx (srvx)

v0.11.15

Compare Source

compare changes

🩹 Fixes
  • node/web: Do not swallow getReader errors (#​199)
❤️ Contributors

v0.11.14

Compare Source

compare changes

🩹 Fixes
  • node: Handle EADDRINUSE port conflict on serve (#​197)
🏡 Chore
❤️ Contributors
svitejs/vitefu (vitefu)

v1.1.3

Compare Source

  • Sort result arrays of crawlFrameworkPkgs to ensure they are deterministic (#​30)
  • Update Vite 8 peer dependency to stable
cloudflare/workers-sdk (wrangler)

v4.80.0

Compare Source

Minor Changes

  • #​13151 9c4035b Thanks @​G4brym! - Add type generation for AI Search bindings

    Running wrangler types now generates AiSearchNamespace and AiSearchInstance types for ai_search_namespaces and ai_search config bindings respectively. Both simple and per-environment modes are supported.

    // wrangler.json
{
  "ai_search_namespaces": [
    { "binding": "AI_SEARCH", "namespace": "production" }
  ],
  "ai_search": [
    { "binding": "BLOG_SEARCH", "instance_name": "cloudflare-blog" }
  ]
}
    // Generated by `wrangler types`
interface Env {
  AI_SEARCH: AiSearchNamespace;
  BLOG_SEARCH: AiSearchInstance;
}

  • #​13011 b9b7e9d Thanks @​ruifigueira! - Add experimental headful browser rendering support for local development

    Experimental: This feature may be removed or changed without notice.

    When developing locally with the Browser Rendering API, you can enable headful (visible) mode via the X_BROWSER_HEADFUL environment variable to see the browser while debugging:

    X_BROWSER_HEADFUL=true wrangler dev
X_BROWSER_HEADFUL=true vite dev

    Note: when using @cloudflare/playwright, two Chrome windows may appear — the initial blank page and the one created by browser.newPage(). This is expected behavior due to how Playwright handles browser contexts via CDP.

  • #​12992 48d83ca Thanks @​RiscadoA! - Add vpc_networks binding support for routing Worker traffic through a Cloudflare Tunnel or network.

    {
  "vpc_networks": [
    // Route through a specific Cloudflare Tunnel
    { "binding": "MY_FIRST_VPC", "tunnel_id": "<tunnel-id>" },
    // Route through the Cloudflare One mesh network
    { "binding": "MY_SECOND_VPC", "network_id": "cf1:network" }
  ]
}
Patch Changes

  • #​13155 5d29055 Thanks @​dependabot! - Update dependencies of "miniflare", "wrangler"

    The following dependency versions have been updated:

    Dependency From To
    workerd 1.20260329.1 1.20260331.1

  • #​13162 fb67a18 Thanks @​dependabot! - Update dependencies of "miniflare", "wrangler"

    The following dependency versions have been updated:

    Dependency From To
    workerd 1.20260331.1 1.20260401.1

  • #​13136 ab44870 Thanks @​petebacondarwin! - Display build errors for auxiliary workers in multi-worker mode

    Previously, when running wrangler dev with multiple -c config flags (multi-worker mode), build errors from auxiliary/secondary workers were only logged at debug level, causing Wrangler to silently hang. Build errors from all workers are now displayed at error level so you can see what went wrong and fix it.

  • #​12992 48d83ca Thanks @​RiscadoA! - Fix remote proxy worker not catching errors thrown by bindings during wrangler dev

  • #​13238 b2f53ea Thanks @​guybedford! - Fix source phase imports in bundled and non-bundled Workers

    Wrangler now preserves import source syntax when it runs esbuild, including module format detection and bundled deploy output. This fixes both --no-bundle and bundled deployments for Workers that import WebAssembly using source phase imports.

  • #​10126 14e72eb Thanks @​nekoze1210! - fix: Sort D1 migration files to ensure consistent chronological ordering

    wrangler d1 migrations list and wrangler d1 migrations apply previously returned migration files in an order dependent on the filesystem, which could vary across operating systems. Migration filenames are now sorted alphabetically before being returned, ensuring consistent chronological ordering.

  • #​13150 4dc94fd Thanks @​dario-piotrowicz! - Polish Cloudflare Vite plugin installation during autoconfig

    Projects using Vite 6.0.x were rejected by auto-configuration because the minimum supported version was set to 6.1.0 (the @cloudflare/vite-plugin peer dependency). The minimum version check is now 6.0.0, and when a project has Vite in the [6.0.0, 6.1.0) range, auto-configuration will automatically upgrade it to the latest 6.x before installing @cloudflare/vite-plugin.

  • #​13051 d5bffde Thanks @​dario-piotrowicz! - Use today's date as the default compatibility date

    Previously, when generating a compatibility date for new projects or when no compatibility date was configured, the date was resolved by loading the locally installed workerd package via miniflare. This approach was unreliable in some package manager environments (notably pnpm). The logic now simply uses today's date instead, which is always correct and works reliably across all environments.

  • Updated dependencies [5d29055, fb67a18, d5bffde, b9b7e9d, b2f53ea, 48d83ca]:

    • miniflare@​4.20260401.0

Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, only on Monday ( * 0-3 * * 1 ) (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

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

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

@renovate renovate bot added the dependencies label Apr 6, 2026
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 3141c86 to aae41c1 Compare April 6, 2026 05:27
@hi-ogawa hi-ogawa merged commit 9bfb1a7 into main Apr 6, 2026
20 checks passed
@hi-ogawa hi-ogawa deleted the renovate/all-minor-patch branch April 6, 2026 06:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

dependencies

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@hi-ogawa