-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
Implement fs.watch
#832
Comments
|
fs.watch
I know watch is problematic even in Node as there are no guarantees it works reliably cross platform but when it comes to Bun core features, being unable to watch a This is also a blocker for anyone liking to indirectly communicate back-forward with Python libraries for IoT purpose on Bun capable targets and if this is of any any help, filebus based on inotifywait-spawn provides all primitives to have watch reliable wherever inotify-tools can run. P.S. inotify-tools are available in both all Linux and Macs via home brew |
Yes important feature needs to be a priority. If not node:fs.watch, at least do Bun.watch() |
Implemented in #3249 (will be available in release 0.6.10) |
Version
Canary 0.1.5
Platform
Linux davidpc 5.15.0-41-generic #44-Ubuntu SMP Wed Jun 22 14:20:53 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
What steps will reproduce the bug?
Earlier I reported that running Chokidar throws lots of errors about
stats.isSymbolicLink
not existing. That is fixed as of the Canary build of 0.1.5, thank you.With 0.1.5 there is still an error in Chokidar -
fs.watch
does not exist, and if you Import thefs
module it is indeed undefined.The following code was written primarily to be a performance test, but it will demonstrate the error.
Another piece of source is this:
How often does it reproduce? Is there a required condition?
Every time
What is the expected behavior?
With
choke.mjs
the output for Node is:And for
fsw.mjs
it is:What do you see instead?
These are run using the Canary build of 0.1.5
And for
choke.mjs
there is one instance of this error for each file:Additional information
No response
The text was updated successfully, but these errors were encountered: