@reduxjs/toolkit
The official, opinionated, batteries-included toolset for efficient Redux development
About
The official, opinionated, batteries-included toolset for efficient Redux development
What detecting @reduxjs/toolkit tells you about a site
@reduxjs/toolkit (RTK) is the modern, batteries-included way to use Redux, so its presence signals a team that wanted Redux's predictability without the historical boilerplate. If RTK Query is also in the bundle, the app is using Redux for data fetching and caching too, not just UI state.
Why the exact @reduxjs/toolkit version matters
RTK bundles immer, reselect and (optionally) RTK Query, so the exact version tells you which generation of those built-ins ships, including the createSlice and createListenerMiddleware APIs that arrived across the 1.x–2.x line.
@reduxjs/toolkit in a real-world stack
When you find @reduxjs/toolkit in a bundle, it rarely travels alone. react-redux and immer (bundled), and often the rest of a React data stack.
Quick facts
npm install @reduxjs/toolkitCommon pairings
Packages this one expects to find in the same project. Each is also a Sourcemap Explorer detection target.
What @reduxjs/toolkit pulls in
@reduxjs/toolkit declares 6 direct dependencies — each one also rides into any bundle that ships @reduxjs/toolkit, so they are detection targets too. Reading them is a quick way to understand the package's real footprint .
How Sourcemap Explorer detects @reduxjs/toolkit
@reduxjs/toolkit ships as v2.12.0, published 2026-05-15 and carries 6 direct dependencies, 2 peer dependencies (react, react-redux), 116 versions on the registry. Those exact numbers are the footprint Sourcemap Explorer matches when @reduxjs/toolkit rides inside a deployed bundle — here is how the detection works.
We catch @reduxjs/toolkit from two complementary signals: bundled source paths and the embedded package.json. Modern bundlers (webpack, Vite, esbuild, Rollup, Turbopack) preserve the original node_modules/@reduxjs/toolkit/ paths inside the JavaScript sourcemap's sources[] array — that's the canonical signal. When the matching package.json is also captured in sourcesContent[], we read the exact version field — patch number included. No regex guessing, no version inference.
- 1
Confirm the site exposes sourcemaps
In DevTools Network, check the response headers of any application script for `SourceMap` or `X-SourceMap`. Failing that, fetch the script's last 4 KB and look for a `//# sourceMappingURL=` comment — that map is where the `@reduxjs/toolkit` paths live.
- 2
Find the package in the bundle
Open DevTools → Network → reload. Click any application script and look at its sourcemap. Inside, search `sources[]` for entries matching `node_modules/@reduxjs/toolkit/` — every match confirms the package is bundled. The matching `sourcesContent[i]` for `node_modules/@reduxjs/toolkit/package.json` gives you the exact installed version.
- 3
Read the version directly from package.json
Run `jq -r '. as $m | $m.sources | to_entries[] | select(.value | endswith("node_modules/@reduxjs/toolkit/package.json")) | $m.sourcesContent[.key] | fromjson | .version' bundle.js.map`. Sourcemap Explorer automates the same query in the popup.
Major releases of @reduxjs/toolkit
When each major version first landed. Major bumps are where breaking changes live, so this timeline is the fastest way to date the @reduxjs/toolkit version a site actually ships against the ecosystem.
Recent versions
FAQ
What is @reduxjs/toolkit used for?
The official, opinionated, batteries-included toolset for efficient Redux development
How can I tell if a website is using @reduxjs/toolkit?
Open the page in Chrome with the Sourcemap Explorer extension installed and read the Stack tab. We catch `@reduxjs/toolkit` from two complementary signals: `node_modules/@reduxjs/toolkit/` paths inside the JavaScript sourcemap, and the embedded `package.json` we read for exact-version detection. Without the extension you can do the same lookup manually in DevTools — the steps are listed in the "How Sourcemap Explorer detects" section above.
How do I find out which version of @reduxjs/toolkit a website is running?
Read it straight from the site's JavaScript sourcemap. When a build ships source maps, the bundled `@reduxjs/toolkit/package.json` carries the exact `version` string — Sourcemap Explorer extracts it in one click on the Stack tab, and you can do it by hand in DevTools by opening the `.map` file and searching for `node_modules/@reduxjs/toolkit/package.json`. That is far more reliable than inferring the version from an asset-hash or a `?ver=` query string, which is all surface-level detectors have to go on. The current npm release is 2.12.0, but real deployments frequently run an older pinned version — which is exactly why reading the bundled number matters.
What is the latest version of @reduxjs/toolkit?
2.12.0, as published on the npm registry. The "Recent versions" table on this page lists the most recent 8 releases with their release dates. Sourcemap Explorer reports the version actually bundled into a site, which can lag the latest release by months on real-world deployments.
Is @reduxjs/toolkit actively maintained?
Very actively maintained — the last release shipped within the past three months. The last published release was 2026-05-15. Source code: https://github.com/reduxjs/redux-toolkit.
Where can I read more?
Project homepage: https://redux-toolkit.js.org. Source code: https://github.com/reduxjs/redux-toolkit. Published on npm: https://www.npmjs.com/package/@reduxjs/toolkit. Licensed as MIT.
Keep reading on Sourcemap Explorer
Detection deep dives
Alternative tools
Detected by Sourcemap Explorer
When a bundle ships sourcemaps, we read the embedded package.json for @reduxjs/toolkit and report the precise version (the registry's latest is v2.12.0, published 2026-05-15; the bundled copy is often older). Without sourcemaps, an import / require in the page's scripts is enough to flag it.