New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update dependency react-redux to v7 - autoclosed #102
Closed
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
renovate
bot
force-pushed
the
renovate/react-redux-7.x
branch
4 times, most recently
from
April 6, 2020 13:24
a1f7ec9
to
e9807a8
Compare
|
renovate
bot
force-pushed
the
renovate/react-redux-7.x
branch
6 times, most recently
from
April 11, 2020 06:09
f67f584
to
29d361e
Compare
renovate
bot
force-pushed
the
renovate/react-redux-7.x
branch
4 times, most recently
from
April 20, 2020 19:20
6384be6
to
7f582af
Compare
renovate
bot
force-pushed
the
renovate/react-redux-7.x
branch
4 times, most recently
from
April 25, 2020 09:04
0d17d65
to
5fb6628
Compare
renovate
bot
force-pushed
the
renovate/react-redux-7.x
branch
3 times, most recently
from
May 2, 2020 06:05
299cce7
to
1480be6
Compare
renovate
bot
force-pushed
the
renovate/react-redux-7.x
branch
3 times, most recently
from
May 16, 2020 10:06
dfffc9a
to
7018506
Compare
renovate
bot
force-pushed
the
renovate/react-redux-7.x
branch
3 times, most recently
from
May 23, 2020 11:07
3374598
to
9baf349
Compare
renovate
bot
force-pushed
the
renovate/react-redux-7.x
branch
from
January 16, 2021 07:38
f0c541d
to
618c928
Compare
renovate
bot
force-pushed
the
renovate/react-redux-7.x
branch
3 times, most recently
from
February 6, 2021 07:48
967a0ad
to
1a7894a
Compare
renovate
bot
force-pushed
the
renovate/react-redux-7.x
branch
2 times, most recently
from
February 20, 2021 07:37
74e2317
to
3f60f49
Compare
renovate
bot
force-pushed
the
renovate/react-redux-7.x
branch
from
February 20, 2021 09:02
3f60f49
to
a0322ff
Compare
renovate
bot
force-pushed
the
renovate/react-redux-7.x
branch
2 times, most recently
from
February 27, 2021 11:23
2b38186
to
9213e5d
Compare
renovate
bot
force-pushed
the
renovate/react-redux-7.x
branch
4 times, most recently
from
March 16, 2021 13:52
bec0ae7
to
88903a8
Compare
renovate
bot
force-pushed
the
renovate/react-redux-7.x
branch
5 times, most recently
from
March 27, 2021 06:03
2806334
to
2a3cb5d
Compare
renovate
bot
force-pushed
the
renovate/react-redux-7.x
branch
3 times, most recently
from
April 3, 2021 07:41
f883e50
to
3ee620a
Compare
renovate
bot
force-pushed
the
renovate/react-redux-7.x
branch
from
April 24, 2021 21:41
3ee620a
to
1bd4ff8
Compare
renovate
bot
force-pushed
the
renovate/react-redux-7.x
branch
from
October 18, 2021 21:06
1bd4ff8
to
2072474
Compare
renovate
bot
force-pushed
the
renovate/react-redux-7.x
branch
from
November 23, 2021 14:49
2072474
to
4ea05fd
Compare
renovate
bot
force-pushed
the
renovate/react-redux-7.x
branch
from
January 12, 2022 14:45
4ea05fd
to
125f7c3
Compare
renovate
bot
force-pushed
the
renovate/react-redux-7.x
branch
from
April 11, 2022 19:27
125f7c3
to
769d4d1
Compare
renovate
bot
changed the title
Update dependency react-redux to v7
Update dependency react-redux to v7 - autoclosed
Apr 24, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
6.0.1
->7.2.8
Release Notes
reduxjs/react-redux
v7.2.8
Compare Source
This release fixes a bug in the 7.x branch that caused
<Provider>
to unsubscribe and stop updating completely when used inside of React 18's<StrictMode>
. The new "strict effects" behavior double-mounts components, and the subscription needed to be set up inside of auseLayoutEffect
instead of auseMemo
. 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!. 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, 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: reduxjs/react-redux@v7.2.7...v7.2.8
v7.2.7
Compare Source
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!. 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
Compare Source
Just a quick fix for a Yarn install warning. Sorry about the noise!
Changes
workspaces
from our package.json to silence a Yarn warning (@timdorr)v7.2.5
Compare Source
This release shrinks the size of our internal
Subscription
class, and updatesuseSelector
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 OptimizationA user noticed that
useSelector
had never been given an early "bail out if the root state is the same" check to match howconnect
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
andalternate-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, 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, and are prototyping compatibility implementation updates. 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
v7.2.4
Compare Source
This release drops our dependency on the core
redux
package by inliningbindActionCreators
, and tweaksuseSelector
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 coreredux
package for use inconnect
. However, that meant that we had to have a peer dependency onredux
, and this was the only reason we actually required thatredux
be installed. This became more annoying with the arrival of Redux Toolkit, which has its own dependency onredux
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<Provider>
andconnect
really only need a Redux-store-compatible value to work right.useSelector
FixesUsers 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 thatselector
andequalityFn
are functions.Changes
v7.2.3
Compare Source
This release improves behavior in
useSelector
by returning the existing reference if the newly returned selector result passes the equality check, and adds a hard dependency on the@types/react-redux
package to ensure TS users always have the typedefs installed.Changes
useSelector
Results ReuseIssue #1654 reported that
useSelector
was returning new references from a selector even if the equality comparison function returnedtrue
. This is because the equality check was only ever being performed during the action dispatch process.We now run the equality comparison against the value calculated by the selector while rendering, and return the existing reference for consistency if the old and new values are considered equal. This should improve some cases where further derived values where being recalculated unnecessarily.
TS Types Now Included
React-Redux has always been written in plain JS, and the typedefs maintained by the community in DefinitelyTyped. We plan on eventually rewriting the library in TypeScript in a future React-Redux v8 release, but until then the types can stay in DT.
However, having to always manually install
@types/react-redux
is annoying, and some users have gotten confused by that. This release adds a hard dependency on@types/react-redux
, so that if you installreact-redux
, you automatically get the types as well. This should simplify the process for TS users.Docs Updates
We've made several docs updates recently:
We are currently working on a new React-Redux tutorial that will teach the React-Redux hooks as the primary approach, based on the "UI and React" page in the Redux docs "Fundamentals" tutorial.
Changelog
v7.2.2
Compare Source
This release allows you to use React Redux with React 17 without a warning when installing. That's about it.
Changes
v7.2.1
Compare Source
This release improves
useSelector
value display in the React DevTools, fixes a potential race condition, and fixes a couple additional minor issues.useSelector
DevTools DisplayThe React DevTools normally show custom hooks with their inspected name (such as "Selector" for
useSelector
), and any calls to core hooks inside. This is not always informative, so React has theuseDebugValue
hook to allow custom hooks to specify what value should be shown instead.useSelector
now callsuseDebugValue
to specifically show the current selected value instead of its internal hooks usage.Bug Fixes
This release has a few different bug fixes:
reactReduxForwardedRef
to avoid a rare situation where someone else might be passing down a field namedforwardedRef
useSelector
error messageChanges
v7.2.0
Compare Source
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.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 adisplayName
set, so it should show up in the React DevTools asReactRedux.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!
Changes
UseEffect
(@larrylin28 - #1506)5e0c50d
)58ae5ed
)v7.1.3
Compare Source
Forgot to remove a
console
statement before I published 7.1.2. Oops!Lint your source code before publishing, folks.
Changes
30101bb
)v7.1.2
Compare Source
This releases fixes a subtle timing bug with
connect
anduseSelector
in React Native environments, and adds the ability to pass through non-Redux-store values as astore
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 whenuseLayoutEffect
is called in SSR environments, so we try to feature-detect that and fall back touseEffect
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 namedstore
(with the exception of v6). As a result, thestore
prop has effectively been treated as a "reserved" prop, in much the same way thatkey
andref
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
store
prop (@markerikson - #1447)latestStoreState
field (@Hypnosphi - #1426)388d9e4
)v7.1.1
Compare Source
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 aProvider
with incompatiblechildren
.Changes
create*Hook
factory APIs (#1309 by @ryaninvents)v7.1.0
Compare Source
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
deps
argument touseSelector
(#1251 by @MrWolfZ)useRedux
(@markerikson)useActions
(@markerikson)deps
argument (#1272 by @josepot)shallowEqual
with reference equality inuseSelector
(#1288 by @perrin4869)v7.0.3
Compare Source
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
v7.0.2
Compare Source
This is a bug fix release with a small performance improvement and fix for nested component unmounting.
Changes
v7.0.1
Compare Source
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.
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.
For discussion on the possible design of a future public hooks API, see:
issue #1179: Discussion: Potential hooks API design
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.
Internal Changes
Direct Component Subscriptions
In v6, we switched from individual components subscribing to the store, to having
<Provider>
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 HooksWe'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 PropWe'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 UpdatesReact'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:If you are using an alternative React renderer, like the Ink CLI renderer, 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. (Usereact-redux/lib/alternate-renderers
for the CJS version). That entry point exports a no-op version ofbatch()
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.Contributors
Thanks to:
v7.0.0
Compare Source
Initial release, but we missed some updated docs. Ignore this 😄
Configuration
📅 Schedule: "every weekend" in timezone America/New_York.
🚦 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.
This PR has been generated by WhiteSource Renovate. View repository job log here.