Merge pull request #45 from sysdevrun/claude/progressinfo-export-p6e36l

Export ProgressInfo and ProgressCallback from package entry point

Author: chtitux

CHANGELOG.md

@@ -2,6 +2,8 @@
 
 ## Upcoming release
 
+- Fix: `ProgressInfo` and `ProgressCallback` types are now exported from the package entry point, as documented in the README (`import { type ProgressInfo } from 'gtfs-sqljs'` previously failed).
+
 ## 0.8.0
 
 - **Add `getTripSchedules(filters)`** — display-ready trip schedules with everything pre-computed: seconds since the start of the service day (past-midnight times > 86400 supported), unix epochs computed in the agency's timezone (DST-safe "noon minus 12h" rule, zero-dependency via `Intl`), realtime delays resolved per the GTFS-RT spec (delay ↔ absolute time cross-computed, arrival ↔ departure borrowed, delay propagated to subsequent stops until the next update, trip-level delay fallback, `stop_id`-only matching), `SKIPPED`/`NO_DATA`/canceled flags, `display_epoch` (departure, or arrival at the terminus; `displayMode: 'arrival'` flips it), and stop names joined in. Filters: `tripId` and/or `routeId` (+ `directionId`), required service `date`, optional `now`, `displayMode`, `timezone`. Batched internally — one trip or a whole route's day costs the same five indexed queries.

package-lock.json

@@ -8,6 +8,8 @@ export {
   GtfsSqlJs,
   type GtfsSqlJsOptions,
   type GtfsSqlJsAttachOptions,
+  type ProgressInfo,
+  type ProgressCallback,
   type AgencyFilters,
   type StopFilters,
   type RouteFilters,