Welcome to the Treehouse Community

Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.

Start your free trial

JavaScript Express Basics (2015) The Request and Response Objects in Express Requests and the request object

Giovanni Dalla Rizza
Giovanni Dalla Rizza
10,637 Points
Posted by Giovanni Dalla Rizza
Giovanni Dalla Rizza
10,637 Points

Error with nodemon debug

It reports this error:

➜  express-basics git:(requests) ✗ nodemon --debug src/app.js 
[nodemon] 1.11.0
[nodemon] to restart at any time, enter `rs`
[nodemon] watching: *.*
[nodemon] starting `node --debug src/app.js`
Error: listen EADDRINUSE :::5858
    at Object.exports._errnoException (util.js:907:11)
    at exports._exceptionWithHostPort (util.js:930:20)
    at Agent.Server._listen2 (net.js:1250:14)
    at listen (net.js:1286:10)
    at Agent.Server.listen (net.js:1382:5)
    at Object.start (_debug_agent.js:21:9)
    at startup (node.js:70:44)
    at node.js:974:3

1 Answer

Ben Myhre
Ben Myhre
28,726 Points
Ben Myhre
Ben Myhre
28,726 Points

I also am running into all sorts of errors with getting the node-inspector and debug to play nicely. I was having job issues (that revealed themselves in the same sort of way you are seeing) and now I cannot get the node-inspector to respect carriage returns.

Your specific error, however, looks like the address is being used. Check to see if you have other tabs in either tour terminal running either a node or web-inspector instance. Close them. I would do the same for any web-inspector windows or any where app.js is running. If you have a similar error, this will help.

I ended up having to use ps and ps aux to find processes and 'kill -9 ####(job number)' to terminate this stuff.... but I am down the rabbit hole of more problems.