Remix Newsletter #36

Audience at Remix Jam 2025 conference in Toronto, with attendees wearing green REMIX JAM lanyards, looking forward during a presentation. Overlaid text reads "Remix NEWSLETTER N° 36 NOV 2025" with topics listed: React Router v7.9.5, Instrumentation API, Remix Jam Recap, and An Outsider's Take on React and Remix.

In this issue of the Remix Newsletter: React Router v7.9.5 is available and includes a new experimental instrumentation API, a recap of Remix Jam and the Remix 3 announcement, and an outside perspective on the different values driving React and Remix's roadmap.

Let's dive in! 💿

React Router v7.9.5 introduces instrumentation APIs, concurrent prerendering for faster builds, and a handful of bug fixes.

Instrumentation (unstable): New unstable_instrumentation APIs let you add runtime instrumentation to server handlers, client navigations and fetches, loaders, actions, middleware, and route.lazy. Track performance, debug issues, and monitor your app's behavior without modifying your route handlers.

Read more about Instrumentation below.

Concurrent Prerendering (unstable): A new prerender.unstable_concurrency option allows you to run prerendering concurrently, which can potentially speed up your build times.

This update also includes a few bug fixes and other improvements:

Ensure action handlers run for routes with middleware even if no loader is present
Ensure route navigation doesn't remove CSS link elements used by dynamic imports
Typegen only registers route module types for routes within the app directory
Add a type-safe handle field to unstable_useRoute() for accessing route-specific handle values
Add unstable_pattern parameter to loaders, actions, and middleware containing the un-interpolated route pattern (e.g., /blog/:slug), useful for aggregating logs and metrics in instrumentation code

Check out the full React Router changelog ↗

React Router's new instrumentation APIs let you add logging, error reporting, and performance tracing without modifying your route handlers. You provide "wrapper" functions that execute around your request handlers, router operations, and route handlers.

You can instrument at three levels: the server handler (all requests), router operations (navigations and fetcher calls), and individual routes (loaders, actions, middleware, and lazy loading).

Here's what it would look like to add instrumentation to your entry.server.tsx in Framework Mode:

Instrumentation API example

Instrumentation is read-only; you can observe what's happening but can't modify runtime behavior. This makes it safe to add to production without introducing bugs. Errors in your instrumentation code are gracefully handled so they don't impact your application.

The purpose of this API is to help you integrate with observability platforms like Sentry, DataDog, or New Relic, implement OpenTelemetry tracing, track user behavior, and monitor performance. You can compose multiple instrumentations and enable them conditionally.

Check out the React Router documentation for Instrumentation ↗

Hand reaching for a Remix Jam CD from 1 of 3 wooden boxes

Last month we hosted Remix Jam at the Shopify offices in Toronto, our first in-person conference since Remix Conf in May 2023. Michael Jackson and Ryan Florence spent over 3 hours unveiling Remix 3, showing how we're building a fullstack JavaScript framework on top of web standards.

Ryan demoed an early prototype of Remix's new interaction and component model, which leans heavily on events, manual updates, and lexical scoping for state management. Michael showed off the server-side pieces, most of which are already on NPM, including @remix-run/route-pattern, @remix-run/fetch-router, and more.

Together, they demoed hydrated() for selective client-side hydration and Frame for async UI. These primitives let you interop hydrated components inside Frames and vice versa. When you mutate data and revalidate, the response is raw HTML that morphs into the existing DOM.

We're aiming to ship the first version of the full-stack remix framework in early 2026. Keep tabs on the remix-run GitHub repository to follow along and stay tuned for more updates in the future.

We also had several amazing speakers in addition to Michael and Ryan:

"Interactive MCP with React Router" by Kent C. Dodds: Making your app agent-friendly with the Model Context Protocol. Kent showed how he built an MCP server that integrates directly with ChatGPT's interface.
"Remixing Shopify's Admin" by Craig Brunner: A peek inside one of the largest React Router apps (~67M daily page views, 3+ million lines of code, 1,000+ routes). Craig showed how they tamed the complexity of the Shopify Admin by leveraging React Router's loader/action patterns, route manifests, and View Transitions to build a highly scalable and maintainable admin interface.
"Building Sidekick: An AI Assistant People Actually Use" by Felipe Leusin: How Shopify built an AI agent that navigates Admin and does real work. Felipe showed how they operate at the framework layer using React Router's loaders/actions and route manifests so the agent can reliably interact with the app.
"Introducing Remix 3 (Part 1): Remixing UI" by Ryan Florence and Michael Jackson: Remix's new events and components model. Ryan demoed building a drum machine with a preview of the component and interaction models he's been developing.
"Introducing Remix 3 (Part 2): Remixing the Server" by Michael Jackson Ryan Florence: Building a JavaScript server from scratch using web standards. Michael showed how packages like @remix-run/fetch-router and @remix-run/route-pattern work together, and demoed hydrated() and Frame for selective hydration and async UI.

Read the full Remix Jam 2025 Recap ↗

Jamie Larson wrote about his takeaways from Remix Jam and offers an outside perspective we enjoyed reading about what we're doing with Remix.

Jamie has spent the last decade shipping production React code and the last two years using Remix. After attending Remix Jam and then watching React Conf 2025, he wrote a thoughtful article about the different values driving React and Remix's respective roadmaps.

Larson argues that React and Remix aren't just taking different technical approaches; they're prioritizing different values. In his words, React focuses on Stability, Composability, and Capability, accepting complexity on developers' behalf (like the React Compiler) to raise the bar for user experience. Remix prioritizes Simplicity, Web Platform Alignment, and Debuggability, choosing explicit control over automatic reactivity.

Larson also raises questions about the tradeoffs: will event-based architecture scale? Is explicit rendering verbose enough to become its own complexity? And how much will Remix 3 change before it settles?

Whether you agree with every point or not, Larson's perspective helps make sense of what's happening in both ecosystems. It's a values decision, not just a technical one.

Read "React and Remix Choose Different Futures" ↗

Remix Meetups are run voluntarily by members of the community all around the globe with in-person and online options. These meetups feature local speakers, hackathons, workshops, and more!

We're excited to share that there's a new Remix Meetup in Miami starting this month!

RSVP for the first meetup on November 11th ↗

Remix Miami

Find other Remix Meetups near you ↗

No meetups near you? Reply to this email if you are interested in starting your own meetup.

If you enjoy getting this email, please let us know! We'd love to hear from you, what you like about Remix and these updates, and any suggestions you have to improve them.

- The Remix Team