fix: fixes issue #1476 after introduced again by version 2.0.2

[marcelkottmann]

Hey @remy , seems like issue #1476 was introduced again by version 2.0.2. Please look at my new comment in #1476 (comment)

We have to wait for all subprocess to shutdown before killing the main process. Killing the main process has the side effect of emitting the exit-event, which in turn starts the program again (too early) before the child processes have been terminated.

I updated the test repository to reproduce this error with nodemon@2.0.2 and to test the fix: https://github.com/marcelkottmann/test-nodemon-issue-1476

[hphvac]

Would be nice, this problem still exists for me

[remy]

The change in the order which the processes are stopped was intentional. Specifically this change: 47dfb8b

Can you check that your change still allows the origin issue to be solved? #1638 (I appreciate this was from a refactor with the release of 2.0.1 that simplified your original code - which was also fixed bugs on linux platforms)

[stale]

This issue has been automatically marked as idle and stale because it hasn't had any recent activity. It will be automtically closed if no further activity occurs. If you think this is wrong, or the problem still persists, just pop a reply in the comments and @remy will (try!) to follow up.
Thank you for contributing <3

[hphvac]

I am currently running 2.0.2. I believe that the issue you referenced doesn't apply to me.

[stale]

This issue has been automatically marked as idle and stale because it hasn't had any recent activity. It will be automtically closed if no further activity occurs. If you think this is wrong, or the problem still persists, just pop a reply in the comments and @remy will (try!) to follow up.
Thank you for contributing <3