Repository navigation
npm install -g corepack enables Corepack #686
Description
Situation
If Corepack is installed globally using npm, as documented in the README > Manual Installs section using
npm install -g corepackthen Corepack behaves as if corepack enable had been executed.
This differs from how Corepack behaves when it is installed together with Node.js as a bundled component. In this case Corepack is not enabled by default.
The difference between defaults of Corepack being enabled or not, depending on how Corepack is installed, is not documented in the README, neither under the Manual Installs section, nor under the corepack enable section.
Suggestion
Add the information to the README document that using npm install -g corepack effectively executes corepack enable.
Activity
MikeMcC399 commentedon Mar 23, 2025
The documentation should also mention that if you had previously selectively enabled Corepack based on a Node.js installation for any individual package manager, then installing with npm enables Corepack for all eligible package managers. It overrides any previous selection.
For example
results in both Yarn and pnpm being enabled.
ljharb commentedon Mar 24, 2025
It's also frustrating there's no reliable/explicit way to determine if corepack is enabled or not.
MikeMcC399 commentedon Mar 24, 2025
@ljharb
I have also found that to be an issue working in a hybrid desktop environment where I need to enable and disable Corepack. I end up just calling
corepack enable/corepack disableblindly, not knowing what the existing status is. Probably this should be a separate topic to add acorepack statuscommand or similar.MikeMcC399 commentedon Apr 8, 2025