Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
raysuelzer opened this issue May 9, 2018 · 4 comments
Closed

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

raysuelzer opened this issue May 9, 2018 · 4 comments

Comments

@raysuelzer
Copy link

raysuelzer commented May 9, 2018

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

@clydin
Copy link
Member

clydin commented May 9, 2018

Duplicate of #10741

@clydin clydin marked this as a duplicate of #10741 May 9, 2018
@clydin clydin closed this as completed May 9, 2018
@jai-rathore
Copy link

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

@Markus-Ende
Copy link

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)

@angular-automatic-lock-bot
Copy link

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.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 8, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants