Jamie 397a375b37 Ensure next commands respect termination signals (#19433) ... Fixes #16173 ## What Restores handling of termination signals, `SIGTERM` and `SIGINT`, to allow graceful termination of next commands. Seems to have been removed during a child process refactor #6450, was this intentional? ## Why Currently the command processes have to be forcefully killed. This would help those using Next.js with custom servers and tools like Docker and Kubernetes that rely on termination signals to shutdown instances. --- Where would be a good location to add some tests? [test/integration/cli/test/index.test.js](fc98c13a2e/test/integration/cli/test/index.test.js)?		2020-11-25 13:30:06 +00:00
..
duplicate-sass	Warn on duplicate Sass deps (#16398)	2020-08-20 16:05:29 +00:00
experimental-react	Allow React experimental version without warning (#16140)	2020-08-18 01:54:31 -04:00
experimental-react-dom	Allow React experimental version without warning (#16140)	2020-08-18 01:54:31 -04:00
old-react	Warn when Fast Refresh is disabled (React <16.10) (#15931)	2020-08-06 10:41:11 -04:00
old-react-dom	Warn when Fast Refresh is disabled (React <16.10) (#15931)	2020-08-06 10:41:11 -04:00
pages	add --node-args option (#5858)	2018-12-15 22:55:59 +01:00
test	Ensure next commands respect termination signals (#19433)	2020-11-25 13:30:06 +00:00