chore(deps-dev): bump @cloudflare/vitest-pool-workers from 0.16.20 to 0.21.1

[dependabot]

Bumps @cloudflare/vitest-pool-workers from 0.16.20 to 0.21.1.

Release notes

Sourced from @​cloudflare/vitest-pool-workers's releases.

@​cloudflare/vitest-pool-workers@​0.21.1

Patch Changes

• #14882 ab9132d Thanks @​petebacondarwin! - Report built-in modules that a Worker's compatibility settings don't provide as module errors, instead of crashing workerd

  Previously, a Worker whose module graph statically reached a compatibility-gated built-in that wasn't enabled — for example import "node:child_process" without nodejs_compat — took down the runtime with *** Received signal [#11](https://github.com/cloudflare/workers-sdk/tree/HEAD/packages/vitest-pool-workers/issues/11): Segmentation fault before any test ran. Vitest reported only Worker exited unexpectedly, naming neither the module nor the file that imported it, which made the cause very hard to find. The import didn't even have to be called; being reachable from the entrypoint was enough.

  The module fallback service answered these specifiers with a redirect to the modules root, but workerd already resolves node:/cloudflare:/workerd: specifiers there, so the redirect pointed back at the module workerd was in the middle of resolving and it recursed until the stack overflowed. Such a specifier only reaches the fallback service when workerd's own registry has already missed, so it's now reported as not found: workerd raises No such module "node:child_process", matching what wrangler dev does for the same Worker. The accompanying pool error names the module and points at compatibility flags rather than suggesting you bundle it, which can't help for a module built into the runtime.

• Updated dependencies [15cad03, 026e058, 731b33a, e1b5b4b, 5b1b930, 6e7d37d, d669088, 15cad03, c7aede7, 0aa8fa5]:

  • wrangler@4.121.0
  • miniflare@5.20260804.1-alpha

@​cloudflare/vitest-pool-workers@​0.21.0

Minor Changes

• #14994 2194f88 Thanks @​emily-shen! - Update the Workers Vitest pool for Miniflare's config-based options

  The Workers Vitest pool now converts the Miniflare options it creates for test sessions to Miniflare's config-based workers shape.

  For the most part, users should not expect to notice any changes.

However, auxiliary workers declared in miniflare.workers that rely on relative local imports now need those imported modules to be declared explicitly in the migrated module manifest.

Patch Changes

• Updated dependencies [6dbd192, 2194f88, 2194f88, 2194f88, 2194f88, 2194f88, 2194f88, 2194f88]:
  • miniflare@5.20260804.0-alpha
  • wrangler@4.120.1

@​cloudflare/vitest-pool-workers@​0.20.3

Patch Changes

• #15013 8cf78c8 Thanks @​dario-piotrowicz! - Update undici from 7.28.0 to 7.29.0

• Updated dependencies [35c87e9, b4f0c97, 8cf78c8, a60ff4d, 99eb50c, 35c87e9]:

  • wrangler@4.120.0
  • miniflare@5.20260801.1-alpha

@​cloudflare/vitest-pool-workers@​0.20.2

Patch Changes

• Updated dependencies [20470fa, 9c74538, 266172b, a88d169, a88d169, daf65f2, a9e5abb]:
  • wrangler@4.119.0
  • miniflare@5.20260801.0-alpha

@​cloudflare/vitest-pool-workers@​0.20.1

Patch Changes

• Updated dependencies [cc63aae, f92d1fc, a249591, f92d1fc, f92d1fc, cec9d88, e0bbf55]:

... (truncated)

Changelog

Sourced from @​cloudflare/vitest-pool-workers's changelog.

0.21.1

Patch Changes

