This is being added to as common issues occur on the issues, and where appropriate the answers will be added here.
This is a working document, and if it makes sense, I'll take pull requests to help make it better.
Create an nodemon.json file with the setting:
{
"restartable": false
}This will leave the STDIN to your application rather than listening for the rs command to restart.
nodemon has three potential methods it uses to look for file changes. First, it polls using the find command to search for files modified within the last second. This method works on systems with a BSD based find (Mac, for example).
Next it tries using node's fs.watch. fs.watch will not always work however, and nodemon will try and detect if this is the case by writing a file to the tmp directory and seeing if fs.watch is triggered when it's removed. If nodemon finds that fs.watch was not triggered, it will then fall back to the third method (called legacy watch), which works by statting each file in your working directory looking for changes to the last modified time. This is the most cpu intensive method, but it may be the only option on some systems.
In certain cases, like when where you are working on a different drive than your tmp directory is on, fs.watch may give you a false positive. You can force nodemon to start using the most compatible legacy method by passing the -L switch, e.g. nodemon -L /my/odd/file.js.
If you see nodemon trying to run two scripts, like:
9 Dec 23:52:58 - [nodemon] starting `node ./app.js fixtures/sigint.js`
This is because the main script argument (fixtures/sigint.js in this case) wasn't found, and a package.json's main file was found. ie. to solve, double check the path to your script is correct.
Everything under the ignore rule has the final word. So if you ignore the node_modules directory, but watch node_modules/*.js, then all changed files will be ignored, because any changed .js file in the node_modules are ignored.
Fedora is looking for nodejs rather than node which is the binary that nodemon kicks off.
The solution is a simple workaround, Linux 101:
sudo ln -s /usr/bin/nodejs /usr/local/bin/node
Fedora and Ubuntu pakage node as nodejs, because node.dpkg is
Description-en: Amateur Packet Radio Node program The node program accepts TCP/IP and packet radio network connections and presents users with an interface that allows them to make gateway connections to remote hosts using a variety of amateur radio protocols. They make the binary is nodejs, rather than node. So long as you're not using that Packet Radio Node Program mentioned above the workaround will work.
Thank you @EvanCarroll
If you're using nodemon with forever (perhaps in a production environment) you can combine the two together. This way if the script crashes, forever restarts the script, and if there are file changes, nodemon restarts your script. For more detail, see issue 30.
To acheive this you need to include the --exitcrash flag to ensure nodemon exits if the script crashes (or exits unexpectedly):
forever nodemon --exitcrash server.js
To test this, you can kill the server.js process and forever will restart it. If you touch server.js nodemon will restart it.
Note that I would not recommend using nodemon in a production environment - but that's because I wouldn't want it restart without my explicit instruction.