CodeVetter · Repo Unpack · Contributor handoff
date-fns/date-fns
Tests and CI were inspected, not executed, and this brief is bounded to the source files read. Begin changes at the owning function or package, then follow construction, locale, and generated-output dependencies. Existing manifests and mise tasks provide more current command evidence than several older contributing examples. Preserve the read-only authority of this investigation; the checks below are future validation guidance when execution is authorized.
- Read AGENTS.md and the owning package's implementation/test/config first; repository instructions identify core, UTC, and TZ boundaries and prohibit unsolicited commits or pushes.
- Preserve the construction contract during date edits: use the existing toDate/constructFrom path so context factories, symbol hooks, subclass constructors, and cloned inputs remain intact.
- For parser changes, read Parser, Setter, the registry, and the specific parser together; compatibility rejection, priority selection, Invalid Date returns, and RangeError branches are distinct contracts.
- Edit generator logic rather than treating generated indices/FP wrappers as independent source; indices.ts rewrites package.json and export indices, and fp.ts labels emitted wrappers as generated.
- Locale work requires the contribution guide and snapshot review; distinguish generation from comparison and address the --test versus test mode mismatch before trusting the existing locale-check task.
- When execution is authorized, start with the relevant Vitest file, then applicable mise type/lint, browser, time-zone, or smoke tasks; this investigation inspected those tests and CI definitions without running them.
- Check documentation commands against current tooling: CONTRIBUTING.md still describes lib output and Prettier/ESLint, while package.sh emits dist/date-fns and root mise uses oxfmt/oxlint.
- Keep verification commands separate from publishing and build mutations: docs CLI writes/deletes remote records, package.sh deletes dist, and Temporal implementations are excluded from production builds despite having their own test project.