React 19 stable is out

The support for optimistic UI should be a good match for Meteor

Also looking forward to Meteor 3 + React 19 SSR support with the following new apis:

  • use()
  • prerender() - does not support streaming content as it comes (addendum: requires changes to Meteor boilerplate)
  • prerenderToNodeStream() - same as above
  • renderToReadableStream() - requires changes to Meteor boilerplate

Erratum:
React 19 SSR is currently not supported by Meteor due to the lack of boilerplate support.

1 Like

I think a big missing piece of Meteor is SSR support.
We can build a website quickly with Meteor, deploy quickly (Galaxy) but then struggle with SEO issues.

1 Like

Because of this, our main app is still at Meteor 2 + React 17. I am working on upgrading to Meteor 3.0 + React 18.3 (canary for the use hook). That should allow us to do SSR using the deprecated renderToNodeStream. I also assume that it will take months for most of our React npm packages to catch up with React 19. By then, there might be progress with Meteor 3 SSR + React 19.

1 Like

I haven’t gotten even as far as SSR yet.
For me right now I will be looking into potentially replacing react-helmet with the new official API to handle headers (if that works outside of SSR that is), another big thing is how form libraries are going to develop with the new form API (probably will have to migrate to a new form library is my guess) and then there is the questions of routing as react-router v7 isn’t yet available in Meteor and while it is backward compatible the new API it is moving towards makes me wonder if it won’t be better for me to go back to Flow Router (will explore that tonight on my stream).
I find it funny that at one point I have been migrating as much as possible to React and now that React is changing towards SSR first it looks like I will be moving a lot of stuff back to Meteor, starting with router.

Have you tried react-helmet-async

You might mean RSC (React Server Components). I see this as a middle ground between PHP templating and SPA. At first, I was scratching my head on RSC. Now that I (supposedly) understand its purpose, I realize how much content handling I am bundling to my SPA, which is a good candidate for RSC. In the end, this is all about UX - an interactive app with a small bundle

Yes, I’m using that one. But in React 19 there is option to handle that by default which I want to try to see if I can reduce dependency. But maybe it will only be for RSC.

Mostly yes, but SSR kind of falls under that as well.

That is interesting, I can see now how that becomes appealing, but I wonder if then it doesn’t become better to move to Hono or something similar.

RSC falls in between SSR and CSR

I don’t know that. Thanks.