btea/corepack

Corepack solves a common frustration for Node.js developers: managing different package managers. Think of it as a traffic cop that intercepts when you run yarn, npm, or pnpm commands and routes them to the right version for your project. The benefit is simple, you don't have to manually install and juggle multiple package manager versions across different projects on your computer. Here's how it works. When you try to run a package manager command in a folder, Corepack checks if that project has specified which manager it wants (via a packageManager field in package.json). If it has, Corepack automatically downloads and uses that exact version. If you try to use the wrong manager for a project (say, running npm install in a Yarn project), it politely tells you to switch. If the project doesn't specify a preference, Corepack falls back to sensible defaults it keeps cached on your machine. The whole thing runs without requiring any extra dependencies, it's built directly into recent Node.js versions. In practice, this is most useful for teams or open-source projects that want to enforce consistency. A Yarn project can guarantee that everyone working on it uses Yarn 3.2.3, not a different version that might produce different results. Individual developers benefit too, you can work on multiple projects with different package managers without conflicts. Corepack comes built-in with Node.js, so you typically just run corepack enable once and you're done. For projects that need it, you can also use Corepack offline or pre-package managers for containerized environments. The README doesn't detail the internal architecture, but the key tradeoff is simplicity: Corepack intentionally avoids runtime dependencies and stays lightweight so it can do its job without adding overhead to your workflow.