react-redux

This bugfix release fixes connect type inference under TS 7, fixes several connect and Provider runtime bugs, adds dev-mode logging for errors thrown in mapStateToProps, and updates our build tooling and TypeScript support matrix.

Changelog

connect Types and TS 7

We had reports that connect sometimes inferred the wrong props when mapStateToProps or mapDispatchToProps was a factory function. The connected component's props would collapse to {}, and a required prop would show up as "missing" at the call site.

Turns out the connect overloads typed those arguments as unions of the factory form (() => (state) => props) and the plain form. TS7 changed the ordering of which union member got selected, so this broke.

As Anders suggested in microsoft/typescript-go#977, we've split those unions into separate overloads listed in order of preference, factory form first. Overload matching no longer depends on how the compiler orders a union. We then applied the same fix to the mergeProps overloads, which still failed under TS 7.

Bug Fixes

Provider now uses serverState when it's a falsy value like 0, false, or ''. Previously it checked for truthiness, so a falsy root state fell back to the client store's state during SSR and hydration. null and undefined are still treated as "no server state".

A connected component's context prop is now honored in production. The assignment that picked up the custom context sat inside the development-only validation block. In production, a component with only a custom provider would throw, and one rendered under both providers would read the default provider's store.

connect no longer overrides a ref passed as a regular prop when forwardRef isn't enabled (#2251). With React 19's ref-as-prop, the wrapper was always passing its own ref (undefined without forwardRef), which replaced the one you passed in.

An explicit dependsOnOwnProps = false on a mapStateToProps or mapDispatchToProps function is now respected. We had been ignoring it for functions declared with two parameters, even though the option exists specifically for functions whose length isn't reliable.

Rendering <Provider> in a React Server Component without "use client" now throws a clear dev-mode error that tells you what's wrong, instead of failing with "useIsomorphicLayoutEffect is not a function" (#2082). Setups that resolve the react-server export condition already got a clear error. This covers the setups that don't.

mapStateToProps Error Logging

Since v8, an error thrown in mapStateToProps during a store update has been caught in the subscription callback and then effectively swallowed. The component just kept rendering its previous props (#1942). connect now logs those errors to console.error in development, so they show up in DevTools. Production behavior is unchanged.

TypeScript Support

The internal NoInfer helper type has been replaced with TypeScript's built-in NoInfer, which was added in TS 5.4. That makes TS 5.4 the minimum version for React-Redux's types. Our CI matrix now covers TS 5.6 through 5.9, 6.0, 7.0, and next.

Build Tooling

We've moved the repo to pnpm, Oxlint, and Oxfmt, and switched the library build from tsup to tsdown. The package exports layout is unchanged, but the build output comes from a different bundler. If you see any packaging or import problems with this release, please file an issue.

What's Changed

• connect: Log mapStateToProps errors to console.error in dev

• breaking

  Switch to native NoInfer utility type

• connect: Split mapStateToProps/mapDispatchToProps unions into ordered overloads

• Modern Tooling, Part 1: PNPM

• Fix TS7 errors and update TS matrix

• Provider: Throw a clearer error when rendered in a React Server Component

• Respect falsy server snapshots and production context overrides

• Don't override ref property when not configured to.

• Honour explicit dependsOnOwnProps=false in getDependsOnOwnProps

This feature release officially marks the connect API as deprecated.

That's it. That's the release. :)

Changelog

connect deprecation

Way back in 2022, I officially marked the original Redux core createStore method as deprecated in Redux 4.2.0. As I clearly stated in that release, the goal of marking createStore as deprecated was to encourage users to migrate to modern Redux Toolkit, especially for those users who don't read our docs (such as beginners following outdated tutorials or in bootcamps, etc). The change was visual-only - adding @deprecated just marks the import with a strikethrough in an IDE, and the docblock references the "use modern Redux Toolkit" docs page. No runtime errors, no behavior changes, just an indication that the function is considered obsolete and you shouldn't use it directly any more. I also exported a legacy_createStore alias - same function, no deprecation attribute.

It's 4 years later, and I'm finally doing the same thing for connect :)

Again, nothing about connect's behavior is changing, and we do not intend to remove the connect API. But it's 2026, and hooks are the correct way to use React and React-Redux today.

We do strongly encourage users to migrate from connect to the useSelector / useDispatch hooks in general. This should result in codebases that are easier to understand and ought to improve performance slightly due to the way updates are handled.

As with before, React-Redux now exports a legacy_connect alias that does not have the deprecation attribute applied.

Trusted Publishing Fixed

We had set up trusted publishing for React-Redux a couple years ago and did some releases with that enabled, but at some point I did a follow-up release that still used the previous manual workflow, and that lost the trusted publishing provenance flag. We had recent issues requesting a new release with trusted publishing enabled again, so we've fixed that with this release.

What's Changed

• deprecated

  Mark connect as deprecated

This feature release updates the React peer dependency to work with React 19, and improves treeshakeability of our build artifacts.

Changelog

React 19 Compat

React 19 was just released! We've updated our peer dep to accept React 19, and updated our runtime and type tests to check against both React 18 and 19.

Also see Redux Toolkit v2.5.0 for the same peer dep update.

Treeshaking

We've done some nitty-gritty optimization work to ensure bundlers correctly treeshake unused parts of the bundle.

What's Changed

• Improve treeshakeability of build artifacts

• Migrate to React

• Migrate to React 19 (take 2)

• Clean up devdeps