nodemon: nodemon fails to see changes in unix -> windows mounts (samba for example)

@remy has edited this title - currently an outstanding issue

Summary

coffee script is compiling to js when the .coffee file changes but nodemon appears to be missing the change.

Details

I’m getting started with node.js and using coffeescript as my default language. All is fine. So I start with some js in a coffee file:

var http = require('http'); http.createServer(function (req, res) { res.writeHead(200, {'Content-Type': 'text/plain'}); res.end('Hello Earth\n'); }).listen(1337, '0.0.0.0'); console.log('Server running at http://localhost:1337/'); console.log('Is anyone home?');

I set up coffee to watch and compile like so: coffee -wc -o js *.coffee &

OK that works fine, I see output like: 16:26:27 - compiled home.coffee

Then I go into the js directory and do this: nodemon *.js and the app starts:

15 Mar 16:24:03 - [nodemon] v0.6.12
15 Mar 16:24:03 - [nodemon] watching: /home/user/.gvfs/thesite on my-pc/js
15 Mar 16:24:03 - [nodemon] starting `node home.js`
Server running at http://localhost:1337/
Is anyone home?

Looks fine.

But when I make a change to the coffee file, nodemon doesn’t do anything even though I can see that coffee is updating the home.js file in the js directory.

The file is on a gvfs share (gvfs = samba?). Could that be the issue?