-
Notifications
You must be signed in to change notification settings - Fork 132
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
'corepack prepare' does not read "packageManager" in package.json #96
Comments
Hey @arcanis I think fixing this introduced an issue that's worth resolving. If have the |
@kylemh I don't think this fix has been released yet, unless you have a configuration where you're running corepack from source. Keep in mind that, when defined, |
The docs for
|
I am installing in CI and using it from source because I'm on Node 14. What you're saying is totally fair, and I gathered as much... but only after a lot of investigation. There's nothing wrong with the logic, but the CLI logging offers no notice. I guess I'm suggesting that the config "winner" gets an announced in the output of a ran command. This isn't a question about docs either. I didn't go to corepack docs because I had no CLI errors or logging which indicated implicit behavior was intercepting my explicit command. |
The docs and comments indicate that
corepack prepare
should look at the package manager configured inpackage.json
and download it, but it currently doesn't.Repro
docker run --rm -it --entrypoint sh node:16.11.1-alpine3.14
echo '{"packageManager": "yarn@3.0.2"}' > package.json
ls ~/.node
doesn't exist (expected)corepack prepare
ls ~/.node
doesn't exist (unexpected)corepack yarn --version
(shows 3.0.2)ls ~/.node
does exist (expected)The text was updated successfully, but these errors were encountered: