Expo Router v5 is stable with API Routes in production
Expo has announced that Expo Router v5 is now officially stable. According to the Expo team, the release focuses mainly on stability and reliability on native, along with more full-stack functionality and performance improvements.
Errors, logging and linting
React Native's default error logging in Expo CLI has been redesigned. Stack traces are now human-readable, the most useful frame prints a code preview, and the [NOBRIDGE] tag has been removed. The default ESLint rules were improved and enabled in the starter template, and npx expo lint can be used as a drop-in replacement for npx eslint with Expo-first defaults. Using it also prepares projects for React Compiler.
API Routes and React Server Functions
API Routes, introduced experimentally in Expo Router v3, now have first-class support for deploying servers alongside native builds via EAS Hosting. Server output can be enabled in app.json, and the experimental EXPO_UNSTABLE_DEPLOY_SERVER environment variable builds, deploys and links versioned deployments to the app.
React Server Functions are available in beta. They provide typed server endpoints with access to secret environment variables, respect platform extensions like .ios.ts, support process.env.EXPO_OS, and can return JSX streamed to the client. Open-source demos include an Expo AI Chatbot, a Spotify client and a Movies demo.
React 19
Expo Router v5 uses React 19. With Expo SDK 53, React 19.1 can be enabled as an experimental canary to use the owner stack system. Expo plans to make React 19.1 the default in Expo Router v6 / SDK 54 later in 2025.
Navigation changes
- A new
<Stack.Protected />semantic performs client-side redirects for entire groups of routes. location.reload()reloads the Hermes engine and clears runtime React/JavaScript state, for example on sign-out.- Server redirects and rewrites can be configured statically in
app.json, and EAS Hosting applies them automatically. initialRouteNameis now calledanchor;unstable_settings.initialRouteNamecontinues to work for migration.- The push behavior that removed a duplicate route and re-added it to the top of the stack is now only available under the
dangerouslySingularflag.
Additional improvements
- A new
prefetchprop on<Link />eagerly loads routes. - The Streams API (
ReadableStream,WritableStream,TransformStream) is available on all platforms. - A babel polyfill for
import.meta.urlwas added, and Metro now uses ESM package exports by default. package.jsonsubpath imports are supported.- Bundling starts about 4x faster thanks to a lazy crawling architecture in Metro.
- A new
npx expo servecommand tests production servers locally afternpx expo export. - Projects using
expo-dev-clientcan be deployed to TestFlight. - Environment variables now support HMR in development.
The announcement also points to a livestream in which Mark Lawlor and Keith Kurak cover Protected Routes in Expo Router v5.
Example
"use server"
import { Image } from 'react-native';
export async function renderProfile(username: string) {
// Securely perform data fetching and access secrets...
const profile = await fetch('...').then(res => res.json());
// Return some React JSX——these are React Server Components.
return <Image source={{ uri: profile.picture }} />
}
Video
Expo Router v5 Livestream YouTube
Links
Source: expo.dev