Unresolved behavior of nodemon’s batch restart logic on rapid file changes
Goal Determine how nodemon handles successive file changes that occur in quick succession. The objective is to understand whether nodemon restarts the application once per detected batch or after each individual change, and how the built‑in debounce mechanism influences this. Context and Constraints Rapid edits trigger multiple file‑watch events before nodem
nodemon