@autobusal/providers 1.44.0 → 1.44.2

package/Setup/analytics.ts

@@ -42,13 +42,46 @@ const analytics = (container: string | null | undefined): void => {
   window.dataLayer = window.dataLayer || [];
   window.dataLayer.push({ 'gtm.start': Date.now(), event: 'gtm.js' });
 
-  const script = document.createElement('script');
+  /*
+   * LOADED IN THE FIRST QUIET MOMENT, not while the page races for the
+   * network.
+   *
+   * Edited: Claude - Date: 2026-09-16
+   *
+   * Measured with Lighthouse against production on a throttled phone: the
+   * container and the GA tag it pulls are 287 KB of script - more than this
+   * app's own entry chunk - fetched in the same window as the bundle, the
+   * translations and the images, on a connection modelled at 1.6 Mbps. The
+   * page is no more usable for having them early, and every byte they take
+   * is one the content is waiting for.
+   *
+   * The dataLayer is filled FIRST, above, and GTM reads whatever is already
+   * in it when it boots - so a page view or a commerce event announced in
+   * the meantime still arrives. That is the only thing that could have made
+   * deferring this wrong.
+   *
+   * Safari has no requestIdleCallback, so setTimeout is the fallback rather
+   * than a polyfill: "soon, after the load" is the whole requirement.
+   */
+  const load = (): void => {
+    if (document.getElementById(CONTAINER_ID)) {
+      return;
+    }
 
-  script.id = CONTAINER_ID;
-  script.async = true;
-  script.src = `https://www.googletagmanager.com/gtm.js?id=${ encodeURIComponent(container) }`;
+    const script = document.createElement('script');
 
-  document.head.appendChild(script);
+    script.id = CONTAINER_ID;
+    script.async = true;
+    script.src = `https://www.googletagmanager.com/gtm.js?id=${ encodeURIComponent(container) }`;
+
+    document.head.appendChild(script);
+  };
+
+  if (typeof window.requestIdleCallback === 'function') {
+    window.requestIdleCallback(load, { timeout: 2000 });
+  } else {
+    window.setTimeout(load, 1200);
+  }
 };
 
 /**

package/package.json

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

package/types/routes.ts

@@ -148,6 +148,24 @@ export interface FoundData extends Omit<RouteData, 'locations' | 'id'> {
   // must read "missing" as unknown, never as direct.
   stops_count?: number
 
+  /**
+   * How many seats are still on sale on this departure.
+   *
+   * Edited: Claude - Date: 2026-09-16
+   *
+   * NOT `trip.available_seats`, which is the coach's CAPACITY - the search
+   * subtracts what every brand has sold and what the operator holds back
+   * before deciding whether to offer the departure at all, and this is that
+   * answer (Routes\Search\Buses::removeOccupied). Reading the capacity
+   * instead announced 49 free seats on a coach with 49 sold, which is the
+   * one number on a result card nobody would think to doubt.
+   *
+   * Optional: an external-provider offer has no seat count of ours, and an
+   * older API does not send this at all - in both cases the card shows
+   * nothing rather than guessing.
+   */
+  seats_left?: number
+
   /**
    * Claude - 2026-08-29 (audit A3-02h)
    *