@autobusal/providers 1.42.0 → 1.43.1

package/Errors/ErrorBoundary.tsx

@@ -1,5 +1,6 @@
 import React from 'react';
 import Message from './Message';
+import { isRecoveringFromStaleChunk } from '../Setup/staleChunk';
 
 interface Props {
   children: JSX.Element[] | JSX.Element
@@ -36,6 +37,26 @@ class ErrorBoundary extends React.Component<Props, { hasError: boolean; missing:
 
   render() {
     if (this.state.hasError) {
+      /*
+       * Claude - 2026-08-31: say nothing while a stale-chunk reload is on its
+       * way.
+       *
+       * A build replaces every hashed chunk, so a tab left open overnight
+       * asks for files that no longer exist the moment somebody clicks a
+       * link. Setup/staleChunk catches that and reloads - which works, and
+       * which the visitor experienced as a flash of "something went wrong"
+       * first, because a synchronous re-render beats a navigation the browser
+       * has merely been asked to perform.
+       *
+       * Nothing at all rather than a spinner: the reload is a few hundred
+       * milliseconds away and the document is about to be replaced wholesale.
+       * A spinner appearing and vanishing in that window is the same flicker
+       * in a friendlier colour.
+       */
+      if (isRecoveringFromStaleChunk()) {
+        return null;
+      }
+
       return <Message type={ this.state.missing ? 'not_found' : 'error' } />;
     }
 

package/Setup/staleChunk.ts

@@ -93,6 +93,30 @@ const remember = (path: string): boolean => {
  * sites. Calling preventDefault stops Vite rethrowing, since we are handling
  * it by replacing the document.
  */
+/*
+ * Whether a recovery reload is already on its way.
+ *
+ * Claude - 2026-08-31. Ferjolt: "When the page is left open for some time and
+ * then click on any link on it, firstly it displays an error page for a
+ * extremely short moment and after that renders the right page."
+ *
+ * That flash is the ERROR BOUNDARY, and it is a race we were always going to
+ * lose. A failed dynamic import produces two things at once: this event, and
+ * a rejected lazy component that React hands to the nearest boundary. The
+ * boundary re-renders synchronously; window.location.reload() only asks the
+ * browser to navigate, and the browser is free to paint the frame it already
+ * has work for first. So the visitor sees "something went wrong" for one
+ * frame of a recovery that is working perfectly.
+ *
+ * A module-level flag rather than state: the boundary that needs to read this
+ * is a class component reacting to a throw, with no chance to subscribe to
+ * anything, and the answer has to be available synchronously inside
+ * getDerivedStateFromError.
+ */
+let recovering = false;
+
+export const isRecoveringFromStaleChunk = (): boolean => recovering;
+
 const registerStaleChunkRecovery = (): void => {
   window.addEventListener('vite:preloadError', (event) => {
     if (!remember(budgetKey())) {
@@ -103,6 +127,14 @@ const registerStaleChunkRecovery = (): void => {
 
     event.preventDefault();
 
+    /*
+     * Set BEFORE the reload is requested, so the error boundary can already
+     * see it on the render that the failed import is about to trigger. Never
+     * cleared: the only thing that follows is a fresh document, which starts
+     * with a fresh module and the flag back to false.
+     */
+    recovering = true;
+
     // reload() and not assign(): the URL is already the destination - React
     // Router changes it before rendering the route whose chunk just failed -
     // so this fetches a fresh index.html and lands on the page that was asked

package/package.json

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

package/types/users.ts

@@ -19,6 +19,12 @@ export interface UserData {
   // operator/employee accounts - whether the company's Shipments module is
   // on, so menus can hide the link instead of advertising a 403.
   shipping_enabled?: boolean | null
+  // Claude - 2026-08-31: whether this admin belongs to the MAIN label. Same
+  // job as shipping_enabled above - the platform-wide screens (database
+  // backups) answer a 404 to a whitelabel admin, and a menu should hide the
+  // link rather than advertise a door that does not open. Null for every
+  // non-admin type.
+  is_main_label?: boolean | null
   comissions: ComissionData
   subscription: SubscribedData
   api: ApiData