You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When watching a directory, .on('watch', ...); fails to trigger after a file is saved for the second time onwards, but it does properly trigger when saved the first time.
However, .on('raw', ...) does trigger.
Versions (please complete the following information):
Chokidar version: 4.0.1
Node version: 18.18.0
OS version: Windows 11
To Reproduce:
Steps to reproduce the behavior. Include filename and chokidar config.
Then have a file in some/dir, open and edit it, make a change and save, then make a change and save again.
Expected behavior
Both onChange and onRaw trigger twice, with onRaw logging a "change" event specifically each time
Actual Behavior
Both onChange and onRaw trigger as expected on the first modification+save.
On the second modification+save, only onRaw triggers logging a "change" event, but no matching onChange event is triggered.
Additional context
This is specifically being observed with Adobe Acrobat editing a pdf, but I believe the issue is present for any type of file and editor on windows 11. I havent tested other OS/Editor/Filetype options yet.
The text was updated successfully, but these errors were encountered:
especially because your cwd is the same as the directory you're watching, in your example
that leads to all sorts of chaos. if I remove the cwd, it works as expected, otherwise I get a whole bunch of unrelated wackiness (which may be another thing to look into separate to this)
Describe the bug
When watching a directory,
.on('watch', ...);
fails to trigger after a file is saved for the second time onwards, but it does properly trigger when saved the first time.However,
.on('raw', ...)
does trigger.Versions (please complete the following information):
To Reproduce:
Steps to reproduce the behavior. Include filename and chokidar config.
Then have a file in
some/dir
, open and edit it, make a change and save, then make a change and save again.Expected behavior
Both
onChange
andonRaw
trigger twice, withonRaw
logging a "change" event specifically each timeActual Behavior
Both
onChange
andonRaw
trigger as expected on the first modification+save.On the second modification+save, only
onRaw
triggers logging a "change" event, but no matchingonChange
event is triggered.Additional context
This is specifically being observed with Adobe Acrobat editing a pdf, but I believe the issue is present for any type of file and editor on windows 11. I havent tested other OS/Editor/Filetype options yet.
The text was updated successfully, but these errors were encountered: