Angular-cli: --proxy-config option missing in new ng e2e

Created on 13 Apr 2018 · 5Comments · Source: angular/angular-cli

Versions

cli 6.0.0-rc.4

Repro steps

npm i @angular/cli@next -g
ng new helloworld
add --proxy-config proxy.config.json to npm e2e script in package.json
cd helloworld
npm run e2e

Observed behavior

Unknown option: '--proxyConfig'

Desired behavior

ng e2e should continue to support a proxy config as before.

Mention any other details that might be useful (optional)

Works with ng serve.

Source

cyrilletuzi

👍5

Most helpful comment

Looks like ng e2e is now taking options directly from ng serve options. For info, you need to config your angular.json like this:

"serve": {
  "options": {
    "browserTarget": "appname:build",
    "proxyConfig": "proxy.conf.json"
   }
}

cyrilletuzi on 13 Apr 2018

👍10

All 5 comments

Looks like ng e2e is now taking options directly from ng serve options. For info, you need to config your angular.json like this:

"serve": {
  "options": {
    "browserTarget": "appname:build",
    "proxyConfig": "proxy.conf.json"
   }
}

cyrilletuzi on 13 Apr 2018

👍10

Hi @cyrilletuzi
I am not sure about latest version of Angular CLI, but in version 1.6.5 you can add a proxy to protractor by a command line like this:
(package.json)
"e2e": "ng e2e --proxy-config proxy.conf.json",
Not sure why it was not documented in the wiki, it looks like a 'natural' way of adding a proxy - similar to the ng serve.

Bartosz-D3V on 4 May 2018

👎7

You can also make a separate "option" in your angular.json like this:

"e2e": {
    "builder": "@angular-devkit/build-angular:dev-server",
    "options": {
       "browserTarget": "appname:build",
       "proxyConfig": "src/proxy.conf.json"
     }
}