Mark Erikson
@acemarke.dev
Redux maintainer, building time-travel devtools at Replay.io. I blog about React, Redux, and TS at https://blog.isquaredsoftware.com . Answering questions anywhere there's a textbox on the internet, and otherwise out on the golf course!
Looks a lot like the pattern we used with RTK Query's "base query" API design, and seen in our `fetchBaseQuery` implementation:
redux-toolkit.js.org/rtk-query/us...
redux-toolkit.js.org/rtk-query/us...
Customizing Queries | Redux Toolkit
RTK Query > Usage > Customizing Queries: overriding default query behavior
redux-toolkit.js.org
November 12, 2025 at 10:21 PM
Looks a lot like the pattern we used with RTK Query's "base query" API design, and seen in our `fetchBaseQuery` implementation:
redux-toolkit.js.org/rtk-query/us...
redux-toolkit.js.org/rtk-query/us...
curious, expand on this thought? Examples?
November 12, 2025 at 8:33 PM
curious, expand on this thought? Examples?
WAIT YOU WERE AT CAVEDOG AND WORKED ON _TOTAL ANNIHILATION_?!?!?!?
That game was one of my all-time favorites during that era! ah, those were the days :)
You've had a truly amazing and impactful career! Thank you again for sharing these posts, and for all the work you've done over the years!
That game was one of my all-time favorites during that era! ah, those were the days :)
You've had a truly amazing and impactful career! Thank you again for sharing these posts, and for all the work you've done over the years!
November 11, 2025 at 4:21 PM
WAIT YOU WERE AT CAVEDOG AND WORKED ON _TOTAL ANNIHILATION_?!?!?!?
That game was one of my all-time favorites during that era! ah, those were the days :)
You've had a truly amazing and impactful career! Thank you again for sharing these posts, and for all the work you've done over the years!
That game was one of my all-time favorites during that era! ah, those were the days :)
You've had a truly amazing and impactful career! Thank you again for sharing these posts, and for all the work you've done over the years!
that's a very keen deep cut reference there :)
November 11, 2025 at 1:16 AM
that's a very keen deep cut reference there :)
this needs a blog post :)
November 10, 2025 at 5:03 PM
this needs a blog post :)
🤣🤣🤣🤣 JUST REREAD THAT ISSUE AND SAW YOU COMMENTED 4 HOURS AGO WHICH IS PROBABLY WHY YOU WERE TWEETING ABOUT THIS _NEVER MIND_! :)
November 10, 2025 at 3:43 AM
🤣🤣🤣🤣 JUST REREAD THAT ISSUE AND SAW YOU COMMENTED 4 HOURS AGO WHICH IS PROBABLY WHY YOU WERE TWEETING ABOUT THIS _NEVER MIND_! :)
I would be very interested in seeing details on this!
related: TanStack Query researched changing their cleanup timer approach to do timestamp comparisons instead of timer-per-entry:
github.com/TanStack/que...
got closed, but interesting. might be something we could adopt somehow.
related: TanStack Query researched changing their cleanup timer approach to do timestamp comparisons instead of timer-per-entry:
github.com/TanStack/que...
got closed, but interesting. might be something we could adopt somehow.
Improve subscription performance by 10-20 times by MrFlashAccount · Pull Request #9827 · TanStack/query
🎯 Changes
This PR introduces a centralized GCManager that consolidates individual timeouts across queries and mutations into a single dynamically-scheduled timeout, resulting in 10-20x performance ...
github.com
November 10, 2025 at 3:43 AM
I would be very interested in seeing details on this!
related: TanStack Query researched changing their cleanup timer approach to do timestamp comparisons instead of timer-per-entry:
github.com/TanStack/que...
got closed, but interesting. might be something we could adopt somehow.
related: TanStack Query researched changing their cleanup timer approach to do timestamp comparisons instead of timer-per-entry:
github.com/TanStack/que...
got closed, but interesting. might be something we could adopt somehow.
My blog is still on the same Hugo 0.17 build I first used in late 2016,specifically because I've tried to avoid falling into that trap :)
(I've made plenty of styling updates, but no "REWRITE THE BLOG / CHANGE ENGINES!")
(I've made plenty of styling updates, but no "REWRITE THE BLOG / CHANGE ENGINES!")
November 8, 2025 at 4:10 PM
My blog is still on the same Hugo 0.17 build I first used in late 2016,specifically because I've tried to avoid falling into that trap :)
(I've made plenty of styling updates, but no "REWRITE THE BLOG / CHANGE ENGINES!")
(I've made plenty of styling updates, but no "REWRITE THE BLOG / CHANGE ENGINES!")
Oh wow. Had no idea you'd ever covered eSports.
Never quite understood the appeal myself, even as a lifelong PC gamer, and never played LOL, but I'm familiar enough , and you did a fantastic job capturing the game _and_ the people.
_Beautiful_ piece of writing! Thank you for sharing this!
Never quite understood the appeal myself, even as a lifelong PC gamer, and never played LOL, but I'm familiar enough , and you did a fantastic job capturing the game _and_ the people.
_Beautiful_ piece of writing! Thank you for sharing this!
November 7, 2025 at 10:48 PM
Oh wow. Had no idea you'd ever covered eSports.
Never quite understood the appeal myself, even as a lifelong PC gamer, and never played LOL, but I'm familiar enough , and you did a fantastic job capturing the game _and_ the people.
_Beautiful_ piece of writing! Thank you for sharing this!
Never quite understood the appeal myself, even as a lifelong PC gamer, and never played LOL, but I'm familiar enough , and you did a fantastic job capturing the game _and_ the people.
_Beautiful_ piece of writing! Thank you for sharing this!
Reposted by Mark Erikson
Reposted by Mark Erikson
I'm curious, expand on that?
I assume this is related to the React community's "separation of concerns are vertical per-component, not horizontal per-file-type" line of thinking?
I assume this is related to the React community's "separation of concerns are vertical per-component, not horizontal per-file-type" line of thinking?
November 4, 2025 at 9:48 PM
I'm curious, expand on that?
I assume this is related to the React community's "separation of concerns are vertical per-component, not horizontal per-file-type" line of thinking?
I assume this is related to the React community's "separation of concerns are vertical per-component, not horizontal per-file-type" line of thinking?
aaaaand followed by v2.10.1 , because I was a bit over-aggressive with the byte-shaving work and broke `window` access in SSR :)
github.com/reduxjs/redu...
github.com/reduxjs/redu...
Release v2.10.1 · reduxjs/redux-toolkit
This bugfix release fixes an issue with window access breaking in SSR due to the byte-shaving work in 2.10.
What's Changed
Fix window SSR breakage by @markerikson in #5132
Full Changelog: v2.10.0...
github.com
November 4, 2025 at 3:37 PM
aaaaand followed by v2.10.1 , because I was a bit over-aggressive with the byte-shaving work and broke `window` access in SSR :)
github.com/reduxjs/redu...
github.com/reduxjs/redu...
FWIW this is a _really_ good post! Lengthy, detailed, summarizes the relevant discussions well, describes the concerns and impacts and involved parties. Comprehensive, but still readable.
Fantastic piece of writing. Thank you!
Fantastic piece of writing. Thank you!
November 1, 2025 at 4:00 PM
FWIW this is a _really_ good post! Lengthy, detailed, summarizes the relevant discussions well, describes the concerns and impacts and involved parties. Comprehensive, but still readable.
Fantastic piece of writing. Thank you!
Fantastic piece of writing. Thank you!