It's not optional in the browser DOM signature which this is emulating, and it's not clear what the behavior of a fetch() should be if it were given undefined. Type-wise, making this optional requires any client code providing a fetch() function to handle the undefined value, even though it's nonsensical.
See also https://github.com/comunica/comunica/pull/1233: Comunica's fetch() implementations don't accept undefined, but it wasn't breaking because "strictFunctionTypes": false was ignoring the errors.
It's not optional in the browser DOM signature which this is emulating, and it's not clear what the behavior of a
fetch()
should be if it were givenundefined
. Type-wise, making this optional requires any client code providing afetch()
function to handle theundefined
value, even though it's nonsensical.See also https://github.com/comunica/comunica/pull/1233: Comunica's
fetch()
implementations don't acceptundefined
, but it wasn't breaking because"strictFunctionTypes": false
was ignoring the errors.