Repository navigation
Conversation
Drop code paths for React Native < 0.79: the pre-0.79 HMRClient named exports, text/plain symbolication requests, the enableNewDebugger dev-middleware experiment, the <= 0.73 Android CallInvoker sources and the pre-0.76 / AGP < 7.3 Android build branches. The pod now uses React Native's min_ios_version_supported deployment target. projectRoot is still passed to dev-middleware, which requires it before 0.83.
Remove ModuleFederationPluginV1 and the Federated helpers, and point ModuleFederationPlugin at ModuleFederationPluginV2. Module Federation support now targets @module-federation/enhanced 2.x: runtime plugins use the ModuleFederation/ModuleFederationRuntimePlugin types, runtime plugins passed as [path, options] tuples are kept, and the warning filter for the 0.x runtime build is gone. The repack-expo doctor treats ModuleFederationPlugin as V2, the MF V1 tester app is removed, and the integration tests cover the 2.0 floor only.
Remove ChunksToHermesBytecodePlugin, getPublicPath, the --webpackConfig CLI option, the commands/rspack and commands/webpack entry points and reanimatedModuleRules. OutputPlugin now rejects the no-op output.bundleFilename, output.sourceMapFilename and output.assetsPath options.
Require Node.js 22.12, React Native 0.79 and @module-federation/enhanced 2.0 in package manifests, compile for Node 22 and drop Node 18/20 from the CI matrix. Update dependencies that were held back by the old floors: vitest 5 with vite 8 (now an explicit peer), @types/node 22, @rslib/core 1, open 11, and execa 10, chalk 6, yargs 18 and @manypkg/find-root 3 in repack-init. Move the Module Federation type dependencies to 2.8.0, lift the terser-webpack-plugin 5.5.0 pin and drop the unused @types/react-dom. Remove the commands/* export for the deleted entry points.
Add a Re.Pack 5 to 6 migration guide, update the minimum requirements, remove the ModuleFederationPluginV1 and --webpackConfig references and switch examples to the unified commands entry point. Add changesets.
Load DevLoadingView and AssetSourceResolver through their default exports only, drop the dev-only __REACT_NATIVE_*_VERSION__ globals that existed to pick between them, and remove the NDK < 27 page-size flag, the merged libreactnativejni.so exclude and the AGP 7.3.1 buildscript from the Android library. ScriptManagerPackage now extends BaseReactPackage and uses the non-deprecated ReactModuleInfo constructor.
React Native 0.82 removed the legacy architecture, so the native module is now built only as a TurboModule. Remove the Android oldarch/newarch spec sources and the IS_NEW_ARCHITECTURE_ENABLED build config field, always apply the React Native Gradle plugin, and read the call invoker from ReactContext instead of CatalystInstance. On iOS, drop the RCT_NEW_ARCH_ENABLED branches; the codegen spec conformance moves into ScriptManager.mm so the public headers stay importable from the pod's Swift module. Reanimated 3 does not support React Native 0.82, so ReanimatedPlugin now requires Reanimated 4 with react-native-worklets and reanimated3ModuleRules is removed. The hermesc fallback stays because React Native 0.82 still ships hermesc inside the react-native package.
Metro has resolved package exports by default since React Native 0.79, and React Native 0.87+ depends on them, so getResolveOptions now defaults enablePackageExports to true. Pass false to resolve through main fields only. Also fix ReanimatedPlugin's warning filter, which no longer matched the setUpTests message from Reanimated 4's Jest utilities after it gained a [Reanimated] prefix.
Replace the deprecated packagingOptions block with packaging, splitting the native library and resource excludes and using keepDebugSymbols for debug builds. The produced AARs are unchanged.
🦋 Changeset detectedLatest commit: 99ca0fb The changes in this PR will be included in the next version bump. This PR includes changesets to release 6 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Resolve conflicts with the dependency security updates (#1486): - apps/tester-federation stays removed - keep vite 8 / vitest 5 from v6 in the catalog - regenerate pnpm-lock.yaml from main's lockfile so its transitive security bumps carry over
Resolve the pnpm-lock.yaml conflict with the metro update (#1488) by regenerating it from main's lockfile with v6's dependency changes applied.
dannyhw
changed the title
dannyhw
added this pull request to stack #1491
October 9, 2026 23:41
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This starts Re.Pack 6. It's limited to raising the minimum supported versions, removing code that only existed for older versions, removing APIs deprecated in Re.Pack 5, and updating dependencies where the new floors allow it. Rspack 2 support will come in a follow-up PR.
New minimum versions
>=18>=22.12>=0.74>=0.82(New Architecture only)@module-federation/enhanced>=0.6.10>=2.0.0react-native-reanimated(plugin)>=3>=4The 0.82 floor is in its own commit (
feat!: require React Native 0.82), so reverting that commit gets back to a 0.79 floor if we decide 0.82 is too aggressive. 0.79 matters for Expo SDK 53, and 0.81 for SDK 54. Node 22.12 is the release whererequire(esm)is no longer behind a flag.Breaking changes
React Native
IS_NEW_ARCHITECTURE_ENABLEDbuild config field and the conditional Gradle setup. The module extends the generated spec directly and gets the call invoker fromReactContext.RCT_NEW_ARCH_ENABLEDbranches. The codegen conformance is declared inScriptManager.mm, so the public headers can still be imported from Swift.HMRClient,DevLoadingView/LoadingViewandAssetSourceResolverinterop__REACT_NATIVE_{MAJOR,MINOR,PATCH}_VERSION__globalstext/plainsymbolication requestsenableNewDebuggerdev-middleware experimentCallInvokersources for RN <= 0.73buildscriptBaseReactPackageand the current Gradle DSLmin_ios_version_supportedinstead of iOS 12.Module Federation
ModuleFederationPluginV1and theFederatedhelpers.Repack.plugins.ModuleFederationPluginis now an alias ofModuleFederationPluginV2.apps/tester-federation(the V1 app) is removed.Removed deprecated APIs
ChunksToHermesBytecodePlugin(useHermesBytecodePlugin)getPublicPath--webpackConfigoption (use--config)@callstack/repack/commands/{rspack,webpack}entry points (use@callstack/repack/commands)reanimatedModuleRulesOutputPluginnow rejects the no-opoutput.bundleFilename,output.sourceMapFilenameandoutput.assetsPathoptions.Behaviour
getResolveOptions()now defaultsenablePackageExportstotrue, which matches Metro since RN 0.79. RN 0.87+ needs it anyway.templates/configs still passtrueexplicitly, becauserepack-initdownloads them frommainand a 5.x init would otherwise pick up Re.Pack 5'sfalsedefault.Reanimated plugin
ReanimatedPluginnow throws for it and always requiresreact-native-worklets.reanimated3ModuleRulesis removed.Fixes found along the way
ModuleFederationPluginV2kept only string entries inruntimePlugins, so[path, options]tuples were silently dropped. It now keeps them.ReanimatedPluginstopped hiding thesetUpTests/Critical dependencywarning once Reanimated 4 added a[Reanimated]prefix to the message. Tester-app builds are warning-free again on both bundlers.@callstack/repackbuild now runsbuild:jsandbuild:tsone after the other. Babel's--delete-dir-on-startcould delete.d.tsfiles emitted by tsc when turbo ran them in parallel.Dependency updates
@rslib/core0.6 → 1.0vitest4 → 5 andvite7 → 8. The vite 7 hold was only there for Node 18.@types/node20 → 22terser-webpack-pluginis no longer pinned to5.5.0; it's now^5.6.1.@module-federation/enhanced2.x in testers and integration testsopen11execa10chalk6yargs18@manypkg/find-root3Kept on purpose:
~5.105:@module-federation/enhanced< 2.4 needs it. Raising the MF floor to 2.4 would let us lift it.exit-hook4: with v5, Ctrl+C triggers aMaxListenersExceededwarning when stdout is redirected.Docs
Verification
build,typecheckandlintpass. The only lint warning is the existing one inrepack-expo. All 13 test tasks pass.ScriptManager.repack-initsmoke tests (mjs/cjs) and the website build pass.