[Miniflare 3] Fix Miniflare#dispose()
immediately after new Miniflare()
#705
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We previously waited for Miniflare to be ready before
dispose()
ing. Unfortunately, we weren't waiting for theworkerd
config to finish being written to stdin. Callingdispose()
immediately afternew Miniflare()
would stop waiting for socket ports to be reported, and kill theworkerd
process while data was still being written. This threw an unhandledEPIPE
error.This changes makes sure we don't report that Miniflare is ready until after the config is fully-written.
Closes cloudflare/workers-sdk#4363