CodeVetter · Repo Unpack · Contributor handoff
reduxjs/redux-toolkit
Begin from the owning package and public entrypoint before following internal builders. Preserve runtime behavior and exported type inference together, especially across cache identity and package-resolution boundaries. Tests and CI were inspected, not executed, so this report provides test-selection guidance rather than validation results. The inventory and investigation are bounded; uninspected files and scenarios remain unknown.
- Read root/package manifests and pnpm-workspace.yaml before selecting commands: pnpm 11.23.0 is pinned, the workspace is selective, hoisted linking is configured, and autoInstallPeers/linkWorkspacePackages are disabled.
- For store changes, inspect configureStore and both default-builder files together; custom enhancer callbacks must retain the middleware enhancer, and invariant middleware is added only outside production.
- For reducer changes, preserve case-before-matcher execution, draft versus primitive handling, and lazy slice reducer construction. The removed object form of extraReducers is rejected outside production.
- For RTK Query fixes, read createApi, core/module, buildInitiate, and buildThunks before changing cache behavior; preserve serializer precedence and the condition order that allows upserts before blocking pending requests.
- For listener changes, keep reducer-before-effect ordering and synchronous getOriginalState semantics; cancellation, child-task joining, and executing-listener tracking require coordinated lifecycle handling.
- When execution is separately authorized, use the owning package's focused Vitest test first, then relevant type tests; Toolkit provides test and type-tests scripts, with type-test discovery configured in tsconfig.test.json. Here these scripts and CI were inspected only.
- Public type or export changes need artifact-level review: declarations include .d.ts/.d.mts variants, CI removes source aliases for tarball testing, and CONTRIBUTING requests updating the API report for external-facing type changes.
- Follow package-specific formatting overrides and edit source rather than emitted bundles. For docs, account for the external website and type-checked MDX; for codegen, distinguish text-return generation from outputFile writes before choosing a verification path.