Bump react-redux from 8.0.5 to 8.1.3 in /client

[dependabot]

Bumps react-redux from 8.0.5 to 8.1.3.

Release notes

Sourced from react-redux's releases.

v8.1.3

This bugfix release fixes an issue with subscriptions being lost when lazy-loaded components are used with React Suspense, and includes stack traces in useSelector usage warnings .

What's Changed

• Add stack to dev mode checks by @​EskiMojo14 in reduxjs/react-redux#2064
• Fix useSelector() in combination with lazy loaded components breaks with react v18 (#1977) by @​jeroenpx in reduxjs/react-redux#2068

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

v8.1.2

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

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 reduxjs/react-redux#2034
• create singleton context by React version by @​phryneas in reduxjs/react-redux#2039
• remove RTK peerDep by @​markerikson in 44fc725

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

v8.1.0

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 ).

... (truncated)

Commits

• 854f3e1 Release 8.1.3
• 2057c5e Merge pull request #2068 from jeroenpx/feature/useSelector-in-combination-wit...
• 6ca0567 Merge pull request #2072 from reduxjs/feature/master-ci-checks
• f0324a1 Copy CI setup for RTK examples
• 6c0ad9e Fix useSelector() in combination with lazy loaded components breaks with reac...
• a1a32d1 Merge pull request #2064 from reduxjs/warning-stack
• bc328d9 Add stack to dev mode checks
• 4a7e129 Release 8.1.2
• 2ac527b RSC-specific workarounds (#2050)
• a669a94 add "publish" workflow
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[nilsstreedain]

Tested, no utilized breaking changes