Corepack is dead, and I'm scared

Summary

The video script discusses the demise of 'corpack', a feature in Node.js designed to streamline package manager usage across projects. Despite its popularity, corpack is being removed due to ongoing debates and technical concerns within the Node community. The decision has sparked controversy, with many developers viewing it as a step backward, especially for those who rely on alternative package managers like pnpm or yarn for complex setups. The video also touches on the Node team's evolving recommendations for package management and the importance of community engagement in such decisions.

Takeaways

• 📦 The script discusses the history and current state of npm and its attempts to standardize packaging solutions, highlighting the emergence of alternatives like pnpm, yarn, and bun.
• 🛠️ Corpac, a built-in solution in Node, allowed specifying a package manager and its version within a project, facilitating easier project hopping and open-source contributions.
• 😔 Corpac is now facing removal from Node, which is a significant setback for developers who relied on its convenience for managing different package managers across projects.
• 📝 The script mentions a heated debate within the Node community regarding the enabling of Corpac by default, which aimed to streamline the setup process for new developers.
• 🔄 The Technical Steering Committee (TSC) of Node confirmed they have no plans to remove npm from distribution, which is a key point since npm is bundled with Node by default.
• 🚫 The decision to remove Corpac from Node has been delegated to the package maintainers working group, who have outlined a roadmap for its eventual removal in the next major release.
• 🔄 The script points out the irony that the push to enable Corpac by default has led to its complete removal, contrary to the community's intentions.
• 🔧 The creator of pnpm, Zoltan, is now working on adding version management to pnpm independently, as Corpac's removal means reliance on it for version management is no longer viable.
• 🗂️ The Node download page is being updated to recommend installing Node via version managers and to provide instructions for installing other package managers like yarn and pnpm.
• 📖 Corpac's documentation will be moved out of the Node API docs to avoid confusion, as it is a separate project from Node.
• 👎 The decision to remove Corpac has faced significant pushback from the community, with many users expressing disappointment and concern over the impact on Node users and the ecosystem.

Q & A

Why was corac considered a valuable tool in the JavaScript ecosystem?

Corac was valuable because it allowed developers to specify a package manager and its version within a project, enabling seamless installation of the correct package manager and running it across different projects, which was particularly useful for monorepos and Windows environments.

What are some alternatives to npm that are mentioned in the script?

The script mentions bun, pnpm, and yarn as alternatives to npm that are considered to work better in terms of speed, reliability, and handling complex setups.

What was the original purpose of corac in the context of Node.js?

The original purpose of corac was to provide a solution for developers to use different package managers within their Node.js projects without having to manually configure each one, thus simplifying the process of managing dependencies.

Why is corac being removed from Node.js, according to the script?

Corac is being removed from Node.js due to a combination of technical and community-driven reasons, including concerns about reproducibility, security, and the fact that it was not as widely adopted as expected.

What is the significance of the 'corac by default' proposal that was discussed in the Node.js community?

The 'corac by default' proposal aimed to make it easier for developers to use Node.js with corac enabled, so they could simply run 'corac install' without additional configuration. This would have encouraged more projects to adopt corac and potentially reduced the reliance on npm.

What was the outcome of the discussions around 'corac by default' in the Node.js community?

The discussions around 'corac by default' led to the ironic outcome of corac being removed entirely from Node.js, instead of being enabled by default, due to various concerns and lack of consensus.

What are the implications of removing corac from Node.js for developers?

The removal of corac from Node.js implies that developers will need to manually configure and install the package manager of their choice for each project, which could increase complexity and reduce the ease of contributing to different projects.

What is the role of the Node.js TSC (Technical Steering Committee) in the decision regarding corac?

The TSC confirmed that they had no intention to remove npm from distribution, which indirectly influenced the decision around corac, as corac was seen as a potential replacement for npm in certain scenarios.

What steps are being taken to phase out corac from the Node.js distribution?

The steps include updating the Node.js download page to recommend version-managed installations, moving corac documentation out of the Node API docs, and eventually removing corac from the Node distribution in the next major release.

How can developers continue to use corac after it is removed from Node.js?

Developers can continue to use corac by following the instructions available on the Node download page or in the corac repository, as corac will still be available as a separate project from Node.

What is the sentiment among the community regarding the removal of corac from Node.js?

The sentiment is mixed, with some community members expressing disappointment and viewing the removal as a step backward, while others see it as an opportunity for corac to evolve independently and for the community to find alternative solutions.