CodeVetter · Repo Unpack · Extension points
iamkun/dayjs
The main extension contract is a plugin function that can modify the class, factory, and shared utilities. Locale objects supply data and callbacks independently of the core bundle. TypeScript declarations extend public interfaces separately from implementation. Build discovery automatically packages conventionally placed modules, making file naming and registration conventions part of the extension surface.
- New plugins implement (option, DayjsClass, dayjsFactory), install through dayjs.extend, and can add instance or factory methods; installation is guarded by the plugin function's $i marker.
- Existing-method extensions capture the previous implementation and delegate with the current instance; localizedFormat wraps format, UTC wraps parse/init, and isoWeek intercepts startOf only for its unit.
- $utils exposes shared helpers under short keys; the core adds locale resolution, Dayjs recognition, and metadata-preserving wrapper functions to the imported utility object.
- Locale modules register named objects with dayjs.locale(locale, null, true); supported hooks include ordinal, meridiem, relative-time functions, and preparse/postformat callbacks.
- Plugin options expose targeted customization: customParseFormat accepts parseTwoDigitYear, relativeTime accepts thresholds and rounding, and calendar accepts per-call format strings or functions.
- customParseFormat's expressions table maps tokens to regex/parser pairs, while formattingTokens determines token recognition; new parsing tokens must fit both stages.
- Type declarations support module augmentation of Dayjs and factory APIs, and ConfigType derives from the augmentable ConfigTypeMap; timezone and duration declarations demonstrate overloaded plugin surfaces.
- Build discovery expects locale files and src/plugin/<name>/index modules, generates matching distribution names, and copies declarations; locale metadata extraction requires the identifying '// Name [code]' comment.