I found the reason. The process “quasar” does not use the proxy settings from the .npmrc file, it uses the environment variable “http_proxy” (I have only checked it under Windows). The syntax corresponds to the syntax of the .npmrc file.

I found the reason. The process “quasar” does not use the proxy settings from the .npmrc file, it uses the environment variable “http_proxy” (I have only checked it under Windows). The syntax corresponds to the syntax of the .npmrc file.

I have the same issue. The proxy server is configured, the data in the .npmrc seems correct to me.

proxy=http://<ip of proxy server>:8080/
http-proxy=http://<ip of proxy server>:8080
https-proxy=http://<ip of proxy server>:8080/

The installation of “npm install -g @quasar/cli” ran smoothly, but

C:\Users\dev>quasar create test001

 / _ \ _   _  __ _ ___  __ _ _ __
| | | | | | |/ _` / __|/ _` | '__|
| |_| | |_| | (_| \__ \ (_| | |
 \__\_\\__,_|\__,_|___/\__,_|_|

  Quasar CLI · Failed to download repo quasarframework/quasar-starter-kit#master: tunneling socket could not be established, cause=getaddrinfo ENOTFOUND 8080

Does anyone have an idea?
Thx