[Snyk] Upgrade react-redux from 7.0.1 to 7.1.3 #18

snyk-bot · 2020-02-05T02:25:47Z

Snyk has created this PR to upgrade react-redux from 7.0.1 to 7.1.3.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 14 versions ahead of your current version.
The recommended version was released 3 months ago, on 2019-11-06.

Release notes

Package name: react-redux

7.1.3 - 2019-11-06
Forgot to remove a console statement before I published 7.1.2. Oops!

Lint your source code before publishing, folks.

Changes
- Remove leftover console statement (@markerikson - 30101bb)
7.1.2 - 2019-11-06
This releases fixes a subtle timing bug with connect and useSelector in React Native environments, and adds the ability to pass through non-Redux-store values as a store prop.

Fixed Store Subscriptions in React Native

Our current implementation requires cascading updates down through connected components. This is primarily done during React's "commit phase" via the useLayoutEffect hook. Unfortunately, React warns when useLayoutEffect is called in SSR environments, so we try to feature-detect that and fall back to useEffect just to avoid that warning.

Unfortunately, a tweak to the feature detection conditions during the pre-7.1.0 work caused the check to accidentally fail in React Native environments. This meant that useEffect was actually being used all the time, and this led to occasional timing bugs such as #1313 and #1437 . This affected the previous v7.1.x releases.

We've fixed that issue, and added additional test cases to ensure that our code works correctly under React Native.

See #1444 for more details on the feature detection and the fix.

Passing Through Non-Store Values

connect has always accepted passing a Redux store directly to connected components as a prop named store (with the exception of v6). As a result, the store prop has effectively been treated as a "reserved" prop, in much the same way that key and ref are "reserved" prop names handled by React.

Some users may be using the word "store" to describe their domain data, and have asked to allow variables that aren't a Redux store through the store prop to the component (#1393). We've finally been able to implement that capability.

