Bump react-redux from 6.0.1 to 7.2.0

[dependabot-preview]

Bumps react-redux from 6.0.1 to 7.2.0.

Release notes

Sourced from react-redux's releases.

v7.2.0

This release fixes two bugs, an algorithmic problem with unsubscribing components and a memory leak with connect. It also has optimizations for production bundle size, and adds a couple small improvements to developer readability while debugging.

Changes

Bug Fixes

connect in v7 is implemented using hooks, and the hooks usage captures numerous values from the surrounding scope. We received a PR informing us that the way we were capturing these values would likely result in a copy of the first version of its props being kept alive indefinitely.

This memory leak has been fixed by extracting a custom hook that receives all the necessary values as arguments, so that they're not captured via closure.

We also received a PR letting us know that the unsubscribe logic had a quadratic algorithm in it, as removing a subscriber would use an indexOf(listener) check to remove that callback. If there were a large number of subscribers, that line's runtime would increase rapidly, causing slowdowns.

This algorithm has been replaced with tracking subscribers via a linked list, which drastically improves the runtime of this section of the code even with large numbers of subscribers.

Thanks to @larrylin28 and @wurstbonbon for finding these bugs and submitting PRs to fix them!

Bundle Size Improvements

We've made a number of small tweaks to the codebase to improve the ability of bundlers to shake and minimize the final included size in a bundle. The net result is that react-redux@7.2.0 is smaller than 7.1.3, dropping 1.3K min and 0.6K min+gzip. (In fact, it's even smaller than the pre-hooks 7.0.0 when gzipped!)

Thanks to @Andarist for doing most of the work on this!

Debugging Improvements

The ReactReduxContext instance now has a displayName set, so it should show up in the React DevTools as ReactRedux.Provider.

Also, when an error is caught in useSelector and re-thrown, we now append the original stack trace.

Thanks to @pieplu and @r3dm1ke for these!

Changelog

• Fix memory leak issue with UseEffect (@larrylin28 - #1506)
• Optimize createListenerCollection (@wurstbonbon - #1523)
• Rethrowing original errors thrown in selector functions (@Andarist - #1474)
• Remove invariant in favor of doing NODE_ENV checks directly (@Andarist - #1472)
• Wrap .propTypes and .displayName assignments with DEV check (@Andarist - #1471)
• Add pure annotations to help with DCE (@timdorr - 5e0c50d)
• Inline this function. (@timdorr - 58ae5ed)
• Add a displayName on ReactReduxContext (@pieplu - #1462)

reduxjs/react-redux@v7.1.3...v7.2.0

v7.1.3

Forgot to remove a console statement before I published 7.1.2. Oops!

Lint your source code before publishing, folks.

Changes

... (truncated)

Commits

• ec38c1b 7.2.0
• fa5a7fd Fix memory leak issue with UseEffect (#1506)
• e649fb6 Optimize createListenerCollection (#1523)
• 3eb5271 Updated links (#1522)
• b3db96c docs: mapDispatchToProps returning undefined (#1520)
• 607f1ba Fix: Fix typo in connect.md (#1517)
• 77a2044 Remove these spaces.
• cff554d Update connect-dispatching-actions-with-mapDispatchToProps.md (#1501)
• 9a10b15 Update hooks.md (#1405)
• 7893b35 Fixed Q&A links (#1500)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by acemarke, a new releaser for react-redux since your current version.

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 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)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)

[ghost]

Congratulations 🍻. DeepCode analyzed your code in 0.119 seconds and we found no issues. Enjoy a moment of no bugs ☀️.

💬 This comment has been generated by the DeepCode bot, installed by the owner of the repository. The DeepCode bot protects your repository by detecting and commenting on security vulnerabilities or other critical issues.

---

☺️ If you want to provide feedback on our bot, here is how to contact us.