-
Notifications
You must be signed in to change notification settings - Fork 29.9k
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
not installed by default with Homebrew
#55366
Comments
Further BackgroundAfter doing a bit of research in the Homebrew repository, I can see the following:
Maybe this should instead be considered a bug in the Homebrew formula? (at least, from the perspective of the Node.js team). If I can get confirmation that this is considered a bug from the Node.js team, I will report a new separate issue in the Homebrew repository. |
Homebrew is compiling Node.js without corepack, hence it not being installed. That's certainly not an issue with Node.js, no? Report issues with the homebrew binary to homebrew. |
It's an issue with the Node.js Download docs, which recommend installing via Homebrew in two divergent ways:
This divergent behavior is a pretty confusing situation for users who are following official Node.js documentation. If Node.js wants to support Homebrew, and Homebrew has divergent behavior, then the Node.js Download page should add an additional command for the latest Node.js version (so that Corepack is also installed there): +brew install corepack Looks like a new PR should be done over here, in case Homebrew does not accept the issue below (which is likely, given historical responses to this issue):
Makes sense, reported again here: |
Since this was a pretty small PR, I opened it here: |
Version
v22.9.0
Platform
Subsystem
No response
What steps will reproduce the bug?
brew install node@22
(on macOS, with@22
version specifier recommended on download page, screenshot below)corepack enable
(as in the Corepack docs page)zsh: command not found: corepack
This also reproduces with no version specifier (
brew install node
)How often does it reproduce? Is there a required condition?
Always
What is the expected behavior? Why is that the expected behavior?
corepack
is installed and on PATHWhat do you see instead?
corepack
is not installedAdditional information
Encountering this bug, I thought that the decision had been made to remove Corepack from Node.js, as is being discussed in various PRs and issues:
yarn
andpnpm
Corepack binaries by default #51886The text was updated successfully, but these errors were encountered: