fix: repair failing cross-package tests and type errors

apps/web/src/lib/api.ts

@@ -7,8 +7,7 @@
  * Fix: change the import to `useDebounce`.
  */
 
-// BUG: useThrottle no longer exists — was renamed to useDebounce
-import { useThrottle } from "@e2e/utils"
+import { useDebounce } from "@e2e/utils"
 import { formatDate, formatAUD } from "@e2e/utils"
 
 export const BASE_URL = process.env.API_URL ?? "http://localhost:3000"
@@ -28,5 +27,5 @@ export async function fetchPosts() {
 // Re-export formatting utilities used throughout the app
 export { formatDate, formatAUD }
 
-// Re-export the debounce hook (currently broken import)
-export { useThrottle as useSearchDebounce }
+// Re-export the debounce hook
+export { useDebounce as useSearchDebounce }

bunfig.toml

@@ -1,2 +1,2 @@
 [test]
-environment = "happy-dom"
+preload = ["./packages/ui/test/setup.ts"]

packages/ui/src/components/Button/Button.tsx

@@ -17,13 +17,10 @@ type Props = {
 /**
  * Button component.
  *
- * BUG: When `iconOnly` is true, the button renders without visible text.
- * An `aria-label` is required for screen reader accessibility (WCAG 2.1 SC 4.1.2),
- * but the component does not enforce or warn about its absence.
- *
- * The test in Button.test.tsx checks that an icon-only button has an accessible name.
- * Fix: throw/warn in development when `iconOnly && !aria-label`, or always render
- * the aria-label attribute when iconOnly is true.
+ * Icon-only buttons render without visible text, so an `aria-label` is required
+ * to give them an accessible name (WCAG 2.2 SC 4.1.2 Name, Role, Value).
+ * When `iconOnly` is set without an `aria-label`, a fallback name is applied and
+ * a development-only warning is emitted.
  */
 export function Button({
   children,
@@ -34,13 +31,30 @@ export function Button({
   onClick,
   "aria-label": ariaLabel,
 }: Props) {
+  // An empty or whitespace-only aria-label provides no accessible name, so it is
+  // treated the same as a missing one (WCAG 2.2 SC 4.1.2 Name, Role, Value).
+  const hasAriaLabel = Boolean(ariaLabel?.trim())
+
+  if (process.env.NODE_ENV !== "production" && iconOnly && !hasAriaLabel) {
+    console.warn(
+      "Button: `aria-label` is required when `iconOnly` is true — icon-only buttons have no visible text and fail WCAG 2.2 SC 4.1.2 without an accessible name.",
+    )
+  }
+
+  const accessibleName = iconOnly
+    ? hasAriaLabel
+      ? ariaLabel
+      : typeof children === "string"
+        ? children
+        : "Button"
+    : ariaLabel
+
   return (
     <button
       className={`btn btn-${variant}`}
       disabled={disabled}
       onClick={onClick}
-      // BUG: aria-label is not applied when iconOnly is true and no ariaLabel is passed
-      // The component should enforce aria-label for icon-only buttons
+      aria-label={accessibleName}
     >
       {icon && <span className="btn-icon">{icon}</span>}
       {!iconOnly && children}

packages/ui/src/components/DataTable/DataTable.tsx

@@ -16,22 +16,19 @@ type Props<T extends Record<string, unknown>> = {
 /**
  * DataTable with client-side sorting.
  *
- * BUG: The sort handler has a stale closure — it captures `sortDir` at the
- * time the handler is created, so toggling sort direction does not work
- * correctly after the first click. The second click always sorts in the same
- * direction as the first.
- *
- * Fix: use the functional form of setState — `setSortDir(prev => ...)` —
- * so the toggle always reads the current value.
+ * The sort handler previously captured `sortDir` in a stale closure, so
+ * toggling the direction only worked on the first click. It now uses the
+ * functional form of setState — `setSortDir(prev => ...)` — which always reads
+ * the current value, so repeated clicks on the same column toggle correctly
+ * between ascending and descending.
  */
 export function DataTable<T extends Record<string, unknown>>({ data, columns }: Props<T>) {
   const [sortKey, setSortKey] = useState<keyof T | null>(null)
   const [sortDir, setSortDir] = useState<SortDir>("asc")
 
-  // BUG: stale closure — sortDir is captured at handler creation time
   const handleSort = (key: keyof T) => {
     if (sortKey === key) {
-      setSortDir(sortDir === "asc" ? "desc" : "asc") // BUG: reads stale sortDir
+      setSortDir((prev) => (prev === "asc" ? "desc" : "asc"))
     } else {
       setSortKey(key)
       setSortDir("asc")

packages/utils/src/format/date.ts

@@ -1,21 +1,28 @@
 /**
  * Date formatting utilities.
  *
- * BUG: formatDate passes `'en-AU'` as the locale but then uses a US-style
- * format string option (`month: 'numeric'` before `day: 'numeric'`), which
- * produces MM/DD/YYYY output instead of DD/MM/YYYY for Australian dates.
+ * formatDate renders Australian day-first dates with an UNPADDED day and a
+ * 2-digit month — e.g. `1/03/2024`, not `01/03/2024`.
  *
- * Fix: use `dateStyle: 'short'` with `'en-AU'` locale, which correctly
- * produces DD/MM/YYYY, or explicitly set `day: 'numeric', month: 'numeric', year: 'numeric'`
- * and rely on the locale to order them correctly.
+ * Note that the order of the option keys passed to Intl.DateTimeFormat is
+ * irrelevant: Intl derives field order from the locale, so `'en-AU'` always
+ * yields day-before-month. The issue was purely zero-padding — `day: 'numeric'`
+ * is still padded to `01` by the en-AU short pattern, so the day part is
+ * re-emitted via `formatToParts` with `String(Number(...))` to strip the
+ * leading zero.
+ *
+ * `dateStyle: 'short'` was rejected as an alternative because en-AU renders it
+ * with a 2-digit year (`1/3/24`), and a 4-digit year is required here.
  */
 export function formatDate(date: Date): string {
-  // BUG: explicit field order overrides locale ordering — produces M/D/YYYY not D/M/YYYY
   return new Intl.DateTimeFormat("en-AU", {
-    month: "numeric",
     day: "numeric",
+    month: "2-digit",
     year: "numeric",
-  }).format(date)
+  })
+    .formatToParts(date)
+    .map((p) => (p.type === "day" ? String(Number(p.value)) : p.value))
+    .join("")
 }
 
 export function formatDateTime(date: Date): string {

tsconfig.json

@@ -6,6 +6,7 @@
     "jsx": "react-jsx",
     "strict": true,
     "skipLibCheck": true,
+    "types": ["bun-types"],
     "paths": {
       "@e2e/ui": ["./packages/ui/src/index.ts"],
       "@e2e/utils": ["./packages/utils/src/index.ts"]