Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Error: listen EADDRINUSE: address already in use :::3000
See original GitHub issuenodemon v2.0.13:nodev14.17.6:- Operating system/terminal environment: Window 10/CMD/bash/wt
- Using Docker? What image: not docker
- Command you ran: nodemon nodemon -w src -e ts -x ts-node ./src/index.ts
Expected behaviour
output from terminal that the node process is restarting
Actual behaviour
Error: listen EADDRINUSE: address already in use :::3000
Steps to reproduce
- listen to the express server on port 3000
nodemon -w src -e ts -x ts-node index.ts
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Node / Express: EADDRINUSE, Address already in use - Kill ...
First, you would want to know which process is using port 3000 sudo lsof -i :3000. this will list all PID listening on...
Read more >How to kill server when seeing “EADDRINUSE: address ...
Nodejs listen EADDRINUSE: address already in use. The Problem. When trying to restart a Node application, the previous one did not shut down ......
Read more >Error: listen EADDRINUSE: address already in use :::3000 #568
This usually means that there are asynchronous operations that weren't stopped in your tests. Consider running Jest with --detectOpenHandles to ...
Read more >Listen EADDRINUSE: address already in use :::3000 - Node
Hi guys, I'm stuck with this damn error, anyone solved this issue?, I'm confidence that the code 100% is the same as Mosh...
Read more >Error: listen EADDRINUSE: address already in use :::3000
Error : listen EADDRINUSE: address already in use :::3000 ... The error would occur if you run your server without stopping the previously...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I am still experiencing this issue in nodemon in 2.0.15
Solved by using npm install nodemon@2.0.14 which is the last version