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

[renovate]

ℹ️ 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.14.0

---

Release Notes

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

v0.14.7

Compare Source

Patch Changes

• Updated dependencies [854d66c, 6f63eaa, aef9825, eaaa728, 58292f6, 5e5bbc1, d5ff5a4, 07a918c, 89c7829, 60565dd, 6cbcdeb, 90aee27]:
  • miniflare@​4.20260415.0
  • wrangler@​4.83.0

v0.14.6

Compare Source

Patch Changes

• Updated dependencies [9b2b6ba]:
  • wrangler@​4.82.2

v0.14.5

Compare Source

Patch Changes

• Updated dependencies [6b11b07, dd4e888]:
  • wrangler@​4.82.1

v0.14.4

Compare Source

Patch Changes

• Updated dependencies [5338bb6, 79fd529, 28bc2be, 4fd138b, bafb96b, c50cb5b, 2589395, 525a46b, 5eff8c1, 1313275]:
  • wrangler@​4.82.0
  • miniflare@​4.20260410.0

v0.14.3

Compare Source

Patch Changes

• Updated dependencies [42c7ef0, c510494, 8b71eca, a42e0e8, 7ca6f6e]:
  • miniflare@​4.20260409.0
  • wrangler@​4.81.1

v0.14.2

Compare Source

Patch Changes

• #​13095 65e6684 Thanks @​penalosa! - Reject V8 coverage provider with a clear error message

  V8 native code coverage (@vitest/coverage-v8) requires node:inspector to collect profiling data from V8's runtime. workerd only provides node:inspector as a non-functional stub, so V8 coverage would silently fail or crash with a confusing No such module "node:inspector" error.

  The pool now detects this configuration early — during Vite plugin setup, before Vitest tries to load the coverage provider — and throws a clear error directing users to use Istanbul coverage instead, which works by instrumenting source code at build time and runs on any JavaScript runtime.

• Updated dependencies [a3e3b57, 7d318e1, fa6d84f, 96ee5d4, 7d318e1, 7a60d4b, 78cbe37, 6fa5dfd]:

  • miniflare@​4.20260405.0
  • wrangler@​4.81.0

v0.14.1

Compare Source

Patch Changes

• #​13131 65acf66 Thanks @​dario-piotrowicz! - Use miniflare's handleStructuredLogs option instead of handleRuntimeStdio for processing workerd output

  Previously, vitest-pool-workers manually processed raw stdout/stderr streams from the workerd runtime via handleRuntimeStdio, with its own filtering of known noisy messages (e.g. LLVM symbolizer warnings). This switches to miniflare's handleStructuredLogs option, which parses workerd's structured JSON log output and automatically filters known unhelpful messages. This aligns with how both wrangler and vite-plugin-cloudflare handle workerd logs.

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

  • wrangler@​4.80.0
  • miniflare@​4.20260401.0

v0.14.0

Compare Source

Minor Changes

• #​12858 f05f2da Thanks @​repository! - Add disableRetryDelays() to WorkflowInstanceModifier to skip retry backoff delays in tests

  When testing Workflows with retry configurations, the backoff delays between retry attempts of a failing step.do() caused real wall-clock waiting (e.g., 35 seconds for 3 retries with 5-second exponential backoff), even when step results were fully mocked. The new disableRetryDelays() method eliminates these delays while preserving retry behavior — all attempts still execute, just without waiting between them.

Patch Changes

• #​13091 6d58f0f Thanks @​penalosa! - Use today's date for the RTTI compat date query instead of a hardcoded "2023-12-01", so newly added Node.js builtin modules are recognized by the module fallback service.

• #​13070 cdb9c88 Thanks @​penalosa! - Suppress CODE_MOVED for unknown code block log spam from workerd

  These are internal workerd diagnostic messages not relevant to application developers. Miniflare's structured log handler already filters them, but vitest-pool-workers uses a custom handleRuntimeStdio that bypasses that pipeline. This adds the pattern to the pool's own ignore list.

• #​13069 6d0e329 Thanks @​penalosa! - fix: suppress outputGateBroken stderr noise when testing Workflows

• #​13075 b8df076 Thanks @​penalosa! - Support @voidzero-dev/vite-plus-test as an alternative to vitest

  Users running tests via Vite+ (@voidzero-dev/vite-plus-test) with the recommended pnpm overrides no longer hit spurious version warnings or Disallowed operation called within global scope errors.

