CodeVetter · Repo Unpack · Testing signals
date-fns/date-fns
Tests and CI were inspected, not executed; no passing status or coverage percentage is established. Vitest discovers package projects, with separate core main and Temporal-oriented suites and package-specific isolation settings. Inspected tests exercise mutation guarantees, invalid input, parsing boundaries, context types, DST gaps, and historical offsets. CI describes browser, Node-version, time-zone, smoke, type, lint, and locale checks, but this bounded inspection does not establish exhaustive coverage.
- Root Vitest discovers pkgs/*; core main includes src/**/test.ts, temporarily includes test.tp.ts, and both use forks, disabled isolation, concurrent sequencing, and optional Chromium via Playwright.
- addMonths tests assert timestamp support, input immutability, month-end clamping, pre-100 AD dates, invalid dates/amounts, UTCDate retention, and TZDate context inference.
- Formatting tests cover quote escaping and formatDate alias behavior; parsing tests cover leap-day bounds, mismatches, invalid references, trailing whitespace, and unescaped-letter errors.
- TZ tests include src/**/tests.ts and test/**/*.test.ts; inspected edge cases assert spring-forward normalization and historical second-offset behavior, while UTC configuration enables isolation.
- Push/PR workflows invoke core Node, browser, and time-zone tasks; Node tests name versions 22/24/25/26, and the zone runner launches Vitest with TZ and VITEST_MAX_WORKERS=1.
- Smoke CI delegates to example tasks; quality CI invokes type checking, linting, and locale snapshots, whose renderer covers format/parse, distances, relative dates, and durations under TZ=utc.
- The inspected docs tests assert export/module-node classification and repository-path conversion; its npm test script is a deliberate failure placeholder despite a Vitest tests.ts configuration, so that script is not a reliable docs-suite entrypoint.
- Coverage CI is workflow_dispatch-only with a TODO; addMonths DST cases are conditional on detected transitions, and inspected docs helper tests do not demonstrate Firebase publication/rollback verification. Tests and workflows were read, not run.