Freelance developer - React Query maintainer - Occasional OSS contributor - Been putting React on servers for a decade - Father of two - Homebrewer

Stockholm
Fredrik Höglund retweeted
📣Lighthouse 6.0 is out! Introducing new metrics to track Core Web Vitals, an updated performance score, multiple new audits, and more. Read the full details: web.dev/lighthouse-whats-new…
21
631
1,701
Fredrik Höglund retweeted
👋 We're looking forward to releasing Lighthouse 6.0 (final) soon with support for Core Web Vitals and other goodness. Look out for an official post from the team next week! 👀
5
121
563
.@pmmmwh Nice work on github.com/pmmmwh/react-refr… v0.3! 🎉 The new dev/hot-middleware support means we can use it in our SSR-setup and it's working great!
1
1
@ManuelBieh I think you were interested in this? 👆
2
1
This was a great read and something that has been on my mind a lot lately. brandonsmith.ninja/blog/libr…
1
Oh how I wish trailing status codes were a thing..
1
2
.@tannerlinsley I just read through the react-query docs from start to finish, fantastic work on both the library and docs! 💯 Quick question, did I understand it correctly that queryCache with methods is not available at all on the server?
2
1
I did some testing and that seems correct. I opened an issue here to discuss SSR: github.com/tannerlinsley/rea… 🥰
1
I'm leaning towards building a decently complex custom solution on top of this, involving custom SSR and something that works a bit like getServerSideProps from Next.js.
2
Fredrik Höglund retweeted
Introducing Web Vitals: web.dev/vitals - quality signals key to delivering great UX on the web. Lighthouse, PageSpeed Insights, DevTools & more tools will support many Core Web Vitals soon.
14
569
1,702
I've written a blog post about why and how we are tweaking the navigation and loading experiences at @PriceRunner with tiered loading states, inspired by the work done on #React Suspense. This post focuses on #UX, stay tuned for a technical follow up. medium.com/pricerunner-tech/…
2
6
One of the hardest parts about this was implementing a temporary solution for manual scroll restoration. We don't have a good cache for most of our data yet, so we fetch again when going Back which means restoration has been broken in places. Still not perfect, but better.
1
I have so many more ideas. We can't stop to refactor our large existing app into new frameworks or solutions over night, so I'm trying to bring some of the best ideas into our custom setup instead so we can get immediate benefits, while buying time to incrementally move forwards.
1
This looks like good news indeed. The scope of the Blocks API seems to be somewhat well defined, exciting!
1
React Blocks is going to be a total gamechanger if it pans out, but will probably take a long time to get to a releasable state. This PR is great if you want to do some digging. github.com/facebook/react/pu…
I’m curious, how many of you are running custom React server rendering setups, as opposed to using a metaframework like Next.js? Poll is for the main project you work on, or what you mostly use, up to you.
29% Next/Gatsby/?
37% Custom SSR setup
17% Only clientside
17% Show me the answers
52 votes • Final results
3
For those of you that do run custom setups, what are your main reasons?
3
Fredrik Höglund retweeted
I think people miss a key point about React performance React makes no attempt at being the fastest virtual dom implementation. Plenty of others can and have done that. Instead React wants to "componentize" your performance What does that mean? Thread:
9
71
406
Fredrik Höglund retweeted
Introducing web-worker: Native universal Web Workers 1️⃣ one import for web + Node 🧰 the same Web Worker API everywhere 🏎 uses worker_threads and native ESM 🕸 zero-cost in the browser 📦 works in npm modules github.com/developit/web-wor…
13
184
815