Angular-cli: ng e2e --no-serve no longer works

Created on 9 May 2018  路  4Comments  路  Source: angular/angular-cli

Versions: 6.0.0

<!--
Output from: `ng --version`.
If nothing, output from: `node --version` and `npm --version`.
  Windows (7/8/10). Linux (incl. distribution). macOS (El Capitan? Sierra?)
-->

Repro steps


*Step 1 > ng serve
*Step 2 > ng e2e --no-serve

Observed behavior

> ng "e2e" "--no-serve"
Port 4200 is already in use. Use '--port' to specify a different port.

Desired behavior

What would like to see implemented? --no-serve option to be back
What is the usecase? Very nice to be able to run e2e tests without the compile step.
What did you expect to see? The same behavior as in previous CLI version.

Mention any other details that might be useful (optional)

Has the --no-serve functionality been moved elsewhere? I haven't been able to find any documentation on this in the release notes (mostly googling).

Most helpful comment

You don't have to change angular.json, you can temporarily have the same effect by running ng e2e --dev-server-target= (yes, empty dev-server-target)

All 4 comments

Duplicate of #10741

In the angular.json file, in the subsection -> "projects" -> "projectName-e2e" -> "architect" ->"options" - remove the "devServerTarget" option,
While running the e2e scripts, use command ng e2e --project=projectName-e2e

You don't have to change angular.json, you can temporarily have the same effect by running ng e2e --dev-server-target= (yes, empty dev-server-target)

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_This action has been performed automatically by a bot._

Was this page helpful?
0 / 5 - 0 ratings