-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(dev): wait until all app server descendants have been killed #6663
Conversation
🦋 Changeset detectedLatest commit: 15489e3 The changes in this PR will be included in the next version bump. This PR includes changesets to release 18 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
6d2b335
to
82e900e
Compare
82e900e
to
15489e3
Compare
🤖 Hello there, We just published version Thanks! |
🤖 Hello there, We just published version Thanks! |
🤖 Hello there, We just published version Thanks! |
🤖 Hello there, We just published version Thanks! |
Previously, only the immediate child process run via
-c
was killed. When that child spawned its own subprocesses (e.g. usingbinode
for MSW support), those descendants stuck around, causing port conflicts and other errors.Testing
Existing HMR tests cover this. Also tested locally with Indie Stack + MSW