Remove corepack tooling to install package managers #1527
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Corepack will no longer be bundled with Node.js starting with the 25.0.0 release. For this buildpack the Corepack tooling is not actually required to install a package manager, it was just a convenient alternative. It's simpler to just remove the tooling and switch to installing the requested package managers using the npm registry. This means developers can still choose to use Corepack tooling locally and this buildpack will respect their configuration via the `packageManager` field in `package.json`. [Node.js TSC Vote](nodejs/TSC#1697 (comment)) [Node.js v25.0.0 Release Notes](https://github.com/nodejs/node/releases/tag/v25.0.0) [Node.js v25.0.0 Corepack docs](https://nodejs.org/dist/latest/docs/api/corepack.html)
Signed-off-by: Colin Casey <[email protected]>
schneems
approved these changes
Jan 9, 2026
Contributor
schneems
left a comment
schneems
left a comment
There was a problem hiding this comment.
Not blocking, requested in chat: Can you write me a changelog entry for the heroku site that tells me what a customer should expect from their perspective?
i.e. if they were previously relying on this behavior what just works and what needs adjustment? Any likely failure modes? Anything they can do about them?
| VENDOR_PATH=$(get_yarn_path "$BUILD_DIR") | ||
|
|
||
| # if we're installing yarn via corepack we don't need to fail | ||
| # if we're installing yarn via packageManager we don't need to fail |
Contributor
There was a problem hiding this comment.
I think we're referencing the variable in the code which is snake case.
Suggested change
| # if we're installing yarn via packageManager we don't need to fail | |
| # if we're installing yarn via package_manager we don't need to fail |
Contributor
There was a problem hiding this comment.
Actually I think this refers to the packageManager field of the customer's app.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Corepack will no longer be bundled with Node.js starting with the 25.0.0 release. For this buildpack the Corepack tooling is not actually required to install a package manager, it was just a convenient alternative. It's simpler to just remove the tooling and switch to installing the requested package managers using the npm registry.
This means developers can still choose to use Corepack tooling locally and this buildpack will respect their configuration via the
packageManagerfield inpackage.json.Node.js TSC Vote
Node.js v25.0.0 Release Notes
Node.js v25.0.0 Corepack docs
W-20075541, W-20075528