The in-person ticket lottery drawings begin today. Sign up for a chance to purchase tickets to attend React Conf in person:
06.06.2025 19:35
👍 10
🔁 2
💬 0
📌 0
The in-person ticket lottery drawings begin today. Sign up for a chance to purchase tickets to attend React Conf in person:
React Conf 2025 speakers: Jack Herrington, Joe Savona, Luna Wei, Lydia Hallie, Mofei Zhang, Seth Webster, and Shruti Kapoor
We're thrilled to announce that @seth.blue @shrutikapoor08.bsky.social @en-js.bsky.social @zmofei.bsky.social @lydiahallie.com @jherr.dev @lunaleaps.bsky.social will be speaking at React Conf 2025!
https://conf.react.dev
React Conf is back for 2025! Join our co-hosts, Meta and @callstack.com , October 7-8 in Henderson, Nevada or join the free livestream
React 19.1 has just been released! Check out the latest updates here:
github.com/facebook/rea...
Screenshot of code sample: $ parcel server.tsx // server.tsx import express from 'express'; import {renderRequest} from '@parcel/rsc/node'; import {Page} from './Page'; const app = express(); app.get('/', async (req, res) => { await renderRequest(req, res, <Page />); }); app.listen(3000); // Page.tsx "use server-entry"; export function Page() { return ( <html> <body> <h1>Hello world!</h1> <Client /> </body> </html> ); }
Happy to announce Parcel v2.14, now with support for React Server Components! 🥳
RSCs can be integrated into client-rendered apps, server rendered, or statically rendered at build time.
Also: rust MDX compiler, create-parcel CLI, new error overlay, and native import maps.
parceljs.org/blog/v2-14-0
Thanks for trying RSCs out! Its encouraging to hear you can see what we're shooting for with RSCs and appreciate the work being done to maintain composability. If you're up for a chat I'd love to hear more about how you're thinking about the tradeoffs of RSC
It was mostly authored by @ricky.fm
There are already shared packages checked into the React codebase for Parcel, Turbopack, and others in various states of completeness.
github.com/facebook/rea...
I'm very excited about this because there is the potential for frameworks that use Vite like React Router v7 & Redwood to use the same RSC-VIte integration instead of each building their own.
Eventually we'd like to create the right API for RSC so any bundler/framework can implement this API and be confident it won't break.
In its current state, RSC involves integrating the internals of React with a bundler and/or framework. The shared package enables React to avoid breaking the bundler/framework integration.
The "opinionated 'official' way to integrate with Vite" React collaboration is scoped to RSCs.
The PR is for a shared package that would support building RSC with Vite.
github.com/facebook/rea...
I don't think about this problem as hiding complexity but providing recommendation that best serves the audience. Recommending a solution that leads people down a path to yet another rewrite doesn't feel right. Ideally, everyone would understand the tradeoffs and decide for themselves
If you have a solution to bundling, routing, code splitting, and data fetching in a composable way that is just as good as a solution that integrates all of them, I'd genuinely love to see it. With the current landscape I think there are significant advantages to solving these problems together.
And what is the LLM trained on?
This isn't perfect and most of the folks reading this post aren't the primary audience for this page (or react.dev) because they know the tradeoffs already and can make their own, informed decision.
We think there is a place to recommend Vite and that is why we created the "Build a React app from Scratch" page. We wanted to have a place to recommend build tools without leading new React users down a path we can't, in good faith, recommend react.dev/learn/build-...
Its hard to recommend a build tool to someone new to React knowing that they might find themselves needing a different rendering strategy (e.g. CSR, SSG, SSR) per route, with data fetching included
Because react.dev's audience is new users, the recommendations are also tailored to new users. We don't want to recommend a path for new user where they may have to rewrite a significant part of their app to get a feture they figure out they need down the line
react.dev is designed for folks who are new to React or are learning basic React concepts. While we'd love to have docs for more advanced users of React (e.g. libraries, frameworks, build tools, etc.) we don't have the resources to make that happen today.
Don't forget @en-js.bsky.social too!
Do you recommend Vite? We provide several Vite-based recommendations. React Router v7 is a Vite based framework which allows you to use Vite’s fast development server and build tooling with a framework that provides routing and data fetching. Just like the other frameworks we recommend, you can build a SPA with React Router v7. We also recommend using Vite when adding React to an existing project, or building a framework. Just like Svelte has Sveltekit, Vue has Nuxt, and Solid has SolidStart, React recommends using a framework that integrates with build tools like Vite for new projects.
react.dev/blog/2025/02...
That error does look strange. Did you manage to figure it out?
I've been working on migrating react.dev to Next 15.1 from 13.4 and besides some `eslint-disable-next-line`'s and our *unique* MDX compilation and consumption it hasn't been too bad.
github.com/reactjs/reac...
I had trouble understanding this so I wrote an example of the problem as I understand it in a CodeSandbox: codesandbox.io/p/sandbox/ke...
Screenshot of react.dev page for ReactDOM prerender API. Included the title text "prerender renders a React tree to a static HTML string using a Web Stream." and an outline with sections for Reference, Usage, and Troubleshooting
A new React 19 feature that might have gone unnoticed:
ReactDOMStatic.prerender(<App />)
It's like the old renderToString API, but unlike renderToString, prerender will wait for Suspense boundaries to finish before returning the HTML.
What's causing all the trouble?
a lot of the re-render "fixes" people are sharing have no perceivable impact other than seeing less of the highlights flashing
React Complier is separate from React releases. React Complier is currently in beta. React Complier works "out of the box" with React 19 without the `react-compiler-runtime` package that is required to use React Complier on React 17 & 18
react.dev/blog/2024/10...
