Zoltan Kochan

This might be related: https://github.com/pnpm/pnpm/pull/4020 pnpm was not setting `scripts-prepend-node-path` and it is set to true by default. So the scripts were executed using the Node.js environment that executed the...

Try with pnpm v6.23.1

What command were you running?

I can't find any code that runs chmod on those files. The exec files get the executable permission when they get unpacked to the global content-addressable store. After that, they...

This may be related: https://github.com/pnpm/pnpm/issues/2343#issuecomment-893486787 >I had an issue where [email protected]/node_modules/mkdirp/bin/cmd.js ended up with root:wheel ownership. That caused me to get ERROR  EPERM: operation not permitted, chmod '/path/to/my/project/node_modules/mkdirp/bin/cmd.js' when attempting...

It might be possible. Can we make the store readonly?

Looks like on Linux a hard link is created even if the user has no permissions to the file. All these errors happened with bin files, which are read only...

Is it consistently happening with `[email protected]`? Even if you remove the store completely?

OK, that is good. Then probably someone with a mac can investigate this.

I can't reproduce this issue on Windows.