Open emanuel-minetti opened 2 years ago
also in v5.0.4, request was replaced by node-fetch and i think this lib is ignoring http(s)_proxy env vars. in vue-cli 4 it worked with the env vars.
same problem in v5.0.4
5.0.7, still doesn't work
I'm facing the exact same issue with @vue/cli 5.0.8 & Node 18.14.0 & npm 9.3.1. The error messages are exactly the same:
ERROR Failed to get response from https://registry.npmjs.org/@vue/cli-plugin-babel ERROR FetchError: request to https://registry.npmjs.org/@vue/cli-plugin-babel failed, reason: connect ETIMEDOUT 104.16.22.35:443
Version
5.0.1
Environment info
Steps to reproduce
Use
vue upgrade
behind a corporate firewall with proxyWhat is expected?
Vue-cli should upgrade the project
What is actually happening?
Running
vue upgrade
gives:✔ Gathering package information... ERROR Failed to get response from https://registry.npmjs.org/@vue/cli-plugin-babel ERROR FetchError: request to https://registry.npmjs.org/@vue/cli-plugin-babel failed, reason: connect ETIMEDOUT 104.16.22.35:443 FetchError: request to https://registry.npmjs.org/@vue/cli-plugin-babel failed, reason: connect ETIMEDOUT 104.16.22.35:443 at ClientRequest. (C:\Users\dvorg22\AppData\Roaming\npm\node_modules\@vue\cli\node_modules\node-fetch\lib\index.js:1491:11)
at ClientRequest.emit (node:events:390:28)
at TLSSocket.socketErrorListener (node:_http_client:447:9)
at TLSSocket.emit (node:events:390:28)
at emitErrorNT (node:internal/streams/destroy:157:8)
at emitErrorCloseNT (node:internal/streams/destroy:122:3)
at processTicksAndRejections (node:internal/process/task_queues:83:21)
npm update
is working as expected. Runningvue --version
gives: @vue/cli 5.0.1