Deno process crashes while using node-fetch 2.x.x

[joamag]

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

software	version
node-fetch	v2.6.8+
deno	v1.31.3
Operating System	Windows

Additional context

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

[joamag]

PR added #1726 @jimmywarting

[jimmywarting]

Why do you want to use node-fetch when deno have it built in already?
...so those NodeJS v18

[joamag]

Why do you want to use node-fetch when deno have it built in already? ...so those NodeJS v18

Transitive dependency of a node API client package that makes use of node-fetch

[github-actions]

🎉 This issue has been resolved in version 2.6.12 🎉

The release is available on:

• npm package (@release-2.x dist-tag)
• GitHub release

Your semantic-release bot 📦🚀