e2e devServerTarget doesn't seem to be working correctly

[oliverdavidt]

Versions

Angular CLI: 6.0.0
Node: 8.9.4
OS: darwin x64
Angular: 6.0.0
... animations, cdk, cli, common, compiler, compiler-cli, core
... elements, forms, http, language-service, material
... platform-browser, platform-browser-dynamic, router

Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.6.0
@angular-devkit/build-angular     0.5.12
@angular-devkit/build-optimizer   0.5.12
@angular-devkit/core              0.6.0
@angular-devkit/schematics        0.6.0
@ngtools/webpack                  6.0.0-rc.10
@schematics/angular               0.6.0
@schematics/update                0.6.0
rxjs                              6.0.0
typescript                        2.7.2
webpack                           4.6.0

Repro steps

This may not be an issue, but rather a lack of understanding of how the new cli config works.

• Update port option in myapp-app:serve to 8080
• Set myapp-app-e2e:e2e option of devServerTarget to myapp-app:serve
• Run ng e2e
• Server starts up on localhost:4200 rather than specified port.

Again, maybe I am not understanding how this works, but I would think that if I set the devServerTarget e2e option then whatever configuration that server has it should pull through during the e2e task.

Observed behavior

ng e2e
** Angular Live Development Server is listening on localhost: 4200, open your browser on http://localhost:4200/ **

Desired behavior

I would expect server to startup on the specified port that is set in myapp-app:serve.

Mention any other details that might be useful (optional)

If I set the port option directly in the myapp-app-e2e:e2e options section, then it does respect that and starts up the server on that port.

[Bjeaurn]

Same issue here, when I tried to add the options to the e2e part of the angular.json it failed because of Schema validation. Example:

Schema validation failed with the following errors:
  Data path "" should NOT have additional properties(publicHost).

Only overriding the port there was fine though but we need some more settings to get serve to work. I managed to override port and host (not publicHost tho) either in the package.json (ng e2e --host <bla>) or in the angular.json (added to the options: {} part of the `e2e definition), as a temporary work around.

Are we misunderstanding what the devServerTarget is refering to?

[sebastian-zarzycki-apzumi]

Same issue here. I was surprised to see that the port for e2e is different than what I specified in myapp:serve. For now overriding just port is fine, but I am confused nevertheless.

[pjmagee]

I am confused too. Documentation is very minimal and there needs to be more verbose examples of how to configure the angular.json file. Especially since the basic examples only show the argument way to define options, e.g --public-host, but doesnt explain if this is "publicHost" in the angular.json

[pjmagee]

I am a god damn legend. I got it working, here is an example for you guys.

 "serve": {
                    "builder": "@angular-devkit/build-angular:dev-server",
                    "options": {
                        "browserTarget": "Project:build",
                        "hmrWarning": false,
                        "host": "myproject.com",
                        "port": 8000
                    },
                    "configurations": {
                        "hmr": {
                            "hmr": true,
                            "browserTarget": "Project:build:hmr"
                        },
                        "production": {
                            "hmr": false,
                            "browserTarget": "Projectbuild:production"
                        }
                    }
                },

Output message from Angular:

Angular Live Development Server is listening on myproject.com: 8000, open your browser on http://myproject.com:8000/ **

[sebastian-zarzycki-apzumi]

You've misunderstood the original issue. It's not about setting a port for serve target.

[listepo-alterpost]

Earlier we run --serve=false with --base-url or baseUrl(protractor.conf) for remote testing, but now that don't work. Any news about this bug?

[Juansasa]

And i dont know why devServerTarget is a requirement either. --sever=false is a valid use case and now its gone

[tongfa]

I was able to delete devServerTarget from angular.json, the change the baseUrl parameter in the e2e project's protractor.conf.js file and point the e2e test to another port on localhost. I imagine adjusting baseUrl to point to another server would work just as well.

Angular 6.0.8

[Smiter15]

With @tongfa's comment i was able to change host and port. Remove the "devServerTarget": "project-name:serve" like he mentions and in protractor.conf.js just update the baseUrl to contain both your host and port eg: baseUrl: 'http://project-name.local:8080/'

But really it should be picking it up as intended from the serve:options in angular.json.

[aniruddhadas9]

@Smiter15 @tongfa it did not working for me. here is my configuration and I running ng e2e --configuration=e2e-ci --suite=home

            "e2e-ci": {
              "protractorConfig": "./protractor.conf.js",
              "baseUrl": "https://udc.dev.finra.org"
            }