Using Corepack
Corepack is Node.js’s package-manager manager. It sits at the top of the local tooling hierarchy and pins which package manager (pnpm, Yarn, …) a project uses so every clone gets the same one.
Before you continue, skim Tool hierarchy for how programs, packages, package managers, and Corepack relate.
Why use Corepack?
The default Node package manager (npm) copies package files into each project on install, which wastes disk. Prefer pnpm: it stores packages once in a central store and links them into the project. Those links stay local and are not uploaded to GitHub (pnpm typically adds its store path to .gitignore).
Corepack (Node.js Corepack docs) is the tool that enables and selects that package manager from project settings. It has been experimental; enable it after installing Node.js, then follow the workflows below.
Preparation
Due to an issue with outdated signatures in Corepack, update Corepack first:
npm install --global corepack@latestLeader workflow
If you create or own the project, run as Admin in the project folder:
corepack enableSet the desired package manager (examples):
corepack use pnpm@latest
corepack use pnpm@latest-10
corepack use [email protected]
corepack use [email protected]
corepack use yarn@stable
Replace this placeholder with an updated image showing Corepack installation options and prompts for corepack enable and corepack use.
|