KrakenJS: Add Lightweight Time‑Zone Helper vs. Rely on External Libraries for Regional Date Conversion

Recommendation

Keep KrakenJS core lean and delegate regional date conversion to application code or a chosen external library. Do not add a time-zone helper to core unless maintainers approve an additive, namespaced wrapper and you verify ICU support on the target runtime.

Confirmed facts

• KrakenJS is Express-based Node.js middleware, and its core modules do not own date or time-zone handling.
• Node.js provides Intl.DateTimeFormat with an IANA timeZone option under ECMAScript Internationalization.
• Available IANA zone data depends on the Node.js ICU build; compact container images may lack full zone support.
• moment-timezone bundles a large time-zone database and is in maintenance mode; Luxon and date-fns-tz are modern alternatives but still add bundle weight.

Likely trade-offs (for review)

• A thin namespaced wrapper around Intl.DateTimeFormat adds very little code, but not zero footprint, and requires review, documentation, tests, and maintainer consensus.
• Intl formatting is sufficient for UI display and simple conversion, but not for DST-aware arithmetic, historical zone rules, parsing zone abbreviations, or offline full IANA lookups.
• An additive utility that does not patch Date or globals is unlikely to break existing KrakenJS modules or downstream projects.

Steps for this case

1. Confirm that the target Node.js image supports the zones you need:

   node -e "try { new Intl.DateTimeFormat('en-US', { timeZone: 'America/New_York' }).format(new Date()); console.log('IANA zone supported'); } catch (e) { console.log('unsupported:', e.message); }"

2. If Intl covers your UI needs, implement an application-level helper instead of changing KrakenJS core.
3. If you need DST-aware arithmetic or historical rules, add a userland dependency such as Luxon or date-fns-tz; avoid new moment-timezone adoption without bundle review.
4. Never patch Date.prototype globally; use an explicit namespaced utility to protect downstream compatibility.
5. Before proposing a core helper, check the KrakenJS repository contribution process and release cadence.

Missing diagnostic detail

Which Node.js runtime or container image will run KrakenJS? This determines whether Intl alone is viable or whether you need a library that bundles its own time-zone data.

Assumptions: You are using an Express-based KrakenJS version and do not want global Date modifications. Claims marked likely require verification against your repository and runtime.