fix: use a normal Error when DOMException isn't available (#5161)

* use a normal Error when DOMException isn't available

* fix instanceof check

* sometimes DOMExceptions aren't Errors, apparently

* account for undefined DOMException

Author: EskiMojo14

packages/toolkit/src/query/fetchBaseQuery.ts

@@ -305,7 +305,10 @@ export function fetchBaseQuery({
       return {
         error: {
           status:
-            e instanceof DOMException && e.name === 'TimeoutError'
+            (e instanceof Error ||
+              (typeof DOMException !== 'undefined' &&
+                e instanceof DOMException)) &&
+            e.name === 'TimeoutError'
               ? 'TIMEOUT_ERROR'
               : 'FETCH_ERROR',
           error: String(e),

packages/toolkit/src/query/utils/signals.ts

@@ -1,10 +1,16 @@
 // AbortSignal.timeout() is currently baseline 2024
 export const timeoutSignal = (milliseconds: number) => {
   const abortController = new AbortController()
-  setTimeout(
-    () => abortController.abort(new DOMException('', 'TimeoutError')),
-    milliseconds,
-  )
+  setTimeout(() => {
+    const message = 'signal timed out'
+    const name = 'TimeoutError'
+    abortController.abort(
+      // some environments (React Native, Node) don't have DOMException
+      typeof DOMException !== 'undefined'
+        ? new DOMException(message, name)
+        : Object.assign(new Error(message), { name }),
+    )
+  }, milliseconds)
   return abortController.signal
 }