CodeVetter · Repo Unpack · Contributor handoff
testing-library/react-testing-library
Begin edits at the runtime/type boundary and read the focused behavioral suite before changing contracts. Existing scripts and workflow definitions describe intended validation, but tests and CI were inspected, not executed during this assignment. The investigation is bounded and supplies neither passing results nor exhaustive security or coverage conclusions.
- For lifecycle work, first read index.js, pure.js, and act-compat.js together: runner registration, root ownership, and React's global act flag cross module boundaries.
- Keep public API edits paired with types/index.d.ts and types/test.tsx; CONTRIBUTING identifies handwritten declarations as the API update location.
- For an authorized implementation, start with the relevant src/__tests__ suite through npm test, then use typecheck or validate as needed; those commands were only inspected here.
- Preserve React 18/19 branches and version-gated assertions; a successful latest-only run would not establish legacy-root compatibility.
- Tests changing global configuration capture and restore it; tests mocking console must respect the harness's unexpected-call and teardown checks.
- Use actual scripts as authority over older documentation: CONTRIBUTING mentions dtslint, while package.json's explicit typecheck invokes tsc and the root config includes types without emitting output.
- Inspect package-manager context before installing: package.json declares Yarn 1.22.22, while contribution setup and CI use npm, and CI explicitly disables lockfile use.
- Treat release automation as a separate authority boundary: configured branch pushes can trigger publication, and maintainer documentation warns that BREAKING CHANGE commit text drives major releases.