Skip to content

chore(deps): update dependency @cloudflare/vitest-pool-workers to v0.21.1 - #6897

Merged
eric-zaharia merged 1 commit into
chore/renovateBaseBranchfrom
renovate/cloudflare-vitest-pool-workers-0.x
Aug 14, 2026
Merged

eric-zaharia merged 1 commit into
chore/renovateBaseBranchfrom
renovate/cloudflare-vitest-pool-workers-0.x

Conversation

@renovate

@renovate renovate Bot commented Aug 14, 2026 •

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
@cloudflare/vitest-pool-workers (source) 0.21.0 β†’ 0.21.1 age confidence

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Release Notes

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

v0.21.1

Compare Source

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


Configuration

πŸ“… Schedule: (in timezone Europe/Paris)

  • Branch creation
    • "after 4pm on friday,before 9am on monday,every weekend"
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

β™» Rebasing: Whenever PR is behind base branch, 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 requested a review from a team as a code owner August 14, 2026 19:40
@renovate
renovate Bot requested review from Fluf22 and eric-zaharia and removed request for a team August 14, 2026 19:40
@algolia-api-clients-automation-bot

algolia-api-clients-automation-bot Bot commented Aug 14, 2026 •

Copy link
Copy Markdown
Contributor

βœ”οΈ Code generated!

Name Link
πŸͺ“ Triggered by 68d3023c7d2a5163bc21b1d4816ae439a6c4cea8
πŸƒ Generated commit e9eb0533b14a81fc7e67004520fffae3fa590b05
🌲 Generated branch generated/renovate/cloudflare-vitest-pool-workers-0.x
πŸ“Š Benchmark results

Benchmarks performed on the method using a mock server, the results might not reflect the real-world performance.

Language Req/s
javascript 2229

@renovate
renovate Bot force-pushed the renovate/cloudflare-vitest-pool-workers-0.x branch from 5c8cbfb to b73a731 Compare August 14, 2026 19:44
@eric-zaharia
eric-zaharia merged commit eb8a3de into chore/renovateBaseBranch Aug 14, 2026
15 checks passed
@eric-zaharia
eric-zaharia deleted the renovate/cloudflare-vitest-pool-workers-0.x branch August 14, 2026 20:01
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.

1 participant