-
Notifications
You must be signed in to change notification settings - Fork 261
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
file watching doesn't work as expected on Windows #69
Comments
Do you mean it's no longer recursively watching everything in a directory? It was working at some point - we couldn't always get the exact filename that had changed, but could at least detect change events. I would like to unify the system calls. I'm hesitant though because as noted in nodejs/node-v0.x-archive#2049, it's not totally clear which option is preferred - the core guys stated at one point that So my point is that neither of the options looks totally great to me right now. Thoughts? |
As you know Not just leaking exact filename, but leaking the event too. I can understand why the implementation of So here is my thought: seek directories recursively like non-windows implementation and watch directory only not each files. pseudo code:
|
Closed by #70. |
fs.watch on Windows lies on below function:
https://github.com/joyent/libuv/blob/95e89c6a0efec2d2228377cfdf55cd14b1b83536/src/win/fs-event.c#L69
as you can see on the fourth option(FALSE) it doesn't watch any changes of subtree's.
I suggest use the same function - watchFile - as used for non-win32 implements.
The text was updated successfully, but these errors were encountered: