Merge pull request #874 from 0xProject/fix/request-timeout-issue

Fix Fetch Timeout Issue

1 files changed, 37 insertions, 0 deletions

diff --git a/packages/utils/src/fetchAsync.ts b/packages/utils/src/fetchAsync.ts
new file mode 100644
index 000000000..c02e5baba
--- /dev/null
+++ b/packages/utils/src/fetchAsync.ts
@@ -0,0 +1,37 @@
+import isNode = require('detect-node');
+import 'isomorphic-fetch';
+
+export const fetchAsync = async (
+    endpoint: string,
+    options: RequestInit = {},
+    timeoutMs: number = 20000,
+): Promise<Response> => {
+    if (options.signal || (options as any).timeout) {
+        throw new Error(
+            'Cannot call fetchAsync with options.signal or options.timeout. To set a timeout, please use the supplied "timeoutMs" parameter.',
+        );
+    }
+    let optionsWithAbortParam;
+    if (!isNode) {
+        const controller = new AbortController();
+        const signal = controller.signal;
+        setTimeout(() => {
+            controller.abort();
+        }, timeoutMs);
+        optionsWithAbortParam = {
+            signal,
+            ...options,
+        };
+    } else {
+        // HACK: the `timeout` param only exists in `node-fetch`, and not on the `isomorphic-fetch`
+        // `RequestInit` type. Since `isomorphic-fetch` conditionally wraps `node-fetch` when the
+        // execution environment is `Node.js`, we need to cast it to `any` in that scenario.
+        optionsWithAbortParam = {
+            timeout: timeoutMs,
+            ...options,
+        } as any;
+    }
+
+    const response = await fetch(endpoint, optionsWithAbortParam);
+    return response;
+};