Changes
- Pass non-Redux-store values through the store prop (@markerikson - #1447)
- Fix RN batching and effect behavior (@markerikson - #1444)
- Remove unused latestStoreState field (@Hypnosphi - #1426)
- Mark the react renderers as optional peer deps. (@timdorr - 388d9e4)
- Use the same condition for checking if SSR in useSelector.js as in connectAdvanced.js (@LeoDanielsson - #1419)
7.1.2-alpha.0 - 2019-11-05
7.1.2-alpha.0
7.1.1 - 2019-08-26
This release is sponsored by Deft, providing technical teams to high-growth SaaS companies with the processes they need to scale successfully. Please reach out to see how we can help with your software development, systems architecture, and infrastructure design needs.

This release includes some new APIs for those that want to use a custom React Context with our Hooks API, a small memory optimization, and has a fix for when the store changes on a Provider with incompatible children.

Changes
- Add create*Hook factory APIs (#1309 by @ryaninvents)
- Free resources (free detached nodes from memory) (#1380 by @MosheZemah)
- Convert Provider into function component with hooks (#1377 by @mpeyper)
P.S. On the sponsorship section above, it's a thing we're trying out to see how it feels and if it causes any problems for your workflows. (Don't worry, no ads are coming to your npm installs!) The idea for future releases is to let those that contributed to that release have the opportunity to sponsor that release. We don't need donations, but we definitely do need PRs! Hopefully, it's a fair way to encourage them. Please let us know if it's a problem in any way.
7.1.0 - 2019-06-11
Hooks!

After much discussion, we've decided these Hook things are probably going to stick around, so we might as well add some. Many thanks to @MrWolfZ, @josepot, @perrin4869, and @mpeyper for their contributions and to everyone else that offered feedback, ideas, and critiques as we built them out. Go open source!

Changes
- Add React Hooks (#1248 by @MrWolfZ)
- Add deps argument to useSelector (#1251 by @MrWolfZ)
- Use react-hooks-testing-library to test hooks (#1259 by @mpeyper)
- Remove useRedux (@markerikson)
- Remove useActions (@markerikson)
- Remove deps argument (#1272 by @josepot)
- Replace shallowEqual with reference equality in useSelector (#1288 by @perrin4869)
- Avoid unnecessary selector evaluations (#1273 by @josepot)
- Minor Hook testing improvements (#1294 by @MrWolfZ)
7.1.0-rc.1 - 2019-05-30
⚠️We've got RC sign! ⚠️

This version is essentially the same as the previous 7.1.0-alpha.5 release. But it has an rc tag on it, so you can more easily justify the upgrade to your manager.

Get to it!
```
npm install react-redux@next
```
7.1.0-alpha.5 - 2019-05-20
We're still making changes to our hooks APIs, but I'm hopeful that we're getting close to having the behavior nailed down.

This release makes three specific changes to useSelector:
- The deps array has been removed. If you want to ensure the same selector function reference is used, you should memoize it yourself.
- The default equality check used to determine if a re-render is needed is now a strict === check, instead of a shallow equality check.
- useSelector now accepts a comparison function as an optional second argument, similar to how React.memo() works conceptually. You may pass your own comparison function to customize how useSelector determines if a re-render is necessary.
In addition, we now export our internal shallowEqual utility function. If you want to return to the prior equality behavior, you may pass that as the equality comparison function:
```
import { shallowEqual, useSelector } from "react-redux"
// later

const selectedData = useSelector(mySelector, shallowEqual)
```
The optional comparison function also enables using something like Lodash's _.isEqual() or Immutable.js's comparison capabilities.

Changes
- Remove deps of useSelector (#1272 by @josepot)
- Replace shallow equality with reference equality in useSelector (#1288 by @perrin4869 , @josepot)
- Avoid unnecessary selector evaluations (#1273 by @josepot)
7.1.0-alpha.4 - 2019-05-01
Our previous alpha versions included both useSelector() (similar to mapState) and useActions() (similar to mapDispatch).

However, Dan Abramov strongly suggested that we consider removing useActions(), as the idea of "binding action creators" is less relevant when using hooks, and also adds conceptual overhead and syntactic complexity. We requested feedback from alpha users, and the initial feedback agreed with Dan's suggestion.

Based on that feedback, v7.1.0-alpha.4 removes the useActions() hook. Instead, call useDispatch() in your component, and manually call dispatch(someActionCreator()) in callbacks and effects as needed.

If you still wish to use useActions(), the hooks alpha docs page has an implementation you can copy and paste into your own code.

Changes
- Remove useActions ( 54fd9dd )
7.1.0-alpha.3 - 2019-04-28
After discussion in the hooks alpha feedback issue, we've decided to remove the useRedux() hook, as it doesn't really bring any benefits. If you were using it in your own code, replace the useRedux() call with separate calls to useSelector() and useActions().

This release also includes the timing bugfix from #1263.

Also, while you won't notice it, @mpeyper was able to simplify our hooks unit tests using react-hooks-testing-library.

Changes
- Remove useRedux hook 8c0750c
- fix timing issue in component updates due to consecutive dispatches (#1263 by @MrWolfZ)
- Use react-hooks-testing-library to test hooks (#1259 by @mpeyper)
7.1.0-alpha.2 - 2019-04-28
7.1.0-alpha.1 - 2019-04-22
7.1.0-alpha.0 - 2019-04-22
7.0.3 - 2019-04-28
7.0.2 - 2019-04-12
7.0.1 - 2019-04-09

from react-redux GitHub release notes

Commit messages

Package name: react-redux

82b39ef 7.1.3
30101bb Remove leftover console statement
5f495b2 7.1.2
2677705 Pass non-Redux-store values through the `store` prop (#1447)
b832f83 Fix RN batching and effect behavior (#1444)
b5034a6 Bump mixin-deep from 1.3.1 to 1.3.2 in /website (#1442)
4be8b3f [ImgBot] Optimize images (#1434)
2eac861 fix spelling in error message (#1427)
6725400 Remove unused `latestStoreState` field (#1426)
388d9e4 Mark the react renderers as optional peer deps.
2297944 Add DEV Community link to Community Resources (#1423)
69d62e4 Use the same condition for checking if SSR in useSelector.js as in connectAdvanced.js (#1419)
31c998a Docs: Fixes code example for API connect mapState (#1415)
4bc231f Revert "Docs: Fix Code Example for API `connect()`" (#1414)
d9c49fa Docs: Fixes code example for API connect (#1413)
063c2ed Troubleshooting: add useLayoutEffect + Jest info (#1411)
6c873c7 Add reference post in hooks description (#1395)
5b268f3 Clarify two way dispatch binding in more detail (#1387)
e228b32 add a line to insist on the pure nature (#1386)
65d7935 7.1.1
66c3833 Upgrade stuff as far as we can get without errors.
07dbe01 Fix a eslint@6 error
0c5f764 Convert Provider into function component with hooks (#1377)
b6b4799 Free resources (free detached nodes from memory) (#1380)