Sign in

Matt Carroll

@mattcarrollcode.com
1.2K followers 161 following 22 posts

React at Meta mattcarrollcode.com

PostsRepliesMedia
Reposted by Matt Carroll
React @react.dev · 06/06/2025
The in-person ticket lottery drawings begin today. Sign up for a chance to purchase tickets to attend React Conf in person:
forms.reform.app
Join the React Conf Ticket Lottery
This form is created with Reform - A form builder for creating clean, on-brand forms. No code required.
0102
Reposted by Matt Carroll
React @react.dev · 06/06/2025
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!
React Conf 2025 speakers: Jack Herrington, Joe Savona, Luna Wei, Lydia Hallie, Mofei Zhang, Seth Webster, and Shruti Kapoor
2588
Reposted by Matt Carroll
React @react.dev · 08/04/2025
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
https://conf.react.dev
25213
Reposted by Matt Carroll
React @react.dev · 28/03/2025
React 19.1 has just been released! Check out the latest updates here: github.com/facebook/rea...
github.com
Release 19.1.0 (March 28, 2025) · facebook/react
Owner Stack An Owner Stack is a string representing the components that are directly responsible for rendering a particular component. By combining Owner Stacks with Component Stacks, you can bette...
115031
Reposted by Matt Carroll
Devon Govett @devongovett.me · 18/03/2025
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
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>
  );
}
915920
Matt Carroll @mattcarrollcode.com · 26/02/2025
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
120
Matt Carroll @mattcarrollcode.com · 26/02/2025
It was mostly authored by @ricky.fm
110
Matt Carroll @mattcarrollcode.com · 20/02/2025
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
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.
010
Matt Carroll @mattcarrollcode.com · 20/02/2025
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.
130
Matt Carroll @mattcarrollcode.com · 20/02/2025
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.
110
Matt Carroll @mattcarrollcode.com · 20/02/2025
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.
140
Matt Carroll @mattcarrollcode.com · 20/02/2025
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...
github.com
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...
150
Matt Carroll @mattcarrollcode.com · 18/02/2025
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
010
Matt Carroll @mattcarrollcode.com · 18/02/2025
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.
010
Matt Carroll @mattcarrollcode.com · 18/02/2025
And what is the LLM trained on?
110
Matt Carroll @mattcarrollcode.com · 18/02/2025
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.
130
Matt Carroll @mattcarrollcode.com · 18/02/2025
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-...
react.dev
Build a React app from Scratch – React
The library for web and native user interfaces
130
Matt Carroll @mattcarrollcode.com · 18/02/2025
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
110
Matt Carroll @mattcarrollcode.com · 18/02/2025
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
110
Matt Carroll @mattcarrollcode.com · 18/02/2025
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.
170
Matt Carroll @mattcarrollcode.com · 18/02/2025
Don't forget @en-js.bsky.social too!
020
Matt Carroll @mattcarrollcode.com · 14/02/2025
react.dev/blog/2025/02...
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.
170
Matt Carroll @mattcarrollcode.com · 17/12/2024
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...
github.com
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...
040
Matt Carroll @mattcarrollcode.com · 17/12/2024
Working on adding it to the docs here: github.com/reactjs/reac...
github.com
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
010
Matt Carroll @mattcarrollcode.com · 17/12/2024
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
120
Reposted by Matt Carroll
Ricky @ricky.fm · 12/12/2024
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.
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
1219215
Matt Carroll @mattcarrollcode.com · 12/12/2024
What's causing all the trouble?
130
Reposted by Matt Carroll
Ricky @ricky.fm · 10/12/2024
a lot of the re-render "fixes" people are sharing have no perceivable impact other than seeing less of the highlights flashing
1515815
Matt Carroll @mattcarrollcode.com · 05/12/2024
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...
react.dev
React Compiler Beta Release – React
The library for web and native user interfaces
1131
Reposted by Matt Carroll
React @react.dev · 05/12/2024
React v19 is now stable! react.dev/blog/2024/12...
react.dev
React v19 – React
The library for web and native user interfaces
321279340