Devon Govett

Ok, I didn't know that. Thanks for the response!

btw, I've spent all day playing with Parcel and RSC, and I think it's amazing

Many projects, SPAs and even server node apps, could adopt RSC incrementally thanks to Parcel

Yeah pnpm is a bit strict about dependencies so you have to install @parcel/runtime-rsc into your project.

Yeah that's exactly what it does. If you actually disable it focus will be lost and screen readers will lose their place / no longer hear updates about what's happening. So you either want focus to remain on the button or move somewhere else that's relevant.

Yeah we've been blocked on having to still support old react versions, but maybe we could add it as a feature that only works in newer versions somehow.

Button Documentation for Button in the React Aria package.

There are some important considerations to how you set up the DOM structure and hide the text with css too. Detailed info in our docs: react-spectrum.adobe.com/react-aria/B...

Getting the accessibility right for pending buttons is actually kinda complicated too, which is why we have built in support for it in React Aria. Just swapping between text/spinner won’t usually be announced by a screen reader, and you want the button to remain focusable (not disabled).

Yeah there’s still a lot of web dev stuff on Twitter. Pretty much the only reason I’m still on there. It’s often more like self promotion than actual discussion but it does seem more active.

currently no

btw, all the diagrams in this article are rendered using graphviz in a React Server Component to generate SVG at build time. Super convenient.

Yeah I don’t want to throw anyone under the bus, especially since most of the other implementations aren’t official / complete yet. Next.js works basically like Parcel though. The others may be blocked on supporting a unified module graph.

Wrote an article about how React Server Components integrate with a bundler. It's a deep dive into how code splitting works, how RSCs eliminate network waterfalls, how environment directives like "use client" work, CSS loading, etc. Check it out! devongovett.me/blog/parcel-...

I think you should be able to just do `styled(RACComponent)`. And then you can use the data attributes to style it based on the state

yes, by default it triggers one "page" before coming into view (the video is really slowed down here so you can actually see the spinners). That can also be customized via the scrollOffset prop.

All React Aria Components now pass through global DOM events and attributes. This improves React Aria's interoperability with other libraries.

For example, you can now use a React Aria button with a Radix Dropdown.

Hopefully this helps make incrementally adopting React Aria much easier!

Our infinite scroll API is pretty cool. You render a special item at the end of your list that triggers its onLoadMore callback when scrolled into view.

This enables a list to have multiple sections from different APIs, or a tree to infinite scroll within each branch.

July 22, 2025 Release Happy summer! This release adds support for async loading and infinite scrolling, improves form integration and drag and drop interactions, and adds support for additional DOM events and attributes.

New React Aria release!

📜 Infinite scroll in ListBox, GridList, Table, & Tree
⚛️ React 19 actions form reset
🐲 Virtualized Tree drag and drop
🤝 Opened API to DOM events – works better with other libraries
📆 DatePicker autocomplete
🚀 And TONS more!

react-spectrum.adobe.com/releases/202...

parcel/packages/utils/rsc/src/server.tsx at v2 · parcel-bundler/parcel The zero configuration build tool for the web. 📦🚀. Contribute to parcel-bundler/parcel development by creating an account on GitHub.

like this github.com/parcel-bundl...

I would do pre-rendering in the "react-server" environment since it's running in node not in the browser. Just like the express server. Then import only "react-dom/server.edge" and "react-server-dom-parcel/client.edge" with {env: "react-client"}. Then you only need two environments.

Hmm if you’re requesting it in the “react-client” environment you’re gonna get a browser polyfill since node builtins don’t exist there. During SSR, the same bundles that run in the browser will be run in Node (important for client references to work correctly). There’s no SSR-specific environment.

Very happy that Parcel helped enable this! 🤩

Untitled UI React — React Component Library Untitled UI React is the world’s largest collection of open-source React components built with Tailwind CSS and React Aria. Just copy, paste, and build.

Absolutely MASSIVE collection of beautifully designed and expertly crafted components built with React Aria. 🤩

Everything from base components to entire marketing sections and dashboards. Comes with a matching Figma UI kit, CLI, themes, icons, and more.

Incredible.

www.untitledui.com/react

Not yet, I need to add one. Stay tuned here for now

Started writing an article about RSCs from a bundler integration perspective. Might end up being multiple parts though. I realized I needed to explain how code splitting works without RSCs first. Already getting kinda long…

I think people are also hesitant to add Babel back into their build after just managing to remove it in many cases. I know the compiler isn’t really a Babel transform internally but it does add an extra parse/generate step, which can be non-trivial for large apps.

Yeah TS definitely has a very different use case than most apps. No worries, I was just curious.

Definitely agree, but I don't think this is one of those cases. This affects many real-world apps (whether it's a good idea to rely on or not), and that's why webpack/parcel currently wrap modules in many cases. The esbuild/rollup issues also have lots of upvotes/comments.

Curious if you tried destructuring imports and using module-local variables. Most exported values are not re-assigned so don't need the live-binding part of ESM. Could be slightly slower initialization, but at least no repeated object access in hot paths.

Sure. I just think correctness should be the default, and if you want to do potentially unsafe optimizations that should be opt-in. That's already the case for many other optimizations that minifiers perform for example.

True. An alternative could be to destructure exports that are never re-assigned at the top of the module where imported. That could have a similar benefit in many cases.

There are other ways to get similar benefits. Most exports aren’t re-assigned so simply destructuring when imported could work. Priority of constituencies applies to API design and specs, not at the expense of correctness.