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) Doing more with Express Making Lists in Jade Templates

Sebastian Andersson
seal-mask
.a{fill-rule:evenodd;}techdegree
Sebastian Andersson
Full Stack JavaScript Techdegree Student 13,003 Points
Posted by Sebastian Andersson
.a{fill-rule:evenodd;}techdegree
Sebastian Andersson
Full Stack JavaScript Techdegree Student 13,003 Points

When debugging, the console seems disabled as the enter key has no effect when pressed.

Hi! So I started the debugger and I put up a breakpoint at the express app-line. The debugger is running and stops where it should. However, when typing something into the console and hitting enter nothing happens. It simply jumps to the next line. Is this a common thing or have I deleted some file from my computer..?

3 Answers

Melanie Archer
Melanie Archer
5,407 Points
Melanie Archer
Melanie Archer
5,407 Points

I upgraded Node to 7.2.1:

sudo npm cache clean -f
sudo npm install -g n
sudo n stable

and reinstalled nodemon:

npm uninstall -g nodemon
npm install -g nodemon

After doing that, this command created a usable debugging environment, with functioning console, in the Chrome browser:

nodemon --inspect --debug-brk  src/app.js
shaunhoyes
shaunhoyes
17,972 Points

I was having the same issues, and this worked for me. Thanks!

Mark Pixel
PLUS
Mark Pixel
Courses Plus Student 2,337 Points
Mark Pixel
Mark Pixel
Courses Plus Student 2,337 Points

Glad to see it's not just me. It must be a new bug. Nodemon forced me to update which may have caused it.

Duncan Taylor
Duncan Taylor
11,263 Points
Duncan Taylor
Duncan Taylor
11,263 Points

I'm having that same issue.