Corepack NPM registry

[felipecrs]

Renovate uses Corepack instead of install-tool in some cases, like when the package.json in the repository has packageManager set with yarn > 2.

However, corepack won't respect settings like:

ENV URL_REPLACE_1_FROM=https://registry.npmjs.org
ENV URL_REPLACE_1_TO=https://npm.example.com

Which is understandable. Corepack only respects COREPACK_NPM_REGISTRY environment variable (nodejs/corepack#540):

ENV COREPACK_NPM_REGISTRY=https://npm.example.com

My feedback is:

1. Should containerbase somehow handle/abstract this?
2. If not, should this be documented?

Reproduction:

❯ docker run --rm -it ghcr.io/containerbase/base:13.25.18 bash
root@f4cfe2475db6:/# export CONTAINERBASE_DEBUG=1
root@f4cfe2475db6:/# export URL_REPLACE_1_FROM=https://registry.npmjs.org
root@f4cfe2475db6:/# export URL_REPLACE_1_TO=https://npm.example.com

root@f4cfe2475db6:/# install-tool node 24.12.0
[14:49:28.462] INFO (10): Install tool node succeeded in 15.4s.

root@f4cfe2475db6:/# install-tool corepack 0.34.5
[14:49:46.606] DEBUG (47): url replaced
    src: "https://registry.npmjs.org/"
    tgt: "https://npm.example.com/"
[14:49:47.647] INFO (47): Install tool corepack succeeded in 1.1s.

root@f4cfe2475db6:/# export DEBUG=corepack

root@f4cfe2475db6:/# corepack prepare pnpm
Preparing pnpm@*...
  corepack Installing pnpm@11.0.0-dev.1005 from https://registry.npmjs.org/pnpm/-/pnpm-11.0.0-dev.1005.tgz +0ms
  corepack Download and install of pnpm@11.0.0-dev.1005 is finished +0ms

root@f4cfe2475db6:/# export COREPACK_NPM_REGISTRY=https://npm.example.com

root@f4cfe2475db6:/# corepack prepare yarn
Preparing yarn@*...
  corepack Installing yarn@4.12.0 from https://npm.example.com/@yarnpkg/cli-dist/-/cli-dist-4.12.0.tgz +0ms
  corepack Download and install of yarn@4.12.0 is finished +0ms

[viceice]

not easily solvable in containerbase 🤔