`undici.fetch` breaks on Node.js <=18.13.0 in [email protected] about undici HOT 10 CLOSED

I think it's safe to say we support only recent versions of Node.js and we didn't update package.json.

Mostly because we do not test for them.
I generically follow the rule that only the latest version of a series is supported, mostly because it's impossible work to test them all and we should be encouraging people to upgrade

from undici.

Why not upgrading node version too?

from undici.

Why not upgrading node version too?

This isn't relevant.

This is caused by 8a07bbd which uses stream.finished. The node docs did not mention that support for web streams was added in some unknown v18 release ☹️.

The fix is either to drop support for v18 prior to said addition, or fallback to the previous solution if we can't use stream.finished.

from undici.

It is relevant for the decision if we drop support for node versions < 18.17.0 or if we fix the support for node 18.14.0. In fastify we expect that a reasonable version of node has to be used. so nobody can demand, that we support node 14.0.0, but we support latest node 14.

from undici.

node 14 is EOL, node 18 isn't

from undici.

it is the principle. We also dont support older versions of node 18 or 20, despite them being not EOL:

from undici.

That's not true, we currently support any version of node >= v18:

from undici.

I was in the context of fastify.

from undici.

Please downgrade undici to v6.12.0 or upgrade your node version to the latest version of v18.

from undici.

Okay, thanks. To be clear, I don't need undici to support the older Node v18 versions for my case. I just needed to be clear what versions it did support.
It would be helpful if "engines" was updated to a realistic value, but perhaps that is difficult if the intent will be to only support the very latest.

from undici.