Skip to content

chore(deps): update dependency @cloudflare/vitest-pool-workers to ^0.13.0#1

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/cloudflare-vitest-pool-workers-0.x
Open

chore(deps): update dependency @cloudflare/vitest-pool-workers to ^0.13.0#1
renovate[bot] wants to merge 1 commit intomainfrom
renovate/cloudflare-vitest-pool-workers-0.x

Conversation

@renovate
Copy link
Copy Markdown

@renovate renovate bot commented Oct 16, 2025

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
@cloudflare/vitest-pool-workers (source) ^0.8.19^0.13.0 age confidence

Release Notes

cloudflare/workers-sdk (@​cloudflare/vitest-pool-workers)

v0.13.0

Compare Source

Minor Changes
  • #​11632 a6ddbdb Thanks @​penalosa! - Support Vitest 4 in @cloudflare/vitest-pool-workers.

    This a breaking change to the @cloudflare/vitest-pool-workers integration in order to support Vitest v4. Along with supporting Vitest v4 (and dropping support for Vitest v2 and v3), we've made a number of changes that may require changes to your tests. Our aim has been to improve stability & the foundations of @cloudflare/vitest-pool-workers as we move towards a v1 release of the package.

    We've made a codemod to make the migration easier, which will make the required changes to your config file:

    npx jscodeshift -t node_modules/@​cloudflare/vitest-pool-workers/dist/codemods/vitest-v3-to-v4.mjs vitest.config.ts

    Or, without installing the package first:

    npx jscodeshift -t https://unpkg.com/@​cloudflare/vitest-pool-workers/dist/codemods/vitest-v3-to-v4.mjs --parser=ts vitest.config.ts
    • Config API: defineWorkersProject and defineWorkersConfig from @cloudflare/vitest-pool-workers/config have been replaced with a cloudflareTest() Vite plugin exported from @cloudflare/vitest-pool-workers. The test.poolOptions.workers options are now passed directly to cloudflareTest():

      Before:

      import { defineWorkersProject } from "@​cloudflare/vitest-pool-workers/config";
      
      export default defineWorkersProject({
      	test: {
      		poolOptions: {
      			workers: {
      				wrangler: { configPath: "./wrangler.jsonc" },
      			},
      		},
      	},
      });

      After:

      import { cloudflareTest } from "@​cloudflare/vitest-pool-workers";
      import { defineConfig } from "vitest/config";
      
      export default defineConfig({
      	plugins: [
      		cloudflareTest({
      			wrangler: { configPath: "./wrangler.jsonc" },
      		}),
      	],
      });
    • isolatedStorage & singleWorker: These have been removed in favour of a simpler isolation model that more closely matches Vitest. Storage isolation is now on a per test file basis, and you can make your test files share the same storage by using the Vitest flags --max-workers=1 --no-isolate

    • import { env, SELF } from "cloudflare:test": These have been removed in favour of import { env, exports } from "cloudflare:workers". exports.default.fetch() has the same behaviour as SELF.fetch(), except that it doesn't expose Assets. To test your assets, write an integration test using startDevWorker()

    • import { fetchMock } from "cloudflare:test": This has been removed. Instead, mock globalThis.fetch or use ecosystem libraries like MSW (recommended).

    • Vitest peer dependency: @cloudflare/vitest-pool-workers now requires vitest@^4.1.0.

Patch Changes

v0.12.21

Compare Source

Patch Changes

v0.12.20

Compare Source

Patch Changes
  • Updated dependencies [ec2459e]:
    • wrangler@​4.71.0
    • miniflare@​4.20260301.1

v0.12.19

Compare Source

Patch Changes

v0.12.18

Compare Source

Patch Changes

v0.12.17

Compare Source

Patch Changes
  • Updated dependencies [3d6e421, 294297e]:
    • wrangler@​4.68.1
    • miniflare@​4.20260302.0

v0.12.16

Compare Source

Patch Changes

v0.12.15

Compare Source

