How to corepack self update?

How should I update the version of corepack?

Since corepack is installed system-wide with Node, it's likely that existing installations (like my Windows machine) will have outdated versions.

For example, the LTS Node installer installs 0.18.0 but the latest version is 0.20.0 and has commands that don't exist in previous versions.

A couple options:

Edit $PATH so the C:\Users\dan\AppData\Roaming\npm comes before C:\Program Files\nodejs and npm install --global corepack
Alias corepack='npx corepack@latest' in my shell profile.
Use a package manager to overwrite the global corepack: cd 'C:\Program Files\nodejs'; npm install corepack@latest --prefix .
Don't install corepack using the Node installer. Instead npm install --global corepack

I think just running npm install --global corepack@latest is fine which will replace the symlink to the corepack binary shipped with the node installation? Maybe not on Windows 🤷🏻‍♂️

No, on Windows it is not working

@rotu

The first workaround offered by @rotu works well on windows if corepack is already installed through your nodejs install, though you may have to move the path of nodejs from system to user variables.

The preferred option is to use the Corepack version that is distributed along with Node.js itself. So if you want to update Corepack, you can update your Node.js version. 😃

No, on Windows it is not working

It does work on Windows 11. This is what I've used to workaround these issues:

Newly published versions of package managers distributed from npm cannot be installed due to key id mismatch #612 (comment)
Cannot install pnpm with corepack: corepack use pnpm@latest-x pnpm/pnpm#9029 (comment)

node -v
# v22.13.1

corepack -v
# 0.30.0

npm install -g corepack@latest
# changed 1 package in 463ms

corepack -v
# 0.31.0

No, on Windows it is not working

It does work on Windows 11. This is what I've used to workaround these issues:

Newly published versions of package managers distributed from npm cannot be installed due to key id mismatch #612 (comment)

Cannot install pnpm with corepack: corepack use pnpm@latest-x pnpm/pnpm#9029 (comment)

node -v

v22.13.1

corepack -v

0.30.0

npm install -g corepack@latest

changed 1 package in 463ms

corepack -v

0.31.0

This did not work for me. I had to uninstall NodeJS and then reinstall it, making sure to disable the corepack integration in the installer. After it was reinstalled without corepack, I could manage corepack via npm. Hopefully this helps someone out.

Just checked updating:

Still don't work. Also checked in new instance of CMD

W11 24h2
Nodejs 23.6, installed with default options from msi package

@inoyakaigor

@inoyakaigor

As @trevor-hackett described, you need to disable the "corepack manager" feature if you installed Node.js using a Windows msi package and you want to update the version of Corepack.

You can access this through Windows Settings > Apps > Installed Apps
Select Node.js and then Modify

Then if you execute

npm install -g corepack@latest

it will install Corepack globally and Windows will not have two different versions of Corepack installed - one from msi and another from npm.

I would like to suggest adding an "Updating Corepack" section to the README to describe how to update Corepack after installing Node.js according to any of the methods described on the Download Node.js page.

See docs: add instructions to update corepack #637 for documentation update suggestion

Please check the updated Corepack Manual Installs section which includes additional advice for dealing with Windows Installer .msi installations when manually updating with npm:

@MikeMcC399

@MikeMcC399 I don't get it. Please point me where I wrong.
Previously I have installed corepack with Nodejs. After the latest discussions I've deinstalled Nodejs and installed the latest 23.7.0 with uncheked the "corepack" checkbox. Then I've ran npm i -g corepack
Executed corepack enable and corepack use yarn@1.22.22 at my project's folder.

At this point I'm expecting that everything will work as previously with as Nodejs has installed within Corepack. But it doesn't.

I'm getting an error:

The path node_modules/corepack/dist/yarn.js I found in C:\Program Files\nodejs\yarn.ps1 that starts by C:\Program Files\nodejs\yarn.CMD

Am I reinstalled corepack wrong or something else?

@inoyakaigor

@inoyakaigor

Could you please open a separate issue for this? You have discovered a different issue working with Node.js msi.

This issue is closed, so it is not a good place to be looking at a new problem.

If you open a new issue I can give you some tips about what you should do next.

@inoyakaigor

@inoyakaigor

The short version of the advice to you is as follows, since Node.js 23.7.0 already has the fix:

npm uninstall -g corepack
Modify the Node.js msi app and Change "corepack manager" to "Will be installed on local drive"

If you want more detail, then please open a new issue.

See also Node.js uninstall Windows Installer .msi leaves stranded Corepack files #646

Navigation Menu

Repository navigation

How to corepack self update? #305

v22.13.1

0.30.0

changed 1 package in 463ms

0.31.0

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

How to corepack self update? #305

Description

Activity

simonhaenisch commented on Oct 24, 2023

inoyakaigor commented on Oct 31, 2023

gskyu commented on Mar 21, 2024

codersjj commented on Jan 18, 2025

hyunbinseo commented on Feb 6, 2025

trevor-hackett commented on Feb 6, 2025

v22.13.1

0.30.0

changed 1 package in 463ms

0.31.0

MikeMcC399 commented on Feb 7, 2025

inoyakaigor commented on Feb 7, 2025

MikeMcC399 commented on Feb 7, 2025

MikeMcC399 commented on Feb 7, 2025

MikeMcC399 commented on Feb 7, 2025

MikeMcC399 commented on Feb 7, 2025

inoyakaigor commented on Feb 10, 2025

MikeMcC399 commented on Feb 10, 2025

MikeMcC399 commented on Feb 10, 2025

MikeMcC399 commented on Feb 11, 2025

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions