React 19 is finally out!

[@iceinvein]

React 19 is here but nobody can upgrade as all the dependencies will take another year to catch up

[@mzf11125]

True

[@LatenightDev]

hahah

[@teslagaming2076]

Haha agreed, but I think some of the dependencies that work for nextjs could work with react19 because of the server component architecture

[@tanavposwal]

my app fucked up when is upgraded to react 19

[@Eckster]

Just upgraded at work today, no issues 👍

[@lolhp._.]

I have to wait till React 20 so that all the dependencies upgrade to react 19

[@kadoosh]

This, or you start contributing with PRs. That would help everybody, including you.

[@kadoosh]

This, or you start contributing with PRs. That would help everybody, including you.

[@lonewolf36s]

Welllllll shit. I still haven't finished upgrading all my company projects to react 18. Man, feel like I'm circling a black hole sometimes.

[@xyzzy12345]

Diffs for hydration errors! DIFFS FOR HYDRATION ERRORS!

[@MadsterV]

about time

[@BigBrotha3459]

This guy knows how to make engaging ads

[@KoenVerheyen]

[@leomotta5376]

Migrated and some of my refs stopped working without any errors or warning

[@sK0pe-d9b]

Typical React

[@lessko9]

How?

[@maciekdeveloper]

@@lessko9 Probably how you pass refs in react 19

[@lev1ato]

bolt is actually really nice, I have used it multiple times to start a project, then export it and continue with cursor or windsurf

[@zacharyebenfeld4137]

Would be cool if it could detect hydration errors caused by chrome extensions

[@SandraWantsCoke]

it can. ColorZilla Chrome extension causes one.

[@zacharyebenfeld4137]

@ yeah I mean if it could tell you that the hydration error is coming from the extension and not from your app

[@Bhannat1234]

hi - compiler demo is awesome 22:41, do you have demo code shared publicly ..?

[@JayPowAtWork]

yeah that would be awesome

[@waleedsharif618]

Why they did not mention anything about React compiler when React 19 was released few days ago ?

[@semerset]

Yeah, as I remember they planned to release the compiler in this version 🤔

[@its4zahoor]

It is unstable and released as a babel plugin "bable-plugin-react-compiler"

[@Lemmy4555]

it's beta and has been decoupled from react 19, now is a babel plugin

[@ivanmaglica264]

Do I need to run Next to get server-side React, or can I get the functionality in regular Express or something similar and import server-side React as library?

[@ItsTheSameCat]

Fun stream. Had to watch the video to refresh my memory though. Thanks Theo!

[@deestort]

rendering content on server vs client ads $$$ for your apps. client rendering is free. server rendering costs a lot

[@miran248]

Except you need to do ssr for seo reasons, so you end up doing both.. :D

[@_kostant]

Really depends on your users’ needs. I won’t be adding ssr for our app any time soon. We keep out marketing material separated from our users’ applications. seo just isn’t required for a web app when it is complimentary to your product, not the product itself. And so I agree that ssr just for the sake of it is just throwing $$$ in the wind. (just saying the choice is not just binary in either direction) ¯\_(ツ)_/¯

[@deestort]

@@miran248 time to first whatever is not that important for SEO.

[@deestort]

@@_kostant Yea.. most people overindex on time to render for SEO even though it barely matters .. not as much as authority .. optimizing SSR workflows is the biggest joke on the web world now

[@aleksd286]

Oh wow, the Taxi company released a product for Devs

[@Igstefano]

I wasn't around yet in the front-end world when the whole Class Components -> React Hooks transition started. How would you gauge the change in mental model then versus now? As in, I heard people were pretty resistant to the change back then; but nearly no-one would go back to Class Components nowadays. Do you see the same thing happening?

[@User948Z7Z-w7n]

100%. In frontend if you refuse to follow the trend you fall quick

[@ceigey-au]

@@Igstefano it was messy but to be honest React’s class components were written in a clunky way, because method calls as event handlers had to be either called in a throwaway arrow function or bound to the `this` context of the class in the constructor. And state management was sort of bolted on. So functions + hooks were simpler after an adjustment period. But some people were pretty annoyed and went to Vue (then got mad when Vue adopted the composition API and then they came back to React) or Svelte (which had a barebones ecosystem at the time). This also coincided with when Redux and MobX were falling out of fashion and alternatives like Zustand and atoms/jotai became more popular, more people were using immer, and then swr and more importantly React Query became popular later and by that point the ecosystem was unrecognisable. So it wasn’t just class > funcs but also redux > anything but redux at the same time. The gradual transition helped a lot though.

[@psychoedge]

The difference isn't as huge as you think. Most components can be rewritten fairly quick. Even Vue now offers a hook-style API and I enjoyed it a lot.

[@Igstefano]

@@psychoedge agreed, it isn't a huge difference. It is, though, big enough to generate resistance, as all change does. My question was more about if it's following a historical pattern or not.

[@deestort]

if something is not intuitive it’s generally not a good idea

[@gluvez]

the wait is over

[@jamesbotwina8744]

Thanks!

[@t3dotgg]

🙏

[@LutherDePapier]

React 19 does not control your server or something like that. React is a library, not a framework. As such, it only controls stuff over which React as agency: modules that export components, modules marked with directives, and modules that export Server Functions. For anything else, you're on your own, and you'll see the errors and the security issues in production soon enough.

[@vinialves12362]

Right but when Nextjs performant dev server?

[@phillipedequeiroz6296]

Which draw editor you use in the video?

[@Ubervisor_]

It's Excalidraw! :)

[@xyzzy12345]

So does this kill Module-Federation?

[@eldarshamukhamedov4521]

Module federation was always 1) a bundler feature, and 2) a client-side feature. In theory, if you stick to client-side components, you should still be able to do module federation the same way it worked in older versions of React. If you want the client/server weave via RSC, I haven't seen any existing solutions yet. You'd want some client-side runtime that's able to stream in server-rendered JSX and bootstrap it from multiple decomposed React servers, or, perhaps have your app shell React server merge streams from multiple sources on the server somehow. Theoretically possible, but not sure if anyone's gotten this working yet.

[@simonhartley9158]

Someone went and said the static part out loud.

[@SeanGill12]

OK legends, can someone tell me the best tech stack to get right. I see crazy updates from tailwind, gsap and now react. What are the exact versions that would lead to the optimal building of a frontend platform? I'm perfectly fine finetuning an LLM to the notation of the new libraries. Just eager for some opinions!

[@24u83qyui3yr8932yi3q]

What’s your theme in cursor?

[@smokenmirrorzYT]

poimandres

[@TruongNguyen-cp9dd]

my

[@sudonur]

Astro 🚀all the way baby!

[@3urobob]

Theo over-dramatising the premise in the first 20 seconds of the video as per usual. Actually, dramatising everything. Bro, it's just the web

[@codestacklab]

we really know nextjs , but still it sucks, the worst thing is we cannot share the data across pages , like fetching at one place , and we have to do alot of things for it, like you have mentioned .

[@SiddharthPant]

Finally I can use React 18 and upgrade to 19 next year😂

[@jeremynguyen-fu8tc]

"React 19 is here but nobody can upgrade as all the dependencies will take another year to catch up" It's not true. Do you guys code react? If you use NextJS or Waku or any React framework, it already used React 19 RC for a while. So react 19 stable version rolled out is not a big change.

[@yojou3695]

a lot of people do not use next and definitely not waku. Most projects are just vite (or even worse webpack) + react router + react

[@jeremynguyen-fu8tc]

@@yojou3695 Ah, yes, I use Remix and React Router as well. Vite 6 has already been released with an environment API, which Remix and React Router need to implement RSC. So, I think it will not take too much time for Remix/React Router.

[@UzHandy]

But inaccessible and it is not working when I tried to install it with npx create-react-app

[@paw565]

React needs some schedule for realeses like angular.

[@lukem7176]

Hey @t3dotgg 🙂, could you please tell us how to store secrets like API KEYS in React? Unfortunately these are visible in a source code of the app 🙏

[@herozero777]

This like is for bolt. Sorry theo, before you could get one the add got in the way 😂😂

[@kasper369]

upgrade existing apps to React 19 will be painful but worth it

[@RemotHuman]

another youtuber forked bolt to support using whatever ai model you want including local ones, instead of claude

[@abdarker1043]

the video i was waiting for

[@LatenightDev]

Well It still make your browser consume 3GB of your PC memory, right ?

[@uspecl]

JS on the client is never the reason your browser consumes such high amounts of ram, it's just the browser itself

[@sK0pe-d9b]

@@uspecl nah it's mostly bad React devs

[@YakovFn]

It's mostly that s take up lot of memory

[@Dnserror88]

Not even a minute in and already trying to sell me crap

[@VinaySharma-ed6fy]

amazing video

[@kevinbueno9174]

19 views nice

[@RexGalilae]

19 comments now

[@nobir98]

That means you're 20th viewer

[@lolingkwarts3999]

What's another way to say first without saying first while being just as vapid 🤔

[@xinaesthetic]

I swear it was on 5678 when I read it, but not as of writing a few seconds later.

[@notthere83]

I don't know - as somebody who loves transparency, I'm not a fan of what the compiler does. Obscuring what's happening doesn't make for great maintainability in my opinion. And given the overhead introduced by memoization, I'm skeptical how often React gets it right. Because without actually running the code or at least using AI, I can't envision how they would be able to reasonably accurately determine what needs to be memoized.

[@tangsi721]

does it mean we can ditch the ridiculous nextjs from now on? 😂

[@TurkeyMaster]

I`m working with NEXT JS for a company and i wish everyday i can uninstall it but its to bloated (api, pages, translations, etc) that i have to work with this s**t until i change the company :(

[@dan_goosewin]

quack

[@ArtemShoobovych]

I feel like these changes do not bustify two years of waiting leave alone a major release

[@hwapyongedouard]

yeah i respected bold 1. it's open source 2. it will make future programmers always juniors

[@alexbrik1802]

It’s so tiresome

[@mattmmilli8287]

I can see your point. NGL I like it though. I think it’s exciting still though. Who wants to do the same thing again and again. I started in the WP/jQuery days and no thx haha

[@ShinSpiegel]

And yet, I’m even more convinced that react use case is even smaller, for the majority of apps and pages doesn’t (and shouldn’t) use react.

[@4ud170r]

no its not stable, npx-create-react app is till having a stroke

[@bruh-qu2uh]

19 likes Bro fell off

[@TJChallstrom916-512]

Love the jacket 👍

[@Arman-kp8jf]

Gj

[@tedchirvasiu]

wher compiler

[@cristian91re]

The only good thing is avoiding Nextjs

[@awaisraza2285]

Still its a library not a framework like Next.js who offers caching, routing, middleware and many more things out of the box.

[@cheesesamwich]

WHY AM I SO EARLY

[@sK0pe-d9b]

because no one cares about React junk

[@koq_utx]

Seriously WTF, Svelte is the one who popularized the Compiler approach and these React people made fun of it and here we are now with a React Compiler, LMAO 🤣

[@race_]

First

[@Lapatate-s1l]

The most useless video en react 19 yet

[@tanavposwal]

react is becoming like php

[@jonnmostovoy2406]

:O

[@kalist8938]

So many new useless things… react become the tech front end with the worse learning curve every year.

[@lessko9]

how

[@mu16zi]

how much shit talking people do about some minor bug fixes and improvements... ohh react 19 looks willd 😒🥱

[@joMojojojo]

But like... did bolt pay you to talk about their paid tool ...? 🥲😄😭

[@PayPer-c1u]

First