FM / cli

/usr/local/lib/node_modules/nodemon/doc/cli/

/usr/local/lib/node_modules/nodemon/doc/cli

Name	Size	Mode	Actions
authors.txt	236	0644	edit dl rm
config.txt	1158	0644	edit dl rm
help.txt	1268	0644	edit dl rm
logo.txt	799	0644	edit dl rm
options.txt	1869	0644	edit dl rm
topics.txt	325	0644	edit dl rm
usage.txt	88	0644	edit dl rm
whoami.txt	1223	0644	edit dl rm

Edit: /usr/local/lib/node_modules/nodemon/doc/cli/config.txt (1158B)

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"
      }
    }

cmd: