Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

support corepack -g ls command #566

Open
gweesin opened this issue Sep 29, 2024 · 3 comments
Open

support corepack -g ls command #566

gweesin opened this issue Sep 29, 2024 · 3 comments

Comments

@gweesin
Copy link

gweesin commented Sep 29, 2024

related to #553

suggest adding a command like corepack -g ls to list all globally installed package managers' configurations. This would allow users to easily view the package managers available in their system and switch between them.

@aduh95
Copy link
Contributor

aduh95 commented Sep 29, 2024

What use case do you have in mind? I'm not sure I understand why it would matters which package managers are installed.

@gweesin
Copy link
Author

gweesin commented Sep 30, 2024

My colleague is experiencing an issue where downloading pnpm using corepack always returns a 302 error. I want to verify if I encounter the same problem when accessing pnpm. However, I've installed almost every version of pnpm, and I'm wondering if there's a command to query the installed versions(corepack -g ls but it doesn't exist). This would help me determine which specific version I need to test that I haven't installed yet.

As a side note, the http 302 issue was resolved for my colleague after upgrading to the latest corepack.

@styfle
Copy link
Member

styfle commented Sep 30, 2024

In that case, I would set the debug environment variable (DEBUG=corepack) to enable verbose logs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants