One engine, native and web
A single Vite/Rolldown plugin pair builds your iOS and Android bundles and a react-native-web companion preview, with one config, one define table, and one platform resolver for .ios / .android / .native / .web.
Vite and Rolldown bundling for React Native and Expo, without Metro — native and web from one engine, any Vite or Rollup plugin, and an Expo Go dev server with Fast Refresh.

Vifx swaps Metro for a single Vite/Rolldown engine across your whole React Native or Expo app. You keep Expo CLI, EAS, and your native projects; you replace the bundler underneath them. You get the standard Vite plugin ecosystem on a native app, an Expo Go dev server with Fast Refresh, a content-addressed cache for warm rebuilds, and scope-hoisted, Oxc-minified release bundles that compile to Hermes bytecode.
Native is the primary target and web is a companion preview built from the same engine. See Vifx vs Metro for the structural differences and the measured numbers.
Vifx is pre-1.0 and experimental. It is validated on one Expo SDK 54 app (about 2,000 modules) and on the Expo SDK 58 default template, on iOS and Android; Expo SDK 55 to 57 are experimental. Keep Metro available for anything Vifx does not cover yet. See Project Status for what has been verified and what is still open.
# Install the CLI, which provides the vifx command
npm install --save-dev @vifx/cli
# Onboard an existing Expo app — writes vifx.config.ts, edits nothing Expo owns
npx vifx setup . --yes --expo-go
# Serve the app to Expo Go, with Fast Refresh
npx vifx expo dev . --expo-go --platform ios
# Build the release bundle + assets for the Xcode / Gradle bundle phase
npx vifx export:embed . --platform ios --dev false \
--bundle-output ios.bundle --sourcemap-output ios.map --assets-dest ./assets# Install the CLI, which provides the vifx command
pnpm add --save-dev @vifx/cli
# Onboard an existing Expo app — writes vifx.config.ts, edits nothing Expo owns
pnpm vifx setup . --yes --expo-go
# Serve the app to Expo Go, with Fast Refresh
pnpm vifx expo dev . --expo-go --platform ios
# Build the release bundle + assets for the Xcode / Gradle bundle phase
pnpm vifx export:embed . --platform ios --dev false \
--bundle-output ios.bundle --sourcemap-output ios.map --assets-dest ./assets# Install the CLI, which provides the vifx command
yarn add --dev @vifx/cli
# Onboard an existing Expo app — writes vifx.config.ts, edits nothing Expo owns
yarn vifx setup . --yes --expo-go
# Serve the app to Expo Go, with Fast Refresh
yarn vifx expo dev . --expo-go --platform ios
# Build the release bundle + assets for the Xcode / Gradle bundle phase
yarn vifx export:embed . --platform ios --dev false \
--bundle-output ios.bundle --sourcemap-output ios.map --assets-dest ./assets# Install the CLI, which provides the vifx command
bun add --dev @vifx/cli
# Onboard an existing Expo app — writes vifx.config.ts, edits nothing Expo owns
bun vifx setup . --yes --expo-go
# Serve the app to Expo Go, with Fast Refresh
bun vifx expo dev . --expo-go --platform ios
# Build the release bundle + assets for the Xcode / Gradle bundle phase
bun vifx export:embed . --platform ios --dev false \
--bundle-output ios.bundle --sourcemap-output ios.map --assets-dest ./assetsBare React Native projects start with vifx init and serve through vifx dev. See the Getting Started guide for the full walkthrough.
Add a vite.config.vifx.ts and Vifx merges it after its own plugins, so platform resolution stays correct while your plugins run against the React Native bundle.
// vite.config.vifx.ts
import { defineConfig } from "vite";
import svgr from "vite-plugin-svgr";
export default defineConfig({
plugins: [svgr()],
});Vifx owns the keys it must — platform resolution, the define table, and the native output format — and warns when a user override is neutralized. Everything else is yours. See Config for the merge contract.
vifx.config.ts and vite.config.vifx.ts contracts.