Add brew install corepack for current / pending releases

[karlhorky]

Description

As reported in the issues below, Homebrew installation behavior is divergent with the latest releases and the older releases:

• corepack not installed by default with Homebrew node#55366
• corepack installed with node@20 but not with node@22 Homebrew/homebrew-core#193982

The short version is this:

• brew install node@22: corepack not installed
• brew install node@20 and older: corepack installed

Homebrew currently expects users to install Corepack separately with brew install corepack:

• corepack not installed with formula node Homebrew/homebrew-core#151439 (comment)

After this PR, brew install corepack is printed for releases with a .status of Current or Pending:

Node.js v22 (note the new line brew install corepack)

Node.js v20

Validation

Read into the issues above to validate the documented behavior of Homebrew.

Related Issues

Already linked above

Check List

• I have read the Contributing Guidelines and made commit messages that follow the guideline.
• I have run npm run format to ensure the code follows the style guide.
• I have run npm run test to check if all tests are passing.
• I have run npx turbo build to check if the website builds without errors.
• I've covered new added functionality with unit tests if necessary.

cc @aduh95

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
nodejs-org	✅ Ready (Inspect)	Visit Preview	Oct 12, 2024 4:18pm

[avivkeller]

Users may not need/want to install corepack, so maybe just add a comment that explains that corepack is not distributed with the bundle?

[ovflowd]

I'm not a fan that Homebrew is intentionally changing how Node is installed (https://github.com/Homebrew/homebrew-core/blob/master/Formula/n/node.rb#L68-L88) by building Node natively and intentionally removing features.

At the same time, I cannot endorse manual extra steps to be added on our side on the downloads page. This must be resolved on Heombrew's side, and I'll report there and ask them to please not change the expected way people expect Node to perform across environments.

Unfortunately I don't think this change should land here, and I would discourage this as a fix.

[karlhorky]

Sounds good, understood and agreed that Homebrew's divergent behavior seems unexpected and incorrect.

Closing.