Patch Changes
  • #​12602 58a4020 Thanks @​anonrig! - Optimize filesystem operations by using Node.js's throwIfNoEntry: false option

    This reduces the number of system calls made when checking for file existence by avoiding the overhead of throwing and catching errors for missing paths. This is an internal performance optimization with no user-visible behavioral changes.

  • Updated dependencies [e93dc01, c2ed7c2, d920811, 896734d, ebdbe52, 58a4020, 6f6cd94]:

    • wrangler@​4.67.1
    • miniflare@​4.20260302.0

v0.12.14

Compare Source

Patch Changes

v0.12.13

Compare Source

Patch Changes

v0.12.12

Compare Source

Patch Changes
  • #​11771 4b6fd36 Thanks @​avenceslau! - Fix Durable Object storage causing SQLITE_CANTOPEN errors on repeated test runs

    When running vitest multiple times in watch mode, Durable Object storage would fail with SQLITE_CANTOPEN errors. This happened because the storage reset function was deleting directories that workerd still had file handles to.

    The fix preserves directory structure during storage reset, deleting only files while
    keeping directories intact. This allows workerd to maintain valid handles to SQLite
    database directories across test runs.

  • Updated dependencies [ad817dd, b900c5a, f7fa326, 734792a, 7aaa2a5, cc5ac22, 62a8d48, 84252b7, e5efa5d, d06ad09, 10a1c4a, be9745f, d7b492c, 122791d, 8809411, 1a9eddd, 41e18aa]:

    • wrangler@​4.65.0
    • miniflare@​4.20260212.0

v0.12.11

Compare Source

Patch Changes

v0.12.10

Compare Source

Patch Changes

v0.12.9

Compare Source

Patch Changes

v0.12.8

Compare Source

Patch Changes

v0.12.7

Compare Source

