Can nodemon watch and restart on changes occurring to files with no extension?

[gizero]

I'm using express-generator from Express.js (>4.0). As already discussed in #330, it sets things up to run the app with node ./bin/www. How should I setup nodemon in order to trigger restarts on changes to ./bin/www.

$ DEBUG=test nodemon --verbose ./bin/www
13 Jan 16:41:47 - [nodemon] v1.2.1
13 Jan 16:41:47 - [nodemon] to restart at any time, enter `rs`
13 Jan 16:41:47 - [nodemon] ignoring: .git /tmp/test/node_modules/**/* bower_components .sass-cache
13 Jan 16:41:47 - [nodemon] watching: *.*
13 Jan 16:41:47 - [nodemon] watching extensions: js
13 Jan 16:41:47 - [nodemon] starting `node ./bin/www`
13 Jan 16:41:47 - [nodemon] child pid: 1516
13 Jan 16:41:47 - [nodemon] watching 806 files

When changing the file:

13 Jan 16:41:52 - [nodemon] files triggering change check: bin/www
13 Jan 16:41:52 - [nodemon] changes after filters (before/after): 1/0

I tryed to explicitly add the file to the watchlist with the following cmdline, but looks like it still get filtered out.

$ DEBUG=test nodemon -w ./bin/www --verbose ./bin/www

[remy]

:-\

Hmm. That's weird. I'll have to run some tests myself. I suspect you're right, it if can't find an extension it might be lost. But because you've explicitly added it should be watched.

Can you run: nodemon -w ./bin/www --verbose ./bin/www --dump and post the result?

[gizero]

Here is the dump...

$ nodemon -w ./bin/www --verbose ./bin/www --dump                                                                                      [ruby-2.0.0-p195]
15 Jan 08:26:12 - [nodemon] v1.2.1
15 Jan 08:26:12 - [nodemon] to restart at any time, enter `rs`
15 Jan 08:26:12 - [nodemon] ignoring: .git /tmp/provetta/node_modules/**/* bower_components .sass-cache
15 Jan 08:26:12 - [nodemon] watching: ./bin/www
15 Jan 08:26:12 - [nodemon] watching extensions: js
--------------
node: v0.10.35
nodemon: v1.2.1
command: node /home/gizero/.nvm/v0.10.35/bin/nodemon -w ./bin/www --verbose ./bin/www --dump
cwd: /tmp/provetta
OS: linux ia32
--------------
{ run: false,
  system:
   { cwd: '/tmp/provetta',
     useFind: false,
     useWatch: true,
     useWatchFile: false },
  required: false,
  dirs: [ '/tmp/provetta' ],
  timeout: 1000,
  options:
   { scriptPosition: 0,
     watch: [ './bin/www', re: /\./bin/www/ ],
     verbose: true,
     dump: true,
     script: './bin/www',
     args: [],
     ignore:
      [ '.git',
        'node_modules',
        'bower_components',
        '.sass-cache',
        re: /\.git|node_modules|bower_components|\.sass\-cache/ ],
     restartable: 'rs',
     execMap: { py: 'python', rb: 'ruby' },
     stdin: true,
     stdout: true,
     execOptions:
      { script: './bin/www',
        exec: 'node',
        args: [],
        nodeArgs: undefined,
        ext: 'js',
        env: {},
        execArgs: [] },
     ext: 'js',
     monitor:
      [ './bin/www',
        '!.git',
        '!/tmp/provetta/node_modules/**/*',
        '!bower_components',
        '!.sass-cache' ] },
  load: [Function],
  reset: [Function: reset],
  lastStarted: 0,
  loaded: [],
  command:
   { raw: { executable: 'node', args: [ './bin/www' ] },
     string: 'node ./bin/www' } }
--------------
15 Jan 08:26:12 - [nodemon] exiting

[gizero]

Hi! Did the dump help figuring out what's wrong with monitoring extension-less files? Let me know if I can help with more testing...

[remy]

I'm back from holiday today, so I'll be checking it out - I'll let you know
if I need any other information.
On 27 Jan 2015 06:15, "gizero" notifications@github.com wrote:

Hi! Did the dump help figuring out what's wrong with monitoring
extension-less files? Let me know if I can help with more testing...

—
Reply to this email directly or view it on GitHub
#461 (comment).

[remy]

Huh. This is weird. I replicated your issue, but then I tried this (which is missing the leading ./ in the watch):

DEBUG=test nodemon -w bin/www --verbose ./bin/www

And it works...

Are you happy with that as a work around or do you want me to dig deeper?

[gizero]

Hi! What you say about removing the leading ./ is confirmed here, but did you then try to change or touch any file other than bin/www? In my test, with your same exact command line, saving any *.js does end up in no script restart anymore. It's probably my fault in grasping the correct use of -w option, but I thought it was supposed to add elements to the default watchlist... Isn't it the case? Thanks for investigating.

[kevinSuttle]

Found this on my own as well. @remy since this is part of the Express scaffold, would it be wise to whitelist?

[SoilChang]

I ran into the problem myself today. My solution is using -e here in the script. it works after that. But a bit verbose if you want to watch several types of files.

[rmariuzzo]

This happened to me as well. The full comand is:

yarn serve
yarn serve v0.24.6
$ cross-env NODE_ENV=development DEBUG=foo:* nodemon --verbose --watch ./src/server/server.js --watch ./src/server/dev.js

When I edit and save changes to any of those two files, nodemon doesn't restarts:

[nodemon] files triggering change check: src/server/server.js
[nodemon] changes after filters (before/after): 1/0