Feature Request: corepack info
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 3.8k
- Forks
- 279
- Avg merge
- 1h 47m
- Merged PRs (30d)
- 2
Description
Feature Request: corepack info
Running corepack info should result in a listing describing what corepack knows about the local directory and how discovered, and then the same information about the global environment
contrived example (created in a pre-caffeinated environment)
$ corepack info
corepack report:
node version: 16.8.0, npm version: 7.21.0
local package manager [via package.json]: yarn@3.2.0
global package manager [via ~/.yarnrc]: yarn@3.2.0
available package managers: yarn@1.22.19, yarn@3.2.0
install directory: /usr/local/bin/corepack
Why?
I've got the package managers lined up and working as described - but when I run docker-compose build I get yarn@1.22.19 -- and I can't figure out why...
Note:
I don't understand exactly, but that's not the install directory... it's what which corepack returns - but the real install directory is here: /usr/local/Cellar/corepack/0.14.0/libexec/lib/node_modules/corepack (installed via brew on a Mac)
I'm trying to disable yarn@1.22.19 but I can't, I think I can only disable yarn and then reactivate yarn@3.2.0
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 files, tests, or entry points, so first locate the corepack CLI handling for local and global package-manager discovery. Done means corepack info reports the requested Node and package-manager details, explains how each was discovered, and distinguishes available versions and installation information.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, typescript
- Domain
- cli, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100