Patch Changes
  • #​12056 6d5f69f Thanks @​edmundhung! - fix: allow Vite query parameters like ?raw on .sql file imports

    Importing .sql files with Vite query parameters (e.g., import sql from "./query.sql?raw") would fail with "No such module" errors in vitest-pool-workers 0.12.x. Both import styles now work:

    • import sql from "./query.sql?raw" (Vite handles the ?raw transform)
    • import sql from "./query.sql" (loaded as Text module)
  • #​11917 7b40ceb Thanks @​ksawaneh! - Fix CommonJS require() of .json files in the module fallback service (avoids SyntaxError: Unexpected token ':').

  • #​11897 bbd8a5e Thanks @​dario-piotrowicz! - Bundle the zod dependency to reduce supply chain attack surface

    In order to prevent possible npm vulnerability attacks, the team's policy is to bundle
    dependencies in our packages where possible. This helps ensure that only trusted code
    runs on the user's system, even if compromised packages are later published to npm.

    This change bundles zod (a pure JavaScript validation library with no native dependencies)
    into miniflare and @​cloudflare/vitest-pool-workers.

    Other dependencies remain external for technical reasons:

    • sharp: Native binary with platform-specific builds
    • undici: Dynamically required at runtime in worker threads
    • ws: Has optional native bindings for performance
    • workerd: Native binary (Cloudflare's JavaScript runtime)
    • @cspotcode/source-map-support: Uses require.cache manipulation at runtime
    • youch: Dynamically required for lazy loading
  • Updated dependencies [a0a9ef6, ad4666c, 014e7aa, e414f05, 77e82d2, f08ef21, 0641e6c, eacedba, 05714f8, e8b2ef5, bbd8a5e]:

    • wrangler@​4.61.0
    • miniflare@​4.20260124.0

v0.12.6

Compare Source

Patch Changes

v0.12.5

Compare Source

Patch Changes

v0.12.4

Compare Source

Patch Changes
  • #​11898 c17e971 Thanks @​petebacondarwin! - Bundle more third-party dependencies to reduce supply chain risk

    Previously, several small utility packages were listed as runtime dependencies and
    installed separately. These are now bundled directly into the published packages,
    reducing the number of external dependencies users need to trust.

    Bundled dependencies:

    • miniflare: acorn, acorn-walk, exit-hook, glob-to-regexp, stoppable
    • kv-asset-handler: mime
    • vite-plugin-cloudflare: @remix-run/node-fetch-server, defu, get-port, picocolors, tinyglobby
    • vitest-pool-workers: birpc, devalue, get-port, semver
  • Updated dependencies [e78186d, fe4faa3, 4714ca1, c17e971, 695b043]:

    • miniflare@​4.20260114.0
    • wrangler@​4.59.2

v0.12.3

Compare Source

Patch Changes
  • Updated dependencies [99b1f32]:
    • wrangler@​4.59.1

v0.12.2

Compare Source

Patch Changes

v0.12.1

Compare Source

Patch Changes
  • Updated dependencies [97e67b9, 7d63fa5]:
    • miniflare@​4.20260107.0
    • wrangler@​4.58.0

v0.12.0

Compare Source

Minor Changes
  • #​11648 eac5cf7 Thanks @​pombosilva! - Add Workflows test handlers in vitest-pool-workers to get the Workflow instance output and error:

    • getOutput(): Returns the output of the successfully completed Workflow instance.
    • getError(): Returns the error information of the errored Workflow instance.

    Example:

    // First wait for the workflow instance to complete:
    await expect(
    	instance.waitForStatus({ status: "complete" })
    ).resolves.not.toThrow();
    
    // Then, get its output
    const output = await instance.getOutput();
    
    // Or for errored workflow instances, get their error:
    await expect(
    	instance.waitForStatus({ status: "errored" })
    ).resolves.not.toThrow();
    const error = await instance.getError();
Patch Changes

v0.11.1

Compare Source

Patch Changes

v0.11.0

Compare Source

Minor Changes
  • #​11533 8d9003e Thanks @​petebacondarwin! - Add support for ctx.exports

    It is now possible to access ctx.exports properties for the main (SELF) worker.

    • Integration tests: in the SELF worker the ctx.exports object now contains the expected stubs to the exported entry-points.
    • Unit tests: the object returned from createExecutionContext() has exports property that exposes the exports of the SELF worker.

    Due to the dynamic nature of Vitest the integration relies upon guessing what the exports of the main Worker are by statically analyzing the Worker source using esbuild. In cases where it is not possible to infer the exports (for example, a wildcard re-export of a virtual module) it is possible to declare these in the vitest-pool-workers config via the additionalExports setting.

Patch Changes

v0.10.15

Compare Source

Patch Changes

v0.10.14

Compare Source

Patch Changes

v0.10.13

Compare Source

Patch Changes
  • Updated dependencies [59534ba, 7e80340]:
    • miniflare@​4.20251202.0
    • wrangler@​4.52.1

v0.10.12

Compare Source

Patch Changes

v0.10.11

Compare Source

Patch Changes
  • Upda

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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.

🔕 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.

@renovate renovate bot force-pushed the renovate/cloudflare-vitest-pool-workers-0.x branch 2 times, most recently from 181bfb9 to d36e8fe Compare October 16, 2025 18:09
@renovate renovate bot force-pushed the renovate/cloudflare-vitest-pool-workers-0.x branch from d36e8fe to 1bc4692 Compare October 25, 2025 07:12
@renovate renovate bot changed the title chore(deps): update dependency @cloudflare/vitest-pool-workers to ^0.9.0 chore(deps): update dependency @cloudflare/vitest-pool-workers to ^0.10.0 Oct 25, 2025
@renovate renovate bot force-pushed the renovate/cloudflare-vitest-pool-workers-0.x branch from 1bc4692 to adc3a66 Compare November 1, 2025 08:02
@renovate renovate bot force-pushed the renovate/cloudflare-vitest-pool-workers-0.x branch from adc3a66 to be0e234 Compare November 8, 2025 16:11
@renovate renovate bot force-pushed the renovate/cloudflare-vitest-pool-workers-0.x branch 3 times, most recently from a5e9122 to 7138c73 Compare November 22, 2025 08:13
@renovate renovate bot force-pushed the renovate/cloudflare-vitest-pool-workers-0.x branch 2 times, most recently from a4b7b54 to 3548608 Compare December 2, 2025 23:42
@renovate renovate bot force-pushed the renovate/cloudflare-vitest-pool-workers-0.x branch 2 times, most recently from 51da923 to b24c116 Compare December 5, 2025 19:13
@renovate renovate bot force-pushed the renovate/cloudflare-vitest-pool-workers-0.x branch 2 times, most recently from dd2d8e7 to e9322a8 Compare December 18, 2025 07:59
@renovate renovate bot changed the title chore(deps): update dependency @cloudflare/vitest-pool-workers to ^0.10.0 chore(deps): update dependency @cloudflare/vitest-pool-workers to ^0.11.0 Dec 18, 2025
@renovate renovate bot force-pushed the renovate/cloudflare-vitest-pool-workers-0.x branch 2 times, most recently from 992b135 to 5246d62 Compare December 19, 2025 11:50
@renovate renovate bot force-pushed the renovate/cloudflare-vitest-pool-workers-0.x branch 2 times, most recently from 940ce63 to 3916255 Compare January 8, 2026 06:59
@renovate renovate bot changed the title chore(deps): update dependency @cloudflare/vitest-pool-workers to ^0.11.0 chore(deps): update dependency @cloudflare/vitest-pool-workers to ^0.12.0 Jan 8, 2026
@renovate renovate bot force-pushed the renovate/cloudflare-vitest-pool-workers-0.x branch 3 times, most recently from 14a49ec to 804145d Compare January 16, 2026 08:09
@renovate renovate bot force-pushed the renovate/cloudflare-vitest-pool-workers-0.x branch 3 times, most recently from bcf9ad4 to a70ff93 Compare January 28, 2026 08:07
@renovate renovate bot force-pushed the renovate/cloudflare-vitest-pool-workers-0.x branch 3 times, most recently from 8646e6a to 641fe6d Compare February 6, 2026 11:12
@renovate renovate bot force-pushed the renovate/cloudflare-vitest-pool-workers-0.x branch 2 times, most recently from 73da25f to f482164 Compare February 13, 2026 08:11
@renovate renovate bot force-pushed the renovate/cloudflare-vitest-pool-workers-0.x branch 4 times, most recently from 0b726ec to 4dd3542 Compare February 24, 2026 05:49
@renovate renovate bot force-pushed the renovate/cloudflare-vitest-pool-workers-0.x branch 2 times, most recently from 3a5a43c to 6d49ea6 Compare March 8, 2026 08:56
@renovate renovate bot force-pushed the renovate/cloudflare-vitest-pool-workers-0.x branch from 6d49ea6 to 3525d82 Compare March 14, 2026 20:48
@renovate renovate bot changed the title chore(deps): update dependency @cloudflare/vitest-pool-workers to ^0.12.0 chore(deps): update dependency @cloudflare/vitest-pool-workers to ^0.13.0 Mar 14, 2026
@renovate
Copy link
Copy Markdown
Author

renovate bot commented Mar 14, 2026

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: rewriter/package-lock.json
npm warn Unknown env config "store". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: rewriter@0.0.0
npm error Found: vitest@3.2.4
npm error node_modules/vitest
npm error   dev vitest@"~3.2.0" from the root project
npm error   peer vitest@"3.2.4" from @vitest/browser@3.2.4
npm error   node_modules/@vitest/browser
npm error     peerOptional @vitest/browser@"3.2.4" from vitest@3.2.4
npm error   1 more (@vitest/ui)
npm error
npm error Could not resolve dependency:
npm error peer vitest@"^4.1.0" from @cloudflare/vitest-pool-workers@0.13.5
npm error node_modules/@cloudflare/vitest-pool-workers
npm error   dev @cloudflare/vitest-pool-workers@"^0.13.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-03-31T10_42_04_161Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-03-31T10_42_04_161Z-debug-0.log

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