Skip to content

ng e2e --no-serve no longer works #10761

@raysuelzer

Description

@raysuelzer

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).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions