@autobusal/utilities 1.5.4 → 1.6.0

package/check-backticks.mjs

@@ -34,7 +34,18 @@
 import { readdirSync, readFileSync, statSync } from 'node:fs';
 import { join } from 'node:path';
 
-const OPEN = /styled(?:\.\w+|\([^)]*\))(?:<[^>]*>)?`/g;
+/*
+ * Claude - 2026-08-30: `css` was missing from this, and the miss was not
+ * theoretical - magus's own `columnStyles = css<{...}>\`` carried a comment
+ * quoting a theme token in backticks, this script reported "clean", and the
+ * build then failed with a parse error pointing somewhere else entirely.
+ *
+ * A shared `css` block is the same template literal as `styled.x` and
+ * breaks in exactly the same way, so it has to be scanned the same way.
+ * `keyframes` and `createGlobalStyle` are here for the same reason before
+ * somebody finds them the hard way.
+ */
+const OPEN = /(?:styled(?:\.\w+|\([^)]*\))|css|keyframes|createGlobalStyle)(?:<[^>]*>)?`/g;
 
 const walk = (dir) => readdirSync(dir).flatMap((entry) => {
   const path = join(dir, entry);

package/date.tsx

@@ -6,6 +6,43 @@ export const createDate = (prepared: string): Date => {
   return new Date(Date.UTC(Number(data[2]), Number(data[1]) - 1, Number(data[0])));
 };
 
+/**
+ * Whether a string is a d/m/Y date this app can actually work with.
+ *
+ * Claude - Date: 2026-08-29
+ *
+ * `createDate` splits on "/" and feeds the pieces to Date.UTC, so anything
+ * that is not a date at all produces an Invalid Date rather than an error -
+ * and a calendar built from one renders January of nothing. The literal
+ * "none" the search URL carries for "no return leg" is exactly that, which
+ * is how the round-trip picker came to open on January instead of the
+ * outbound's month.
+ */
+export const isPreparedDate = (value?: string | null): boolean => {
+  if (!value) {
+    return false;
+  }
+
+  const parts = value.split('/');
+
+  if (parts.length !== 3) {
+    return false;
+  }
+
+  const [ day, month, year ] = parts.map(Number);
+
+  if (!day || !month || !year) {
+    return false;
+  }
+
+  const date = new Date(Date.UTC(year, month - 1, day));
+
+  // round-trips through Date so 31/02/2026 is refused as well as "none"
+  return date.getUTCFullYear() === year
+    && date.getUTCMonth() === month - 1
+    && date.getUTCDate() === day;
+};
+
 export const prepareDate = (date: Date): string => {
   const day = date.getDate();
   const month = date.getMonth() + 1;

package/index.ts

@@ -1,4 +1,4 @@
-import { createDate, prepareDate, getFormattedShort, getDayParts, differenceYears, futureDate } from './date';
+import { createDate, prepareDate, isPreparedDate, getFormattedShort, getDayParts, differenceYears, futureDate } from './date';
 import { Validate, Display } from './form';
 import { error, notify, success } from './notify';
 import { getAllowed, getLanguages, getPayments } from './options';
@@ -17,6 +17,7 @@ export {
   success,
   createDate,
   prepareDate,
+  isPreparedDate,
   getFormattedShort,
   getDayParts,
   differenceYears,

package/package.json

@@ -1,10 +1,13 @@
 {
   "name": "@autobusal/utilities",
-  "version": "1.5.4",
+  "version": "1.6.0",
   "author": "Ferjolt Ozuni",
   "type": "module",
   "main": "index.ts",
   "dependencies": {
     "dompurify": "^3.4.14"
+  },
+  "publishConfig": {
+    "access": "public"
   }
 }

package/CHANGELOG.md

@@ -1,79 +0,0 @@
-# Changelog
-
-## 1.5.4 (2026-08-28)
-
-- DisplayStatus renders status 4 (awaiting approval) as a badge instead of a blank cell in the admin agent/visitor/API-consumer lists (sweep #61).
-
-## 1.5.3
-
-### Fixed
-
-- **The backtick guard tripped on prose about styled-components**, and was refusing to publish the whole repo. Its opening pattern matches `styled.x` followed by a backtick as *text*, so a JSDoc line describing another file - "labels as `<span>` (Viewer/styles.ts: `Label = styled.span`)" - opened a template no code had opened, and every comment up to the next `` `; `` in the file counted as inside it. A comment about the hazard tripping the guard against the hazard. Openings found inside comments are now ignored; backticks inside comments, which are the thing being hunted, still are not.
-
-## 1.5.2
-
-### Changed
-
-- DOMPurify raised to `^3.4.14` for GHSA-55q2-fjhq-7xh7. It rates as moderate, which understates it here: DOMPurify is what `sanitizeHtml` is, so it sits directly on the path every piece of admin-authored and model-generated HTML takes before reaching a browser.
-
-## 1.5.1
-
-### Changed
-
-- **`error` collapses repeats into one toast** - it now raises the toast
-  under an id, defaulting to the message itself, so a page whose parallel
-  queries all fail the same way shows one red box rather than a stack of
-  identical ones. Existing call sites need no change. A repeat of the same
-  failure once the toast has gone still raises a fresh one.
-
-## 1.5.0
-
-### Added
-
-- **`GetStatus` knows status 4, "awaiting approval"** - distinct from 3
-  (pending, waiting on the account to finish its own form) and from 2
-  (suspended, a decision already taken against it).
-
-
-## 1.4.1
-
-### Changed
-
-- **Gender can be "not declared".** `getOptionsSex` gains it as the first
-  option and `getSex` reports it, instead of treating everything that is not
-  `1` as male — which is what three existing rows with no value were already
-  rendering as.
-
-  Carried by `null`: the `visitors`.`sex` column has always been nullable, so
-  nothing migrated. The option's id is `''`, which Laravel's
-  `ConvertEmptyStringsToNull` turns into a real null on the way in, so "not
-  declared" is the *absence* of a value at every layer rather than a magic
-  number each one has to learn.
-
-  Deliberately not shared with the checkout passenger forms — those build
-  their own field, and gender there is a per-route requirement a carrier can
-  insist on. A profile is the person; a passenger record is what a carrier
-  demands in order to board them.
-
-## 1.4.0
-
-### Added
-
-- **`check-backticks.mjs`**, moved here from the autobusal repo root so the
-  apps can run it too.
-
-  A backtick used as quoting inside a styled-components template *terminates
-  the template*. The bundler then reports a syntax error somewhere further
-  down, pointing at a line that is perfectly fine — so the search starts in
-  the wrong place every time. Per the script's own history that cost five
-  build failures in one session before anyone connected the two.
-
-  It only ever guarded `packages`, and the trap is not confined there: it bit
-  `magus/src` the moment a public page grew its own styled-components, with
-  nothing watching. Each app's `prebuild` now runs it over its own `src`
-  (first, so a broken template stops the build before it spends minutes
-  copying files), and `publish.sh` still runs it over `packages`.
-
-  One script with three callers, rather than a copy per repo that drifts.
-
-  Takes the directory to scan as its argument.