Matt Carroll
@mattcarrollcode.com
Reposted by Matt Carroll
The in-person ticket lottery drawings begin today. Sign up for a chance to purchase tickets to attend React Conf in person:
Join the React Conf Ticket Lottery
This form is created with Reform - A form builder for creating clean, on-brand forms. No code required.
forms.reform.app
June 6, 2025 at 7:35 PM
The in-person ticket lottery drawings begin today. Sign up for a chance to purchase tickets to attend React Conf in person:
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
February 26, 2025 at 10:14 PM
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
There are already shared packages checked into the React codebase for Parcel, Turbopack, and others in various states of completeness.
github.com/facebook/rea...
github.com/facebook/rea...
react/packages/react-server-dom-parcel at main · facebook/react
The library for web and native user interfaces. Contribute to facebook/react development by creating an account on GitHub.
github.com
February 20, 2025 at 12:26 AM
There are already shared packages checked into the React codebase for Parcel, Turbopack, and others in various states of completeness.
github.com/facebook/rea...
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.
February 20, 2025 at 12:26 AM
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.
February 20, 2025 at 12:26 AM
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.
February 20, 2025 at 12:26 AM
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...
The PR is for a shared package that would support building RSC with Vite.
github.com/facebook/rea...
React server dom vite by jacob-ebey · Pull Request #31768 · facebook/react
Summary
This adds a new react-server-dom-vite package implementing the RSC touch points in a way that is suitable for use with the Vite bundler.
Differences from other implementations:
No prescrib...
github.com
February 20, 2025 at 12:26 AM
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...
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
February 18, 2025 at 9:13 PM
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.
February 18, 2025 at 9:10 PM
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?
February 18, 2025 at 7:50 PM
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.
February 18, 2025 at 6:02 PM
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-...
Build a React app from Scratch – React
The library for web and native user interfaces
react.dev
February 18, 2025 at 6:02 PM
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
February 18, 2025 at 6:02 PM
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
February 18, 2025 at 6:02 PM
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
Don't forget @en-js.bsky.social too!
February 18, 2025 at 5:32 PM
Don't forget @en-js.bsky.social too!
February 14, 2025 at 7:14 PM
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'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...
Upgrade to React 19, Next 15.1 and enable React Compiler by mattcarrollcode · Pull Request #6996 · reactjs/react.dev
This change upgrades react.dev to React 19, Next 15.1, TypeScript 5.7.2, enables the React Complier, and removes the patches for next, next-remote-watch and removes the patch-package package.
Previ...
github.com
December 17, 2024 at 12:40 PM
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'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...
Working on adding it to the docs here: github.com/reactjs/reac...
Add troubleshooting section for hanging refs when using ref callback cleanup functions by mattcarrollcode · Pull Request #7372 · reactjs/react.dev
Inspired by this post
Preview
github.com
December 17, 2024 at 10:23 AM
Working on adding it to the docs here: 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...
codesandbox.io
December 17, 2024 at 10:15 AM
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...