CodeVetter · Repo Unpack · Contributor handoff
reduxjs/redux
Start with the public export surface and the implementation/type pair for the affected API. Preserve synchronous reduction, subscriber snapshot behavior, and package-format compatibility when editing the core. Tests and CI were inspected, not executed, and this bounded report does not establish exhaustive coverage or passing checks. Website acquisition and root build commands have side effects, so future execution requires authority beyond this read-only investigation.
- For a core change, first read src/index.ts, the affected implementation, and matching public types; these jointly define exported names, runtime behavior, and consumer contracts.
- Subscription changes must preserve copy-on-write Maps, idempotent unsubscribe, and nested-dispatch snapshots; read the corresponding createStore tests before changing listener bookkeeping.
- Do not handle randomized Redux INIT, REPLACE, or probe strings as application action types; reducers must initialize undefined state and return current state for unknown actions.
- createStore's deprecation annotation recommends external Toolkit configureStore while explicitly retaining the core API; legacy_createStore is the documented alternative without the visual deprecation warning.
- When execution is authorized, use the existing pnpm test, pnpm type-tests, pnpm lint, and pnpm format:check scripts and scope the first runtime check to the affected suite; tests and CI in this report were inspected, not executed.
- Packaging changes require reviewing exports, all tsdown output variants, TEST_DIST aliasing, and CI's packed-artifact checks; source-direct imports can bypass artifact resolution even in the dist job.
- Keep project installation boundaries distinct: root/docs/website are independent pnpm projects, and standalone examples have their own manifests; older examples' Redux 4 dependencies are not proof of Redux 5 compatibility.
- Before website execution, inspect fetch-external-docs and Netlify settings for clone/copy/removal behavior, moving external refs, warning-only snippet checks, and required isolation headers; publishing also has separate manual npm and automatic commit-preview workflows.