Node.js TSC Votes to Stop Distributing Corepack

The Node.js Technical Steering Committee (TSC) has officially voted to stop distributing Corepack with future versions of Node.js. The decision, made via an encrypted ballot, will impact future releases of Node.js (i.e. 25+), though Corepack will remain available in Node.js 24 and earlier as an experimental feature.

The Role of Corepack in Node.js#

Corepack was introduced in Node.js version 16.9.0 as an experimental tool to bridge the gap between different package managers. It provided a way for users to install and manage package managers like Yarn and pnpm directly via Node.js, without needing to install them separately. This made it easier for projects to enforce a specific package manager version without requiring developers to manually install it.

However, despite its potential, Corepack faced several hurdles. Many developers were unaware of its existence or misunderstood its purpose, leading to adoption struggles. Additionally, its integration into the Node.js distribution was questioned, as package managers typically function independently of the runtime.

The Road to Corepack's Removal#

The discussion around Corepack’s removal has been ongoing for years. In November 2023, a proposal was made to enable Corepack by default, sparking debate within the Node.js community. The discussion intensified in February 2024, particularly around concerns that Corepack could be used as a way to decouple npm from Node.js releases. By March, the TSC clarified that there were no plans to remove npm from the Node.js distribution, but Corepack’s future remained uncertain.

The TSC delegated Corepack-related decisions to the Package Maintenance Working Group (PMWG), which then outlined a roadmap for its removal. The key steps included:

• Revising the Node.js download page to emphasize version managers like nvm and fnm.
• Moving Corepack’s documentation out of the Node.js API docs and into its own repository.
• Removing Corepack from the Node.js distribution starting with the next major release.

The roadmap received strong support within the PMWG, paving the way for the final vote that confirmed Corepack’s removal.

Why Is Corepack Being Removed?#

The TSC vote reflected a preference for phasing out Corepack rather than keeping it bundled with Node.js. The winning proposal—"Phase out later"—ensures that Corepack will no longer be distributed with future Node.js releases, while keeping it in Node.js 24 as an experimental feature. Other proposals, including keeping Corepack in Node.js but disabling it by default, failed to gain enough support.

Key Reasons for the Decision:

• Lack of widespread adoption: Many developers and teams continued to use their preferred package manager installations, bypassing Corepack entirely.
• Distribution concerns: Corepack’s inclusion in the Node.js binary was seen as an unnecessary bundling of a tool that could be installed separately.
• Long-term maintenance: Removing Corepack from the Node.js distribution allows package managers to evolve independently without requiring changes in Node.js itself.

Reactions from the Community#

The decision to remove Corepack has been met with mixed reactions. Some developers see it as a necessary step to simplify Node.js, while others feel it is a regression. Corepack has been particularly useful for those who avoid npm due to its performance and reliability concerns.

“I've been using pnpm exclusively through Corepack,” one developer commented on last year's proposal to remove it. “Forcing people to use npm to install the package manager they actually want to use is a terrible step backwards.”

Others, including Node.js maintainers, contend that Corepack was never meant to be a permanent part of the runtime and is better maintained separately.

What Happens Next?#

While Corepack will no longer be bundled with Node.js in future releases, it will remain available as a separate installation. Developers who relied on Corepack’s functionality will need to manually install it using:

npm install -g corepack

For projects using Corepack to manage package managers, updating documentation and workflows will be necessary to ensure smooth transitions.

To clarify, the vote does not define Corepack’s deprecation status—only its removal from the Node.js distribution. There are no current plans to deprecate Corepack, and it will continue to be maintained at least as long as Node.js 24.x is not end-of-life (EOL).

Historical Context: Node.js and Package Managers#

This decision is reminiscent of past debates in the Node.js ecosystem about what should or shouldn’t be included in the core distribution. Similar discussions arose around bundled dependencies like npm, which has historically shipped with Node.js but has undergone significant changes, including the introduction of alternative package managers like Yarn and pnpm.

The removal of Corepack marks a shift towards a leaner Node.js distribution, reinforcing the idea that package managers should remain decoupled from the runtime itself. This move aligns with trends in other ecosystems, where runtimes focus on core functionality while package managers operate independently.

For developers, the key takeaway is to prepare for Corepack’s removal by ensuring their workflows don’t depend on it being pre-installed in future Node.js releases.