kourosz last edited by
After some weeks of studying and testing Quasar at home, I’m going to propose this framework to a company I’m working for. I tried to run Quasar init <project name>, but I receive the following error:
i Generating Quasar App…
x Failed to download App template @quasarframework/app-template-default: Error: tunneling socket could not be established, cause=write EPROTO 101057795:error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol:openssl\ssl\s23_clnt.c:794:
There is a proxy in our network and npm has been configured to use it (and it works fine). Also the variables http_proxy and https_proxy have been added to the Environment variables in a MS Windows 8 machine.
Can I do something to fix this issue?
Great to hear you are recommending Quasar! It needs to be said though, the API is still evolving and won’t be “BC fixed” until version 1.0 is released. Please also take that into account.
I found an issue fairly similar to yours and this links to what seems to be a possible solution. https://github.com/jspm/github/issues/59#issuecomment-167107576
Since it seems to be a settings iisue, we’ll need to find the right ones for you. That is about all we can do.
quasar initbasically does is that it downloads app-template-default repo (https://github.com/quasarframework/app-template-default) and copies the /template folder to the destination you are indicating. Nothing more. Unfortunately, the download is made through
download-github-repopackage which seems to not take into account http proxies. Will search for a replacement or write our own package.
And thanks for recommending Quasar!
Sorry about that. I should have looked deeper.
How about this Razvan? https://github.com/bearjaws/node-wget
Seems to take proxies into account. I’ll make an issue in the CLI and work on this.
Ok Scott. Let’s see how it goes.