feat(expo): add first-class Re.Pack integration

[whydidoo]

Summary

This PR introduces first-class Expo support for Re.Pack through a new @callstack/repack-expo package.

It allows Expo SDK 56 applications using prebuild/CNG to use Rspack and the existing Re.Pack runtime, including ScriptManager and Module Federation v2, without changing the core Re.Pack packages.

The package remains private while we validate the initial integration contract.

What’s included

• An Expo Config Plugin that configures generated iOS and Android projects for Re.Pack.
• An ExpoPlugin for Rspack that owns the required Expo/Re.Pack defaults:
  • Expo Router and plain entry resolution
  • Babel configuration
  • React Native and monorepo module resolution
  • images, density variants, fonts and XML assets
  • EXPO_PUBLIC_* environment variables
  • source maps and symbolication
  • packaged local chunks through ScriptManager
• CLI commands for initial setup and diagnostics:
  • npx @callstack/repack-expo init
  • npx @callstack/repack-expo doctor
• Development, native Release and EAS Build integration.
• Expo Router support without importing Metro runtime behavior.
• Module Federation v2 support using the existing public Re.Pack plugin and ScriptManager.
• Expo host and Expo widget validation applications for iOS and Android.

Module Federation v2

Module Federation remains explicit and application-owned, matching regular Re.Pack behavior.

The implementation supports:

• Expo host → Expo widget
• Expo host → regular Re.Pack MF v2 widget
• packaged local React.lazy() chunks alongside remote widgets
• remotely deployed widget chunks, assets and fonts
• platform-specific iOS and Android manifests
• the existing ScriptManager resolver, storage and security mechanisms

Remote widgets cannot provide native dependencies. Native modules must already be installed and linked in the host application.

Native integration

@callstack/repack-expo init only updates application-owned configuration.

Native changes are applied through the Expo Config Plugin during expo prebuild. The integration does not require users to maintain custom Swift, Kotlin, Gradle or Xcode changes manually.

Development applications are launched with:

npm run repack:start
npm run repack:ios
# or
npm run repack:android

[changeset-bot]

⚠️ No Changeset found

Latest commit: f0d1727

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[vercel]

@whydidoo is attempting to deploy a commit to the Callstack Team on Vercel.

A member of the Team first needs to authorize it.

[dannyhw]

@whydidoo can you check the merge conflicts?

[dannyhw]

I recently updated our react native version to "0.86.0"
also note that we have some of our package versions in catalogs in pnpm workspace
would be good to keep react native versions in sync across projects I think

[whydidoo]

Expo SDK 57 currently expects React Native 0.86.2 and React 19.2.3.
I’ve kept both Expo examples on the same Expo-compatible versions rather than forcing the default catalog versions. We could add a dedicated Expo SDK 57 catalog later to keep those versions centralized as well.