-
-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
program not found
for corepack on Windows
#110
Comments
Interesting bug, I'm not very familiar with Corepack nor how it works so will have to dig more into this. Do you know how Corepack exposes package manager commands without having them registered in |
program not found
when package manager not in PATHprogram not found
for corepack on Windows
Apologies for the delay - I just got around to looking at it today and dug into some source code for corepack. I realised the culprit was not because of PATH, but because of how Rust handles commands on Windows. From the documentation on
This is potentially due to a CVE released earlier last year on undocumented behaviour of the underlying spawner. On the other hand, corepack uses I am not the Rust expert here, but I've seen some people mention |
Thanks for the dig deep here. I do not have access to a Windows machine so this might hard to fix and test for me. I'll try to setup a VM on my mac and see if I can reproduce the issue first. |
Thanks for this handy package! I have a monorepo set up with pnpm (side note: perhaps in addition to testing lock files to resolve the package manager, the program can prioritise the
packageManager
field inpackage.json
if it's defined?), but it's installed via corepack and not globally. Hence, when I runsherif --fix
, it's giving me an error.Is there any way to honour the corepack version in rust?
The text was updated successfully, but these errors were encountered: