Offline workflow about corepack HOT 6 CLOSED

yeah, environment variables could work too. I think configuration files are more user-friendly (especially for users not super familiar with Unix systems or for Windows users), but env variables work especially if we have a really limited set of configuration options.

from corepack.

Implemented pmm pack & pmm hydrate + tests, along with the PMM_ENABLE_NETWORK environment value.

from corepack.

Of note, this would also enable private proxies & registries at no configuration cost: users would just have to fetch the tarballs themselves, using their preferred tools. Basic example:

wget https://user:[email protected]/yarn-1.22.4.tgz

from corepack.

cc @mmarchini

from corepack.

yeah, I think that works. Would it also be possible to have a global config file for pmm where we could set pmm to never download the package manager (useful for Docker images) or to always download without asking (useful for adventurous users on development environments), along other settings?

from corepack.

It could - one tricky thing with configuration variables is that .. well .. you need to load this configuration, and things get ever so slightly more complicated. Do you think keeping that as an environment variable would work? Something like:

PMM_FALLBACK_BEHAVIOR=<none|request|accept>

from corepack.