Closed tom-kuca closed 2 months ago
All we can tell about what's going on in the filesystem is what the OS tells us, filtered through the watcher library we use (since it looks like you're using the native Dart VM CLI, that would be Dart's watcher
package). I recommend trying to find a reproduction of this using that package and filing an issue with it. In the meantime, you can use the --poll
option to fall back on a manual filesystem polling strategy rather than using the OS-level watcher, which is less efficient but more reliable.
Closing this because there's no action we can take in this repo to fix it.
Thanks for the feedback. I added a few debug prints and I confirm that dart-sass receives only remove event when it happens, the problem is not here.
I edit a file in my editor while
dartsass --watch
is running. When the last write was more than ~10 s ago, the file is not compiled and the output file is deleted.In order to simulate it, I opened neovim, and called
:write
repeatedly without doing any changes toapplication.sass
.I expected the file to be always compiled, but it was Deleted twice. I had to run
:write
again in order to compile it.Here is the output of
inotifywait
from the timeframe:I can reproduce it reliably. The idle time needed for a failure varies a little bit, it's close to 10 s.
I'm running Arch linux: