chore(deps): update dependency react-redux to v9

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
react-redux	^7.1.1 || ^8.1.1 -> ^7.1.1 || ^8.1.1 || ^9.0.0
react-redux	^8.1.1 -> ^9.0.0

---

Release Notes

reduxjs/react-redux (react-redux)

v9.2.0

Compare Source

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 by @​aryaemami59 in #​2176
• Migrate to React by @​aryaemami59 in #​2172
• Migrate to React 19 (take 2) by @​markerikson in #​2216
• Clean up devdeps by @​markerikson in #​2217

Full Changelog: reduxjs/react-redux@v9.1.2...v9.2.0

v9.1.2

Compare Source

This bugfix release removes the no-longer-necessary peer dependency on react-native, and tweaks a few TS types for compat with the upcoming React 19 release.

Changes

React Native Peer Dependency Removed

We've always had an awkward peer dependency on both ReactDOM and React Native, because of the need to import the unstable_batchedUpdates API directly from each reconciler. That's part of what led to the sequence of 9.x patch releases to deal with RN compat.

As of 9.0.3, we dropped the batching imports completely, since React 18 now batches by default. That means we didn't even have any remaining imports from react-native.

Meanwhile, React 18.3 just came out, but so did React Native 0.74. RN 0.74 still requires React 18.2.

This caused NPM users to have installation failures when trying to use React-Redux:

• React-Redux has a peer dep on RN
• RN has a peer dep on React 18.2
• But the latest React, 18.3 would get installed in the app
• NPM errors with a peer dep mismatch

We no longer need to list RN as a peer dep, and dropping that also fixes the NPM installation issues as well.

What's Changed

• Fix useRef usages to be called with an explicit argument of undefined. by @​aryaemami59 in #​2164
• Replace usage of deprecated JSX global namespace with React.JSX by @​aryaemami59 in #​2163
• Drop now-unneeded RN peer dep by @​markerikson in #​2167
• Fix remaining React 19 types issues by @​markerikson in #​2168

Full Changelog: reduxjs/react-redux@v9.1.1...v9.1.2

v9.1.1

Compare Source

This bugfix release fixes an issue with connect and React Native caused by changes to our bundling setup in v9. Nested connect calls should work correctly now.

What's Changed

• Remove unused isProcessingDispatch by @​Connormiha in #​2122
• Move Equals constraint into an intersection type. by @​DanielRosenwasser in #​2123
• Fix useIsomorphicLayoutEffect usage in React Native environments by @​aryaemami59 in #​2156

Full Changelog: reduxjs/react-redux@v9.1.0...v9.1.1

v9.1.0

Compare Source

This minor release adds a new syntax for pre-typing hooks.

.withTypes

Previously, the approach for "pre-typing" hooks with your app settings was a little varied. The result would look something like the below:

import type { TypedUseSelectorHook } from "react-redux"
import { useDispatch, useSelector, useStore } from "react-redux"
import type { AppDispatch, AppStore, RootState } from "./store"

export const useAppDispatch: () => AppDispatch = useDispatch
export const useAppSelector: TypedUseSelectorHook<RootState> = useSelector
export const useAppStore = useStore as () => AppStore

React Redux v9.1.0 adds a new .withTypes method to each of these hooks, analogous to the .withTypes method found on Redux Toolkit's createAsyncThunk.

The setup now becomes:

import { useDispatch, useSelector, useStore } from "react-redux"
import type { AppDispatch, AppStore, RootState } from "./store"

export const useAppDispatch = useDispatch.withTypes<AppDispatch>()
export const useAppSelector = useSelector.withTypes<RootState>()
export const useAppStore = useStore.withTypes<AppStore>()

What's Changed

• Update hooks.md — reselect usage with multiple instances simplified by @​VorontsovIE in #​2110
• Modernize ESLint configuration by @​aryaemami59 in #​2115
• Introduce pre-typed hooks via hook.withTypes<RootState>() method by @​aryaemami59 in #​2114

New Contributors

• @​VorontsovIE made their first contribution in #​2110

Full Changelog: reduxjs/react-redux@v9.0.4...v9.1.0

v9.0.4

Compare Source

This bugfix release updates the React Native peer dependency to be >= 0.69, to better reflect the need for React 18 compat and (hopefully) resolve issues with the npm package manager throwing peer dep errors on install.

What's Changed

• Allow react-native newer than 0.69 as peer dependency by @​R3DST0RM in #​2107

Full Changelog: reduxjs/react-redux@v9.0.3...v9.0.4

v9.0.3

Compare Source

This bugfix release drops the ReactDOM / React Native specific use of render batching, as React 18 now automatically batches, and updates the React types dependencies

Changelog

Batching Dependency Updates

React-Redux has long depended on React's unstable_batchedUpdates API to help batch renders queued by Redux updates. It also re-exported that method as a util named batch.

However, React 18 now auto-batches all queued renders in the same event loop tick, so unstable_batchedUpdates is effectively a no-op.