• Updated dependencies [ffbc268, 9eff028, ed20a9b, f214760, 746858a, 9aad27f, 1fc5518, b539dc7, 9282493, a532eea, cd0e971, d4c6158, 2565b1d]:

  • wrangler@​4.79.0
  • miniflare@​4.20260329.0

v0.13.5

Compare Source

Patch Changes

• #​13077 11c77b7 Thanks @​penalosa! - fix: runInDurableObject now correctly returns redirect responses (3xx) from Durable Object callbacks instead of throwing "Expected callback for X" errors

• #​13056 8384743 Thanks @​penalosa! - fix: Support dynamic import() inside entrypoint and Durable Object handlers

  Previously, calling exports.default.fetch() or SELF.fetch() on a worker whose handler used a dynamic import() would hang and fail with "Cannot perform I/O on behalf of a different Durable Object". This happened because the module runner's transport — which communicates over a WebSocket owned by the runner Durable Object — was invoked from a different DO context.

  The fix patches the module runner's transport via the onModuleRunner hook so that all invoke() calls are routed through the runner DO's I/O context, regardless of where the import() originates.

• #​13074 4618c05 Thanks @​penalosa! - fix: only apply module fallback extension probing for require(), not import

  The module fallback service previously tried adding .js, .mjs, .cjs, and .json suffixes to extensionless specifiers unconditionally. Per the Node.js spec, this extension-probing behaviour is specific to CommonJS require(). ESM import statements must include explicit file extensions.

  Extension-less TypeScript import specifiers continue to work correctly — they are resolved by Vite's resolver rather than the fallback's extension loop.

• #​13073 baec845 Thanks @​penalosa! - Add adminSecretsStore() to cloudflare:test for seeding secrets in tests

  Secrets store bindings only expose a read-only .get() method, so there was previously no way to seed secret values from within a test. The new adminSecretsStore() helper returns Miniflare's admin API for a secrets store binding, giving tests full control over create, update, and delete operations.

  import { adminSecretsStore } from "cloudflare:test";
  import { env } from "cloudflare:workers";
  
  const admin = adminSecretsStore(env.MY_SECRET);
  await admin.create("test-value");
  
  const value = await env.MY_SECRET.get(); // "test-value"

• #​13083 cfd513f Thanks @​penalosa! - Add a 30-second timeout to waitUntil promise draining to prevent hanging tests

  Previously, if a ctx.waitUntil() promise never resolved, the test suite would hang indefinitely after the test file finished. Now, any waitUntil promises that haven't settled within 30 seconds are abandoned with a warning, allowing the test suite to continue. This aligns with the production waitUntil limit.

• Updated dependencies [eeaa473, 9fcdfca, bc24ec8, 1faff35, 0b4c21a, 535582d, 992f9a3, f4ea4ac, 91b7f73, f6cdab2, 53ed15a, ce65246, 7a5be20, 6b50bfa, 0386553, 9c5ebf5, 53ed15a, 53ed15a]:

  • wrangler@​4.78.0
  • miniflare@​4.20260317.3

v0.13.4

Compare Source

Patch Changes

• #​12999 f9728fd Thanks @​hiendv! - chore: update some tests and fixtures to Vitest 4 / vpw 0.13.x

• Updated dependencies [593c4db, b8f3309, 451dae3, 5aaaab2, 5aaaab2, f8516dd, 9c9fe30, 379f2a2, c2e9163, 6a6449e, 9a1cf29, 875da60]:

  • wrangler@​4.77.0
  • miniflare@​4.20260317.2

v0.13.3

Compare Source

Patch Changes

• #​12881 8729f3d Thanks @​pombosilva! - Workflows testing util waitForStatus now supports waiting for "terminated" and "paused" states.

• Updated dependencies [782df44, 3c988e2, 62545c9, cb71403, 71ab981, 3a1c149, 7c3c6c6, ce48b77, 8729f3d]:

  • wrangler@​4.76.0
  • miniflare@​4.20260317.1

v0.13.2

Compare Source

Patch Changes

• Updated dependencies [c9b3184, 13df6c7, df0d112, 81ee98e, c600ce0, f509d13, 3b81fc6, 0a7fef9]:
  • wrangler@​4.75.0
  • miniflare@​4.20260317.0

