"Port 4200 is already in use" when running the ng serve command

[danielehrhardt]

Command

serve

Is this a regression?

• Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was

No response

Description

• run ng serve
• kill ng serve with cmd + c
• run ng serve again
• ➤ Port 4200 is already in use
• tmp fix: sudo kill $(sudo lsof -t -i:4200)

i had this already some years ago and now again
node -v
v18.12.1
npm -v
8.19.2

MacOS 13.2.1 (22D68)

Minimal Reproduction

Exception or Error

-

Your Environment

Angular CLI: 15.2.4
Node: 18.12.1
Package Manager: yarn 1.22.19
OS: darwin arm64

Angular: 15.2.3
... animations, cdk, common, compiler, compiler-cli, core, forms
... google-maps, language-service, platform-browser
... platform-browser-dynamic, router, service-worker

Package Version
---------------------------------------------------------
@angular-devkit/architect 0.1502.4
@angular-devkit/build-angular 15.2.4
@angular-devkit/core 15.2.4
@angular-devkit/schematics 14.0.6
@angular/cli 15.2.4
@schematics/angular 15.2.4
rxjs 7.8.0
typescript 5.0.2

Anything else relevant?

No response

[MickL]

I am on macOS 13.2.1 as well, with also the latest Angular versions and dont have the same issue

[alan-agius4]

Hello, we reviewed this issue and determined that it doesn't fall into the bug report or feature request category. This issue tracker is not suitable for support requests, please repost your issue on StackOverflow using tag angular-cli.

If you are wondering why we don't resolve support issues via the issue tracker, please check out this explanation.

[angular-automatic-lock-bot]

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