Jesus sucks

backend/frontend/node_modules/@restart/hooks/esm/useStateAsync.js

@@ -0,0 +1,55 @@
+import { useCallback, useEffect, useRef, useState } from 'react';
+/**
+ * A hook that mirrors `useState` in function and API, expect that setState
+ * calls return a promise that resolves after the state has been set (in an effect).
+ *
+ * This is _similar_ to the second callback in classy setState calls, but fires later.
+ *
+ * ```ts
+ * const [counter, setState] = useStateAsync(1);
+ *
+ * const handleIncrement = async () => {
+ *   await setState(2);
+ *   doWorkRequiringCurrentState()
+ * }
+ * ```
+ *
+ * @param initialState initialize with some state value same as `useState`
+ */
+export default function useStateAsync(initialState) {
+  const [state, setState] = useState(initialState);
+  const resolvers = useRef([]);
+  useEffect(() => {
+    resolvers.current.forEach(resolve => resolve(state));
+    resolvers.current.length = 0;
+  }, [state]);
+  const setStateAsync = useCallback(update => {
+    return new Promise((resolve, reject) => {
+      setState(prevState => {
+        try {
+          let nextState;
+          // ugly instanceof for typescript
+          if (update instanceof Function) {
+            nextState = update(prevState);
+          } else {
+            nextState = update;
+          }
+
+          // If state does not change, we must resolve the promise because
+          // react won't re-render and effect will not resolve. If there are already
+          // resolvers queued, then it should be safe to assume an update will happen
+          if (!resolvers.current.length && Object.is(nextState, prevState)) {
+            resolve(nextState);
+          } else {
+            resolvers.current.push(resolve);
+          }
+          return nextState;
+        } catch (e) {
+          reject(e);
+          throw e;
+        }
+      });
+    });
+  }, [setState]);
+  return [state, setStateAsync];
+}