Skip to content

Tweet by pcattori

October 12, 2025

One thing most people don't realize is that 3rd party libraries shouldn't need to add special support for Remix 3. E.g. we don't https://t.co/ekl7wQXg1b to have a "Remix" option like they do for React, Vue, etc. You should be able to use the JS version directly. No need for a wrapper library like `remotion`. I think this will be possible thanks to the native events-based model. So some libraries may work out-of-the-box with Remix 3, and if not they should just need to add events that _all_ frameworks — even vanilla JS — would benefit from. That's the vision for now, but we'll see how close to that we can get. Not sure what you mean by "DOM interactivity testing", but any DOM/browser testing library — Playwright, Vitest, etc. — should work with Remix 3. There's no "adapter layer" necessary for that. For UI libraries: yes, there are a couple essential UI libraries that React has that Remix 3 will need. That's one big reason why we are going to build a component library / design system ala shadcn. So yes, there's a gap here that needs to be filled, but I think that its not as big of a gap as you might think thanks to the events-based interop I mentioned at the beginning.

Author
pcattori
Date
October 12, 2025
Open on X