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

fix: corepack proxy #35

Merged
merged 2 commits into from
Apr 19, 2024
Merged

fix: corepack proxy #35

merged 2 commits into from
Apr 19, 2024

Conversation

SyMind
Copy link
Collaborator

@SyMind SyMind commented Apr 19, 2024

Install latest corepack to install package manager behind a corporative proxy.

As of Corepack 0.26.0, we're now using proxy-from-env. It should not require anything to install on your end, only setting env variable AFAIK (so HTTPS_PROXY, or ALL_PROXY). I recommend opening a new issue if you're need more help.

From: nodejs/corepack#67 (comment)

But when i installed [email protected] it is not working. You can reference the related bug report here: nodejs/corepack#451 .

So we should lock corepack with 0.24.1 version.

@SyMind SyMind force-pushed the fix-corepack-proxy branch from c55379b to ec153ec Compare April 19, 2024 03:30
@SyMind SyMind force-pushed the fix-corepack-proxy branch from ec153ec to a88b03d Compare April 19, 2024 03:38
@SyMind SyMind force-pushed the fix-corepack-proxy branch 3 times, most recently from 02f44d1 to a88b03d Compare April 19, 2024 04:15
@SyMind SyMind force-pushed the fix-corepack-proxy branch 4 times, most recently from 1bc18c2 to 86bf3c2 Compare April 19, 2024 05:50
@SyMind SyMind merged commit 28f0e26 into main Apr 19, 2024
17 of 19 checks passed
@SyMind SyMind deleted the fix-corepack-proxy branch April 19, 2024 06:09
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

Successfully merging this pull request may close these issues.

3 participants