reduxjs/react-redux
### [`v7.0.3`](https://togithub.com/reduxjs/react-redux/releases/v7.0.3)
[Compare Source](https://togithub.com/reduxjs/react-redux/compare/v7.0.2...v7.0.3)
This release includes a bugfix for a timing issue in `connect()`, and also lowers our React peer dependency slightly to allow better usage with React Native 0.59.
#### [Changes](https://togithub.com/reduxjs/react-redux/compare/v7.0.2...v7.0.3)
- fix timing issue in component updates due to consecutive dispatches ([#1263](https://togithub.com/reduxjs/react-redux/issues/1263) by [@MrWolfZ](https://togithub.com/MrWolfZ))
- Lower react peer dependency to ^16.8.3 ([#1242](https://togithub.com/reduxjs/react-redux/issues/1242) by [@jeremy-deutsch](https://togithub.com/jeremy-deutsch))
### [`v7.0.2`](https://togithub.com/reduxjs/react-redux/releases/v7.0.2)
[Compare Source](https://togithub.com/reduxjs/react-redux/compare/v7.0.1...v7.0.2)
This is a bug fix release with a small performance improvement and fix for nested component unmounting.
#### [Changes](https://togithub.com/reduxjs/react-redux/compare/v7.0.1...v7.0.2)
- Memoize renderedWrappedComponent separately ([#1234](https://togithub.com/reduxjs/react-redux/issues/1234) by [@vzaidman](https://togithub.com/vzaidman))
- Fix timing issue with setting up store subscription inside a connected component ([#1235](https://togithub.com/reduxjs/react-redux/issues/1235) by [@MrWolfZ](https://togithub.com/MrWolfZ))
### [`v7.0.1`](https://togithub.com/reduxjs/react-redux/releases/v7.0.1)
[Compare Source](https://togithub.com/reduxjs/react-redux/compare/v7.0.0...v7.0.1)
React-Redux version 7 resolves the performance issues that were reported with version 6, and lays the groundwork for us to design and ship a public `useRedux()`-type Hooks API in a later 7.x release.
The major change for this release is that `connect` is now implemented using Hooks internally. Because of this, we now require a minimum React version of 16.8.4 or higher.
This release has undergone extensive performance benchmarking, and we're confident that it's the fastest version of React-Redux yet! We've also expanded our test suite to cover a number of additional use cases and scenarios.
npm install react-redux@latest
For discussion on the reasons for the major version change and the development process, see:
[issue #1177 - React-Redux Roadmap: v6, Context, Subscriptions, and Hooks](https://togithub.com/reduxjs/react-redux/issues/1177).
For discussion on the possible design of a future public hooks API, see:
[issue #1179: Discussion: Potential hooks API design](https://togithub.com/reduxjs/react-redux/issues/1179)
#### Changes
This release should be public-API-compatible with version 6. The only public breaking change is the update of our React peer dependency from 16.4 to 16.8.4.
> **Note**: `connect` now uses [`React.memo()`](https://reactjs.org/blog/2018/10/23/react-v-16-6.html) internally, which returns a special object rather than a function. Any code that assumed React components are only functions is wrong, and has been wrong since the release of React 16.6. If you were using PropTypes to check for valid component types, you should change from `PropTypes.func` to `PropTypes.elementType` instead.
>
> ##### Internal Changes
>
> ##### Direct Component Subscriptions
In v6, we switched from individual components subscribing to the store, to having `` subscribe and components read the store state from React's Context API. This worked, but unfortunately the Context API isn't as optimized for frequent updates as we'd hoped, and our usage patterns led to some folks reporting performance issues in some scenarios.
In v7, we've switched back to using direct subscriptions internally, which should improve performance considerably.
(This does result in some changes that are visible to user-facing code, in that updates dispatched in React lifecycle methods are immediately reflected in later component updates. Examples of this include components dispatching while mounting in an SSR environment. This was the behavior through v5, and is not considered part of our public API.)
##### Batched Updates
React has an `unstable_batchedUpdates` API that it uses to group together multiple updates from the same event loop tick. The React team encouraged us to use this, and we've updated our internal Redux subscription handling to leverage this API. This should also help improve performance, by cutting down on the number of distinct renders caused by a Redux store update.
##### `connect` Rewritten with Hooks
We've reimplemented our `connect` wrapper component to use hooks internally. While it may not be visible to you, it's nice to know we can take advantage of the latest React goodies!
##### Public API Changes
##### Return of `store` as a Prop
We've brought back the ability to pass a store as a prop directly to connected components. This was removed in version 6 due to internal implementation changes (components no longer subscribed to the store directly). Some users expressed concerns that working with context in unit tests was not sufficient. Since our components use direct subscriptions again, we've reimplemented this option, and that should resolve those concerns.
##### New `batch` API for Batched React Updates
React's `unstable_batchedUpdate()` API allows any React updates in an event loop tick to be batched together into a single render pass. React already uses this internally for its own event handler callbacks. This API is actually part of the renderer packages like ReactDOM and React Native, not the React core itself.
Since React-Redux needs to work in both ReactDOM and React Native environments, we've taken care of importing this API from the correct renderer at build time for our own use. We also now re-export this function publicly ourselves, renamed to `batch()`. You can use it to ensure that multiple actions dispatched outside of React only result in a single render update, like this:
```js
import { batch } from "react-redux";
function myThunk() {
return (dispatch, getState) => {
// should only result in one combined re-render, not two
batch(() => {
dispatch(increment());
dispatch(increment());
})
}
}
```
If you are using an alternative React renderer, like the [Ink CLI renderer](https://togithub.com/vadimdemedes/ink), that method isn't available for us to import. In that case, you will need to change your code to import from the new `react-redux/es/alternate-renderers` entry point instead. (Use `react-redux/lib/alternate-renderers` for the CJS version). That entry point exports a no-op version of `batch()` that just executes the callback immediately, and does not provide React batching.
In that situation, you may want to consider aliasing `react-redux` to one of those alternate entry points in your build tool for the best compatibility, especially if you're using any other libraries that depend on React-Redux.
> Note: v7.0.1 is identical code-wise to v7.0.0 . The extra patch release was to update the React requirement listed in the README.
>
> #### Contributors
Thanks to:
- [@markerikson](https://togithub.com/markerikson) for the writeup in [#1177](https://togithub.com/reduxjs/react-redux/issues/1177) and the primary implementation work on version 7
- [@ephem](https://togithub.com/ephem), [@saboya](https://togithub.com/saboya), [@maxkostow](https://togithub.com/maxkostow), [@mrwolfz](https://togithub.com/mrwolfz) for contributing unit tests and critiques
- [@andarist](https://togithub.com/andarist) for some perf tweaks
- [@migueloller](https://togithub.com/migueloller), [@alexreardon](https://togithub.com/alexreardon), [@luskin](https://togithub.com/luskin), [@navneet-g](https://togithub.com/navneet-g), and [@josepot](https://togithub.com/josepot) for diagnosing edge cases, working with us to debug them, and coming up with fixes
- [@wgao19](https://togithub.com/wgao19) for adding API versioning to the docs site
- everyone else who helped give feedback in the issues and beta testing
### [`v7.0.0`](https://togithub.com/reduxjs/react-redux/releases/v7.0.0)
[Compare Source](https://togithub.com/reduxjs/react-redux/compare/v6.0.1...v7.0.0)
Initial release, but we missed some updated docs. Ignore this 😄
### [`v6.0.1`](https://togithub.com/reduxjs/react-redux/releases/v6.0.1)
[Compare Source](https://togithub.com/reduxjs/react-redux/compare/v6.0.0...v6.0.1)
This is a minor release with support for react-hot-loader and a few small bug fixes for edge cases.
While you're here, please stop by [#1177](https://togithub.com/reduxjs/react-redux/issues/1177) to see our roadmap for the next versions of React Redux. We are aware that performance is not so hot in 6.0. Short version: We put too much traffic on React's context API, which isn't really designed for high levels of reads and writes. We're looking to reduce that load and get performance back on track in a minor release, so there won't be backwards compatibility concerns. We have [a new extensive benchmark suite](https://togithub.com/reduxjs/react-redux-benchmarks) to keep us on track and ensure we're not regressing on speed in the future.
And yes, we know about Hooks. Check out [#1179](https://togithub.com/reduxjs/react-redux/issues/1179).
#### [Changes](https://togithub.com/reduxjs/react-redux/compare/v6.0.0...v6.0.1)
- Fix for circular component object structures, such as Emotion styled components. ([#1122](https://togithub.com/reduxjs/react-redux/issues/1122) by [@Andarist](https://togithub.com/Andarist))
- Minor optimization: remove conditional ([#1131](https://togithub.com/reduxjs/react-redux/issues/1131) by [@ericanderson](https://togithub.com/ericanderson))
- Ensure that component `context` prop really contains a React context ([#1134](https://togithub.com/reduxjs/react-redux/issues/1134) by [@casdevs](https://togithub.com/casdevs))
- react-hot-loader compatibility ([#1168](https://togithub.com/reduxjs/react-redux/issues/1168)/[#1137](https://togithub.com/reduxjs/react-redux/issues/1137) by [@theKashey](https://togithub.com/theKashey))
- Upgrade to react-is v16.7.0 ([#1174](https://togithub.com/reduxjs/react-redux/issues/1174) by [@nobezawa](https://togithub.com/nobezawa))
Renovate configuration
:date: Schedule: At any time (no schedule defined).
:vertical_traffic_light: Automerge: Disabled by config. Please merge this manually once you are satisfied.
:recycle: Rebasing: Whenever PR becomes conflicted, or if you modify the PR title to begin with "rebase!".
:no_bell: Ignore: Close this PR and you won't be reminded about these updates again.
[ ] If you want to rebase/retry this PR, check this box
This PR has been generated by Renovate Bot. View repository job log here.
This PR contains the following updates:
7.0.1->7.0.96.0.0->7.0.3Release Notes
reduxjs/react-redux
### [`v7.0.3`](https://togithub.com/reduxjs/react-redux/releases/v7.0.3) [Compare Source](https://togithub.com/reduxjs/react-redux/compare/v7.0.2...v7.0.3) This release includes a bugfix for a timing issue in `connect()`, and also lowers our React peer dependency slightly to allow better usage with React Native 0.59. #### [Changes](https://togithub.com/reduxjs/react-redux/compare/v7.0.2...v7.0.3) - fix timing issue in component updates due to consecutive dispatches ([#1263](https://togithub.com/reduxjs/react-redux/issues/1263) by [@MrWolfZ](https://togithub.com/MrWolfZ)) - Lower react peer dependency to ^16.8.3 ([#1242](https://togithub.com/reduxjs/react-redux/issues/1242) by [@jeremy-deutsch](https://togithub.com/jeremy-deutsch)) ### [`v7.0.2`](https://togithub.com/reduxjs/react-redux/releases/v7.0.2) [Compare Source](https://togithub.com/reduxjs/react-redux/compare/v7.0.1...v7.0.2) This is a bug fix release with a small performance improvement and fix for nested component unmounting. #### [Changes](https://togithub.com/reduxjs/react-redux/compare/v7.0.1...v7.0.2) - Memoize renderedWrappedComponent separately ([#1234](https://togithub.com/reduxjs/react-redux/issues/1234) by [@vzaidman](https://togithub.com/vzaidman)) - Fix timing issue with setting up store subscription inside a connected component ([#1235](https://togithub.com/reduxjs/react-redux/issues/1235) by [@MrWolfZ](https://togithub.com/MrWolfZ)) ### [`v7.0.1`](https://togithub.com/reduxjs/react-redux/releases/v7.0.1) [Compare Source](https://togithub.com/reduxjs/react-redux/compare/v7.0.0...v7.0.1) React-Redux version 7 resolves the performance issues that were reported with version 6, and lays the groundwork for us to design and ship a public `useRedux()`-type Hooks API in a later 7.x release. The major change for this release is that `connect` is now implemented using Hooks internally. Because of this, we now require a minimum React version of 16.8.4 or higher. This release has undergone extensive performance benchmarking, and we're confident that it's the fastest version of React-Redux yet! We've also expanded our test suite to cover a number of additional use cases and scenarios. npm install react-redux@latest For discussion on the reasons for the major version change and the development process, see: [issue #1177 - React-Redux Roadmap: v6, Context, Subscriptions, and Hooks](https://togithub.com/reduxjs/react-redux/issues/1177). For discussion on the possible design of a future public hooks API, see: [issue #1179: Discussion: Potential hooks API design](https://togithub.com/reduxjs/react-redux/issues/1179) #### Changes This release should be public-API-compatible with version 6. The only public breaking change is the update of our React peer dependency from 16.4 to 16.8.4. > **Note**: `connect` now uses [`React.memo()`](https://reactjs.org/blog/2018/10/23/react-v-16-6.html) internally, which returns a special object rather than a function. Any code that assumed React components are only functions is wrong, and has been wrong since the release of React 16.6. If you were using PropTypes to check for valid component types, you should change from `PropTypes.func` to `PropTypes.elementType` instead. > > ##### Internal Changes > > ##### Direct Component Subscriptions In v6, we switched from individual components subscribing to the store, to having `Renovate configuration
:date: Schedule: At any time (no schedule defined).
:vertical_traffic_light: Automerge: Disabled by config. Please merge this manually once you are satisfied.
:recycle: Rebasing: Whenever PR becomes conflicted, or if you modify the PR title to begin with "
rebase!".:no_bell: Ignore: Close this PR and you won't be reminded about these updates again.
This PR has been generated by Renovate Bot. View repository job log here.