Mark Stacey b124ac29fc Improve detection of task process exit (#10776) ... Our build script waits for the `close` event to determine whether the task has exited. The `exit` event is a better representation of this, because if a stream is shared between multiple processes, the process may exit without the `close` event being emitted. We aren't sharing streams between processes, so this edge case doesn't apply to us. This just seemed like a more suitable event to listen to, since we care about the process exiting not the stream ending. See this description of the `close` event from the Node.js documentation [1]: >The `'close'` event is emitted when the stdio streams of a child >process have been closed. This is distinct from the `'exit'` event, >since multiple processes might share the same stdio streams. And see this description of the `exit` event: >The `'exit'` event is emitted after the child process ends. [1]: https://nodejs.org/docs/latest-v14.x/api/child_process.html#child_process_event_exit		2021-03-31 13:13:17 -02:30
..
display.js
etc.js
index.js
manifest.js
sass-compiler.js
scripts.js
static.js	build - fix use of empty file to replace unused js files (#10780)	2021-03-31 16:13:37 +08:00
styles.js
task.js	Improve detection of task process exit (#10776)	2021-03-31 13:13:17 -02:30