reduxjs

Activity

Stars and mentions · Last 30 days, Oct 5 – Nov 3

GitHub stars21
Mentions11
02468Oct 5Oct 19Nov 3
UTC days · repositories reduxjs owns1 repository

Top repositories

reduxjs’s repositories ranked by new stars, as on trending.

Loading

Contributes to

Repositories outside reduxjs’s account where reduxjs opened or reviewed pull requests in the past 365 days.

Who noticed reduxjs

Everyone who starred or forked reduxjs’s repositories since the archive began in 2011.

Notable accounts

Ordered by the stars their own repositories have received.

Biggest fans

Accounts that starred the most of these repositories.

Breakout weeks

Each repository’s best week of new stars, with the release published around it.

Mentions

12posts
Nov 41 post
  1. (Replay engineer and Redux OSS maintainer) Yep. I see it myself, both in other people's code, and our own. The _default_ behavior is a tendency to pile slop on slop, make poor architectural choices, slap bandaids on edge cases without considering the full ramifications, etc. This is more true if there isn't oversight or feedback, and also depending on model quality. On the flip side: I personally use a strongly human-in-the-loop AI dev workflow [0]. Going back and forth on how much of that code I review myself (and I've found that AI code review frankly does a better job than _I_ do most of the time :) ). But, between staying hands-on, and the ongoing improvements in models, I've seen that the code my own agentic dev sessions produces is actually pretty high quality, and I've been able to clean up a lot of low-quality slop from unmonitored agent sessions. I've also been able to build some pretty major features from scratch and even execute massive migrations with excellent results, again by having me drive the work. I actually just got done shipping Redux Toolkit 2.14 [1] with a massive set of bug fixes, and almost all of those were found by my agent researching the already-mature RTK codebase, at my direction, and identifying existing logic flaws or weaknesses. Once we knew what those bugs were, we could fix them. Which, honestly, is the point of the blog post, of Replay QA as an automated testing product, and of Replay as a company in the first place. Once you know what a bug _is_ and why it happens, fixing it is usually fairly straightforward. _Finding_ it is the hard part. I've given a conf talk the last few years on "Debugging Software" [2]. One of the main points I make is that no one is _taught_ how to debug - we figure it out on the job as we go, because we have to ship. It's part of the job. But few people like doing it, and most people just want to slap in some console logs and call it a day. Very few people even use existing graphical debuggers (VS Code, Chrome DevTools, etc). We built a time-travel debugger. The original idea was: make a DVR-style recording of a bug happening once, then you can dive in as deep as you need to investigate. Originally, that was supposed to be a human using the Replay DevTools UI - browser devtools with time travel debugging features built in. It's awesome, I wish I'd had it much earlier in my career :) But we found most people didn't want to spend time doing it themselves. Earlier this year we shipped Replay MCP, which gives agents the same time-travel debugging capabilities: see hit counts for any line of code, dynamic logpoints and evaluations for every time a line of code ran, see the DOM tree or React component tree at any point in time. I built most of the React analysis features and MCP tools myself, based on my years of experience in the React ecosystem and maintaining Redux. So, today you _could_ make a Replay recording of your app, point your agent at the MCP, and have it investigate. I've done that, and wrote some blog posts about how that helped my own agent find bugs in React itself and Next.js apps [3] [4]. I've seen my agent nail a bug from a recording on someone else's machine in <10min, starting from scratch. We've productized that as Replay QA, so that you don't have to do any of the recording or setup - just point Replay QA at your app and repo and we do all the site analysis and recording and bug root cause investigation ourselves. Essentially, encoding our own expertise as debuggers, so you get the benefits [5] So, back to the original point. Yeah, AI tends to crank out bad code by default, that code is buggy. We can't help your agent choose a better architecture. But we can help identify the bugs proactively, identify the root causes, and suggest solutions, based on the actual runtime behavior of the app. Up to you to get your agents to write _better_ code, but we can give your agent what it needs to fix the bugs it wrote :) - [0]: blog.isquaredsoftware.com - [1]: github.com/reduxjs/redux-toolkit/releases/tag/v2.… - [2]: blog.isquaredsoftware.com - [3]: replay.io - [4]: replay.io - [5]: replay.io

  2. Just published Redux Toolkit 2.14! Faster dispatch and RTK Query types perf, new entity adapter and RTKQ methods, and a _ridiculous_ number of RTKQ bugfixes. This sets the stage for upcoming 2.x features and the rest of the 3.0 roadmap: github.com/reduxjs/redux-toolkit/releases/tag/v2.…

    28 likes · 3 reposts · 867 views
  3. Just published Redux Toolkit 2.14! Faster dispatch and RTK Query types perf, new entity adapter and RTKQ methods, and a _ridiculous_ number of RTKQ bugfixes. This sets the stage for upcoming 2.x features and internal improvements, and the rest of the 3.0 roadmap: github.com/reduxjs/redux-toolkit/releases/tag/v2.…

  4. Frontend #310 Frontend November 03 • Issue #310 • Tweet • Forward Unreadit ⚠️ Can't load styles Hello! This digest is made with Mailbrew ☕️ Sign up here to get a 30% discount and customize it with your favorite sources ❤️ r/webdev Manager thinks anything can be coded in 1 hour or less with AI. 554190 I work for a large accounting firm where the impact of getting things wrong feels quite big. We’ve started a new sprint for the next chunk of work. The team has put together estimates for various elements of a new accounting feature involving bank transactions, VAT calculations and reconciliation, … Who remembers when web developers portfolio websites had a “skills chart” 354109 HTML 95% PHP 70% jQuery/JavaScript 80% MySQL 58% Gives me the shudders thinking about it… Your AI UI skill is doing the part you were supposed to learn 312127 So a few of my friends have stopped using Figma. They go straight to production and make changes there. When I first heard this I was honestly confused. Like where do you try things out? Where do you compare two versions? Then I saw what they were building. … DEV Community llm 0.37 Adds Multimodal Embeddings and a Cheaper Default — What That Means for Local Audio Pipelines devsNov 3 Build a Secure OTP Service: Custom Node.js Generation, Validation, and External SMS callumreed2198Nov 3 A beginner's guide to the P-Video model by Prunaai on Replicate aimodels-fyiNov 3 r/frontend The best way to use icons in Web UIs • Lea Verou 537lea.verou.me The best way to use icons in Web UIs • Lea Verou A Modern CSS Guide to Responsive Web Design 3111stephcraft.net If I missed anything, let me know! building the basics in webdev for absolute noob 81github.com I made this doc for a friend of mine who just started college and wanted to know basic frontend for starter, everyone keeps saying claude or gpt can code that easily and you gotta learn the tougher topics but you need to code a bit without any ai aid to … r/javascript I've proven that you don't need quotes or parentheses in JavaScript 9717blog.ikaes.de You can overwrite the prepareStackTrace property of the Error object by String prototype's functions and invoke them without parentheses. Then by overwriting the Error and Array prototype it is possible to control the arguments. Combining this behavior, together with some JSFuck-inspired tricks, it is possible to generate arbitrary JavaScript strings … We stopped installing npm packages less than a week old 7130brunoj.com We stopped installing npm packages less than a week old No, npm, “estee” is not a typo of “testem” 414smoores.dev No, npm, “estee” is not a typo of “testem” Since 2017 I've been trying to get zoom navigation right. Zumly is the closest I've got 3113zumerlab.com Since 2017 I've been trying to get zoom navigation right. Zumly is the closest I've got r/reactjs My honest Interview Experience for a React developer role 13840 Made a React button that tilts, squishes and actually feels pressable 5814 Redux Toolkit v2.x and v3.0 roadmap 5023github.com Did you remove your useMemo calls after turning on the React Compiler? 4013 r/vuejs Struggling to find any Vue/Nuxt job in 2026 6033 Working on an open-source goopy ui framework... Shadcn, but it drips 4920 r/CSS Crazy what you can do with just CSS right?? 22251 I spent the last few weeks building the "perfect" liquid glass effect with just CSS (e.g. SVG Filters), No WebGL used and it works page wide, which means it picks up anything of the background behind it. The core is a backdrop-filter with an SVG displacement map. I screen … CSS Tricks is back! 1205css-tricks.com CSS Tricks is back! CSS-Tricks What’s !important #20: GTA 6 Scroll Effects, Scrollspies, random() Daniel SchwarzNov 2 The Frankenstein Table PreethiOct 29 What’s !important #19: CSS Refraction Effects, Scroll State Queries, @custom-media, and More Daniel SchwarzOct 27 Smashing Magazine A Spark Of Color In November’s Gray (2026 Wallpapers Edition) smashingmagazine.comhello@smashingmagazine.com (Cosima Mielke)Oct 31 Let’s kick of November with a new collection of desktop wallpapers! Designed by creatives from across the globe, the wallpapers come in a variety of screen resolutions and can be downloaded for free. Enjoy! © Mailbrew EVERNOMIC LTD, Gladstonos 12-14, Paphos 8046, Cyprus Frontend is a digest by Unreadit. building the basics in webdev for absolute noob: github.com/kh-yourtechally/getting-started-webdev… Redux Toolkit v2.x and v3.0 roadmap: redux-toolkit#5536

  5. @mattpocockuk Incidentally redux-toolkit#5536

    2 likes · 256 views
  6. Reddit · · r/reactjs · u/acemarke · reduxjs/redux-toolkit

    Redux Toolkit v2.x and v3.0 roadmap

    53 points · 23 comments
  7. I'm thrilled to announce a roadmap to Redux Toolkit 3.0! 3.0 will have some breaking changes to improve DX going forward, including shipping ESM-only. We've also planned significant correctness, perf, and feature improvements for 2.x leading up to 3.0: redux-toolkit#5536

    60 likes · 3 reposts · 2,400 views
  8. The full workstream roadmap is here: redux-toolkit#5483 we'd also appreciate feedback on several usage patterns as well as the planned breaking changes: redux-toolkit#5534 redux-toolkit#5535

    1 like · 225 views
  9. The full workstream roadmap is here: redux-toolkit#5483 we'd also appreciate feedback on several usage patterns as well as the planned breaking changes: redux-toolkit#5534 redux-toolkit#5535

    1 like
  10. I'm thrilled to announce a roadmap to Redux Toolkit 3.0! 3.0 will have some breaking changes to improve DX going forward, including shipping ESM-only. We've also planned significant correctness, perf, and feature improvements for 2.x leading up to 3.0: redux-toolkit#5536

    20 likes

Achievements

Awards earned by the repositories reduxjs owns. Select an award to embed its badge.

Gold
01st place finishes
Silver
12nd place finishes
Bronze
03rd place finishes
Awarded repositories
1Owned by reduxjs now

Repositories

Ordered by gold, then silver, then bronze.

  1. reduxBest: 2nd by stars, 304 stars010

Every award

Top-three finishes of these repositories in completed trending days and weeks, newest first.

  1. redux

A repository earns an award for finishing first, second or third in a completed trending day or week, ranked by new stars, new forks or pull request authors. Awards follow a repository through renames and transfers and count toward its current owner. Weeks run Monday to Sunday, UTC.