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

redux-toolkit

The official, opinionated, batteries-included toolset for efficient Redux development

Explore on GitHubRead Hacker News discussions
8Distinct people
55Mentions
1Explicit recommenders
11.2KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

The official, opinionated, batteries-included toolset for efficient Redux development

GitHub

Where it is used

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

What people are saying

I've been using redux toolkit's OpenAPI code generator for a side project and it's been pretty good. The documentation is a bit lacking and it could certainly use more work to…

SCUSKU used a recommendation phrase. One indexed comment matches. 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 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 5:05:26 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 year55 dated mentions

Observed mentions: 2018-04-11 15:51:39 UTC to 2023-12-04 14:33:19 UTC.

051015202018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 18 mentions; 2 submissions, 16 comments20182019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 7 mentions; 0 submissions, 7 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 8 mentions; 1 submissions, 7 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 10 mentions; 1 submissions, 9 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 8 mentions; 1 submissions, 7 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 4 mentions; 1 submissions, 3 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
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC18216
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC707
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC817
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC1019
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC817
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC413

What Hacker News says

18 sources
acemarke·Dec 5, 2018
Yes, absolutely! Per my other comment in this thread [0], please check out our `redux-starter-kit` package [1]. I'd appreciate any feedback on whether or not it helps you, and what other capabilities would be beneficial to include. Lots of people throw around the word "boilerplate", but everyone seems to mean something different by it [2]. Can you clarify what _specific_ things you mean by that? [0] https://news.ycombinator.com/item?id=18605421 [1] https://github.com/reduxjs/redux-starter-kit [2] https://github.com/reduxjs/redux/issues/2295
In React Redux 6.0 released
acemarke·Dec 5, 2018
Since it's a Redux-related thread, I'll toss out one other sub-thread to let people know what we're working on, and ask for feedback. We've already completely revamped the React-Redux docs [0]. They're now published as a separate site, and we're writing all-new content, like guides on how to best use `connect`. There's plenty more topics we plan to cover, but it's a big improvement already. Meanwhile, we're also working on a new build setup for the Redux core docs. Once that's ready, we'll turn our attention to actually revamping the actual Redux docs content and structure. (There's an existing issue if you'd like some info on some of the plans [1]). So, with that in mind, I'd specifically like to ask: - What do you think are the biggest strengths and weakness of the current Redux docs at https://redux.js.org ? - What topics do we do
Read the rest
well? - What is not covered, or explained poorly? - What would be the biggest improvements we can make to the docs structure and content? I'd appreciate any constructive feedback people can offer. Finally, we've got a new `redux-starter-kit` package [2] that can help simplify common use cases like store setup, writing reducers, immutable update logic, and even creating "slices" of your store automatically. I'd encourage people to try it out. I talked some about this package in my recent ReactBoston talk on "The State of Redux" [3]. We'll be emphasizing this package when we rework the tutorials and other parts of the docs in the near future. [0] https://react-redux.js.org [1] https://github.com/reduxjs/redux/issues/2590 [2] https://github.com/reduxjs/redux-starter-kit [3] https://blog.isquaredsoftware.com/2018/10/presentation-state...
In React Redux 6.0 released
acemarke·Nov 29, 2018
We've actually got a new `redux-starter-kit` package which includes some reducer utilities similar to `redux-actions`, but using the Immer library internally. That allows you to write simpler immutable updates that look like "mutation". There's also some helpers for common use cases like simplifying store setup, and generating entire "slices" of state at once (including generating action creators and action types automatically). I put together an example of using this the other day: https://www.reddit.com/r/reactjs/comments/a0b1sa/frustrated_... Please try it out and let us know what you think! https://github.com/reduxjs/redux-starter-kit
In Learn React for free
acemarke·Oct 27, 2018
Sagas are a great power tool, but I personally wouldn't use them for most simple API requests, largely because of the need for "signal actions" to trigger the logic. You might want to check out our new `redux-starter-kit` package [0], which can simplify some common use cases for things like action creators and reducers. There's also many other existing libraries to handle repetitive code like API requests as well [1]. [0] https://github.com/reduxjs/redux-starter-kit [1] https://github.com/markerikson/redux-ecosystem-links/blob/ma... , https://github.com/markerikson/redux-ecosystem-links/blob/ma...
In Introducing Hooks
acemarke·Oct 25, 2018
Funny you should mention that :) There's a lot of existing libraries out there that will indeed generate action creators, reducers, etc (see my Redux addons list [0] for examples). One of the most interesting ones I've seen is Eric Elliott's `autodux` project [1], which does some clever bits of handling inside a `createSlice()` function. Earlier this year, I put together a new project called `redux-starter-kit`] [2]. Its goal is to simplify several common use cases with Redux usage, including store setup, reducer definitions and immutable update logic, and default behavior out of the box. While we don't plan to add these things to the Redux core itself, `redux-starter-kit` is an official Redux-branded library, and we're going to start encouraging that people use it in most situations. We just added a `createSlice` function to `redux-sta
Read the rest
rter-kit`, based on the `autodux` approach. I'd encourage you to try it out, as it does _exactly_ what you're asking for. I'd also really appreciate some feedback on how well it works, and any additional ideas for things the starter kit should include! [0] https://github.com/markerikson/redux-ecosystem-links [1] https://github.com/ericelliott/autodux [2] https://github.com/reduxjs/redux-starter-kit
In Introducing Hooks
acemarke·Oct 15, 2018
Hi, I'm a Redux maintainer. We're currently working on a package called `redux-starter-kit` that contains some utilities to help simplify common concerns about Redux, including store setup, generating action creators, and writing reducer logic and immutable updates: https://github.com/reduxjs/redux-starter-kit I'd appreciate it if you could take a look, try it out, and give us some feedback. It's currently JS-only, but we're planning to convert it to be written in TS in the near future. As for as Redux and TS in general... I know I've seen comments similar to yours ("duplicating action constants and enums", etc). Unfortunately, I don't use TS myself, and don't know enough to offer meaningful suggestions there. If you've got specific pain points with Redux and TS, please go ahead and file an issue for discussion, and perhaps we can work o
Read the rest
n some solutions.
In Show HN: I Built a Metasearch Engine with React, Redux, Express and TypeScript
acemarke·Oct 2, 2018
Absolutely - all you've ever needed to do is `npm i redux react-redux`, then add them to the app. They're just libraries, no special behavior needed. See the "Configuring Your Store" docs page [0] for copy-pasteable examples of adding Redux to a React project. Also, we're working on a `redux-starter-kit` project [1] that will soon become an official Redux-branded tool to help with common pain points, like setting up the store properly, simplifying immutable reducer update logic, and more. I talked about it in my React Boston "State of Redux" presentation [2] over the weekend. Please try it out, and let us know how it works and what else we should add! [0] https://redux.js.org/recipes/configuringyourstore [1] https://github.com/markerikson/redux-starter-kit [2] https://blog.isquaredsoftware.com/2018/10/presentation-state...
In Create React App 2.0: Babel 7, Sass, and More
acemarke·Aug 27, 2018
I'm a Redux maintainer. FWIW, I'm always open to suggestions on how we can make using Redux easier and better for everyone (example prior discussion: https://github.com/reactjs/redux/issues/2295 ). We're currently working on a "starter kit" package that's intended to address some of the most common concerns about using Redux, and hope to make it an official Redux-branded package in the near future. I'd appreciate any feedback or ideas you have for improving it: https://github.com/markerikson/redux-starter-kit Also, since you mention stack traces: if anyone out there has a bit of free time on their hands, I'd _love_ to see the Redux DevTools core and extension updated to show a stack trace for where each action was dispatched: https://github.com/zalmoxisus/redux-devtools-extension/issue...
In Why is a Java guy so excited about Node.js and JavaScript?
strken·Jul 6, 2018
> Not sure I follow that train of thought - could you point to an example? Something like const store = createStore(...) export const dispatch = (action) => store.dispatch(action) It removes the temptation to read directly from the store. > `redux` and `react-redux` are deliberately separate packages Yeah, my bad, got the import wrong. > ...limits the reusability of your logic... When would this become a problem, in practice? Reusable actions across different react/react-native UI, or multiple apps? Switching between user accounts? How common a use case is it? Even if this is a constraint, I'm of two minds about whether a hack in isolation is worse than more complicated action boilerplate in general. > ...and also makes it a lot harder to test... This can be mitigated by Jest's mocks. > https://github.com/markerikson/redux-starter-ki
Read the rest
t That's really good. Unfortunately, it's not the same thing as bundling it with Redux proper. Anyway, thanks for engaging with me. I never intended to do a deep dive into Redux's design, only to sympathise with stupidcar's comments about third-party state management, but it's interesting to hear the perspective of a maintainer.
In Vue.js: the good, the meh, and the ugly
acemarke·Jul 6, 2018
Yeah, for a while it seemed like there was a new Redux side effects lib coming out every week. At this point, though, it's pretty much standardized on thunks for basic use cases, and either sagas or observables for more advanced use cases based on your preference of writing async logic. > What I've taken to doing is exporting a dispatch function that calls the store's dispatch, not the store. Not sure I follow that train of thought - could you point to an example? > Actions themselves make perfect sense from the perspective of a reducer, and clearly they must be dispatched, but they're a state management detail that the UI doesn't need to know about. Something similar to redux-action could be the default. This is why we recommend use of action creators, so that a component is just calling `this.props.doSomething()` without it "knowing" t
Read the rest
hat a Redux action is actually being dispatched. Per your snippet there at the end: - `redux` and `react-redux` are deliberately separate packages, because the Redux core is 100% vanilla JS, and independent from React (in the same way that `react` and `react-dom` are separate packages - the core React logic is independent of the platform-specific reconcilers). So, `import {connect} from "redux"` wouldn't be appropriate. - The use of `deleteFoo()` that way assumes that it's pre-bound to a specific store instance, which limits the reusability of your logic, and also makes it a lot harder to test. `connect` abstracts away the question of "which store instance am I interacting with?", so that your components and logic are more testable and reusable. > Something similar to redux-action could be the default. For what it's worth, earlier this year I threw together a small `redux-starter-kit` package: https://github.com/markerikson/redux-starter-kit . The goal behind it is to simplify some of the most common pain points around Redux: store setup (including thunks and devtools), writing immutable updates in reducers, and having to install multiple packages out of the box. The biggest thing I know it's still missing at this point is indeed something akin to `redux-actions` - see my notes at https://github.com/markerikson/redux-starter-kit/issues/17 . I haven't had time to push it forward further, but I would seriously like to get some more eyes on it, see if there's any other use cases we should be covering, and then make it an official Redux-branded package and update our docs to recommend that people use it.
In Vue.js: the good, the meh, and the ugly
acemarke·Jun 20, 2018
Part of the issue is that _everyone_ has a different definition of what "boilerplate" means. So, legit question: what do _you_ mean by that term? Use of actions? Action creators? `connect()`? Immutable update logic in a reducer? Store setup? I honestly get frustrated that people keep throwing around that term, but few people seem to point to a specific _thing_ that can be improved. (People also don't seem to understand the context that Redux came from and the intent behind its original design, something that I tried to capture in an extended blog post a while back [0]). Early last year, I filed an issue asking for discussion of ways we can improve the learning / getting started experience, and resolve some of these "boilerplate" complaints [1]. There were a bunch of comments and some decent ideas, but I already have a lot on my pla
Read the rest
te, and no one from the community really stepped up to help push any of the ideas forward. I do have a small "redux-starter-kit" lib [2] prototype that I've put together as a tool that can help simplify the store setup process and reducer logic. Again, though, I haven't had time to do much more with it myself since I first threw it together. I am _always_ open to legit suggestions on ways we can improve the docs or find ways to make using Redux easier. Unfortunately, it seems like very few people are interested in actually getting in touch with us and offering assistance in doing so. [0] https://blog.isquaredsoftware.com/2017/05/idiomatic-redux-ta... [1] https://github.com/reactjs/redux/issues/2295 [2] https://github.com/markerikson/redux-starter-kit
In React Native at Airbnb

Showing the 15 most recent of 18 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.