Using unstable_batchedUpdates has always been a pain point, because it's exported by the renderer package (ReactDOM or React Native), rather than the core react package. Our prior implementation relied on having separate batch.ts and batch.native.ts files in the codebase, and expecting React Native's bundler to find the right transpiled file at app build time. Now that we're pre-bundling artifacts in React-Redux v9, that approach has become a problem.

Given that React 18 already batches by default, there's no further need to continue using unstable_batchedUpdates internally, so we've removed our use of that and simplified the internals.

We still export a batch method, but it's effectively a no-op that just immediately runs the given callback, and we've marked it as @deprecated.

We've also updated the build artifacts and packaging, as there's no longer a need for an alternate-renderers entry point that omits batching, or a separate artifact that imports from "react-native".

What's Changed

• Drop renderer-specific batching behavior and deprecate batch by @​markerikson in #​2104
• Drop @types/react-dom and lower @types/react to min needed by @​markerikson in #​2105

Full Changelog: reduxjs/react-redux@v9.0.2...v9.0.3

v9.0.2

Compare Source

This bugfix release makes additional tweaks to the React Native artifact filename to help resolve import and bundling issues with RN projects.

What's Changed

• Change react-native output extension from .mjs to .js by @​aryaemami59 in #​2102

Full Changelog: reduxjs/react-redux@v9.0.1...v9.0.2

v9.0.1

Compare Source

This bugfix release updates the package to include a new react-redux.react-native.js bundle that specifically imports React Native, and consolidates all of the 'react' imports into one file to save on bundle size (and enable some tricky React Native import handling).

What's Changed

• Add an RN-specific bundle and consolidate imports by @​markerikson in #​2100

Full Changelog: reduxjs/react-redux@v9.0.0...v9.0.1

v9.0.0

Compare Source

This major release:

• Switches to requiring React 18 and Redux Toolkit 2.0 / Redux 5.0
• Updates the packaging for better ESM/CJS compatibility and modernizes the build output
• Updates the options for dev mode checks in useSelector
• Adds a new React Server Components artifact that throws on use, to better indicate compat issues

This release has breaking changes.

This release is part of a wave of major versions of all the Redux packages: Redux Toolkit 2.0, Redux core 5.0, React-Redux 9.0, Reselect 5.0, and Redux Thunk 3.0.

For full details on all of the breaking changes and other significant changes to all of those packages, see the "Migrating to RTK 2.0 and Redux 5.0" migration guide in the Redux docs.

[!NOTE]
The Redux core, Reselect, and Redux Thunk packages are included as part of Redux Toolkit, and RTK users do not need to manually upgrade them - you'll get them as part of the upgrade to RTK 2.0. (If you're not using Redux Toolkit yet, please start migrating your existing legacy Redux code to use Redux Toolkit today!)
React-Redux is a separate, package, but we expect you'll be upgrading them together.

### React-Redux
npm install react-redux
yarn add react-redux

### RTK
npm install @​reduxjs/toolkit
yarn add @​reduxjs/toolkit

### Standalone Redux core
npm install redux
yarn add redux

Changelog

React 18 and RTK 2 / Redux core 5 Are Required

React-Redux 7.x and 8.x worked with all versions of React that had hooks (16.8+, 17.x, 18.x). However, React-Redux v8 used React 18's new useSyncExternalStore hook. In order to maintain backwards compatibility with older React versions, we used the use-sync-external-store "shim" package that provided an official userland implementation of the useSyncExternalStore hook when used with React 16 or 17. This meant that if you were using React 18, there were a few hundred extra bytes of shim code being imported even though it wasn't needed.

For React-Redux v9, we're switching so that React 18 is now required! This both simplifies the maintenance burden on our side (fewer versions of React to test against), and also lets us drop the extra bytes because we can import useSyncExternalStore directly.

React 18 has been out for a year and a half, and other libraries like React Query are also switching to require React 18 in their next major version. This seems like a reasonable time to make that switch.

Similarly, React-Redux now depends on Redux core v5 for updated TS types (but not runtime behavior). We strongly encourage all Redux users to be using Redux Toolkit, which already includes the Redux core. Redux Toolkit 2.0 comes with Redux core 5.0 built in.

ESM/CJS Package Compatibility

The biggest theme of the Redux v5 and RTK 2.0 releases is trying to get "true" ESM package publishing compatibility in place, while still supporting CJS in the published package.

The primary build artifact is now an ESM file, dist/react-redux.mjs. Most build tools should pick this up. There's also a CJS artifact, and a second copy of the ESM file named react-redux.legacy-esm.js to support Webpack 4 (which does not recognize the exports field in package.json). There's also two special-case artifacts: an "alternate renderers" artifact that should be used for any renderer other than ReactDOM or React Native (such as the ink React CLI renderer), and a React Server Components artifact that throws when any import is used (since using hooks or context would error anyway in an RSC environment). Additionally, all of the build artifacts now live under ./dist/ in the published package.

Previous releases actually shipped separate individual transpiled source files - the build artifacts are now pre-bundled, same as the rest of the Redux libraries.

Modernized Build Output

We now publish modern JS syntax targeting ES2020, including optional chaining, object spread, and other modern syntax. If you need to . If you need to target older browsers, please transpile the packages yourself (or use the legacy-esm build artifact for ES2017).

Build Tooling

We're now building the package using https://github.com/egoist/tsup. We also now include sourcemaps for the ESM and CJS artifacts.

Dropping UMD Builds

Redux has always shipped with UMD build artifacts. These are primarily meant for direct import as script tags, such as in a CodePen or a no-bundler build environment.

We've dropped those build artifacts from the published package, on the grounds that the use cases seem pretty rare today.

There's now a react-redux.browser.mjs file in the package that can be loaded from a CDN like Unpkg.

If you have strong use cases for us continuing to include UMD build artifacts, please let us know!

React Server Components Behavior

Per Mark's post "My Experience Modernizing Packages to ESM", one of the recent pain points has been the rollout of React Server Components and the limits the Next.js + React teams have added to RSCs. We see many users try to import and use React-Redux APIs in React Server Component files, then get confused why things aren't working right.

To address that, we've added a new entry point with a "react-server" condition. Every export in that file will throw an error as soon as it's called, to help catch this mistake earlier.

Dev Mode Checks Updated

In v8.1.0, we updated useSelector to accept an options object containing options to check for selectors that always calculate new values, or that always return the root state.

We've renamed the noopCheck option to identityFunctionCheck for clarity. We've also changed the structure of the options object to be:

export type DevModeCheckFrequency = 'never' | 'once' | 'always'

export interface UseSelectorOptions<Selected = unknown> {
  equalityFn?: EqualityFn<Selected>
  devModeChecks?: {
    stabilityCheck?: DevModeCheckFrequency
    identityFunctionCheck?: DevModeCheckFrequency
  }
}

hoist-non-react-statics and react-is Deps Inlined

Higher Order Components have been discouraged in the React ecosystem over the last few years. However, we still include the connect API. It's now in maintenance mode and not in active development.

As described in the React legacy docs on HOCs, one quirk of HOCs is needing to copy over static methods to the wrapper component. The hoist-non-react-statics package has been the standard tool to do that.

We've inlined a copy of hoist-non-react-statics and removed the package dep, and confirmed that this improves tree-shaking.

We've also done the same with the react-is package as well, which was also only used by connect.

This should have no user-facing effects.

TypeScript Support

We've dropped support for TS 4.6 and earlier, and our support matrix is now TS 4.7+.

What's Changed

• Update packaging, build config, and entry points for v9 by @​markerikson in #​2038
• Add stack to dev mode checks by @​EskiMojo14 in #​2064
• add an extra entrypoint for React Server Components by @​phryneas in #​2062
• Inline hoist-non-react-statics to eliminate a dep and help shaking by @​markerikson in #​2066
• Make context typing more accurate by @​EskiMojo14 in #​2041
• Fix uSES imports and run against RTK CI examples by @​markerikson in #​2070
• Copy CI setup for RTK examples by @​markerikson in #​2072
• Fix useSelector() in combination with lazy loaded components breaks with react v18 (#​1977) by @​jeroenpx in #​2068
• Actually add sideEffects: "false" to package.json in v9 by @​markerikson in #​2079
• Inline react-is utils to fix tree-shaking in 9.0 by @​markerikson in #​2085
• Rename noopCheck to identityFunctionCheck by @​aryaemami59 in #​2091
• Use scoped JSX for React types by @​markerikson in #​2092

Full Changelog: reduxjs/react-redux@v8.1.2...v9.0.0

---

Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, only on Monday ( * 0-3 * * 1 ) in timezone America/New_York, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: @edx/[email protected]
npm error Found: [email protected]
npm error node_modules/react
npm error   dev react@"17.0.2" from the root project
npm error
npm error Could not resolve dependency:
npm error peer react@"^18.0" from [email protected]
npm error node_modules/react-redux
npm error   dev react-redux@"^9.0.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2024-05-06T07_57_02_171Z-eresolve-report.txt

npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-05-06T07_57_02_171Z-debug-0.log

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm warn Unknown env config "store". This will stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: [email protected]
npm error Found: [email protected]
npm error node_modules/redux
npm error   dev redux@"4.2.1" from the root project
npm error
npm error Could not resolve dependency:
npm error peerOptional redux@"^5.0.0" from [email protected]
npm error node_modules/react-redux
npm error   dev react-redux@"^9.0.0" from the root project
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/redux
npm error   peerOptional redux@"^5.0.0" from [email protected]
npm error   node_modules/react-redux
npm error     dev react-redux@"^9.0.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2025-10-24T00_44_13_566Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-10-24T00_44_13_566Z-debug-0.log