-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Cannot terminate the dev server process with Ctrl+C
while running nx serve <app-name>
#3348
Comments
This issue should be fixed with Nx 10 in #3330. We plan on backporting this fix to Can you please try with Nx 10 to see if the issue is resolved there please? |
@vlodko what version of Node are you using? Also, could you provide a repo with a repro? |
thanks @FrozenPandaz @vsavkin |
@vlodko could you provide a repo with a repro using Nx 9.5.1? |
The issue has been fixed in Nx 9.6 and Nx 10.1. I'm sorry it took so long to get this right. |
@vsavkin thank you! |
I'm still encounter this issue in my Nx + Nextjs project with following dependency: |
same here, no matter what app I serve, when I kill the process in the terminal the server is still running on the same port: "@nrwl/cli": "13.4.4", Может быть проблема в самом ноджс? |
Having this issue as well with v13.5.2. Running a Nextjs app and despite terminating the process, the port is still running |
I'm seeing this as well with |
Still present also in 13.5.2 [ ready ] on http://localhost:4200 |
NX 14.7.5 I've run my server on localhost:8080 and now no matter what I do I can't use that port. It still tries to serve up that application. I've killed every PID resembling 8080 and they come back. Shut down my machine and it still tries to serve the app. Any tips? |
this has started happening for me since upgrading from It was fine on 14.3. |
Same error here. |
Noticed the same error. |
Same thing
OS: MacOS Monterey 12.2.1 (Intel based) Please, reopen |
This is happening to us as well on nx version 14.7.6 and node v16.14.0 |
This also occurs on nx version 15, and the node version doesn't really matter, IG. |
@vsavkin This is still happening |
@vsavkin @FrozenPandaz |
Mine was caused by version mismatching between the monorepos. Try to update all the |
@turboninh I'm not sure what you mean - do you have multiple nx monorepos? We do not use a globally installed version of nx when running generators and commands. i.e. something like |
This bug occurs for me with nx 14.8.3 when upgrading node from 16.17.1 to 16.18.1. |
This issue has been closed for more than 30 days. If this issue is still occuring, please open a new issue with more recent context. |
Steps to Reproduce
nx serve <app-name>
in Zsh or BashCurrent Behavior
When you try to start the dev server again the following error appears:
Note: using
ng serve <app-name>
works as expectedExpected Behavior
When you start a server again the port is available for use
Environment
OS: macOS
Shell: Zsh, Bash
nx report:
The text was updated successfully, but these errors were encountered: