@autobusal/providers 1.29.4 → 1.30.1

package/CHANGELOG.md

@@ -1,5 +1,30 @@
 # Changelog
 
+## 1.30.1
+
+### Fixed
+
+- **Only the documents 403 redirects to the documents page.** This fired on
+  every 403 there is. The intent is sound - an account blocked by an unsigned
+  document should be taken to the screen that unblocks it - but the other
+  source of a 403 in this API is the email-verification gate, and sending
+  somebody there for that told them nothing and fixed nothing. It read as a
+  deliberate product redirect and was this line. Keyed on a `reason` the
+  server sets rather than the message, which is translated fifteen ways, and
+  guarded against redirecting the documents page to itself.
+
+## 1.30.0
+
+### Added
+
+- **`BootstrapError` tells a transient failure from a real one and recovers
+  by itself.** A rate limit or a dropped connection is not a system error,
+  and "something broke on our side" is wrong twice for either: it blames the
+  wrong thing, and it hands the visitor a reload button for a situation where
+  reloading immediately makes it worse. 429/503/504 and a request with no
+  response at all now get their own wording and an automatic retry that backs
+  off 5s, 10s, 20s, 30s.
+
 ## 1.29.4
 
 ### Added

package/Errors/BootstrapError.tsx

@@ -35,11 +35,63 @@ interface Props {
  * *into*. A full reload is the honest recovery, and it is what a visitor
  * would do anyway.
  */
-class BootstrapError extends React.Component<Props, { failed: boolean }> {
-  state = { failed: false };
+/**
+ * Is this a failure that fixes itself?
+ *
+ * Edited: Ferjolt Ozuni - Date: 2026-08-07
+ *
+ * A rate limit and a dropped connection are not system errors, and telling
+ * somebody "something broke on our side" for either is wrong twice over: it
+ * blames the wrong thing, and it hands them a reload button for a situation
+ * where reloading immediately is the one move that makes it worse.
+ *
+ * Read off the axios error rather than the message text, which is not
+ * stable. A 429 carries a status; a network failure carries none at all,
+ * which is what distinguishes it from a server that answered with a fault.
+ */
+const transient = (error: any): 'busy' | 'offline' | null => {
+  const status = error?.response?.status ?? error?.status;
+
+  if (status === 429) {
+    return 'busy';
+  }
+
+  if (status === 503 || status === 504) {
+    return 'busy';
+  }
+
+  // No response at all - DNS, offline, connection refused, CORS preflight
+  // that never landed. Distinct from a server that replied with a 500.
+  if (error?.isAxiosError && !error?.response) {
+    return 'offline';
+  }
+
+  return null;
+};
+
+/**
+ * How long to wait before trying again.
+ *
+ * The rate limiter's window is a minute, so a few seconds is usually enough
+ * and a full minute feels broken. Backs off on each successive failure so a
+ * genuinely overloaded server is not hammered by every open tab at once.
+ */
+const DELAYS = [ 5, 10, 20, 30 ];
+
+interface State {
+  failed: boolean
+  kind: 'busy' | 'offline' | null
+  attempt: number
+  countdown: number
+}
 
-  static getDerivedStateFromError() {
-    return { failed: true };
+class BootstrapError extends React.Component<Props, State> {
+  state: State = { failed: false, kind: null, attempt: 0, countdown: 0 };
+
+  private timer?: ReturnType<typeof setInterval>;
+
+  static getDerivedStateFromError(error: Error) {
+    return { failed: true, kind: transient(error) };
   }
 
   componentDidCatch(error: Error, info: React.ErrorInfo): void {
@@ -47,6 +99,45 @@ class BootstrapError extends React.Component<Props, { failed: boolean }> {
     // knows the app failed to start, and a white page with a `log` entry is
     // easy to miss when somebody finally does open the console.
     console.error('[bootstrap] the application could not start', error, info);
+
+    /*
+     * A transient failure retries itself. The visitor did nothing wrong and
+     * has nothing useful to do, so asking them to press a button is asking
+     * them to do our waiting for us - and the thing they would press it for
+     * is a rate limit that clears on its own.
+     */
+    if (transient(error)) {
+      this.countdownTo(this.state.attempt);
+    }
+  }
+
+  componentWillUnmount(): void {
+    if (this.timer) {
+      clearInterval(this.timer);
+    }
+  }
+
+  private countdownTo(attempt: number): void {
+    const seconds = DELAYS[Math.min(attempt, DELAYS.length - 1)];
+
+    this.setState({ countdown: seconds });
+
+    this.timer = setInterval(() => {
+      this.setState(state => {
+        if (state.countdown > 1) {
+          return { ...state, countdown: state.countdown - 1 };
+        }
+
+        clearInterval(this.timer);
+
+        // A full reload rather than resetting this boundary: whatever
+        // suspended did so during bootstrap, so there is no reliable state
+        // to retry INTO - the same reasoning as the button below.
+        window.location.reload();
+
+        return { ...state, countdown: 0 };
+      });
+    }, 1000);
   }
 
   render() {
@@ -59,6 +150,26 @@ class BootstrapError extends React.Component<Props, { failed: boolean }> {
     const language = getLanguage('en');
     const copy = errors[language as keyof typeof errors] ?? errors.en;
 
+    /*
+     * Edited: Ferjolt Ozuni - Date: 2026-08-07
+     * A transient failure gets its own words and its own countdown. The
+     * generic system error keeps the reload button, because for a real
+     * fault there is nothing to wait for.
+     */
+    const { kind, countdown } = this.state;
+
+    const title = kind === 'busy' ? (copy as any).busy ?? copy.system : copy.system;
+
+    const detail = kind === 'busy'
+      ? ((copy as any).busy_detail ?? copy.system_detail)
+      : kind === 'offline'
+        ? ((copy as any).offline_detail ?? copy.system_detail)
+        : copy.system_detail;
+
+    const message = kind
+      ? String(detail).replace('{n}', String(countdown))
+      : detail;
+
     return (
       <div
         role="alert"
@@ -75,11 +186,11 @@ class BootstrapError extends React.Component<Props, { failed: boolean }> {
       >
         <div style={ { maxWidth: '460px', textAlign: 'center' } }>
           <h1 style={ { fontSize: '20px', lineHeight: 1.4, margin: '0 0 12px' } }>
-            { copy.system }
+            { title }
           </h1>
 
           <p style={ { fontSize: '15px', lineHeight: 1.6, margin: '0 0 24px', opacity: 0.8 } }>
-            { copy.system_detail }
+            { message }
           </p>
 
           <button

package/Queries/apiClient.ts

@@ -88,8 +88,31 @@ apiClient.interceptors.response.use(response => (
       return Promise.reject(error);
     }
 
-    // if the user is not valid
-    if (error.response.status === 403) {
+    /*
+     * Edited: Ferjolt Ozuni - Date: 2026-08-07
+     *
+     * Only the DOCUMENTS 403 goes to the documents page.
+     *
+     * This used to fire on every 403 there is. The intent is sound - an
+     * account blocked by an unsigned document should be taken to the one
+     * screen that unblocks it - but the other source of a 403 in this API is
+     * the email-verification gate, and sending somebody there for that told
+     * them nothing and fixed nothing. It read as a deliberate product
+     * redirect; it was this line.
+     *
+     * Keyed on a `reason` the server sets (Middleware\ValidUser), not on the
+     * message: that text is translated into fifteen languages, so comparing
+     * it would work in one.
+     *
+     * The pathname guard matters as much as the reason. Without it, a 403
+     * raised BY the documents page redirects the documents page to itself,
+     * which is a reload loop rather than a fix.
+     */
+    if (
+      error.response.status === 403
+      && error.response.data?.reason === 'documents'
+      && window.location.pathname !== '/account/documents'
+    ) {
       window.location.href = '/account/documents';
     }
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@autobusal/providers",
-  "version": "1.29.4",
+  "version": "1.30.1",
   "author": "Ferjolt Ozuni",
   "type": "module",
   "main": "index.ts"