• #14882 ab9132d Thanks @​petebacondarwin! - Report built-in modules that a Worker's compatibility settings don't provide as module errors, instead of crashing workerd

  Previously, a Worker whose module graph statically reached a compatibility-gated built-in that wasn't enabled — for example import "node:child_process" without nodejs_compat — took down the runtime with *** Received signal [#11](https://github.com/cloudflare/workers-sdk/tree/HEAD/packages/vitest-pool-workers/issues/11): Segmentation fault before any test ran. Vitest reported only Worker exited unexpectedly, naming neither the module nor the file that imported it, which made the cause very hard to find. The import didn't even have to be called; being reachable from the entrypoint was enough.

  The module fallback service answered these specifiers with a redirect to the modules root, but workerd already resolves node:/cloudflare:/workerd: specifiers there, so the redirect pointed back at the module workerd was in the middle of resolving and it recursed until the stack overflowed. Such a specifier only reaches the fallback service when workerd's own registry has already missed, so it's now reported as not found: workerd raises No such module "node:child_process", matching what wrangler dev does for the same Worker. The accompanying pool error names the module and points at compatibility flags rather than suggesting you bundle it, which can't help for a module built into the runtime.

• Updated dependencies [15cad03, 026e058, 731b33a, e1b5b4b, 5b1b930, 6e7d37d, d669088, 15cad03, c7aede7, 0aa8fa5]:

  • wrangler@4.121.0
  • miniflare@5.20260804.1-alpha

0.21.0

Minor Changes

• #14994 2194f88 Thanks @​emily-shen! - Update the Workers Vitest pool for Miniflare's config-based options

  The Workers Vitest pool now converts the Miniflare options it creates for test sessions to Miniflare's config-based workers shape.

  For the most part, users should not expect to notice any changes.

  However, while miniflare.modulesRules is preserved for common text and WASM fixture imports, it is not a full replacement for Miniflare's old modules: true module graph collection and you may notice some differences in behaviour.

Patch Changes

• Updated dependencies [6dbd192, 2194f88, 2194f88, 2194f88, 2194f88, 2194f88, 2194f88, 2194f88]:
  • miniflare@5.20260804.0-alpha
  • wrangler@4.120.1

0.20.3

Patch Changes

• #15013 8cf78c8 Thanks @​dario-piotrowicz! - Update undici from 7.28.0 to 7.29.0

• Updated dependencies [35c87e9, b4f0c97, 8cf78c8, a60ff4d, 99eb50c, 35c87e9]:

  • wrangler@4.120.0
  • miniflare@5.20260801.1-alpha

0.20.2

Patch Changes

• Updated dependencies [20470fa, 9c74538, 266172b, a88d169, a88d169, daf65f2, a9e5abb]:
  • wrangler@4.119.0
  • miniflare@5.20260801.0-alpha

... (truncated)

Commits

• 15fc568 Version Packages (#15118)
• ab9132d [vitest-pool-workers] Report unavailable built-ins as module errors instead o...
• d2f377e Version Packages (#15111)
• 2194f88 new config miniflare attempt 3 (#14994)
• b0aea76 Version Packages (#15036)
• 2938c01 Version Packages (#15021)
• b6a8629 Revert "Version Packages (#14977)" (#15033)
• 42c4227 Version Packages (#14977)
• 95d9b12 Version Packages (#14946)
• 83a37e3 docs: point vitest-pool-workers BUILD section at the tsdown config (#14940)
• Additional commits viewable in compare view

[changeset-bot]

⚠️ No Changeset found

Latest commit: 6ce28b6

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 92.25%. Comparing base (ab35e05) to head (6ce28b6).

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #2094   +/-   ##
=======================================
  Coverage   92.25%   92.25%           
=======================================
  Files         116      116           
  Lines        4130     4130           
  Branches     1081     1081           
=======================================
  Hits         3810     3810           
  Misses        285      285           
  Partials       35       35           

Flag	Coverage Δ
firebase-auth	96.61% <ø> (ø)
react-renderer	88.88% <ø> (ø)
session	98.91% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[dependabot]

Superseded by #2108.