Update dependency react-redux to v8

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
react-redux	`^7.2.3` -> `^8.0.0`

Release Notes

reduxjs/react-redux

### [`v8.0.5`](https://togithub.com/reduxjs/react-redux/releases/tag/v8.0.5) [Compare Source](https://togithub.com/reduxjs/react-redux/compare/v8.0.4...v8.0.5) This release fixes a few minor TS issues. #### What's Changed - `Provider`: pass state (`S`) generic through to `ProviderProps` by [@OliverJAsh](https://togithub.com/OliverJAsh) in [https://github.com/reduxjs/react-redux/pull/1960](https://togithub.com/reduxjs/react-redux/pull/1960) - wrap `equalityFn` type in `NoInfer` by [@phryneas](https://togithub.com/phryneas) in [https://github.com/reduxjs/react-redux/pull/1965](https://togithub.com/reduxjs/react-redux/pull/1965) - Fix wrapped component prop types when passing nullish mapDispatchToProps by [@marconi1992](https://togithub.com/marconi1992) in [https://github.com/reduxjs/react-redux/pull/1928](https://togithub.com/reduxjs/react-redux/pull/1928) **Full Changelog**: https://github.com/reduxjs/react-redux/compare/v8.0.4...v8.0.5 ### [`v8.0.4`](https://togithub.com/reduxjs/react-redux/releases/tag/v8.0.4) [Compare Source](https://togithub.com/reduxjs/react-redux/compare/v8.0.3...v8.0.4) This patch release fixes some minor TS types issues, and updates the rarely-used `areStatesEqual` option for `connect` to now pass through `ownProps` for additional use in determining which pieces of state to compare if desired. > **Note**: 8.0.3 was accidentally published without one of these fixes. Use 8.0.4 instead. #### Changelog ##### TS Fixes We've fixed an import of `React` that caused issues with the `allowSyntheticDefaultImports` TS compiler flag in user projects. `connect` already accepted a custom context instance as `props.context`, and had runtime checks in case users were passing through a real value with app data as `props.context` instead. However, the TS types did not handle that case, and this would fail to compile. If your own component expects `props.context` with actual data, `connect`'s types now use that type instead. The `ConnectedProps` type had a mismatch with React's built-in `React.ComponentProps` type, and that should now work correctly. ##### Other Changes The `areStatesEqual` option to `connect` now receives `ownProps` as well, in case you need to make a more specific comparison with certain sections of state. The new signature is: ```ts { areStatesEqual?: ( nextState: State, prevState: State, nextOwnProps: TOwnProps, prevOwnProps: TOwnProps ) => boolean } ``` #### What's Changed - Don't require allowSyntheticDefaultImports: true by [@apepper](https://togithub.com/apepper) in [https://github.com/reduxjs/react-redux/pull/1924](https://togithub.com/reduxjs/react-redux/pull/1924) - Fixed type issue with `ComponentProps` from older `@types/react` by [@Andarist](https://togithub.com/Andarist) in [https://github.com/reduxjs/react-redux/pull/1956](https://togithub.com/reduxjs/react-redux/pull/1956) - connect: pass ownProps to areStatesEqual by [@jspurlin](https://togithub.com/jspurlin) in [https://github.com/reduxjs/react-redux/pull/1951](https://togithub.com/reduxjs/react-redux/pull/1951) - Omit built-in context prop if user component props include context by [@markerikson](https://togithub.com/markerikson) in [https://github.com/reduxjs/react-redux/pull/1958](https://togithub.com/reduxjs/react-redux/pull/1958) **Full Changelog**: https://github.com/reduxjs/react-redux/compare/v8.0.2...v8.0.4 ### [`v8.0.3`](https://togithub.com/reduxjs/react-redux/releases/tag/v8.0.3) [Compare Source](https://togithub.com/reduxjs/react-redux/compare/v8.0.2...v8.0.3) **This release was accidentally published without an intended fix - please use [v8.0.4](https://togithub.com/reduxjs/react-redux/releases/tag/v8.0.4) instead** ### [`v8.0.2`](https://togithub.com/reduxjs/react-redux/releases/tag/v8.0.2) [Compare Source](https://togithub.com/reduxjs/react-redux/compare/v8.0.1...v8.0.2) This patch release tweaks the behavior of `connect` to print a one-time warning when the obsolete `pure` option is passed in, rather than throwing an error. This fixes crashes caused by libraries such as `react-beautiful-dnd` continuing to pass in that option (unnecessarily) to React-Redux v8. #### What's Changed - Show warning instead of throwing error that pure option has been removed by [@ApacheEx](https://togithub.com/ApacheEx) in [https://github.com/reduxjs/react-redux/pull/1922](https://togithub.com/reduxjs/react-redux/pull/1922) **Full Changelog**: https://github.com/reduxjs/react-redux/compare/v8.0.1...v8.0.2 ### [`v8.0.1`](https://togithub.com/reduxjs/react-redux/releases/tag/v8.0.1) [Compare Source](https://togithub.com/reduxjs/react-redux/compare/v8.0.0...v8.0.1) This release fixes an incorrect internal import of our `Subscription` type, which was causing TS compilation errors in some user projects. We've also listed `@types/react-dom` as an optional peerDep. There are no runtime changes in this release. #### What's Changed - Add optional peer dependency on [@types/react-dom](https://togithub.com/types/react-dom) by [@Methuselah96](https://togithub.com/Methuselah96) in [https://github.com/reduxjs/react-redux/pull/1904](https://togithub.com/reduxjs/react-redux/pull/1904) - fix(ts): incorrect import of `Subscription` causes `noImplicitAny` error by [@vicrep](https://togithub.com/vicrep) in [https://github.com/reduxjs/react-redux/pull/1910](https://togithub.com/reduxjs/react-redux/pull/1910) **Full Changelog**: https://github.com/reduxjs/react-redux/compare/v8.0.0...v8.0.1 ### [`v8.0.0`](https://togithub.com/reduxjs/react-redux/releases/tag/v8.0.0) [Compare Source](https://togithub.com/reduxjs/react-redux/compare/v7.2.9...v8.0.0) This **major version** release updates `useSelector`, `connect`, and `` for compatibility with React 18, rewrites the React-Redux codebase to TypeScript (obsoleting use of `@types/react-redux`), modernizes build output, and removes the deprecated `connectAdvanced` API and the `pure` option for `connect`. npm i react-redux@latest yarn add react-redux@latest #### Overview, Compatibility, and Migration Our public API is still the same ( ``, `connect` and `useSelector/useDispatch`), but we've updated the internals to use the new `useSyncExternalStore` hook from React. React-Redux v8 is still compatible with all versions of React that have hooks (16.8+, 17.x, and 18.x; React Native 0.59+), and *should* just work out of the box. In most cases, it's very likely that the only change you will need to make is bumping the package version to `"react-redux": "^8.0"`. *If* you are using the rarely-used `connectAdvanced` API, you will need to rewrite your code to avoid that, likely by using the hooks API instead. Similarly, the `pure` option for `connect` has been removed. If you are using Typescript, React-Redux is now written in TS and includes its own types. You should remove any dependencies on `@types/react-redux`. While not directly tied to React-Redux, note that **the recently updated `@types/react@18` major version has changed component definitions to remove having `children` as a prop by default**. This causes errors if you have multiple copies of `@types/react` in your project. To fix this, tell your package manager to resolve `@types/react` to a single version. Details: [**React issue #24304: React 18 types broken since release**](https://togithub.com/facebook/react/issues/24304#issuecomment-1094565891) Additionally, please see the React post on [**How to Ugprade to React 18**](https://reactjs.org/blog/2022/03/08/react-18-upgrade-guide.html) for details on how to migrate existing apps to correctly use React 18 and take advantage of its new features. #### Changelog ##### React 18 Compatibility React-Redux now requires the new [`useSyncExternalStore` API in React 18](https://togithub.com/reactwg/react-18/discussions/86). By default, it uses the "shim" package which backfills that API in earlier React versions, so **React-Redux v8 is compatible with all React versions that have hooks** (16.8+, and React Native 0.59+) as its acceptable peer dependencies. We'd especially like to thank the React team for their extensive support and cooperation during the `useSyncExternalStore` development effort. They specifically designed `useSyncExternalStore` to support the needs and use cases of React-Redux, and we used React-Redux v8 as a testbed for how `useSyncExternalStore` would behave and what it needed to cover. This in turn helped ensure that `useSyncExternalStore` would be useful and work correctly for other libraries in the ecosystem as well. Our performance benchmarks show parity with React-Redux v7.2.5 for both `connect` and `useSelector`, so we do not anticipate any meaningful performance regressions. ##### `useSyncExternalStore` and Bundling The `useSyncExternalStore` shim is imported directly in the main entry point, so it's *always* included in bundles even if you're using React 18. This adds roughly 600 bytes minified to your bundle size. If you are using React 18 and would like to avoid that extra bundle cost, React-Redux now has a new `/next` entry point. This exports the exact same APIs, but directly imports `useSyncExternalStore` from React itself, and thus avoids including the shim. You can alias `"react-redux": "react-redux/next"` in your bundler to use that instead. ##### SSR and Hydration React 18 introduces a new `hydrateRoot` method for hydrating the UI on the client in Server-Side Rendering usage. As part of that, the `useSyncExternalStore` API requires that we pass in an alternate state value other than what's in the actual Redux store, and that alternate value will be used for the entire initial hydration render to ensure the initial rehydrated UI is an exact match for what was rendered on the server. After the hydration render is complete, React will then apply any additional changes from the store state in a follow-up render. React-Redux v8 supports this by adding a new `serverState` prop for ``. If you're using SSR, you should pass your serialized state to `` to ensure there are no hydration mismatch errors: ```ts import { hydrateRoot } from 'react-dom/client' import { configureStore } from '@reduxjs/toolkit' import { Provider } from 'react-redux' const preloadedState = window.__PRELOADED_STATE__ const clientStore = configureStore({ reducer: rootReducer, preloadedState, }) hydrateRoot( document.getElementById('root'), ) ``` ##### TypeScript Migration and Support The React-Redux library source has always been written in plain JS, and the community maintained the TS typings separately as `@types/react-redux`. We've (finally!) [migrated the React-Redux codebase to TypeScript](https://togithub.com/reduxjs/react-redux/issues/1737), using the existing typings as a starting point. This means that **the `@types/react-redux` package is no longer needed, and you should remove that as a dependency**. > **Note** Please ensure that any installed copies of `redux` and `@types/react` are de-duped. You are also encouraged to update to the latest versions of Redux Toolkit (1.8.1+) or Redux (4.1.2), to ensure consistency between installed types and avoid problems from types mismatches. We've tried to maintain the same external type signatures as much as possible. If you do see any compile problems, please file issues with any apparent TS-related problems so we can review them. The TS migration was a great collaborative effort, with many community members contributing migrated files. Thank you to everyone who helped out! In addition to the "pre-typed" `TypedUseSelectorHook`, there's now also a `Connect` type that can be used as a "pre-typed" version of `connect` as well. As part of the process, we also updated the repo to use Yarn 3, copied the typetests files from DefinitelyTyped and expanded them, and improved our CI setup to test against multiple TS versions. ##### Removal of the `DefaultRootState` type The `@types/react-redux` package, which has always been maintained by the community, included a `DefaultRootState` interface that was intended for use with TS's "module augmentation" capability. Both `connect` and `useSelector` used this as a fallback if no state generic was provided. When we migrated React-Redux to TS, we copied over all of the types from that package as a starting point. However, the Redux team [specifically considers use of a globally augmented state type to be an anti-pattern](https://togithub.com/reduxjs/react-redux/issues/1879). Instead, we direct users to [extract the `RootState` and `AppDispatch` types from the store setup](https://redux.js.org/tutorials/typescript-quick-start#define-root-state-and-dispatch-types), and [create pre-typed versions of the React-Redux hooks](https://redux.js.org/tutorials/typescript-quick-start#define-typed-hooks) for use in the app. Now that React-Redux itself is written in TS, we've opted to remove the `DefaultRootState` type entirely. State generics now default to `unknown` instead. Technically [the module augmentation approach can still be done in userland](https://togithub.com/reduxjs/react-redux/issues/1879#issuecomment-1073284804), but we discourage this practice. ##### Modernized Build Output We've always targeted ES5 syntax in our published build artifacts as the lowest common denominator. Even the "ES module" artifacts with `import/export` keywords still were compiled to ES5 syntax otherwise. With IE11 now effectively dead and many sites no longer supporting it, we've updated our build tooling to target a more modern syntax equivalent to ES2017, which shrinks the bundle size slightly. If you still need to support ES5-only environments, please compile your own dependencies as needed for your target environment. ##### Removal of Legacy APIs We announced in 2019 that [the legacy `connectAdvanced` API would be removed in the next major version](https://togithub.com/reduxjs/react-redux/issues/1236), as it was rarely used, added internal complexity, and was also basically irrelevant with the introduction of hooks. As promised, we've removed that API. We've also removed the `pure` option for `connect`, which forced components to re-render regardless of whether props/state had actually changed if it was set to `false`. This option was needed in some cases in the early days of the React ecosystem, when components sometimes relied on external mutable data sources that could change outside of rendering. Today, no one writes components that way, the option was barely used, and React 18's `useSyncExternalStore` strictly requires immutable updates. So, we've removed the `pure` flag. Given that both of these options were almost never used, this shouldn't meaningfully affect anyone. #### Changes Due to the TS migration effort and number of contributors, this list covers just the major changes: - Integrate TypeScript port by [@markerikson](https://togithub.com/markerikson) in [https://github.com/reduxjs/react-redux/pull/1739](https://togithub.com/reduxjs/react-redux/pull/1739) - Initial experimental React 18 compat prototyping by [@markerikson](https://togithub.com/markerikson) in [https://github.com/reduxjs/react-redux/pull/1808](https://togithub.com/reduxjs/react-redux/pull/1808) - Fix compatibility with React 18 strict effects by [@markerikson](https://togithub.com/markerikson) in [https://github.com/reduxjs/react-redux/pull/1817](https://togithub.com/reduxjs/react-redux/pull/1817) - Update to latest React 18 alpha dependencies by [@markerikson](https://togithub.com/markerikson) in [https://github.com/reduxjs/react-redux/pull/1834](https://togithub.com/reduxjs/react-redux/pull/1834) - Port remaining v7 typetests and improve v8 types by [@markerikson](https://togithub.com/markerikson) in [https://github.com/reduxjs/react-redux/pull/1855](https://togithub.com/reduxjs/react-redux/pull/1855) - Add initial SSR support for React 18 and React-Redux v8 by [@markerikson](https://togithub.com/markerikson) in [https://github.com/reduxjs/react-redux/pull/1835](https://togithub.com/reduxjs/react-redux/pull/1835) - test: Adjust type tests to be compatible with React 18 typings by [@eps1lon](https://togithub.com/eps1lon) in [https://github.com/reduxjs/react-redux/pull/1868](https://togithub.com/reduxjs/react-redux/pull/1868) - Switch back to Subscription in useSelector to fix unsubscribe perf by [@markerikson](https://togithub.com/markerikson) in [https://github.com/reduxjs/react-redux/pull/1870](https://togithub.com/reduxjs/react-redux/pull/1870) - Cleanup more code after `pure` removal by [@Andarist](https://togithub.com/Andarist) in [https://github.com/reduxjs/react-redux/pull/1859](https://togithub.com/reduxjs/react-redux/pull/1859) - Swap `useSyncExternalStore` shim behavior and update React deps by [@markerikson](https://togithub.com/markerikson) in [https://github.com/reduxjs/react-redux/pull/1884](https://togithub.com/reduxjs/react-redux/pull/1884) - Remove `DefaultRootState` type by [@markerikson](https://togithub.com/markerikson) in [https://github.com/reduxjs/react-redux/pull/1887](https://togithub.com/reduxjs/react-redux/pull/1887) - Add SSR test for `serverState` behavior by [@markerikson](https://togithub.com/markerikson) in [https://github.com/reduxjs/react-redux/pull/1888](https://togithub.com/reduxjs/react-redux/pull/1888) - Cleanup internal types in selectorFactory.ts by [@Methuselah96](https://togithub.com/Methuselah96) in [https://github.com/reduxjs/react-redux/pull/1889](https://togithub.com/reduxjs/react-redux/pull/1889) - Remove ts-ignore for initMergeProps by [@Methuselah96](https://togithub.com/Methuselah96) in [https://github.com/reduxjs/react-redux/pull/1891](https://togithub.com/reduxjs/react-redux/pull/1891) - fix(deps): add optional peer deps into `peerDependencies` by [@kyletsang](https://togithub.com/kyletsang) in [https://github.com/reduxjs/react-redux/pull/1893](https://togithub.com/reduxjs/react-redux/pull/1893) - Update peer deps for v8 by [@markerikson](https://togithub.com/markerikson) in [https://github.com/reduxjs/react-redux/pull/1895](https://togithub.com/reduxjs/react-redux/pull/1895) - Port DT fix for `dispatchProp` arg in `mergeProps` by [@markerikson](https://togithub.com/markerikson) in [https://github.com/reduxjs/react-redux/pull/1897](https://togithub.com/reduxjs/react-redux/pull/1897) - Update docs for v8 final by [@markerikson](https://togithub.com/markerikson) in [https://github.com/reduxjs/react-redux/pull/1902](https://togithub.com/reduxjs/react-redux/pull/1902) ### [`v7.2.9`](https://togithub.com/reduxjs/react-redux/releases/tag/v7.2.9) [Compare Source](https://togithub.com/reduxjs/react-redux/compare/v7.2.8...v7.2.9) This patch release updates the rarely-used `areStatesEqual` option for `connect` to now pass through `ownProps` for additional use in determining which pieces of state to compare if desired. The new signature is: ```ts { areStatesEqual?: ( nextState: State, prevState: State, nextOwnProps: TOwnProps, prevOwnProps: TOwnProps ) => boolean } ``` #### What's Changed - connect: pass ownProps to areStatesEqual by [@jspurlin](https://togithub.com/jspurlin) in [https://github.com/reduxjs/react-redux/pull/1952](https://togithub.com/reduxjs/react-redux/pull/1952) **Full Changelog**: https://github.com/reduxjs/react-redux/compare/v7.2.8...v7.2.9 ### [`v7.2.8`](https://togithub.com/reduxjs/react-redux/releases/tag/v7.2.8) [Compare Source](https://togithub.com/reduxjs/react-redux/compare/v7.2.7...v7.2.8) This release fixes a bug in the 7.x branch that caused `` to unsubscribe and stop updating completely when used inside of React 18's ``. The new "strict effects" behavior double-mounts components, and the subscription needed to be set up inside of a `useLayoutEffect` instead of a `useMemo`. This was previously fixed as part of v8 development, and we've backported it. **Note**: If you are now using React 18, **we strongly recommend using [the React-Redux v8 beta instead of v7.x!](https://togithub.com/reduxjs/react-redux/releases/tag/v8.0.0-beta.3)**. v8 has been rewritten internally to work correctly with React 18's Concurrent Rendering capabilities. React-Redux v7 will run and generally work okay with existing code, but may have rendering issues if you start using Concurrent Rendering capabilities in your code. Now that React 18 is out, we plan to finalize React-Redux v8 and release it live within the next couple weeks. Per [an update yesterday in the "v8 roadmap" thread](https://togithub.com/reduxjs/react-redux/issues/1740#issuecomment-1085190240), React-Redux v8 will be updated in the next couple days to ensure support for React 16.8+ as part of the next beta release. We would really appreciate final feedback on using React-Redux v8 beta with React 18 before we publish the final version. **Full Changelog**: https://github.com/reduxjs/react-redux/compare/v7.2.7...v7.2.8 ### [`v7.2.7`](https://togithub.com/reduxjs/react-redux/releases/tag/v7.2.7) [Compare Source](https://togithub.com/reduxjs/react-redux/compare/v7.2.6...v7.2.7) This release updates React-Redux v7's peer dependencies to accept React 18 as a valid version, *only* to avoid installation errors caused by NPM's "install all the peer deps and error if they don't match" behavior. **Note**: If you are now using React 18, **we strongly recommend using [the React-Redux v8 beta instead of v7.x!](https://togithub.com/reduxjs/react-redux/releases/tag/v8.0.0-beta.3)**. v8 has been rewritten internally to work correctly with React 18's Concurrent Rendering capabilities. React-Redux v7 will run and generally work okay with existing code, but may have rendering issues if you start using Concurrent Rendering capabilities in your code. Now that React 18 is out, we plan to finalize React-Redux v8 and release it live within the next couple weeks. We would really appreciate final feedback on using React-Redux v8 beta with React 18 before we publish the final version. ### [`v7.2.6`](https://togithub.com/reduxjs/react-redux/releases/tag/v7.2.6) [Compare Source](https://togithub.com/reduxjs/react-redux/compare/v7.2.5...v7.2.6) Just a quick fix for a Yarn install warning. Sorry about the noise! #### [Changes](https://togithub.com/reduxjs/react-redux/compare/v7.2.5...v7.2.6) - Remove `workspaces` from our package.json to silence a Yarn warning ([@timdorr](https://togithub.com/timdorr)) ### [`v7.2.5`](https://togithub.com/reduxjs/react-redux/releases/tag/v7.2.5) [Compare Source](https://togithub.com/reduxjs/react-redux/compare/v7.2.4...v7.2.5) This release shrinks the size of our internal `Subscription` class, and updates `useSelector` to avoid an unnecessary selector call on mount. #### Changes ##### Subscription Size Refactor Our internal `Subscription` implementation has been written as a class ever since it was added in v5. By rewriting it as a closure factory, we were able to shave a few bytes off the final bundle size. ##### `useSelector` Mount Optimization A user noticed that `useSelector` had never been given an early "bail out if the root state is the same" check to match how `connect` works. This resulted in a usually-unnecessary second call to the provided selector on mount. We've added that check. ##### Entry Point Consolidation We've consolidated the list of exported public APIs into a single file, and both the `index.js` and `alternate-renderers.js` entry points now re-export everything from that file. No meaningful change here, just shuffling lines of code around for consistency. #### Other Updates ##### React-Redux v8 and React 18 Development With [the announcement of React 18](https://togithub.com/reactwg/react-18/discussions/4), we've been working with the React team to plan our migration path to keep React-Redux fully compatible with React's upcoming features. We've already [migrated the React-Redux main development branch to TypeScript](https://togithub.com/reduxjs/react-redux/issues/1737), and are [prototyping compatibility implementation updates](https://togithub.com/reduxjs/react-redux/pull/1808). We'd appreciate any assistance from the community in testing out these changes so that we can ensure React-Redux works great for everyone when React 18 is ready! ##### Internal Tooling Updates Our `master` branch now uses Yarn v2 for package management, is built with TypeScript, and we've made CI updates to test against multiple TS versions. The `7.x` branch has also been updated to use Yarn v2 for consistency. These only affect contributors to the React-Redux package itself. #### Changelog - Port entry point consolidation from 8.x branch ([#1811](https://togithub.com/reduxjs/react-redux/issues/1811) - [@markerikson](https://togithub.com/markerikson)) - Update v7 branch to use Yarn v2 and improve CI process ([#1810](https://togithub.com/reduxjs/react-redux/issues/1810) - [@markerikson](https://togithub.com/markerikson)) - Reduce unnecessary calls to useSelector selector ([#1803](https://togithub.com/reduxjs/react-redux/issues/1803) - [@sufian-slack](https://togithub.com/sufian-slack) ) - Port Subscription closure implementation from 8.x to 7.x ([#1809](https://togithub.com/reduxjs/react-redux/issues/1809) - [@mbelsky](https://togithub.com/mbelsky)) ### [`v7.2.4`](https://togithub.com/reduxjs/react-redux/releases/tag/v7.2.4) [Compare Source](https://togithub.com/reduxjs/react-redux/compare/v7.2.3...v7.2.4) This release drops our dependency on the core `redux` package by inlining `bindActionCreators`, and tweaks `useSelector` to ensure that selectors aren't run an extra time while re-rendering. #### Changelog ##### Redux Dependency Removal React-Redux has always imported the `bindActionCreators` utility from the core `redux` package for use in `connect`. However, that meant that we had to have a peer dependency on `redux`, and this was the *only* reason we actually required that `redux` be installed. This became more annoying with the arrival of Redux Toolkit, which has its own dependency on `redux` internally, and thus users typically saw peer dependency warnings saying that "`redux` isn't listed as a dependency in your app". Code reuse across separate packages is a great thing, but sometimes the right thing to do is duplicate code. So, we've inlined `bindActionCreators` directly into React-Redux, and we've completely dropped the dependency on Redux. This means that React-Redux will no longer produce a peerDep warning when used with Redux Toolkit, and `` and `connect` really only need a Redux-store-compatible value to work right. ##### `useSelector` Fixes Users reported that `useSelector` was re-running selector functions again unnecessarily while rendering after a dispatch. We've tweaked the logic to ensure that doesn't happen. `useSelector` also now has checks in development to ensure that `selector` and `equalityFn` are functions. #### Changes - Remove wrapActionCreators ([#1709](https://togithub.com/reduxjs/react-redux/issues/1709) - [@xty](https://togithub.com/xty)) - Verify that selector and equalityF of useSelector are functions ([#1706](https://togithub.com/reduxjs/react-redux/issues/1706) - [@gshilin](https://togithub.com/gshilin)) - Import bindActionCreators from redux ([#1705](https://togithub.com/reduxjs/react-redux/issues/1705) - [@timdorr](https://togithub.com/timdorr)) - Don't re-run the selector after update ([#1701](https://togithub.com/reduxjs/react-redux/issues/1701) - [@timdorr](https://togithub.com/timdorr))

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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.

Thierry-Chain / Library-Management-App

Update dependency react-redux to v8 #71

Release Notes

Configuration

Renovate Ignore Notification