CodeVetter · Repo Unpack · Contributor handoff
avajs/ava
Start with the manifest, local test/configuration files, and the source modules governing the behavior being changed. Preserve worker protocol, test ordering, snapshot compatibility, and public declaration semantics across edits. Tests and CI were inspected, not executed, so this brief provides no passing baseline. Under this task's read-only authority, commands below are future validation guidance rather than authorization to run them.
- Read package.json, ava.config.js, .taprc, and scripts/test.sh first to distinguish published runtime entrypoints from the @ava/test and TAP development harnesses.
- For CLI/configuration changes, follow loadCli(), loadConfig(), and existing loader tests; explicit configuration has different conflict semantics from automatically discovered configuration.
- For worker lifecycle changes, read fork.js, worker/base.js, and worker/channel.js together; preserve ready-for-options, worker-finished/free-worker, peer-failed, and channel reference semantics.
- Keep file concurrency distinct from within-file concurrency, and preserve success-only after hooks versus always hooks; fail-fast does not cancel concurrent tests already started within a file.
- Snapshot edits must preserve title/index identity, skipped-block retention, deterministic encoding, and format versioning; the source explicitly requires a major AVA version bump for incompatible encoding changes.
- Update runtime declaration chains and public types together; TypeScript cases are checked by tsc, and examples pin AVA ^6 despite the root package being 8.0.1.
- When execution is separately authorized, use the documented smallest test selection first: npx test-ava test/{file}.js or npx tap test-tap/{file}.js; npm test adds lint, types, and coverage.
- Tests and CI were inspected, not executed; future validation must account for serial watch testing, non-Linux reporter exclusions, and compile-only type cases rather than assuming uniform suite execution.