-
-
Notifications
You must be signed in to change notification settings - Fork 578
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
Watching network drive '\\server\folder' does not work #895
Comments
I have the same issue watching a directory on a CIFS drive on Windows 10. |
I too had this problem |
I have the exact same issue as Zireal, watching a folder on our network drive does not work on Windows 10. I downgraded to 3.1.1, it does not fix the issue. |
Bump |
Changing to @3.1.1 worked for me |
Changing to @3.1.1 worked for me as well. I was on 3.4.0 when it wasn't working. |
+1 here 👋 @paulmillr What's the status for this issue? Thank you! |
No status. Feel free to debug this and provide a pull req. |
Confirming version If I Map network drive to |
I did some debugging, I think I see the issue: And here's the line that causes the trouble: while (str.match(DOUBLE_SLASH_RE)) {
str = str.replace(DOUBLE_SLASH_RE, SLASH);
} Simply replaces the double slash with a single slash |
@paulmillr -- thank you for your excellent library 🙇 I feel like I've correctly identified where the problem happens (replacing double slashes with a single slash) ✅ I suspect one solution is to somehow ignore the double slashes if they occur as the first characters 🤔 I don't know what would be the best way to fix this without breaking something for everyone else. I'm happy to make a PR if you suggest how I should handle it 😁 🤝 😄 |
This worked for me to get it to listen to a network folder correctly. But then I eventually had to shut it off and reroute things to a local project folder. The reason being once I had this monitoring a network folder my database called with the OracleDB package slowed WAY down. Simple Select queries were taking around 10 seconds and once I changed Chokidar to monitor a network folder I got the queries back down to less than .1 seconds. I'm not sure why but just passing along my experience. |
👋 @paulmillr -- please let me know if the solution I propose to this problem (see above) is acceptable, namely: do not replace double slash I would like to create a PR, but wanted confirmation that this is an acceptable (mergeable) solution or if you prefer something else 🙇 |
@whyboris try doing this and see if tests fail on any platform |
PR to solve the problem 🤞 #1025 😁 |
@paulmillr I think this issue should not be closed while there is no new chokidar release available via npm that includes the fix provided by @whyboris. BTW: Thanks a lot for your work on chokidar 👍 🙏 |
I'm still having this issue, I hope the PR that fixes it will be available in the next chokidar update |
@oumad -- seems like the fix is available since release |
Interesting, then I don't know why for some reason I get no event fired when I try watching a directory in this format Edit : I have been using the |
have the same issue with chokidar 3.5.3 In local folders, it works perfectly. But it doesn't work with remote folders with the same functions Linux machine |
Hi
I have a problem where chokidar does not report changes to network shared folder, i.e.
\\\\file.server.net\\dev\\7500
. Usingfs.writeFile()
on that folder works fine and a file gets created by Node. I'm under Win10.My config is below. I tried both with
usePolling
true and false, no change.I don't get any errors, just changes to network folder don't get reported. Watching a folder on local drive C:\db works fine. Watching that network drive using drive letter path format actually works too
s:\\dev\\7500
. I'd prefer to use server path notation in case drive mapping letters get changed in future, or some users in the company have different letters mapped.Do you see anything amiss in my setup?
The text was updated successfully, but these errors were encountered: