Watching extra files (or treating -w <file> as -w <folder>?)

[elmigranto]

Hey, Remy and everyone working on nodemon 🖖
First of all, thanks for an awesome tool, been using it for as long as node and it's really helpful ❤️

---

• nodemon -v: 1.14.0
• node -v: v8.9.3
• macOS; Terminal.app; fish 2.7.0.

Command you ran

`env DEBUG=nodemon nodemon --verbose --watch mocha.opts --watch package.json --exec echo 123`

$ env DEBUG=nodemon nodemon -v -w mocha.opts --w package.json -x echo 123
  nodemon bus new listener: reset (0) +0ms
  nodemon bus new listener: reset (0) +2ms
  nodemon bus new listener: quit (0) +12ms
  nodemon bus new listener: quit (0) +0ms
  nodemon bus new listener: restart (0) +0ms
  nodemon bus new listener: restart (0) +0ms
  nodemon bus new listener: reset (2) +2ms
  nodemon bus emit: reset +1ms
  nodemon resetting watchers +0ms
  nodemon reset +0ms
[nodemon] Looking in package.json for nodemonConfig
  nodemon config: dirs [ '/<project-root>/mocha.opts',
  '/<project-root>/package.json' ] +55ms
[nodemon] 1.14.0
[nodemon] reading config /<project-root>/package.json
[nodemon] to restart at any time, enter `rs`
[nodemon] or send SIGHUP to 67557 to restart
[nodemon] ignoring: /<project-root>/.git/**/* .nyc_output .sass-cache bower_components coverage /<project-root>/node_modules/**/*
[nodemon] watching: mocha.opts package.json
[nodemon] watching extensions: js,json
[nodemon] starting `echo 123`
  nodemon spawning echo 123 +7ms
[nodemon] child pid: 67559
  nodemon bus new listener: exit (0) +4ms
  nodemon bus new listener: exit (0) +0ms
  nodemon start watch on: mocha.opts,package.json +0ms
  nodemon start watch on: /<project-root>/mocha.opts, /<project-root>/package.json +0ms
  nodemon ignore dirs regex(/\.git|\.nyc_output|\.sass\-cache|bower_components|coverage|node_modules/) +0ms
123
  nodemon bus.emit(exit) via SIGUSR2 +6ms
  nodemon bus emit: exit +1ms
[nodemon] clean exit - waiting for changes before restart
  nodemon watch is complete +1ms
  nodemon watch is complete +0ms
[nodemon] watching 3 files
^C  nodemon bus emit: quit +4s
  nodemon bus emit: quit +0ms
[nodemon] exiting

same command with `--dump` flag

$ env DEBUG=nodemon nodemon -V -w mocha.opts -w package.json --dump -x echo 123
  nodemon bus new listener: reset (0) +0ms
  nodemon bus new listener: reset (0) +2ms
  nodemon bus new listener: quit (0) +13ms
  nodemon bus new listener: quit (0) +0ms
  nodemon bus new listener: restart (0) +0ms
  nodemon bus new listener: restart (0) +0ms
  nodemon bus new listener: reset (2) +2ms
  nodemon bus emit: reset +2ms
  nodemon resetting watchers +0ms
  nodemon reset +0ms
[nodemon] Looking in package.json for nodemonConfig
  nodemon config: dirs [ '/<project-root>/mocha.opts',
  '/<project-root>/package.json' ] +47ms
[nodemon] 1.14.0
[nodemon] reading config /<project-root>/package.json
[nodemon] to restart at any time, enter `rs`
[nodemon] or send SIGHUP to 67312 to restart
[nodemon] ignoring: /<project-root>/.git/**/* .nyc_output .sass-cache bower_components coverage /<project-root>/node_modules/**/*
[nodemon] watching: mocha.opts package.json
[nodemon] watching extensions: js,json
--------------
node: v8.9.3
nodemon: 1.14.0
command: /Users/elmigranto/.nvm/versions/node/v8.9.3/bin/node /Users/elmigranto/.nvm/versions/node/v8.9.3/bin/nodemon -V -w mocha.opts -w package.json --dump -x echo 123
cwd: /<project-root>
OS: darwin x64
--------------
{ run: false,
  system: { cwd: '/<project-root>' },
  required: false,
  dirs: 
   [ '/<project-root>/mocha.opts',
     '/<project-root>/package.json' ],
  timeout: 1000,
  options: 
   { verbose: true,
     watch: [ 'mocha.opts', 'package.json', re: /mocha\.opts|package\.json/ ],
     dump: true,
     exec: 'echo',
     ignore: 
      [ '.git',
        '.nyc_output',
        '.sass-cache',
        'bower_components',
        'coverage',
        'node_modules',
        re: /\.git|\.nyc_output|\.sass\-cache|bower_components|coverage|node_modules/ ],
     ignoreRoot: 
      [ '.git',
        '.nyc_output',
        '.sass-cache',
        'bower_components',
        'coverage',
        'node_modules' ],
     restartable: 'rs',
     colours: true,
     execMap: { py: 'python', rb: 'ruby' },
     stdin: true,
     runOnChangeOnly: false,
     signal: 'SIGUSR2',
     stdout: true,
     watchOptions: {},
     execOptions: 
      { script: null,
        exec: 'echo',
        args: [ '123' ],
        scriptPosition: null,
        nodeArgs: undefined,
        execArgs: [],
        ext: 'js,json',
        env: {} },
     monitor: 
      [ 'mocha.opts',
        'package.json',
        '!/<project-root>/.git/**/*',
        '!.nyc_output',
        '!.sass-cache',
        '!bower_components',
        '!coverage',
        '!/<project-root>/node_modules/**/*' ] },
  load: [Function],
  reset: [Function: reset],
  lastStarted: 0,
  loaded: [ '/<project-root>/package.json' ],
  watchInterval: null,
  signal: 'SIGUSR2',
  command: 
   { raw: { executable: 'echo', args: [ '123' ] },
     string: 'echo 123' } }
--------------
[nodemon] exiting

Expected behaviour

Watches exactly 2 files I specified.

Actual behaviour

Watches 3 files (or reports as it was the case).

It gets even worse when I put in more files. In my test project I have about 20 js files total and when every single one of those is specified as --watch arg, nodemon reports that it is watching ~300, DEBUG=nodemon logs show something like this:

nodemon start watch on: <22 filepathes I specified VERBATIM>
nodemon start watch on: <22 filepathes I specified again, but with full path instead of relative>
nodemon watch is complete <22 times>

Like this:

nodemon start watch on: src/index.js src/something-else.js
nodemon start watch on: /<project-root>/src/index.js /<project-root>/src/something-else.js
nodemon watch is complete +20ms
nodemon watch is complete +1ms

This kinda hints that totals are wrong, and it actually does watch only those I specified. But would like to double-check with you people, since I can't dig any deeper into nodemon sources than a brief looking I tried and came up empty.

Steps to reproduce

--watch more than one file (or perhaps even one is enough, but multiple work consitenlty for me…).

[remy]

Is it always one more? If it is, it's because nodemon also watches (or tries to watch) the running script.

[elmigranto]

Not always +1. When all 22 files are specified as --watch flag, it says it watches 293.

DEBUG=nodemon and --verbose flag show that it puts it into some config param called dirs even though all are files. And same double reporting for "start watch on" happens.

For script watching, if I only specify single file (say, --watch mocha.opts) and run --exec echo 123, it correctly reports "watching 1 file".