NPM_MIRROR dont work with repo.yarn.com

[cangSDARM]

Internal Error: Error when performing the request to https://repo.yarnpkg.com/3.6.3/packages/yarnpkg-cli/bin/yarn.js; for troubleshooting help, see https://github.com/nodejs/corepack#troubleshooting

i configed COREPACK_NPM_REGISTRY in my process.env

[cangSDARM]

I don't understand what's the point of corepack (so many registry/repo/mirror need to be resolve)

[aduh95]

Can you set DEBUG=corepack in your env and share the commands you're trying and the output? Please refrain from sending screenshots, it makes it harder for e.g. folks using screen readers, instead copy/paste the output please.

[cangSDARM]

DEBUG="corepack" yarn install
2024-10-30T03:46:35.983Z corepack Installing [email protected] from https://repo.yarnpkg.com/3.6.3/packages/yarnpkg-cli/bin/yarn.js to C:\Users\Administrator\AppData\Local\node\corepack\corepack-10640-3bdb2582.cb621
Internal Error: Error when performing the request to https://repo.yarnpkg.com/3.6.3/packages/yarnpkg-cli/bin/yarn.js; for troubleshooting help, see https://github.com/nodejs/corepack#troubleshooting
    at ClientRequest.<anonymous> (C:\Users\Administrator\AppData\Roaming\nvm\v20.10.0\node_modules\corepack\dist\lib\corepack.cjs:42195:14)
    at ClientRequest.emit (node:events:514:28)
    at TLSSocket.socketErrorListener (node:_http_client:495:9)
    at TLSSocket.emit (node:events:514:28)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)

corepack -v
0.22.0

node -v
v20.10.0

seems like node didn't ship the latest corepack, and #67 (comment)

[aduh95]

You are using old versions of Node.js and Corepack, consider updating and report back if the problem still exists with up-to-date versions. Closing for now, let's reopen if necessary.

[cangSDARM]

If the problem with corepack is that it has to go with node, then isn't it IE (activeX) on the server side?

[aduh95]

It doesn't have to "go with node", whatever you mean by that; getting it alongside node is certainly the most common way for using Corepack, but it's not the only one.