Skip to content

Vifx, Re.Pack and One ​

Metro is not the only way to bundle a React Native app: Re.Pack and One replace it too, for different needs. This page compares the three as their own documentation described them in November 2026. Their docs, linked under Sources, are the reference: they change faster than this page.

Re.PackOneVifx
What it isA toolkit that replaces MetroA React framework for web and nativeA bundler swap for an existing Expo or React Native app
BundlerRspack by default, or webpackVite; Rolldown for native by default, Metro as an optionVite and Rolldown
Your appUnchangedAdopts One's router (derived from Expo Router) and project conventionsUnchanged, Expo Router included
Expo GoNot covered by its docsNo: native needs a custom buildYes, with Fast Refresh
SetupCommands in react-native.config.js, an rspack.config file, and a change to the Xcode bundle phaseOne's CLI and layout (one prebuild, one run:ios)vifx setup writes vifx.config.ts; Expo-owned files are left alone
Pluginswebpack and Rspack loaders and pluginsVite pluginsVite and Rollup plugins
Built forModule Federation and code splitting (mini apps in a host app)One codebase and one router for web and nativeMoving an Expo app to Vite's tooling without leaving Expo Go

Which one fits ​

  • Re.Pack if you need Module Federation or code splitting, for example to load mini apps into a host app, or if your team already works with webpack or Rspack. Its own docs advise keeping Metro installed for tools that assume it.
  • One if you are starting an app and want web and native from one framework on Vite. For an existing Expo app, adopting it is a move to a new framework rather than a bundler swap.
  • Vifx if you have an Expo or React Native app and want Vite and Rolldown without changing the app, its router or the Expo Go workflow. It is younger than both: Project Status lists what has been validated.

For how Vifx compares with Metro itself, with measurements, see vifx vs Metro.

Sources ​

Released under the MIT License.