Log inSign up
Dominik 🔮
21.3K posts
Dominik 🔮 profile banner
@TkDodo

Dominik 🔮

@TkDodo
Maintaining TanStack Query • blog at tkdodo.eu • Software Engineer @getsentry • ReactJs • TypeScript • 🇦🇹 Vienna, Austria • Father of two 👧‍👦
🔮 available now ➡️
query.gg
Joined June 2009
410
Following
58.6K
Followers
RepliesRepliesRepostsRepostsMediaMedia

Log in or sign up for X

See what’s happening and join the conversation

Continue with phone
or
Log in with username or email
Terms·Privacy·Cookies·Accessibility·Ads Info·© 2026 X Corp.
  • Pinned
    @TkDodo
    Dominik 🔮
    @TkDodo
    May 29, 2024
    📢 I'm so stoked to announce that today, 🔮 query.gg - the brand new, official @tan_stack React Query course - is live and available for everyone 🎉
    Image
    The Official React Query Course - 🔮 query.gg
    From query.gg
    43
  • @TkDodo
    Dominik 🔮
    @TkDodo
    2h
    📢 We have mostly moved the TanStack Query API reference docs to being auto-generated from JsDoc comments. This might mean some of the pages will temporarily have less information than before. If you see something that doesn't look right, please reach out and/or file a PR 🙏
    4
  • @TkDodo
    Dominik 🔮
    @TkDodo
    Aug 18
    📚 It's been way too long since my last blogpost. Today, I'm continuing my @tan_stack router series with a pattern that I've been teaching in my workshops for over a year: How to keep prefetches in sync between route loaders and components:
    Image
    Reliable Query Prefetching with TanStack Router
    From tkdodo.eu
    6
  • @TkDodo
    Dominik 🔮
    @TkDodo
    Aug 18
    📢 I've decided to remove the experimental_prefetchInRender flag and the associated promise returned from useQuery. There are too many "gotchas" with this approach. This currently puts use(promise) off the table, sorry. We'll have to think some more how to make this possible...
    3
  • @TkDodo
    Dominik 🔮
    @TkDodo
    Jun 25
    Guido Started a great 7-part blog series, explaining ATproto to people outside the ecosystem. Give it a read if you're interested in ATproto or why I think it's the future (not just for social media). Part 1: Who actually owns your network?
    Every time I moved a community to a new platform, the exit cost members and history. Platforms come and go; the lock-in architecture underneath is why. Part of 'Apps as Views, Not Vaults': the things you make are yours; apps are just the viewers.
    Who actually owns your network?
    From gui.do
    2
Advertisement
Advertisement