Freelance developer - React Query maintainer - Occasional OSS contributor - Been putting React on servers for a decade - Father of two - Homebrewer
Stockholm
- Tweets 2,072
- Following 414
- Followers 921
- Likes 3,503
Fredrik Höglund retweeted
Urql now has a new package @urql/next which adds support for the app-router part of Next.JS. It has an export for both server components as well as the usual ssr workflow.
An example: github.com/urql-graphql/urql…
1
6
27
3,419
In the example above, if B is also code split, you have to load the code for B before it can start fetching the data, so you'll get a double waterfall. On the server, this is fine, on client page transition, not so much.
So I wouldn't throw away my prefetches just yet. 5/5
2
4
445
With this solution, you now have a client side request waterfall which hurts performance, especially when the user has high latency (which happens all the time).
This gets worse the more nested useQuery you have, and gets even worse when you factor in code splitting too. 4/5
1
5
470
With this kind of prefetch-less solution, if two components <A><B /></A> both useQuery, you have a waterfall and for the server render that's usually fine, BUT, what happens when you do a client side page transition? 3/5
2
3
359
This kind of "just use useQuery wherever, no prefetching needed" is great for DX, but can be terrible for performance. Why?
SCs and app router works by mostly eliminating waterfalls, and when they can't be eliminated, they at least guarantee they always happen on the server. 2/5
1
3
345
This is very cool, and useful for some cases, and kudos to everyone involved, truly great job, but I have some reservations against this kind of prefetch-less data fetching solution I have to note.
This reintroduce waterfalls into SSRd apps that has not had them previously. 1/5
📢 Yesterday, we released an experimental react-query-nextjs package for the app directory. Wrap your app in the <ReactQueryStreamedHydration> component to enjoy direct useQuery fetches on the server with suspense, which streams to the client 🎉
Example: tanstack.com/query/v5/docs/r…
3
1
11
7,840
Hard agree. I see so much purely negative criticism and so little constructive.
The misinterpreting motivations one is the worst. If you have just a tad of empathy it's so easy to see how they are a tiny team trying to do tons and it just takes time. Stop being so entitled.
2
17
3,007
Fredrik Höglund retweeted
I lol'd pretty hard at this comment from @ephemjs 😂
ALT code reads: cache.subscribe((event) => { comment reads: Side effect in render which directly mutates state and also doesn't unsubscribe? Hat-trick, I like it. 😉
1
1
24
6,789
Fredrik Höglund retweeted
Excited to say I'm now considering new job opportunities! I was an early user of React, managed the team at FB, and recently finished a VP Eng role at Humu.
Now I'm looking to join a diverse, kind, hypercompetent team, with a role where I can empower and upskill engineers.
17
111
841
213,563
Fredrik Höglund retweeted
It’s true. Anyone can now run “partykit deploy”!!! Go nuts.
4
13
63
26,972
Doesn't always apply of course, like when you have multiple generics you might want to name them for clarity etc, but good rule of thumb.
In general though, people should name more generics..
2
1
261
I can't find the tweet now, but @TkDodo recently had a good point about how using e vs error/event depends on the distance between declaration and use. Just realised this goes for TS generics too.
If you only use the generic in the function declaration, T is fine, otherwise not.
2
8
1,225
Fredrik Höglund retweeted
Was great to be at #reactsummit again. Lovely atmosphere as always and awesome to hang out with all these kind people like @RyanCarniato @timneutkens @mhevery @Eli_White @acemarke @TkDodo @nikgraf @cnakazawa @jevakallio @elibelly @chatterboxCoder @mettinparzinski and so many more!
6
5
57
8,393
Fredrik Höglund retweeted
It's been an _amazing_ 2 days at @reactsummit :
- Met @phry (RTK co-maintainer) in person after 4 years working together :)
- Met @tkdodo , @mweststrate , @ephemjs , @jherr, and many others I've chatted with for years
- My "Debugging JS" talk + live @replayio demo went well!
3
2
53
4,840
(Before anyone asks, OF COURSE it's about server components, but I now know the story I want to tell.)
1
6
157
Most unexpected part about #ReactSummit is that I now know what I want to give a talk about. Stay tuned.
1
12
880
I'm sorry for not including a whole bunch of lovely people on this list, either I failed catching your full name or couldn't find you on Twitter, please ping me if we talked.
Still parsing so many great discussions and the best part is, there's still another day to go.
1
171
I'm overwhelmed, it's been SO nice meeting you all! ❤️ @jevakallio @elibelly @kadikraman @marcelcutts @SylwiaVargas @TkDodo @nikgraf @cnakazawa @tazsingh @timneutkens @wSokra @feedthejim @PhilippSpiess @acemarke @trastknast @marijanajdova @mweststrate @mhevery @danieljcafonso
3
21
2,009