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

feat(@angular/cli): ng e2e defaults to random port #4753

Merged
merged 2 commits into from
Feb 17, 2017

Conversation

filipesilva
Copy link
Contributor

No description provided.

BREAKING CHANGE: `ng e2e` will use a random port for serving by default
instead of using 4200.
Copy link
Contributor

@hansl hansl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.

@filipesilva filipesilva merged commit d2bef98 into angular:master Feb 17, 2017
@filipesilva filipesilva deleted the e2e-port-auto branch February 17, 2017 19:53
asnowwolf pushed a commit to asnowwolf/angular-cli that referenced this pull request Apr 12, 2017
BREAKING CHANGE: `ng e2e` will use a random port for serving by default
instead of using 4200.
.then((foundPort: number) => {

// If the port isn't available and we weren't looking for any port, throw error.
if (port !== foundPort && port !== 0) {

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wonder why you did not just return the found port instead of throwing an error. This would help developers in case the port is already in use, I work with multiple projects at the same time and often find my self having to serve with a random port number. For example ng serve --port=2010

@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 12, 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

Successfully merging this pull request may close these issues.

4 participants