Server IP : 162.213.251.212 / Your IP : 3.149.214.43 [ Web Server : LiteSpeed System : Linux business55.web-hosting.com 4.18.0-553.lve.el8.x86_64 #1 SMP Mon May 27 15:27:34 UTC 2024 x86_64 User : allssztx ( 535) PHP Version : 8.1.31 Disable Function : NONE Domains : 1 Domains MySQL : OFF | cURL : ON | WGET : ON | Perl : ON | Python : ON | Sudo : OFF | Pkexec : OFF Directory : /home/allssztx/nodevenv/needapair.com/20/lib/node_modules/nodemon/doc/cli/ |
Upload File : |
Typically the options to control nodemon are passed in via the CLI and are listed under: nodemon --help options nodemon can also be configured via a local and global config file: * $HOME/nodemon.json * $PWD/nodemon.json OR --config <file> * nodemonConfig in package.json All config options in the .json file map 1-to-1 with the CLI options, so a config could read as: { "ext": "*.pde", "verbose": true, "exec": "processing --sketch=game --run" } There are a limited number of variables available in the config (since you could use backticks on the CLI to use a variable, backticks won't work in the .json config). * {{pwd}} - the current directory * {{filename}} - the filename you pass to nodemon For example: { "ext": "*.pde", "verbose": true, "exec": "processing --sketch={{pwd}} --run" } The global config file is useful for setting up default executables instead of repeating the same option in each of your local configs: { "verbose": true, "execMap": { "rb": "ruby", "pde": "processing --sketch={{pwd}} --run" } }