Is YARN_ENABLE_NETWORK a thing?

[sparrowt]

At the top of https://yarnpkg.com/configuration/yarnrc it says:

... most settings can also be defined through environment variables (at least for the simpler ones; arrays and objects aren't supported yet). To do this, just prefix the names and write them in snake case: YARN_CACHE_FOLDER will set the cache folder ...

so enableNetwork should become YARN_ENABLE_NETWORK.

However searching for this in quotes produces no results whatsoever (though I guess this post might show up eventually...!)

My question therefore is whether YARN_ENABLE_NETWORK is a valid environment variable which can be used to disable network access? e.g. by doing something like YARN_ENABLE_NETWORK=0 yarn install

[sparrowt]

P.S. I should've thought of this before but this simple test case suggests that it does work...

If I delete a package from .yarn/cache and then run:

YARN_ENABLE_NETWORK=0 yarn install

it seems to be refusing to go to the internet as I was hoping: 🎉

➤ YN0013: │ something@npm:1.2.3 can't be found in the cache and will be fetched from the remote registry
➤ YN0080: │ something@npm:1.2.3: Request to 'https://registry.yarnpkg.com/...' has been blocked because of your configuration settings

and build fails.

Whereas without setting that env var, it just fetches the missing package and build succeeds.

So I guess the answer is "yes" and it's just a bit strange that there were absolutely zero search results for it on the internet.

This discussion may remedy that in this case, though it might be helpful if https://yarnpkg.com/configuration/yarnrc included more of the resultant env var names for settings which might frequently be used in a temporary basis - e.g. most people wouldn't want enableNetwork: false in .yarnrc.yml but might want to enable it via an env var in CI.