It looks like the workaround with –exec isn’t necessary anymore, at least when using the newest version of nodemon and Webstorm 7 or 8. All you have to do is specify your path to nodemon by obtaining its path with running which nodemon in your console (e.g. /usr/local/bin/nodemon) under “Node parameters”: @Bela Clark, thanks for … Read more
Official issue: https://github.com/npm/registry/issues/255 Official status: https://status.npmjs.org/incidents/41zfb8qpvrdj Several packages including “require-from-string” are currently unavailable. We are aware of the issue and are working to restore the affected user and packages. Please do not attempt to republish packages, as this will hinder our progress in restoring them. Update from NPM: Resolved We apologize for the temporary unavailability … Read more
You need to install it globally npm install -g nodemon # or if using yarn yarn global add nodemon And then it will be available on the path (I see now that you have tried this and it didn’t work, your path may be messed up) If you want to use the locally installed version, … Read more
If you are using Linux, your project is hitting your system’s file watchers limit To fix this, on your terminal, try: echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p
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
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
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
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