There are a few things wrong with your code. You never told your app to run. When you’re ready creating your routes you should start your server with: app.listen(<port on which the server should run here>); Also you have an Express app and a router in the same file. The router should only be used … Read more
In some networked environments (such as a container running nodemon reading across a mounted drive), you will need to use the legacyWatch: true which enabled Chokidar’s polling. Via the CLI, use either –legacy-watch or -L for short: nodemon -L
Use nodemon –legacy-watch to poll for file changes instead of listening to file system events. VirtualBox doesn’t pass file system events over the vboxfs share to your Linux VM. If you’re using Docker for Windows, it would appear HyperV doesn’t propagate file system events either. As a 2021 side note, Docker for Mac/Windows new GRPCfuse … Read more
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 … Read more
With ts-node 5.0.0 you no longer pass the –inspect flag the same way. The suggested way is node –inspect -r ts-node/register path/to/ts. For example: nodemon –watch src/**/* -e ts,json –exec node –inspect-brk -r ts-node/register src/app.ts see https://github.com/TypeStrong/ts-node/issues/537
Just specify watching html on the nodemon command line (or better yet, add a config file). From the documentation: By default, nodemon looks for files with the .js, .coffee, .litcoffee, and .json extensions. If you use the –exec option and monitor app.py nodemon will monitor files with the extension of .py. However, you can specify … Read more
When you develop a node app and you make some changes, to see them in effect you have to restart the server. When you launch your node.js application with Nodemon it will monitor for any changes and automatically restart the server, improving your productivity.
–delay helped me to fix both of issues on auto-restart stopping with ctrl-c nodemon –delay 500ms app.js And I also added: process.once(‘SIGUSR2’, function () { process.kill(process.pid, ‘SIGUSR2’); }); process.on(‘SIGINT’, function () { // this is only called on ctrl+c, not restart process.kill(process.pid, ‘SIGINT’); });
You can resolve this problem by adding nodemon to your package.json: npm install nodemon –save-dev The problem happens when nodemon does not exist in /node_modules/.bin. Added –save-dev since it’s required during development only.
For people coming from search engines, there could be a bug related to nodemon and ts-node. Error: Unknown or unexpected option: –inspect This can be a way to use inspect with nodemon: nodemon –exec ‘node –inspect=0.0.0.0:9229 –require ts-node/register src/index.ts’ For more information see here