HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
markerikson
react-redux-links
Web Development2016–2020
markerikson / react-redux-links

react-redux-links

Curated tutorial and resource links I've collected on React, Redux, ES6, and more

Web DevelopmentLearning & Reference
Explore on GitHubRead Hacker News discussions
8Distinct people
168Mentions
2Explicit recommenders
22.5KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Curated tutorial and resource links I've collected on React, Redux, ES6, and more

GitHub

Where it is used

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

What people are saying

For books, I recommend - Full Stack React ( https://www.fullstackreact.com/ ) - Robin Wieruch's "The Road to Learn React" ( https://roadtoreact.com/ ) - Dave Ceddia's "Pure…

acemarke used a recommendation phrase. 7 indexed comments match. This is a phrase match, not a verdict.

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 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 1:49:46 PM 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 year168 dated mentions

Observed mentions: 2016-02-27 18:26:32 UTC to 2020-11-03 18:23:00 UTC.

0204060801002016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 38 mentions; 1 submissions, 37 comments20162017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 99 mentions; 0 submissions, 99 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 19 mentions; 0 submissions, 19 comments20182019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 6 mentions; 0 submissions, 6 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 6 mentions; 0 submissions, 6 comments2020

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 UTC38137
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC99099
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC19019
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC606
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC606

What Hacker News says

168 sources
acemarke·Nov 3, 2020
Short version: React already knows what component instance it's rendering. Whenever a hook is called, React looks up the right data from a linked list stored in the internal component metadata objects. For more details, see: - Shawn Wang's talk "Getting Closure on Hooks": https://www.swyx.io/getting-closure-on-hooks/ - React Hooks Demystified: https://dev.to/kayis/react-hooks-demystified-2af6 - React Hooks - Not Magic, Just Arrays: https://medium.com/@ryardley/react-hooks-not-magic-just-arra... - additional articles: https://github.com/markerikson/react-redux-links/blob/master...
In React Fundamentals: What I’m Learning
acemarke·Sep 30, 2020
I gotcha covered there :) See my "Idiomatic Redux" blog post series [0] for info on how Redux was designed, why it works the way it does, and the implementation details of both the Redux core, React-Redux, and our new Redux Toolkit package. I also recommend the post "Build Yourself a Redux" [1] as the best "build a mini Redux" post I've seen. Rodrigo Pombo's "Didact" series [2] does the same process but for React, showing how to build a miniature reconciler that even includes hooks. I also have links to further articles about React's implementation [3] as well. Finally, I specifically recommend reading my post "A (Mostly) Complete Guide to React Rendering Behavior [4] and Dan Abramov's extensive article "A Complete Guide to `useEffect`" to better understand how React behaves and how to use it correctly. [0] https://blog.isquaredsoftware.c
Read the rest
om/series/idiomatic-redux [1] https://zapier.com/engineering/how-to-build-redux/ [2] https://github.com/pomber/didact [3] https://github.com/markerikson/react-redux-links/blob/master... [4] https://blog.isquaredsoftware.com/2020/05/blogged-answers-a-... [5] https://overreacted.io/a-complete-guide-to-useeffect/
In The Architecture of Open Source Applications
acemarke·Sep 3, 2020
For starters, I'd suggest going through Rodrigo Pombo's walkthrough "Build Your Own React" [0], my post "A (Mostly) Complete Guide to React Rendering Behavior" [1], Dan Abramov's treatise "A Complete Guide to `useEffect`" [2], and Shawn Wang's talk "Getting Closure on Hooks" [3]. I also have additional links on both React's internals [4] and React hooks specifically [5] that should be useful. [0] https://pomb.us/build-your-own-react/ [1] https://blog.isquaredsoftware.com/2020/05/blogged-answers-a-... [2] https://overreacted.io/a-complete-guide-to-useeffect/ [3] https://www.swyx.io/speaking/react-hooks/ [4] https://github.com/markerikson/react-redux-links/blob/master... [5] https://github.com/markerikson/react-redux-links/blob/master...
In React is becoming a black box
acemarke·Apr 27, 2020
The ordering question is literally just about how you call them within a single specific component. That component can then be used as many times as you want, in as many apps as you want. In other words, this is not legal: const [stateA, setStateA] = useState(false); if(stateA) { const [stateB, setStateB] = useState(42); } Call as many hooks as you want, in whatever sequence you want. Just make sure all the calls are at the top level of that function component, and that you don't somehow change the sequence of those from one render pass to the next. As for how they work, React already has metadata that describes each component in the tree. There's a specific field in those metadata objects that gets used for tracking internal component state, and for function components, that field stores an array / linked list of
Read the rest
the hook calls you've made and their last saved results. See these resources for more explanations on how hooks are implemented: https://github.com/markerikson/react-redux-links/blob/master...
In A Critique of React Hooks
acemarke·Feb 10, 2020
Hi, I'm a Redux maintainer. You may be interested in my suggested resources for learning React and Redux: https://blog.isquaredsoftware.com/2017/12/blogged-answers-le... https://blog.isquaredsoftware.com/2017/12/blogged-answers-le... https://github.com/markerikson/react-redux-links Also, please check out our new official Redux Toolkit package. It includes utilities to simplify several common Redux use cases, including store setup, defining reducers, immutable update logic, and even creating entire "slices" of state at once. It's our recommended way to write Redux logic: https://redux-toolkit.js.org Meanwhile, we're working on a major rewrite of the Redux core docs. I'm hoping to put together a new "Quick Start" tutorial page that will show how to use Redux Toolkit and React-Redux in a "top-down" approach as a fast way to get productive.
Read the rest
The current tutorials take a "bottom-up" approach, teaching how Redux works from first principles. I also want to rewrite those, keeping the same teaching flow, but updating the content to be easier to understand and to teach patterns that result in simpler code.
In Things I wish I knew about state management when I started writing React apps
acemarke·Jul 22, 2019
Yep. The Redux "Three Principles" docs page [0] emphasizes the "single source of truth" aspect. It's a good selling point, but has unfortunately led to a lot of folks interpreting that as "you _must_ keep _everything_ in Redux". (Doing so is a valid design decision, and I've certainly talked to folks who deliberately did that to make everything trackable and time-travel-able. But, most UI state probably doesn't need to go in Redux, particularly form state [1].) In reality, there should be a good balance between global and local state. I wrote a Redux FAQ entry that tries to give some rules of thumb for determining what state goes where [2]. When we do the docs revamp, hopefully we can make that kind of thinking more explicit. I'd be very interested in hearing more details on any issues you may be having with React-Redux, and I'm happ
Read the rest
y to offer advice for you or anyone else on using it better. HN comments aren't a great place for that, but please file an issue for discussion or contact me in the Reactiflux chat channels on Discord in the #redux channel. I'd also greatly appreciate any feedback folks would have on weaknesses with the current docs, so we can improve those issues with the docs revamp. We've had open issues to cover writing a "Performance" docs page for a long time, but no one got around to contributing that, and there's been too many other higher priorities for us to write it. My React/Redux links list does have a section of articles on improving Redux perf [3], if that helps, and there's an FAQ section on that topic [4]. In general, connect more components [5], and use memoized selectors [6] to read data and do transforms. [0] https://redux.js.org/introduction/three-principles [1] https://redux.js.org/faq/organizing-state#should-i-put-form-... [2] https://redux.js.org/faq/organizing-state#do-i-have-to-put-a... [3] https://github.com/markerikson/react-redux-links/blob/master... [4] https://redux.js.org/faq/performance [5] https://redux.js.org/faq/react-redux#should-i-only-connect-m... [6] https://blog.isquaredsoftware.com/2017/12/idiomatic-redux-us...
In When a rewrite isn’t: rebuilding Slack on the desktop
acemarke·Jan 4, 2019
Which specific "best practices" are you referring to? Ignore the CSS-related discussions for now. React itself doesn't care how you handle the CSS in your app. You can write standalone stylesheets and match the classnames in your HTML output, same as you always have, write inline styles, or use one of the fancy new "CSS-in-JS" libs that have popped up. Other than that, the aspects of "reusability" and "easier to work with than hand-written DOM manipulation" are certainly true. "Easy to learn" is just an observation, not a reason to use it. In general, React is beneficial if you're doing any kind of interactive client-side application, regardless of how big your company is. It provides a consistent mental model for how your app is constructed and updated: given some set of state values, the resulting UI output will be X, and the data a
Read the rest
nd updates flow top-down in the tree. This becomes more valuable as the size of the client-side logic and UI grows. I'd suggest taking some time to actually try out React and get a feel for how it works in practice. The easiest way to do it is to open up https://codesandbox.io and start a new React project. Here's a couple meta-links that may be helpful for learning more. My suggested list of resources for getting started with React: http://blog.isquaredsoftware.com/2017/12/blogged-answers-lea... My React/Redux links list: https://github.com/markerikson/react-redux-links If you've got any further questions I can help with, ping me @acemarke on Twitter. Also, come by the Reactiflux chat channels on Discord. The invite link is at https://www.reactiflux.com .
In Ask HN: What is the draw of React?
acemarke·Nov 29, 2018
This actually looks like a pretty good resource. The combination of a voiceover and an interactive editor looks pretty neat. Noting this for future reference. If anyone's interested in further resources, I'd suggest checking out my suggested resources for learning React [0], my React/Redux links list [1], and the Reactiflux chat channels on Discord [2]. [0] http://blog.isquaredsoftware.com/2017/12/blogged-answers-lea... [1] https://github.com/markerikson/react-redux-links [2] https://reactiflux.com
In Learn React for free
acemarke·Jul 19, 2018
Rather generic question, so I'll give you a generic answer: check out my React/Redux links list [0], which points to many categorized articles on various React and Redux topics. You might also be interested in my "Practical Redux" tutorial series [1] and "Idiomatic Redux" best practices and explanations series [2]. [0] https://github.com/markerikson/react-redux-links [1] https://blog.isquaredsoftware.com/series/practical-redux [2] https://blog.isquaredsoftware.com/series/idiomatic-redux
In Ask HN: Any advanced react/redux tips you'd like to share?

Showing the 15 most recent of 168 sources. Enable JavaScript to search and browse every indexed mention.

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.