HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
reduxjs
react-redux
TypeScript2016–2023
reduxjs / react-redux

react-redux

Official React bindings for Redux

Web DevelopmentLibraries & SDKs
Explore on GitHubRead Hacker News discussions
13Distinct people
43Mentions
0Explicit recommenders
23.4KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Official React bindings for Redux

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 4:01:40 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year43 dated mentions

Observed mentions: 2016-10-04 01:09:15 UTC to 2023-12-04 14:33:19 UTC.

0510152016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 5 mentions; 2 submissions, 3 comments20162017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 5 mentions; 0 submissions, 5 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 13 mentions; 1 submissions, 12 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 10 mentions; 4 submissions, 6 comments20192020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 4 mentions; 1 submissions, 3 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2023

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC523
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC505
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC13112
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC1046
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC303
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC101
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC413
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC202

What Hacker News says

10 sources
acemarke·Feb 9, 2019
Hi, I'm a Redux maintainer. I wouldn't call it a _significant_ performance hit. There's a measurable difference in our artificial stress tests benchmarks, and some users have reported slowdowns in specific scenarios (especially when large forms are connected to Redux). I recently posted a roadmap issue with our plans for addressing the perf issues, and moving towards the ability to ship a hooks-based API for React-Redux: https://github.com/reduxjs/react-redux/issues/1177 I've specifically spent the last week experimenting with reworking the internals of `connect` to come up with an alternative implementation that relies on direct store subscriptions again, and as of a couple days ago, I seem to have come up with something that is actually _faster_ than both v6 _and_ v5 in our benchmarks: https://github.com/reduxjs/react-redux/issues/1177
Read the rest
#issuecomm... Still needs more investigating and testing, but this approach looks very promising.
In Ask HN: How do you manage state in your React application?
acemarke·Jan 3, 2019
Hi, I'm a Redux maintainer. We recently released React-Redux v6 [0]. The major change for this release was how React-Redux internally makes the Redux store state accessible to nested components, by switching from React's old (and broken) context API to using the new context API. I wrote a blog post about the technical details of the change and why we did it [1]. A number of libraries in the ecosystem were accessing the Redux store directly out of legacy context, which was not part of the React-Redux public API. Because of this, those libraries broke when used with v6 (as described in our release notes). Note that this was not an issue with React or Redux themselves. This was caused by other libraries in the ecosystem relying on non-public implementation details, which are always at risk of breaking no matter what the library or langua
Read the rest
ge is. As you noted, react-redux-firebase is working on updating itself to work correctly with the latest version of React-Redux. (We've also added some docs to React-Redux that describe how libraries can safely access the store directly [2], albeit with the caveat that this is still not directly part of the public API.) You can also stay on React-Redux v5 and the existing version of react-redux-firebase if you'd like. There's nothing specifically wrong with those versions, and they still work together. Let me know if you've got any questions on this. [0] https://github.com/reduxjs/react-redux/releases/tag/v6.0.0 [1] https://blog.isquaredsoftware.com/2018/11/react-redux-histor... [2] https://react-redux.js.org/using-react-redux/accessing-store
In Ask HN: Which JavaScript framework changes the least?

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.