General stuff
v3 may have been short lived, cuz of how long time we dragged out on esm.
We already have a milestone for v4 with few issues in it.
NodeJS v12 will soon end its LTS version in April, so i was thinking of dropping support any prior version and remove all the hacks we have around it in the current branch.
I was thinking about setting the lowest supported node version to v14.17.0
not 14.13.1 as we have today that is meant for ESM
why? cuz http.request supports signal in v14.17.0
then we can also use finalizers that got introduced in v14.6.0 and cleanup the response (and the cloned res) when it's forgotten and not consumed
Is there any bug/issue/features we would like to finish or complete before we branch out of v3 and start working on v4?
cc @bitinn @TimothyGu @jkantr @gr2m @Richienb @ronag @LinusU
General stuff
v3 may have been short lived, cuz of how long time we dragged out on esm.
We already have a milestone for v4 with few issues in it.
NodeJS v12 will soon end its LTS version in April, so i was thinking of dropping support any prior version and remove all the hacks we have around it in the current branch.
I was thinking about setting the lowest supported node version to v14.17.0
not 14.13.1 as we have today that is meant for ESM
why? cuz http.request supports signal in v14.17.0
then we can also use finalizers that got introduced in v14.6.0 and cleanup the response (and the cloned res) when it's forgotten and not consumed
Is there any bug/issue/features we would like to finish or complete before we branch out of v3 and start working on v4?
http.request(url { signal }).bodyto be a whatwg stream^ 14.17.0 || >=16.0.0"?ReadableStream.prototype.teeinstead.buffer()#1485sizeoption (fixes Deprecate size option #1438)cc @bitinn @TimothyGu @jkantr @gr2m @Richienb @ronag @LinusU