We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I get the following error if I delete a directory that is within the directory I am watching. It crashes the node server. I'm on Windows 8 64bit.
events.js:71 throw arguments[1]; // Unhandled 'error'event Error: watch EPERM at errnoException (fs.js:806:11) at FSEvent._handle.onchange (fs.js:824:26)
It happens on both hard delete and deleting to recycle bin, and whether the directory is empty or not.
When using pure fs.watch it does not happen, although oddly fs.watch reports a rename event, not a delete or remove.
The text was updated successfully, but these errors were encountered:
Thanks for reporting!
Actually the unhandled error was caused by the fs.watch. Its underlying implemetation varies across platforms as stated in this issue, same problem.
fs.watch
Anyway I've submited a quick patch for this issue by handling the error silenlty. Just do npm update node-watch and hope that will work for your code.
npm update node-watch
Sorry, something went wrong.
Awesome. Worked Great. Thanks for fixing that so fast.
No branches or pull requests
I get the following error if I delete a directory that is within the directory I am watching. It crashes the node server. I'm on Windows 8 64bit.
It happens on both hard delete and deleting to recycle bin, and whether the directory is empty or not.
When using pure fs.watch it does not happen, although oddly fs.watch reports a rename event, not a delete or remove.
The text was updated successfully, but these errors were encountered: