CodeVetter
← All unpacks
CodeVetter · Repo Unpack evidence

reduxjs/redux-toolkit

Scanned commit e7a8b318df dated 2026-09-29 — last upstream commit. Generated by codevetter 1.15.0 on 2026-10-02.

github.com/reduxjs/redux-toolkit ↗ · 923 files · 4.1 MB

Redux Toolkit docs The pages in this folder are published as part of the combined Redux docs site, at https://redux.js.org/toolkit.

Deep analysis by cli:codex via the codex CLI on 2026-10-02 (513s) — every claim below links to its cited source files. Source inspection; upstream code and tests were not executed.

Overview

Redux Toolkit is a TypeScript library monorepo for developers building Redux applications, with APIs for store configuration, immutable reducers, normalized entities, and asynchronous workflows. Its optional RTK Query entrypoints turn endpoint definitions into Redux-backed request caches, lifecycle utilities, and React hooks. The repository also contains OpenAPI code generation, GraphQL transport integration, migration codemods, documentation, and application fixtures that exercise package compatibility.

System map

The main product is a set of published library entrypoints consumed by application stores. RTK Query separates framework-independent request machinery from React hook generation. Redux state and middleware-local maps have distinct ownership responsibilities. Build configuration emits several module formats, while documentation deployment incorporates this checkout into the separate Redux website.

Feature catalog

The user-facing product consists primarily of programming APIs and developer tooling. Store and reducer helpers address application-owned state, while RTK Query handles server-state requests and cache coordination. React examples expose fetching, editing, authentication, polling, and pagination interfaces. This catalog describes inspected capabilities and routes rather than claiming exhaustive coverage of every fixture.

Data flow

Application arguments enter endpoint initiation and become serialized cache keys before request execution. Endpoint query functions translate arguments into transport inputs, while optional schemas and transforms shape results before Redux receives them. Hooks select cached state and manage subscriptions rather than owning the shared response cache. Rehydration and code generation introduce separate application-action and filesystem boundaries.

Behavior traces

The following traces follow inspected execution paths through initialization, fetching, editing, authentication, rehydration, and generation. They include cache-hit, failure, and subscription branches that change observable behavior. These are source-derived walkthroughs, not runtime observations.

Testing signals

Tests and CI were inspected, not executed; no passing result or measured coverage is asserted. The inspected suites combine Vitest runtime/type checks, mocked HTTP, React Testing Library, transformation fixtures, and Playwright application checks. Coverage includes consequential failure and concurrency branches, but mock-based assertions have specific limits. This investigation is bounded and does not establish exhaustive repository coverage.

Risk map

These findings describe source-visible trust boundaries and maintenance hazards, not confirmed vulnerabilities. Network destinations, executable configuration, and generated-file writes deserve explicit ownership in consuming applications. Cache behavior also depends on middleware installation, request completion, and rehydration timing. Test limitations and package-resolution coupling constrain what source inspection alone can establish.

Extension points

Customization is organized around factories, endpoint definitions, middleware registration, and reducer injection. RTK Query modules augment a shared API during initialization and endpoint injection. Application-specific lifecycle callbacks and transport implementations sit above the core machinery. Companion tools expose configuration and AST-transform boundaries for extending generated or migrated code.

Contributor handoff

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.

Languages

LanguageFilesShare of source
TypeScript56394%
Markdown100docs/config
JSON95docs/config
JavaScript346%
YAML23docs/config
CSS17docs/config
HTML11docs/config
Kotlin20%

Start reading here

Probable source entrypoint: packages/ — inferred from the directory tree and manifest, not the upstream docs.

Source roots

packages/ (361 files)

Repository structure

Top-level pathFiles
examples/463
packages/361
docs/74
.github/8
_artifacts/3
skills/2

Docs found: CONTRIBUTING.mddocs/README.mddocs/introduction/getting-started.mddocs/rtk-query/comparison.mddocs/rtk-query/overview.mddocs/usage/immer-reducers.mddocs/usage/usage-guide.mddocs/usage/usage-with-typescript.md

Package

package.json — rtk-monorepo, 20 declared dependencies.

@babel/code-frame@babel/core@babel/generator@babel/helper-compilation-targets@babel/traverse@babel/types@size-limit/webpack@types/react@types/react-domnetlify-plugin-cacheoxfmtoxlint

CI & config entrypoints

Structural health signals

Average score 7.3/10 across 96 analyzed source files; 13 hotspots surfaced.

These are deterministic review leads — size, churn, and structural signals — not proof of a bug in this project.

Recent history