You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I’m currently evaluating Re.Pack as an alternative bundler for a React Native project and I’d like to clarify its compatibility with the Expo ecosystem.
Specifically, I’m trying to understand:
Can Re.Pack run inside an Expo (expo-cli) project?
Since Expo uses Metro by default, I’m wondering whether Re.Pack can be integrated at the project level without ejecting or modifying the native build pipeline.
If integration is not supported, I’d like to confirm if the main blockers are related to the managed workflow, Metro Dev Server assumptions, or Expo's custom build environment.
Is Re.Pack compatible with EAS Build?
If I build the app using EAS Build, is it technically possible to replace Metro with Re.Pack during the native build process?
Does EAS provide any hooks or configuration surfaces that allow overriding the bundler?
Are there known limitations or recommended workarounds?
Context
I’m considering Re.Pack mainly for:
Faster builds (Webpack/Rspack)
Improved code splitting capabilities
Better long-term flexibility for a large-scale application
Before investing more time, I’d appreciate guidance on whether Expo’s current toolchain supports (or plans to support) this level of bundler customization.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hi team,
I’m currently evaluating Re.Pack as an alternative bundler for a React Native project and I’d like to clarify its compatibility with the Expo ecosystem.
Specifically, I’m trying to understand:
Since Expo uses Metro by default, I’m wondering whether Re.Pack can be integrated at the project level without ejecting or modifying the native build pipeline.
If integration is not supported, I’d like to confirm if the main blockers are related to the managed workflow, Metro Dev Server assumptions, or Expo's custom build environment.
If I build the app using EAS Build, is it technically possible to replace Metro with Re.Pack during the native build process?
Does EAS provide any hooks or configuration surfaces that allow overriding the bundler?
Are there known limitations or recommended workarounds?
Context
I’m considering Re.Pack mainly for:
Faster builds (Webpack/Rspack)
Improved code splitting capabilities
Better long-term flexibility for a large-scale application
Before investing more time, I’d appreciate guidance on whether Expo’s current toolchain supports (or plans to support) this level of bundler customization.
Thanks in advance for any clarification!
Beta Was this translation helpful? Give feedback.
All reactions