--------------
node: v5.1.1
nodemon: 1.8.1
command: C:\Users\Alexander Moon\AppData\Local\scoop\apps\nodejs\5.1.1\nodejs\node.exe C:\Users\Alexander Moon\AppData\Local\scoop\apps\nodejs\5.1.1\nodejs\node_modules\nodemon\bin\nodemon.js -e js -w lib main.js --dump
cwd: D:\Tactic\nurse.git\backend
OS: win32 x64
--------------
{ run: false,
system: { cwd: 'D:\\Tactic\\nurse.git\\backend' },
required: false,
dirs: [ 'D:\\Tactic\\nurse.git\\backend\\lib' ],
timeout: 1000,
options:
{ watch: [ 'lib', re: /lib/ ],
dump: true,
ignore:
[ '.git',
'node_modules',
'bower_components',
'.sass-cache',
re: /\.git|node_modules|bower_components|\.sass\-cache/ ],
ignoreRoot: [ '.git', 'node_modules', 'bower_components', '.sass-cache' ],
restartable: 'rs',
colours: true,
execMap: { py: 'python', rb: 'ruby' },
stdin: true,
runOnChangeOnly: false,
verbose: false,
stdout: true,
execOptions:
{ script: 'main.js',
exec: 'node',
args: [],
scriptPosition: 0,
nodeArgs: undefined,
ext: 'js',
env: {},
execArgs: [] },
monitor:
[ 'D:\\Tactic\\nurse.git\\backend\\lib/**/*',
'!.git',
'!D:\\Tactic\\nurse.git\\backend\\node_modules/**/*',
'!bower_components',
'!.sass-cache' ] },
load: [Function],
reset: [Function: reset],
lastStarted: 0,
loaded: [],
watchInterval: null,
command:
{ raw: { executable: 'node', args: [ 'main.js' ] },
string: 'node main.js' } }
--------------
I suspect it's this:
'D:\\Tactic\\nurse.git\\backend\\lib/**/*',
Looks like this was the issue some time ago: #260
I'm experiencing the same issue
This issue has been automatically marked as idle and stale because it hasn't had any recent activity. It will be automtically closed if no further activity occurs. If you think this is wrong, or the problem still persists, just pop a reply in the comments and @remy will (try!) to follow up.
Thank you for contributing <3
It is still an issue. If you update from a Windows 10 64 machine a file that is being monitored in an alpine distribution in docker, nodemon doesn't restart.
Just putting it up here for anyone who experiences the issue and cannot find a work-around.
The official docs say:
Application isn't restarting
In some networked environments (such as a container running nodemon reading across a mounted drive), you will need to use the
legacyWatch: truewhich enables Chokidar's polling.Via the CLI, use either
--legacy-watchor-Lfor short:
bash nodemon -LThough this should be a last resort as it will poll every file it can find.
@AdamBraun I confirm that the workaround works. The strange thing is that this only happens on my Windows 10 environment. Same docker and codebase don't give this problem on my other OSX environment. Is this a bug on Nodemon?
No, is a missing functionality in Samba. More exactly the notify system in Linux based systems which basically monitors and propagate any change to listening applications.
Just putting it up here for anyone who experiences the issue and cannot find a work-around.
The official docs say:Application isn't restarting
In some networked environments (such as a container running nodemon reading across a mounted drive), you will need to use the
legacyWatch: truewhich enables Chokidar's polling.
Via the CLI, use either--legacy-watchor-Lfor short:nodemon -LThough this should be a last resort as it will poll every file it can find.
This works for me! Thanks!
Most helpful comment
Just putting it up here for anyone who experiences the issue and cannot find a work-around.
The official docs say: