cc @kricsleo wdyt? I think we dont need to use the custom AbortController, we should be able to only use the signal 😄

I'm not using these APIs just for compatibility reasons; AbortSignal.timeout() is available in Chrome 124+, and AbortSignal.any is available in Node.js 20.3+. This seems too strict.

AbortSignal.timeout() is available in Chrome 124+

Actually it is Chrome 103+, but with AbortError instead of Timeout Error. But you are right AbortSignal.any is Chrome 116+ 🤔

Both are available in latest baseline which is good. However we could do better with backward compat and introduce new API requirements in a major.

• If there is only one signal, we don't need AbortSignal.any wrapper
  -AbortSignal.timeout is not always required.

Codecov Report

❌ Patch coverage is 75.00000% with 1 line in your changes missing coverage. Please review.
✅ Project coverage is 93.17%. Comparing base (27996d3) to head (5be353a).
⚠️ Report is 90 commits behind head on main.

@@             Coverage Diff             @@
##             main     #508       +/-   ##
===========================================
+ Coverage   56.86%   93.17%   +36.30%     
===========================================
  Files          16        4       -12     
  Lines         728      205      -523     
  Branches      113      110        -3     
===========================================
- Hits          414      191      -223     
+ Misses        303       14      -289     
+ Partials       11        0       -11     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

like this?