What problem does it solve? Integrating a Temporal-first date library into real applications raises boundary questions: how to build stable cache keys and router params from dates, how to move nanosecond timestamps across JSON and databases without precision loss, how to convert foreign epochs like NTP or Excel serials, and which lint plugin to install for Date-ban enforcement. ## Core Features & Use Cases - Stable boundary representations: Build cache keys, router params, and table-sort keys from validated ISO 8601 strings and normalized epoch numbers instead of Date objects. - Nanosecond-safe serialization: Keep bigint nanoseconds internally, cross JSON with formatNanoseconds/parseNanoseconds, and truncate to the target store's precision (e.g., PostgreSQL microseconds) before persisting. - Foreign epoch bridges: Convert to and from NTP timestamps, Windows FILETIME, .NET ticks, Excel day serials, and PostgreSQL microseconds using the precision/convert helpers. - Lint package selection: Match the project's toolchain to @northguild/gmt-eslint, @northguild/gmt-biome, or @northguild/gmt-oxlint. - Use Case: A user storing event timestamps in PostgreSQL uses toNanoseconds internally, truncates to microseconds before insert, and validates timezone ids with isValidTimeZone before using them as cache keys. ## Quick Start Ask the assistant to help integrate @northguild/gmt into your app, for example to build validated date cache keys or convert an Excel serial date to an ISO string.
