Doesn't detect change in nested files (on Linux)
See original GitHub issueHey, Luke 👋🏻
So I was trying snowpack out, and the docs brought me here. Their doc highly recommends servor
. 😉 I’ve watched you in YT on pushing the web forward on a bundle-less future. I’m excited that it’s becoming more mainstream.
So I’m using this in Ubuntu via WSL / Windows 10; while it reloads fine when I change the index.html, it doesn’t reload if I change the JS file.
Here’s a screencast I made to document the error.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:3
- Comments:23 (9 by maintainers)
Top Results From Across the Web
Why doesn't inotifywatch detect changes on added files?
The command used by the OP will never output file names because the watches are set for /tmp and any subdirectories therefore statistics...
Read more >How can I detect if some file in a subdir changed?
Basically I have a big directory (>10GB)(each subdir only has a few other subdirs) and want to do sth to any files that...
Read more >Execute a Command Whenever File or Directory Changes
Learn how to monitor a directory recursively and execute a command whenever the files and directories within it change.
Read more >File nesting rules for Solution Explorer - Visual Studio (Windows)
Solution Explorer how to nest files. You can add as many custom file nesting settings as you like, and you can switch between...
Read more >How To Use Find and Locate to Search for Files on Linux
The Linux “find” and “locate” commands can both be used to search for ... To find files that last had their meta information...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@nakleiderer I actually agree with you on size being less important, since this is a dev dependency.
But the author seems he wanted this to be fixed at the main library level without dependency. Let’s wait. The main thing here is we can’t rely on Node’s Native fs.watch. It’s a buggy implementation. 🙊 That’s the whole reason, chokidar, node-watch, cheap-watch, and other permutations exist.
@thisguychris Fair points all around. I’ve mainly used chokidar in environments where dependency size is largely irrelevant, so I wasn’t familiar with the size. Thanks for the insight!
Is it a goal of this project to be light-weight on dependencies? I see that mentioned as a feature in the docs, but I’m curious if that is intended to be a defining trait of this project or a reflection of its current state. Is it a goal of this project to be used in deployed environments or as a development tool? If it’s a development tool, then dependency weight is less important in this project than it is for Sapper, which is run in deployed environments. I agree that chokidar’s size is disproportionate to the current size of this project, though it appears to be a more mature project than some of the alternatives with a large following. Popularity isn’t everything though.
Obviously, I’m happy with any solution to the problem. I think a clarification on the principles/goals of this project can help the community contribute more effectively. Again, thanks for the reply 😃