Using deno (which now supports npm packages) and node-fetch 2.x.x yields an unhandled error due to "socket" event not being triggered.

I believe keeping deno compatibility is not a priority but a simple undefined testing in the socket variable should fix the issue.

Reproduction

Steps to reproduce the behavior:

1. Use deno and node-fetch
2. Perform a simple fetch operation (ex: GET)
3. Verify that the deno process has exited with an Uncaught error on fixResponseChunkedTransferBadEnding()

Expected behavior

No unhandled error is raised and the fetch requests are handled properly.

Screenshots

Your Environment

Additional context

This is verified only while using deno and not in node.js.