Doesn't work with file watches

[yuanchuan]

Doesn't work with file watches

[yuanchuan]

I can't reproduce on my computer. What's your os and the node version?

Could you provide some code samples?

[Robinfr]

It might be because the path contains a ~ for the home folder. I've tried to get samples, but it works in most cases, just not the one I need it..

[yuanchuan]

Nodejs does not recognize '~' as the home path, so that might be the reason which caused the error.

By the way, make sure to copy the error message when you encounter the same error again.

[Robinfr]

The thing is, it never threw an error message, since you're catching the lstat error.. It simply didn't do anything at all.

[yuanchuan]

i'm a bit confusing. what's the exact lstat error?

[Robinfr]

That the path doesn't exist, since Node cannot resolve the `~` to the home folder. But that error is catched in a try/catch Op 9 mei 2017 9:02 a.m. schreef Yuán Chuān <[email protected]>: i'm a bit confusing. what's the exact lstat error? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<#44 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AD90FNzy-cwfGdcEP145xWq0h6ScaMEdks5r4A-WgaJpZM4NRl6D>.

[yuanchuan]

hmm.. Any suggestions on this?

[yuanchuan]

Wait.. Did you mean the error failed to catch this way:

watcher.on('error', function() {
  //
})

But can be caught by ?

try {
  watch('path_does_not_exist', function() {})
} catch (e) {
  // error
}

[Robinfr]

Ahh I realized I'm using an older version (0.4.1), so maybe the problem doesn't exist anymore in the latest version..

[Robinfr]

I will close this issue since it's not relevant to the latest version. Thanks for the help!