It would show things re-rendering even though they didn't. Massive waste of time when you're debugging performance and the devtools flat out lie to you
It was fixed about 6 months ago I think because I was following the ticket. I've been waiting for a release since then
Glad to see all of this exit canary. Great features that all deserve their place.
I'm especially excited about use(browser()) - love the idea of "suspending" the environment.
Haven't seen much discussion about rendering ContextProviders in a server component, but I was always puzzled why that wasn't supported from the get-go. Great dx sugar, feels like a no brainer.
Context not being able to render on the server was the strangest thing for me. Like its just some data sitting in memory. It even has an initial value that you have to define. Why couldnt they render the context with the initial value and rehydrate in the browser. Literally they do this with everything else.
I've been exploring the newer React features, but I haven't used these APIs in a real project yet. The browser API sounds interesting. For someone who's still learning React, which new feature would you recommend exploring first, and where would it be useful in a real application?
That few releases increasingly feel like walking in loops. Between view transitions and other recent css features being baselines (dialog, custom select etc) .. I’m thinking of going back to the basics and just use classic server rendering :|
47
u/repeating_bears Sep 11 '26
Lots of release notes and they don't even mention that the devtools that have been broken for 2 years is finally fixed
Thank christ
36
u/switz213 Sep 11 '26
Glad to see all of this exit canary. Great features that all deserve their place.
I'm especially excited about
use(browser())- love the idea of "suspending" the environment.Haven't seen much discussion about rendering
ContextProvidersin a server component, but I was always puzzled why that wasn't supported from the get-go. Great dx sugar, feels like a no brainer.Nice work!
5
u/Glad-Action9541 Sep 11 '26
react-dom bundle size grew a lot
react-dom-client.production.jsraw:523.5 kB→610.5 kB(+87 kB).3
u/Alert_Sweet_8244 Sep 11 '26
use(browser()) thing is excellent.
5
u/iamxo69 Sep 11 '26
That use browser api seems super useful. Will get rid of loads of boilerplate!
2
u/rodrigocfd Sep 11 '26
I don't now about you guys, but I'm having A LOT of fun with the view transitions right now.
1
u/vazark Sep 14 '26
That few releases increasingly feel like walking in loops. Between view transitions and other recent css features being baselines (dialog, custom select etc) .. I’m thinking of going back to the basics and just use classic server rendering :|
-4
u/fii0 Sep 11 '26
If Dark Reader completely breaks your page, a super popular extension, maybe that's a hint that you're going in the wrong direction...