Every service in KatanaKit follows the same architecture: a small public API
over a pure core, with the runtime I/O isolated behind it and SSR guards
where the browser or Node/Bun is touched. Two public shapes exist, and both are
re-exported as use* helpers from the package root:
Singleton facade classes — every src/core/services/ module is one:
FormatterService, UnitConverterService, CurrencyConverterService,
LoggerService, DatesService, FetchApiManager, … expose use* methods
and a getInstance() accessor (plus create() where dependencies are
injected). Service architecture explains
the pattern vocabulary and the use* vs on* naming rule.
Function modules with strategies — the infrastructure modules (DOM,
storage, theme, viewport, observer and friends) ship standalone use*
functions; behavior is swapped through strategy objects (for example,
LocalStorageStrategy, SessionStorageStrategy and MemoryStorageStrategy
behind the storage API).
The API Reference is generated from the source; the pages below are
the hand-written reference companion: an overview paragraph, a quick example
and one section per method with runnable examples.