Update dependency react-redux to v8.1.3

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
react-redux	8.0.4 -> 8.1.3

---

Release Notes

reduxjs/react-redux (react-redux)

v8.1.3

Compare Source

v8.1.2

Compare Source

This version changes imports from the React package to namespace imports so the package can safely be imported in React Server Components as long as you don't actually use it - this is for example important if you want to use the React-specifc createApi function from Redux Toolkit.

Some other changes:

• The behaviour of the "React Context Singletons" from 8.1.1 has been adjusted to also work if you have multiple React instances of the same version (those will now be separated) and if you are in an environment without globalThis (in this case it will fall back to the previous behaviour).
• We do no longer use Proxies, which should help with some very outdated consumers, e.g. smart TVs, that cannot even polyfill Proxies.

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

v8.1.1

Compare Source

This bugfix release tweaks the recent lazy context setup logic to ensure a single React context instance per React version, and removes the recently added RTK peerdep to fix an issue with Yarn workspaces.

Changelog

React Context Singletons

React Context has always relied on reference identity. If you have two different copies of React or a library in a page, that can cause multiple versions of a context instance to be created, leading to problems like the infamous "Could not find react-redux context" error.

In v8.1.0, we reworked the internals to lazily create our single ReactReduxContext instance to avoid issues in a React Server Components environment.

This release further tweaks that to stash a single context instance per React version found in the page, thus hopefully avoiding the "multiple copies of the same context" error in the future.

What's Changed

• fix: fix typescript error on non exported type by @​luzzif in https://github.com/reduxjs/react-redux/pull/2034
• create singleton context by React version by @​phryneas in https://github.com/reduxjs/react-redux/pull/2039
• remove RTK peerDep by @​markerikson in 44fc725

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

v8.1.0

Compare Source

This feature release adds new development-mode safety checks for common errors (like poorly-written selectors), adds a workaround to fix crash errors when React-Redux hooks are imported into React Server Component files, and updates our hooks API docs page with improved explanations and updated links.

Changelog

Development Mode Checks for useSelector

We've had a number of users tell us over time that it's common to accidentally write selectors that have bad behavior and cause performance issues. The most common causes of this are either selectors that unconditionally return a new reference (such as state => state.todos.map() without any memoization ), or selectors that actually return the entire root state ( state => state ).

We've updated useSelector to add safety checks in development mode that warn if these incorrect behaviors are detected:

• Selectors will be called twice with the same inputs, and useSelector will warn if the results are different references
• useSelector will warn if the selector result is actually the entire root state

By default, these checks only run once the first time useSelector is called. This should provide a good balance between detecting possible issues, and keeping development mode execution performant without adding many unnecessary extra selector calls.

If you want, you can configure this behavior globally by passing the enum flags directly to <Provider>, or on a per-useSelector basis by passing an options object as the second argument:

// Example: globally configure the root state "noop" check to run every time
<Provider store={store} noopCheck="always">
  {children}
</Provider>

// Example: configure `useSelector` to specifically run the reference checks differently:
function Component() {
  // Disable check entirely for this selector
  const count = useSelector(selectCount, { stabilityCheck: 'never' })
  // run once (default)
  const user = useSelector(selectUser, { stabilityCheck: 'once' })
  // ...
}

This goes along with the similar safety checks we've added to Reselect v5 alpha as well.

Context Changes

We're still trying to work out how to properly use Redux and React Server Components together. One possibility is using RTK Query's createApi to define data fetching endpoints, and using the generated thunks to fetch data in RSCs, but it's still an open question.

However, users have reported that merely importing any React-Redux API in an RSC file causes a crash, because React.createContext is not defined in RSC files. RTKQ's React-specific createApi entry point imports React-Redux, so it's been unusable in RSCs.

This release adds a workaround to fix that issue, by using a proxy wrapper around our singleton ReactReduxContext instance and lazily creating that instance on demand. In testing, this appears to both continue to work in all unit tests, and fixes the import error in an RSC environment. We'd appreciate further feedback in case this change does cause any issues for anyone!

We've also tweaked the internals of the hooks to do checks for correct <Provider> usage when using a custom context, same as the default context checks.

Docs Updates

We've cleaned up some of the Hooks API reference page, and updated links to the React docs.

What's Changed

• check for Provider even when using custom context by @​EskiMojo14 in https://github.com/reduxjs/react-redux/pull/1990
• Add a stability check, to see if selector returns stable result when called with same parameters. by @​EskiMojo14 in https://github.com/reduxjs/react-redux/pull/2000
• Add an E2E-ish test that verifies behavior when imported into RSCs by @​markerikson in https://github.com/reduxjs/react-redux/pull/2030
• lazily create Context for RSC compat by @​phryneas in https://github.com/reduxjs/react-redux/pull/2025
• Add warning for selectors that return the entire state by @​EskiMojo14 in https://github.com/reduxjs/react-redux/pull/2022

Full Changelog: reduxjs/react-redux@v8.0.7...v8.1.0

v8.0.7

Compare Source

This release updates the peer dependencies to accept Redux Toolkit, and accept the ongoing RTK and Redux core betas as valid peer deps.

Note: These changes were initially in 8.0.6, but that had a typo in the peer deps that broke installation. Sorry!

What's Changed

• Bump Redux peer deps to accept 5.0 betas, and bump RTK dev dep by @​markerikson in https://github.com/reduxjs/react-redux/pull/2017
• d45204f : Fix broken RTK peer dep

Full Changelog: reduxjs/react-redux@v8.0.5...v8.0.7

v8.0.6

Compare Source

~~This release updates the peer dependencies to accept Redux Toolkit, and accept the ongoing RTK and Redux core betas as valid peer deps.~~

This release has a peer deps typo that breaks installation - please use 8.0.7 instead !

What's Changed

• Bump Redux peer deps to accept 5.0 betas, and bump RTK dev dep by @​markerikson in https://github.com/reduxjs/react-redux/pull/2017

Full Changelog: reduxjs/react-redux@v8.0.5...v8.0.6

v8.0.5

Compare Source

This release fixes a few minor TS issues.

What's Changed

• Provider: pass state (S) generic through to ProviderProps by @​OliverJAsh in https://github.com/reduxjs/react-redux/pull/1960
• wrap equalityFn type in NoInfer by @​phryneas in https://github.com/reduxjs/react-redux/pull/1965
• Fix wrapped component prop types when passing nullish mapDispatchToProps by @​marconi1992 in https://github.com/reduxjs/react-redux/pull/1928

Full Changelog: reduxjs/react-redux@v8.0.4...v8.0.5

---

Configuration

📅 Schedule: Branch creation - "after 10pm every weekday,before 5am every weekday,every weekend" (UTC), Automerge - At any time (no schedule defined).

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

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

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

---

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

---

This PR has been generated by Mend Renovate. View repository job log here.

[codecov]

Codecov Report

All modified lines are covered by tests ✅

Comparison is base (7c81500) 96.23% compared to head (9173443) 96.23%.

Additional details and impacted files

@@           Coverage Diff            @@
##           develop    #1557   +/-   ##
========================================
  Coverage    96.23%   96.23%           
========================================
  Files          161      161           
  Lines         6935     6935           
  Branches      2147     2147           
========================================
  Hits          6674     6674           
  Misses         240      240           
  Partials        21       21           

Flag	Coverage Δ
common	95.53% <ø> (ø)
dataview	96.94% <ø> (ø)
download	96.32% <ø> (ø)
search	96.47% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.