Open
Description
Version
v20.15.1
Platform
Linux derby 6.6.46-0-lts #1-Alpine SMP PREEMPT_DYNAMIC 2024-08-16 08:05:54 x86_64 Linux
Subsystem
No response
What steps will reproduce the bug?
f.js contains only console.log('hello')
node --watch f.js
hello
Completed running 'f.js'
Change f.js to console.log('hello world')
Restarting 'f.js'
hello world
Completed running 'f.js'
Change f.js again, e.g. console.log('this change will not restart watcher')
No change in the watch output.
(I'm changing the file outside of the debounce/throttle period)
How often does it reproduce? Is there a required condition?
It happens every time.
What is the expected behavior? Why is that the expected behavior?
I would expect that --watch
would restart after every write to f.js
, not just after the first change made to the file.
What do you see instead?
--watch
only seems to restart after making the first change to the file.
Additional information
Also seeing this problem on Termux for Android node v22.5.1