v0.13.1

Compare Source

Patch Changes

• Updated dependencies [ade0aed, 2b9a186, 65f1092, 7b0d8f5, 351e1e1, 2b9a186]:
  • miniflare@​4.20260312.1
  • wrangler@​4.74.0

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

• Updated dependencies [f7de0fd, ff543e3, 8e89e85, e63539d, 8d1e130, 6ee18e1, ecc7f79, 1dda1c8, 4bb61b9]:
  • miniflare@​4.20260312.0
  • wrangler@​4.73.0

v0.12.21

Compare Source

Patch Changes

• #​12790 5451a7f Thanks @​petebacondarwin! - Bump devalue to ^5.6.3 to address security vulnerabilities

  Devalue had denial of service and prototype pollution vulnerabilities. This is a bundled dependency.

• Updated dependencies [5451a7f, 5451a7f, 82cc2a8, 3c67c2a, d645594, 211d75d, 6ed249b, 9f93b54, de65c58, cb14820, a7c87d1, b8c33f5, e4d9510]:

  • miniflare@​4.20260310.0
  • wrangler@​4.72.0

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

• #​12682 b5b91c9 Thanks @​hiendv! - Fix resource leak where remote proxy sessions were not disposed during pool shutdown, causing vitest processes to hang.

• Updated dependencies [6a8aa5f, d672e2e, 35b2c56, 5f7aaf2, 209b396, 23a365a, 596b8a0, 00e729e, 0769056, 150ef7b, bf9cb3d]:

  • wrangler@​4.70.0
  • miniflare@​4.20260301.1

v0.12.18

Compare Source

Patch Changes

• Updated dependencies [99037e3, 295297a, f765244, c0e9e08]:
  • miniflare@​4.20260305.0
  • wrangler@​4.69.0

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

• Updated dependencies [8d882fa, 8d882fa]:
  • wrangler@​4.68.0

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

• Updated dependencies [f239077, aaa7200, 2f19a40, 8723684, e2a6600, 527e4f5, aa82c2b, 0b17117, ca58062]:
  • miniflare@​4.20260219.0
  • wrangler@​4.67.0

v0.12.13

Compare Source

Patch Changes

• Updated dependencies [5a868a0, caf9b11, c58e81b, 33a9a8f, 8077c14, caf9b11, 7d2355e, 936187d, 7ea69af, 5cc7158, caf9b11, 43c462a, c4c86f8, 7d2355e, c9d0f9d, 5cc7158, 5cc7158, c9d0f9d]:
  • miniflare@​4.20260217.0
  • wrangler@​4.66.0

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

• Updated dependencies [5d56487, 2d90127, 2acb277, c8dda16, e02b5f5, 8ba1d11, 555b32a, d636d6a, bf8df0c, e02b5f5, 988dea9, 1f1c3ce, 62635a0, fd902aa, 961705c, 355c6da, bfd17cd, 3388c84, ce9dc01, 21ac7ab, 937425c]:
  • wrangler@​4.64.0
  • miniflare@​4.20260210.0

v0.12.10

Compare Source

Patch Changes

• Updated dependencies [ee9b81f, 63f1adb, ba13de9, 447daa3, fe3af35, bd4bb98, dab4bc9, 83adb2c, 18c0784]:
  • wrangler@​4.63.0
  • miniflare@​4.20260205.0

v0.12.9

Compare Source

Patch Changes

• Updated dependencies [964a39d, 253a85d, ce736b9, 0c9625a, 47944d1, 4c4d5a5, b05b919, 0aaf080, b981db5, a113c0d, fdd7a9f, a5fca2c, 1bd1488, f7aa8c7]:
  • wrangler@​4.62.0
  • miniflare@​4.20260131.0

v0.12.8

Compare Source

Patch Changes

• Updated dependencies [8a210af, eb8a415, 3b06b18, 17961bb, 52fdfe7, 6d8d9cd, cb72c11]:
  • miniflare@​4.20260128.0
  • wrangler@​4.61.1

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](

---

Configuration

📅 Schedule: (UTC)

• 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]

⚠️ 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.14.7
npm error node_modules/@cloudflare/vitest-pool-workers
npm error   dev @cloudflare/vitest-pool-workers@"^0.14.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-04-15T11_44_15_546Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-04-15T11_44_15_546Z-debug-0.log