You’re running express 4, which has the app.listen call in a different file than app.js. The command you’re looking for is nodemon bin/www (localhost and 3000 are not needed in this scenario). In fact, you can even run nodemon with no args, and it’ll read what command needs to be run from scripts.start in package.json (which express generates automatically).
If you are using Linux, your project is hitting your system’s file watchers limit To fix this, on your terminal, try:
You can resolve this problem by adding nodemon to your package.json: The problem happens when nodemon does not exist in /node_modules/.bin. Added –save-dev since it’s required during development only.
You can resolve this problem by adding nodemon to your package.json: The problem happens when nodemon does not exist in /node_modules/.bin. Added –save-dev since it’s required during development only.
I’m on a Mac running El Capitan. I have node v5.6.0 and npm v3.6.0. When I try to run nodemon, I get: I thought this may mean that I didn’t have nodemon installed, so when I tried to install it using… …I get this: If it makes a difference, I’m trying to run nodemon on … Read more
Mongoose expects you to specify types using the built-in constructor functions, which are named with capital letters, e.g. String, Number, Boolean, etc.
Since node prefix is not in the PATH ENV variable , any of the globally installed modules are not getting recognized. Please try this. Open cmd prompt npm config get prefix append the resulting path to PATH env variable. Now you should be able to run nodemon from any location. This is what i have … Read more