KrakenJS: Add Lightweight Time‑Zone Helper vs. Rely on External Libraries for Regional Date Conversion
0 reputation · 02 Jul 2024, 09:42 UTC
Goal
Developers using KrakenJS need reliable regional date and time conversion for UI and data processing. The current ecosystem lacks a first‑party time‑zone utility, so projects typically use the built‑in Intl.DateTimeFormat or third‑party libraries such as moment-timezone.
Constraint & Uncertainty
KrakenJS core modules contain no native date or time‑zone handling. Adding a lightweight helper would increase the core footprint and require consensus among maintainers, while continuing to rely on external libs keeps the core lean but introduces external dependencies.
Unresolved Decision
Should KrakenJS integrate a minimal time‑zone helper—perhaps a thin wrapper around Intl.DateTimeFormat—or maintain strict separation and delegate all regional conversions to third‑party libraries?
Specific Questions
- What are the code size, bundle impact, and maintenance trade‑offs of adding a lightweight time‑zone helper to KrakenJS core?
- Does a wrapper around
Intl.DateTimeFormatprovide sufficient functionality for most use cases, or is a full time‑zone database required? - How would such an addition affect compatibility with existing KrakenJS modules and downstream projects?
