@autobusal/routes-order 1.37.6 → 1.37.7

package/Availability/Schema.tsx

@@ -36,9 +36,27 @@ interface Props {
  * is a single parse for a consumer and a single tag in the snapshot;
  * scattering them would multiply the boilerplate by the number of coaches.
  */
+const TRIPS = 100;
+
 const Schema = ({ data, t }: Props): (JSX.Element | null) => {
   const stop = (name: string) => ({ '@type': 'BusStop', name });
 
+  /**
+   * HOW MANY DEPARTURES GET MARKUP, which is not the same as how many the
+   * page shows.
+   *
+   * Edited: Claude - Date: 2026-09-16
+   *
+   * MEASURED on a busy pair (Tirana-Thessaloniki, ten coaches a day): thirty
+   * days produced 300 BusTrip nodes and 194 KB of JSON-LD - 41% of a 482 KB
+   * page, for a hundred near-identical descriptions of the same two-hour
+   * journey at different clock times. The table underneath still lists every
+   * one of the thirty days in plain text, so nothing is hidden from a reader
+   * or from a crawler; what is capped is the repetition in the markup.
+   *
+   * A hundred is roughly a fortnight on the busiest pair here and the whole
+   * month on most of them, which is the horizon anybody books within.
+   */
   const trips = data.days.flatMap(day => day.departures.map(row => ({
     '@type': 'BusTrip',
     name: t('routes_order.facts.title', { from: data.from, to: data.to }),
@@ -103,7 +121,7 @@ const Schema = ({ data, t }: Props): (JSX.Element | null) => {
     return null;
   }
 
-  return <JsonLd data={ { '@context': 'https://schema.org', '@graph': trips } } />;
+  return <JsonLd data={ { '@context': 'https://schema.org', '@graph': trips.slice(0, TRIPS) } } />;
 };
 
 export default Schema;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@autobusal/routes-order",
-  "version": "1.37.6",
+  "version": "1.37.7",
   "author": "Ferjolt Ozuni",
   "type": "module",
   "main": "index.ts",