-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
v15 express address already in use on restart #14006
Comments
this is happening to me creating a new nestjs application too |
The same thing happens when using
|
With |
PR fixing this was merged |
I still get the error on my nestjs project and I use the version |
@alex-w0 whats nx report say |
@AgentEnder Here's the report, the project was also created from scratch:
|
Can you open a new issue including repro steps? The problem in this issue was addressed and confirmed as fixed, and it's hard to keep track of reports on closed issues. |
@AgentEnder New issue is created, if you need a repository to reproduce the bug, let me know so I can provide it, but should be the same one as in this issue. |
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. |
Current Behavior
If you create a brand new nx project with the express preset, if you start the express app and change a source file to restart the server the following error is shown
Error: listen EADDRINUSE: address already in use :::3333
Expected Behavior
When the express server restarts, it should wait for the previous process to terminate before attempting to restart the server and should be able to restart on the same port number
Github Repo
https://github.com/kizzlebot/nx-bug-report-example
Steps to Reproduce
npx create-nx-workspace@15.x.x --preset=express
Nx Report
Failure Logs
Additional Information
This issue is occurring because of this Map.
The key of the
Map
is an instance of a array when the value is set. When the value is retrieved it creates a new array instance containing the same elements and uses it to retrieve the value. The issue is the key is using two different references even though they contain the same elements.The text was updated successfully, but these errors were encountered: