April 18, 2017 at 1:09 pm #520084
Hello, I am having difficulties with installation of ngide and creation & import of a angular project via webclipse. I don’t need both to work but would like one or the other. Do you have configuration/environment variables that can be defined to set the http/s proxy and path to certificates files?
1) When attempting to create a new angular project in webclipse the project wizard hangs waiting for: Angular CLI version “Loading list of versions…”
2) When importing an existing angular project in webclipse the terminal says “Downloading and extracting Node 7.4.0…” then a few minutes later “Download of Node 7.4.0 failed”
3) When attempting to instal ngide via “ngide install ~/toolbox/angular-ide” I get the following error1234567891011121314151617ngide install ~/toolbox/angular-ideInstalling Angular IDE in: /home/me/toolbox/angular-ide/home/me/toolbox/node-v7.9.0-linux-x64/lib/node_modules/angular-ide/node_modules/rx/dist/rx.js:77throw e;^SyntaxError: Unexpected end of JSON inputat JSON.parse (<anonymous>)at MapObservable.buffer$.map.buffer (/home/me/toolbox/node-v7.9.0-linux-x64/lib/node_modules/angular-ide/node_modules/mt-downloader/.dist/Utils.js:124:37)at MapObservable.selector (/home/me/toolbox/node-v7.9.0-linux-x64/lib/node_modules/angular-ide/node_modules/rx/dist/rx.js:5386:51)at MapObservable.selector (/home/me/toolbox/node-v7.9.0-linux-x64/lib/node_modules/angular-ide/node_modules/rx/dist/rx.js:5386:67)at /home/me/toolbox/node-v7.9.0-linux-x64/lib/node_modules/angular-ide/node_modules/rx/dist/rx.js:5386:67at tryCatcher (/home/me/toolbox/node-v7.9.0-linux-x64/lib/node_modules/angular-ide/node_modules/rx/dist/rx.js:63:31)at InnerObserver.next (/home/me/toolbox/node-v7.9.0-linux-x64/lib/node_modules/angular-ide/node_modules/rx/dist/rx.js:5407:43)at InnerObserver.Rx.internals.AbstractObserver.AbstractObserver.onNext (/home/twelvesb/toolbox/node-v7.9.0-linux-x64/lib/node_modules/angular-ide/node_modules/rx/dist/rx.js:1762:31)at InnerObserver.tryCatcher (/home/me/toolbox/node-v7.9.0-linux-x64/lib/node_modules/angular-ide/node_modules/rx/dist/rx.js:63:31)at AutoDetachObserverPrototype.next (/home/me/toolbox/node-v7.9.0-linux-x64/lib/node_modules/angular-ide/node_modules/rx/dist/rx.js:5883:51)
Hoops i have jumped through at this point:
1) set the http_proxy, https_proxy and ftp_proxy in my env.
2) imported self signed certificates using java keytool into the system keystore and truststore
3) configured npm for proxy and certs: Here is my .npmrc:12345678proxy=http://proxy-my.corp.com:80/https-proxy=http://proxy-my.corp.com:80/cafile=/usr/java/default/jre/lib/security/cacertsstrict-ssl=falseregistry=http://registry.npmjs.org/
4) confured eclipse for proxy and certs. At this point i can download, install from eclipse marketplace, get http updates in the webclipse dashboard so I know http/https and certs are working in eclipse:
ng: @angular/cli: 1.0.0
os: linux x64April 19, 2017 at 4:01 pm #520224
Thank you for writing in with this issue, and explaining the problem as well as your steps in so much detail.
The first thing to check, is whether you are on 2017 CI 4, because proxy fixes for our entire Angular tooling did go into this version – prior to that we did not work well behind a proxy. To confirm this, can you go to Window > Preferences > Webclipse and let us have the version and build Id? If it does not say CI 4, please update to this version and try again.
Our proxy support reads values from Eclipse’s proxy preferences and uses those same values to configure node, npm and the tooling that downloads these binaries in the first place. I believe the values in the .npmrc file could possibly override the values set by our internal tooling, so just to reduce the number of variables in this picture, you should remove the proxy settings in this file so that the configuration is in a single place. Of course, this would only help if you get to the point where node and npm have been successfully downloaded and now npm itself needs to run. As you stated, if Eclipse is able to install items from the marketplace, that would indicate that it does have the right settings and these should just work for the Angular tooling as well.
If none of these work, are there any additional details you can share about your proxy configuration that we could use to try and replicate your issue locally?