'corepack use pnpm' installs faulty pnpm@11.0.0-dev.1005 resulting in MODULE_NOT_FOUND #772

Activity

1. tkesici commented on Nov 24, 2025

   

   tkesici

   on Nov 24, 2025

   Author

   More actions

   After some discussion on the pnpm issue (pnpm/pnpm#10214), it turns out the problem is not caused by a faulty pnpm release, pnpm v11 has changed its binary entry path from bin/pnpm.cjs to bin/pnpm.mjs., so the development build 11.0.0-dev.1005 is not faulty. Corepack is expecting the old path and fails.

   So the issue appears to be:

   • Corepack’s version resolution prefers a dev build over the latest stable
   • Corepack seems to rely on a hardcoded pnpm binary path instead of reading the correct bin path from package.json.

   As a workaround I'm currently using corepack use pnpm@10.22.0 or corepack use pnpm@latest (or latest-9, latest-10 etc.)

   Leaving this update here so the root cause is clearer.
2. tkesici commented on Nov 24, 2025

   

   tkesici

   on Nov 24, 2025

   Author

   More actions

   Closing this issue since the root causes are now split into two issues:

   • Corepack incorrectly selects prerelease/dev versions of pnpm when no version is specified #774
   • Corepack hardcodes pnpm binary path instead of reading package.json bin field (breaks with pnpm v11) #775
3. tkesici

   closed this as completedon Nov 24, 2025
4. aduh95

   reopened this on Nov 24, 2025
5. aduh95

   closed this as completedin #776on Nov 24, 2025