Mark Erikson

Like, this is the short bullet-point list of fairly concrete items I'm pulling together for RTK3 (or 2.x), _not_ including the following bullets of ideas I want to research:

We're so proud of our very own @acemarke.dev - his enthusiasm in infectious...no?

Had a blast talking about all things Replay! Time travel debugging superpowers, why Replay QA's automated testing is so critical in today's AI coding world, and how we've used time travel to analyze React to provide debugging and perf data no other tool can provide!

Really enjoyed this conversation! Appreciated the chance to share what we're up to with Redux, and my thoughts on AI, docs, and career in today's ecosystem.

For what it's worth, react-window is still the recommended option for most use cases (unless you need some of the more complex components only available in react-virtualized)

⚛️ After a few years of being in "maintenance mode", a new version of react-virtualized is now available on NPM with full React 19 support

“You’re constantly missing gaps in what is being tested, and you can’t test fast enough.” Natacha Grey, founder of swoon.ai 20 years in web development. The same QA problem the whole time - until Replay.

All of my 300+ browser tabs are beautiful https://www.zachleat.com/web/firefox-list-all-tabs/

blabbing here bc I can :) I haven't written a formal announcement / roadmap post yet, but I've got local prototypes for what will hopefully become Redux Toolkit / RTK Query v3 . The recent docs cleanup + consolidation cleared the deck for that, and I hope to start working towards v3 soon!

Connected her GitHub repo in seconds. First run surfaced issues that had been sitting undetected. No testing suite to configure. No QA code to write. Replay connects to your repo and shows you what’s breaking at runtime from the first run.

🙋‍♂️ so, what are the git forges you are using - or want to be using? asking for … reasons. (would appreciate sharing for reach)

20 years in web dev. 14+ active client projects. No dedicated QA hire. "You don't need to hire a QA resource for your projects. Replay can definitely take a handle on it." Natacha Grey, founder of swoon.ai

Full write-up: replay.io/blog/what-ou...

We ran a self-healing loop on our own codebase for two weeks - FullStory detecting, Replay QA diagnosing, Obvious fixing, humans merging. 152 PRs. 80 merged. 5.4 bugs/day. What earned engineer trust wasn't velocity. It was proof of reproduction.

We've turned our time-travel debugging tech and expertise into a powerful automated app QA system that can find bugs in any website! Check out how much it's helping one of our customers manage app QA load (especially with the rise of AI-driven dev)

TMiR 2026-09: React 19.3; a eulogy to software engineering?

I am looking for my next career opportunity! I’m an engineering leader, consultant, author, and open-source maintainer. I've been VP of Eng, written books, get 20M weekly downloads on NPM, and more. Know of a role you think I'd be a good fit for? Book time on my cal or DM me: corbincrutchley.com

And we think we managed to do just that, with your help. So here’s a heartfelt thank you for showing up. For believing in the craft and its people For being an important part of what connects us all across the globe. And for being true artisans of the web.

WHAT. A. CONFERENCE. 💛 It’s been a couple of weeks, and we’re still recovering from the high from our first ZurichJS Conf edition. With our dopamine resets comes a time for reflection and starting to plan the very loudly requested second edition.

Preact 11 is out 🎉 We’ve been hard at work at making our diffing use modern features like moveBefore , leveraging ESM for tree-shaking Preact Compat and ensuring you have a great experience with resumed hydration.

Releasing Preact 11 with better hydration, moveBefore support and some reshuffling may sound like a boring release but to me it feels like completing something I've thought about for a while, I want to thank everyone for supporting Preact and enabling my journey

It's @farisaziz.com time in Alicante 🙌

@tkdodo.eu kicking us off at @reactalicante.es 🚀

CSS keeps getting better and better, but the problem with hearing about amazing new features is that we're stuck not being able to use them for a few years because of browser support. So, this week I looked at a bunch of well-supported CSS features that I still see people turn to JS for.

Now that Schema Benchmarks has been officially released for 7 months, I thought it'd be useful to look at how it's improved over that time, and how it's helped the ecosystem! schemabenchmarks.dev/blog/7-month...

Haven't been active much here, sorry, AI-in-OSS burnout is real. How do you care when nobody else does? When nobody engages? When all the human connection is gone? When all you read is AI slop? I want to go back to coding for fun. Because whatever this is, it's very much _not_ fun.

@danieljcafonso.bsky.social opening the day at @reactalicante.es

Yay, Alicante! @nst.blue @acemarke.dev @tkdodo.eu @mkrl.xyz

I'm so grateful for the communities we're part of, both offline and online. Such wonderful folks all around us.

you can read what I've written about why this is EXACTLY my role in leading nuxt > I would be remiss not to speak about values. > Values shape the direction of projects and people [and] the culture of open source communities […] both in where we end up + what the journey there is like.

Actual request: has _anyone_ come up with a userscript or extension or alternate version of the Github Notifications tab that lets you actually filter out PR/issue entries by some criteria, like a text match or whether the last comment is from a bot? I live in that tab, but it's _painful_ :(