Grunt watch spawn:false leads to persistent global state
Problem Context The goal is to understand how the watch task’s spawn option influences global state across successive file changes. In particular, when spawn:false is used, tasks run in the same process, allowing variables and configuration to persist. This can be advantageous for speed but may introduce stale or corrupted data, memory leaks, and unpredictab