[create-cloudflare] Disable pnpm self-provisioning in framework E2E - #14955
Conversation
|
|
The repo is on Vitest 4.1.0. As confirmed by the docs, Let me assess whether there's a real functional concern. The stated goal is to check if concurrent pnpm-version provisioning causes the Nuxt failures. The change makes only Nuxt tests sequential. That is exactly what the code does. No logic bug. I've evaluated:
No actionable issues. LGTM |
@cloudflare/autoconfig
@cloudflare/build-output-utils
@cloudflare/config
create-cloudflare
@cloudflare/deploy-helpers
@cloudflare/kv-asset-handler
miniflare
@cloudflare/pages-functions
@cloudflare/pages-shared
@cloudflare/unenv-preset
@cloudflare/vite-plugin
@cloudflare/vitest-pool-workers
@cloudflare/workers-auth
@cloudflare/workers-editor-shared
@cloudflare/workers-utils
wrangler
commit: |
|
Codeowners approval required for this PR:
Show detailed file reviewers |
workers-devprod
left a comment
There was a problem hiding this comment.
Codeowners reviews satisfied
Framework generators may write a pnpm version to their generated
packageManagerfield that differs from the C3 E2E matrix version. pnpm then downloads and runs that version. When concurrent framework tests provision it through the same pnpm tool store, provisioning can recurse until Node fails withERANGE: uv_cwd.Disable automatic package-manager version provisioning only for the framework E2E run. This keeps concurrent framework coverage while avoiding shared pnpm tool-store mutation. Other C3 E2E jobs retain their existing behavior.
This addresses the failure reproduced consistently across attempts 2–6 of #14924.
A picture of a cute animal (not mandatory, but encouraged)