CodeVetter · Repo Unpack · Contributor handoff
remeda/remeda
Start with contributor policy and the target utility's complete public contract before changing implementation. Keep runtime, inferred types, lazy semantics, generated docs, exports, and migration guidance aligned. Tests and CI were inspected, not executed, and this brief is a bounded source inventory rather than comprehensive coverage or a clean bill of health. For this investigation, repository commands remain descriptions only: no installs, tests, builds, hooks, publishing, or file writes were authorized.
- Read AGENTS.md and CONTRIBUTING.md first; PR-directed work requires confirmation of a human operator's personal stake and commitment to participate through review and merge.
- Use the remeda-utility skill for utility or mapping edits, and account for five coupled surfaces: implementation, tests, JSDoc, public exports, and applicable migration mappings.
- Preserve exactOptionalPropertyTypes, inferred API types, and interface/class compatibility; suppressions require explanations and TypeScript error codes rather than untracked casts hiding type problems.
- For an authorized code change, use the package's test:runtime, test:types, and test:prop scripts as relevant; separate runtime and type assertions, cover both calling styles, and red-green verify bug regressions.
- The checks described here were inspected, not executed: Vitest project configuration and CI matrices establish intended checks only, and the docs package's declared lack of tests limits browser-flow assurance.
- Before touching distribution or compiler compatibility, read tsdown.config.ts and the CI matrix: TypeScript 5.1 is the declared minimum, declaration polyfills are injected, and declaration generation must precede runtime generation.
- Do not assume eager and lazy callback contexts are interchangeable: pipe supplies processed prefixes, ordinary callbacks terminate batches, and the existing take(0) test expects one upstream mapper call.
- Review formatter and lint-generated diffs when those hooks are active, restart docs development after static-script edits, and use Remeda's inverted release labels: feat produces patch releases and fix produces minor releases.