Investigate why `jest` exits immediately, since a socket pool is created about fetch HOT 5 CLOSED

@styfle Looks like a mistake, 32d78b4 is just a license update entirely unrelated to this issue.

from fetch.

Just had this problem the other day - it was an async/await issue. May be unrelated, but I remember wondering the same thing.

Let's make sure we're using promises correctly and not missing some async keyword or something

from fetch.

It's possible to call socket.deref() or something like that as well to have an open socket that doesn't keep the event loop running. Perhaps they're using that feature (I believe that the built-in HTTP agent does this).

from fetch.

The solution I've used in the past is a timeout promise that either times out and rejects, or otherwise allows you to mark something as resolved by exposing the resolver function.

I've noticed this be a problem with the async function main(argv) { return 0; } approach, cc @rauchg

from fetch.

Thank you for the report. We are archiving this project; you can read more details here: #83

from fetch.