False "change" events fired

[catamphetamine]

In on Windows 8.1
I use Webpack for client code.
The server is run with nodemon simultaneously with Webpack.
When Webpack runs it parses all require()s and reads files from disk.
As it happens, false "change" event is being fired for each file accessed by Webpack (atime is not modified).

[1] { dev: 2113014378,
[1]   mode: 33206,
[1]   nlink: 1,
[1]   uid: 0,
[1]   gid: 0,
[1]   rdev: 0,
[1]   blksize: undefined,
[1]   ino: 2280215808,
[1]   size: 128,
[1]   blocks: undefined,
[1]   atime: Fri Sep 04 2015 00:00:00 GMT+0300 (Russia TZ 2 Standard Time),
[1]   mtime: Wed Aug 26 2015 16:53:02 GMT+0300 (Russia TZ 2 Standard Time),
[1]   ctime: Thu Oct 24 1940 05:26:18 GMT+0300 (Russia TZ 2 Standard Time),
[1]   birthtime: Mon Aug 24 2015 12:51:18 GMT+0300 (Russia TZ 2 Standard Time) }

[1] 4 Sep 16:27:03 - [nodemon] files triggering change check: code\client\application.entry.js
...

[es128]

Via whatever combination of processes you're running, the OS is reporting change events. It isn't based on changing timestamps. You can log what's passed with the raw event to get more details on that. Aside from when it is a misreported add or unlink chokidar has no way to validate the accuracy of whether a file was actually changed.

You could try the usePolling: true option to see if it gives you results more like you'd expect and the perf impact is tolerable.