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 Getting Started with Express Adding Multiple Routes to the App

Daniel Hernandez
Daniel Hernandez
13,437 Points
Posted by Daniel Hernandez
Daniel Hernandez
13,437 Points

Nodemon is not working

I have successfully installed nodemon but it refuses to automatically load updated webpages. It will tell me which version of nodemon I am using and that it is restarting the page from updates to the code but then it never updates the page. And if I write "rs" then it will appear idle until I close the command prompt. My operating system is Windows 8.1 pro and the laptop is a Toshiba. Anyone have ideas of what I can do to get nodemon working?

Amelia Groen
Amelia Groen
6,144 Points

Are you getting any errors?

In package.json is "main" set to "app.js" (by default it will be index.js, which is what nodemon will be looking for, but that file does not exist)

3 Answers

Daniel Hernandez
Daniel Hernandez
13,437 Points
Daniel Hernandez
Daniel Hernandez
13,437 Points

It seems to be working now although I already had the main as app.js. Thanks for the reply though!

Alan McClenaghan
seal-mask
.a{fill-rule:evenodd;}techdegree seal-36
Alan McClenaghan
Full Stack JavaScript Techdegree Graduate 56,501 Points
Alan McClenaghan
.a{fill-rule:evenodd;}techdegree seal-36
Alan McClenaghan
Full Stack JavaScript Techdegree Graduate 56,501 Points

Glad you worked out your problem.

nodemon was crashing on me, but it turned out I had put my h1 tags outside the the quote marks in my response callback so its worth checking if something seemingly unrelated is causing the problem.

The Terminal output can seem a bit unfriendly if not incomprehensible but its worth checking out for clues about any problems.