i guess not many won't even pass in the shouldKeepAlive option in the request, it's just another node-fetch specific option, I'm always a bit hesitated adding node-fetch specific option into node-fetch that isn't part of the spec. We should try to automatically solve this kind of issues if we can, So that developers don't have to worry about such edge cases.

Nowhere in the readme is there any mention of the option shouldKeepAlive option.
so the readme needs to be updated if we want to expose this shouldKeepAlive option.

basically the fixResponseChunkedTransferBadEnding will likely never be used cuz nobody is using the new shouldKeepAlive option today... will this change improve things rather then bringing back an old issue that the fixResponseChunkedTransferBadEnding function is doing?

For the v4 milestone we will likely not be using pipeline anymore as we will transition to whatwg streams and instead uses pipeThrough and pipeTo... do you think it will have any impact when we ditch the pipeline?

v4 will also likely drop support for NodeJS below v14.17