Application and module developers can find a summary of API changes in the API updates overview.
This document describes changes in server behavior that might require you to change your configuration or how you use the server in order to continue using 2.4 as you are currently using 2.2.
By default nodemon monitors the current working directory.
If you want to take control of that option, use the Java Script file changes.
nodemon will watch the files in the directory in which nodemon was started, and if any files change, nodemon will automatically restart your node application. If your script exits cleanly, nodemon will continue to monitor the directory (or directories) and restart the script if there are any changes.
nodemon was originally written to restart hanging processes such as web servers, but now supports apps that cleanly exit.
System Center Configuration Manager synchronizes with the Microsoft cloud service to get updates.
You can then install these updates from within the Configuration Manager console.
There have been significant changes in authorization configuration, and other minor configuration changes, that could require changes to your 2.2 configuration files before using them for 2.4.
To take advantage of new features in 2.4, see the New Features document.
This document describes only the changes from 2.2 to 2.4.
Whilst nodemon is running, if you need to manually restart your application, instead of stopping and restart nodemon, you can simply type .
Please see doc/nodemon can also be used to execute and monitor other programs.