How to update/upgrade from older version?
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 3.8k
- Forks
- 279
- Avg merge
- 1h 47m
- Merged PRs (30d)
- 2
Description
I am using yarn 1.22.19 with node 14.19.1 (actually using nvm to be able to use multiple node versions, but I'm not sure this is important here). I assume yarn installed corepack 0.10.0, because I definitely didn't install it manually myself.
How can I upgrade to the latest version 0.13.0? Do I need to uninstall yarn first? I tried with npm and it fails with the following error:
npm WARN rm not removing /home/digeomel/.nvm/versions/node/v14.19.1/bin/yarn as it wasn't installed by /home/digeomel/.nvm/versions/node/v14.19.1/lib/node_modules/corepack
npm WARN rm not removing /home/digeomel/.nvm/versions/node/v14.19.1/bin/yarnpkg as it wasn't installed by /home/digeomel/.nvm/versions/node/v14.19.1/lib/node_modules/corepack
npm ERR! code EEXIST
npm ERR! path /home/digeomel/.nvm/versions/node/v14.19.1/bin/corepack
npm ERR! Refusing to delete /home/digeomel/.nvm/versions/node/v14.19.1/bin/corepack: ../lib/node_modules/corepack/dist/corepack.js symlink target is not controlled by npm /home/digeomel/.nvm/versions/node/v14.19.1/lib/node_modules/corepack
npm ERR! File exists: /home/digeomel/.nvm/versions/node/v14.19.1/bin/corepack
npm ERR! Remove the existing file and try again, or run npm
npm ERR! with --force to overwrite files recklessly.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no repository files, tests, or entry points. Start by reproducing the npm/Corepack installation error with Node 14.19.1 and Yarn 1.22.19; done means documenting a verified upgrade path to Corepack 0.13.0.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js
- Domain
- cli, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100