Updated (05/2023) There are some tips in the comments and I brought them to update this question. If you’re facing this problem, then you are probably using a Linux distro and your project is hitting your system’s file watchers limit. Check your current inotify file watch limit by executing: $ cat /proc/sys/fs/inotify/max_user_watches You can set … Read more
Change your Procfile to this: web: node app.js Being app.js the entry point to your app. This is assuming you don’t really need nodemon in your app, since you have listed it at the package.json sample you provided.
In order to make NodeMon ignore a bunch of files from monitoring, you can start it as nodemon –ignore PATTERN [–ignore PATTERN2] where PATTERN is the name of a specific file, directory, or wildcard pattern. Make sure that if you use a wildcard, it is escaped. For example nodemon –ignore ‘lib/*.js’ –ignore README Alternatively, if … Read more
You can now simply npm install –save-dev ts-node nodemon and then run nodemon with a .ts file and it will Just Work: nodemon app.ts Previous versions: I was struggling with the same thing for my development environment until I noticed that nodemon‘s API allows us to change its default behaviour in order to execute a … Read more
Root cause: inotify is not fully supported in the 9P filesystem protocol on WSL2. There are several github issues on the WSL project related to this, but perhaps the most relevant is #4739. Possible Workarounds: Try nodemon -L (a.k.a. –legacy-watch) as Simperfy suggested. Try running from the default ext4 filesystem (e.g. mkdir -p $HOME/Projects/testserver). Note … Read more
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