Could we support `corepack enable --yes`? about node

[Mr-Python-in-China]

You may need https://github.com/nodejs/corepack/blob/a62cd7b977a71a534ef8fb01cbfe944b59162b22/README.md#environment-variables COREPACK_ENABLE_DOWNLOAD_PROMPT

[Kolobamanacas]

@VobileLiuZhiwu Can someone from the team rationalize the not planned decision please? The corepack seems to be the future standard approach of dealing with package managers. And it works fine and well, but today for example I was fixing a bug in our dockerized Yarn v4.1.1 Nest application and I needed to run integration tests dozens times and instead of re-running just one command as I did before, I now need to type y and press Enter as additional step for every container build. I'm aware that my application require some stuff downloaded, including packages in node_modules and package manager. Why would I need to confirm it on every run?

[Kolobamanacas]

@Mr-Python-in-China I've tested both values (0 and 1) of COREPACK_ENABLE_DOWNLOAD_PROMPT key. It doesn't remove prompt when downloading yarn.

[VobileLiuZhiwu]

@Mr-Python-in-China I've tested both values (0 and 1) of COREPACK_ENABLE_DOWNLOAD_PROMPT key. It doesn't remove prompt when downloading yarn.

@Kolobamanacas Hi, this command works for me, u could try it.

export COREPACK_ENABLE_DOWNLOAD_PROMPT=0 && corepack enable && yarn -v

[Mr-Python-in-China]

@Mr-Python-in-China I've tested both values (0 and 1) of COREPACK_ENABLE_DOWNLOAD_PROMPT key. It doesn't remove prompt when downloading yarn.

You can try to run corepack yarn. It works for me.