ERROR: spawn /Users/<username>/.cache/node/corepack/v1/pnpm/11.13.1/bin/pnpm.cjs EACCES

[miikaah]

When installing pnpm v11 via corepack the pnpm.cjs file lacks the execute permission.

This causes the ERROR: spawn /Users/<username>/.cache/node/corepack/v1/pnpm/11.13.1/bin/pnpm.cjs EACCES error when running an npm script with pnpm.

Running chmod +x /Users/<username>/.cache/node/corepack/v1/pnpm/11.13.1/bin/pnpm.cjs fixes it.

The CommonJS scripts don't have the execute permission in v11. Only the ES module scripts have it.

ls -al /Users/username/.cache/node/corepack/v1/pnpm/11.13.1/bin
total 32
drwxr-xr-x@  6 username  group   192 16 heinäkuuta  11:18 .
drwxr-xr-x@ 10 username  group   320 16 heinäkuuta  11:18 ..
-rw-r--r--@  1 username  group   105 26 lokakuuta    1985 pnpm.cjs
-rwxr-xr-x@  1 username  group  1464 26 lokakuuta    1985 pnpm.mjs
-rw-r--r--@  1 username  group   105 26 lokakuuta    1985 pnpx.cjs
-rwxr-xr-x@  1 username  group   127 26 lokakuuta    1985 pnpx.mjs

The v10 scripts had it

ls -al /Users/username/.cache/node/corepack/v1/pnpm/10.33.4/bin
total 16
drwxr-xr-x@ 4 username  group   128 16 kesäkuuta   11:11 .
drwxr-xr-x@ 8 username  group   256 16 kesäkuuta   11:11 ..
-rwxr-xr-x@ 1 username  group  1102 26 lokakuuta    1985 pnpm.cjs
-rwxr-xr-x@ 1 username  group   122 26 lokakuuta    1985 pnpx.cjs

I'm running MacOS Tahoe.

[MikeMcC399]

I don't have macOS, but when I looked on Ubuntu the permissions you listed are the same as with a global install of pnpm@11.13.1 without Corepack. Does your problem only occur when you use pnpm together with Corepack?

What about if you use a global installation of pnpm instead?

corepack disable pnpm
npm install pnpm@11.13.1 -g

If you see the issue without using Corepack, then you may need to log a regression issue on https://github.com/pnpm/pnpm/issues. I understood you to imply that it worked with pnpm@10 and stopped working with pnpm@11.

---

If your problem only occurs with Corepack, please provide some more information to allow the issue to be reproduced: for instance, a minimum package.json and commands to carry out which cause an error.

Please also confirm that you are using the latest version of Corepack (0.35.0) and provide logs running with the environment variable DEBUG set to corepack.

[miikaah]

Thanks for the quick response!

I understood you to imply that it worked with pnpm@10 and stopped working with pnpm@11.

You understood correctly. This only started happening once I upgraded pnpm to v11 in a CommonJS project. I also have another repository with pnpm v11, but it's an ES Module so I assume that's why it works.

What about if you use a global installation of pnpm instead?

Using a global install of pnpm from npm works without issues.

Upon further investigation this is happening with the npm package npm-run-all2 most likely because it spawns new child processes to run the scripts its given. Here is a repro repo: https://github.com/miikaah/pnpm-repro.

I am indeed using Corepack version 0.35.0. Running the repro with the debug flag prints stuff like this:

DEBUG=corepack pnpm test
corepack Checking /Users/username/repos/pnpm-repro/package.json +0ms
corepack Checking /Users/username/repos/pnpm-repro/.corepack.env +1ms
corepack No env file found at /Users/username/repos/pnpm-repro/.corepack.env +0ms
corepack /Users/username/repos/pnpm-repro/package.json defines pnpm@11.13.1 as local package manager +1ms
corepack Using pnpm@11.13.1 as defined in project manifest /Users/username/repos/pnpm-repro/package.json +0ms
corepack Reusing pnpm@11.13.1 found in /Users/username/.cache/node/corepack/v1/pnpm/11.13.1 +3ms
$ run-p script1 script2
ERROR: spawn /Users/username/.cache/node/corepack/v1/pnpm/11.13.1/bin/pnpm.cjs EACCES

[MikeMcC399]

Would you like to check if you have allowed public access to https://github.com/miikaah/pnpm-repro ? It looks like it may be set to private access.

[miikaah]

@MikeMcC399 I could swear it said the visibility was public when I created the new repo. Oh well, it should be public now!

[MikeMcC399]

@miikaah

Thanks for enabling access! I wasn't able to reproduce on Ubuntu, so this may be a macOS-only problem.

The https://github.com/miikaah/pnpm-repro has conflicting requirements at the moment.

Using .node-version of 22.14.0 displays a warning when attempting to install corepack@0.35.0

$ npm install corepack@0.35.0 -g
npm warn EBADENGINE Unsupported engine {
npm warn EBADENGINE   package: 'corepack@0.35.0',
npm warn EBADENGINE   required: { node: '^22.22.2 || ^24.15.0 || >=26.0.0' },
npm warn EBADENGINE   current: { node: 'v22.14.0', npm: '10.9.2' }
npm warn EBADENGINE }

changed 1 package in 715ms

[miikaah]

Ahh yes. It's probably because the package.json engines.node is set to 22 and I ran corepack enable pnpm before setting that. Removing that could allow to update to 0.35.0. Previously I was using corepack version 0.31.0. The error happens on both versions.

In any case, there's an easy workaround so you can close this if you'd like.

[MikeMcC399]

In any case, there's an easy workaround so you can close this if you'd like.

You might like to describe the workaround you mean, in case anyone else is facing this issue.

I'm not able to close the issue, as I only have Contributor status in this repo. I'm not actually a Maintainer here. So if you don't want any further investigation on the issue, you should be able to close it yourself with the button below ⬇️