💬 Aborted requests for streams & deprecation notice

Hi 👋

I'm running into the exact same issue as described in #607. That seems to have been fixed but I'm afraid that it might not work with newer Node.js versions since aborted has been deprecated meaning it has stability 0:

Stability: 0 - Deprecated. The feature may emit warnings. Backward compatibility is not guaranteed.

So even with the fix in the above issue, Fastify will throw the error rather than just log it for me when I abort a request from the Browser. If I add a simple check for destroyed instead which is the recommended property to check for, Fastify will log the error and not throw it, which is the desired behaviour.

Thank you!

Your Environment

• node version: 20.11.0
• fastify version: 4.26.0
• os: Mac, Linux