Skip to content

Bundle native builds with Re.Pack + OXC transform pipeline - #99407

Merged
roryabraham merged 51 commits into
Expensify:mainfrom
callstack-internal:eliran/2733-dotlottie-hermes-parse
Sep 20, 2026
Merged

roryabraham merged 51 commits into
Expensify:mainfrom
callstack-internal:eliran/2733-dotlottie-hermes-parse

Conversation

@elirangoshen

@elirangoshen elirangoshen commented Aug 25, 2026 •

Copy link
Copy Markdown
Contributor

Explanation of Change

This PR switches native (iOS/Android) JS bundling from Metro to Re.Pack (Rspack-based), with a Rust transform pipeline (OXC + SWC) for app source and almost all of node_modules.

What changed

  • Native builds now bundle via Re.Pack: rock builds go through pluginRepack (rock.config.mjs), with the bundler config at config/repack/rspack.config.mjs and a root rspack.config.mjs re-export.
  • App source and all node_modules outside a small allowlist are transformed by the same Rust pipeline: oxc-transform (React Compiler disabled for third-party code; Fast Refresh injection disabled for node_modules, since Re.Pack's refresh runtime does not wrap them), then worklets-loader (Reanimated worklets text-sniff), then cjs-inline-requires-loader (SWC CJS lowering + Metro-style inlined requires). All loaders run with parallel: true worker pools.
  • A BABEL_PACKAGES allowlist (~23 packages) stays on Re.Pack's babel-swc-loader with hermes-parser: Flow-typed React Native core packages, packages that call codegenNativeComponent in shipped JS (they need the RN Babel preset's codegen plugin to register Fabric view configs), and @callstack/repack's own runtime.
  • cjs-inline-requires-loader gained two options:
    • sourcemap: false: prebuilt packages ship multi-source maps that @jridgewell/remapping cannot compose.
    • hermesLowering: true: adds transform-async-to-generator + transform-async-generator-functions, because Hermes cannot parse async generators. The full RN-preset lowering set was measured and rejected as pure size bloat.
  • Merged latest main (React Native 0.86, oxc-transform-react 0.145).

Why

Re.Pack previously ran hermes-parser on every .js file. That parser is pathological on prebuilt, minified single-line files: 95s for one 0.5MB file vs 0.1s with @babel/parser. Metro never pays this cost because its hermesParser option defaults to false.

Results (same machine, same day; cold = cache wiped):

Metric Metro Re.Pack + OXC Delta
Prod bundle, cold 88–94s 54s ~1.7x faster
Prod bundle, warm 11s 2.0s ~5.5x faster
Dev server cold (single platform) 63s 47s ~25% faster
Dev server warm 8s 4s ~50% faster
Minified JS size 38.12MB 35.73MB −6.3%
Hermes bytecode size 45.15MB 46.75MB +3.5%

Hermes bytecode grew 3.5%. The likely cause is duplicated import wrappers from the inline-requires step; a contained loader fix is tracked as a follow-up, and staging ManualAppStartup telemetry will show whether it affects startup.

Known follow-ups

  • CI guard script that re-scans packages for codegenNativeComponent / Flow syntax on dependency bumps, so the BABEL_PACKAGES allowlist can't silently go stale.

Fixed Issues

$ #100202
PROPOSAL: N/A (build tooling change, not a contributor proposal)

Automated Tests

No new automated tests: this PR changes the native bundling pipeline only, not runtime app code. Existing CI (typecheck, lint, Jest) covers the unchanged sources; the bundle itself is verified by building and booting each platform (see Tests).

Tests

  1. Build and boot each native target, sign in, and exercise core flows:
    • iOS standalone simulator build ("New Expensify Dev" scheme)
    • Android emulator (Pixel 9 Pro, developmentDebug)
    • HybridApp simulator build (built with the callstack-repack pod; verify the ScriptManager TurboModule loads on the hybrid RN host)
  2. In each build, verify sign-in completes, the LHN loads, a report opens, and chat messages render and send.
  3. Verify React Native DevTools works end-to-end: console evaluation into live Hermes, Sources panel with working breakpoints and scope panes, React Components tree (React Compiler Memo badges visible).
  4. Verify Fast Refresh: edit a component and confirm the change applies in ~1s without a full reload; edits to non-component modules require a manual reload (Metro parity). Verify the dev menu and LogBox behave as before.
  5. Verify the production bundle compiles cleanly with hermesc -O (bytecode builds without errors).
  • Verify that no errors appear in the JS console

Offline tests

Bundling change only; no runtime network behavior is affected. Launch the app once online, then relaunch offline and verify it boots from the bundled JS and renders cached data normally.

QA Steps

Same as Tests (steps 1–2): build and boot each native platform, sign in, verify the LHN loads, open a report, and send a chat message.

  • Verify that no errors appear in the JS console

PR Author Checklist

  • I linked the correct issue in the ### Fixed Issues section above
  • I wrote clear testing steps that cover the changes made in this PR
    • I added steps for local testing in the Tests section
    • I added steps for the expected offline behavior in the Offline steps section
    • I added steps for Staging and/or Production testing in the QA steps section
    • I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
    • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
    • I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
  • I included screenshots or videos for tests on all platforms
  • I ran the tests on all platforms & verified they passed on:
    • Android: Native
    • Android: mWeb Chrome
    • iOS: Native
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
  • I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
  • I followed proper code patterns (see Reviewing the code)
    • I verified that comments were added to code that is not self explanatory
    • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
    • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
  • I followed the guidelines as stated in the Review Guidelines
  • I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
  • If a new CSS style is added I verified that:
    • A similar style doesn't already exist
    • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))
  • If new assets were added or existing ones were modified, I verified that:
    • The assets are optimized and compressed (for SVG files, run npm run compress-svg)
    • The assets load correctly across all supported platforms.
  • If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
  • If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
  • If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
  • If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
  • If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
    • I verified that all the inputs inside a form are aligned with each other.
    • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
  • I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user flow.
  • If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native Screenshot_1787739833 Screenshot_1787739838 Screenshot_1787739854
Android: mWeb Chrome
iOS: Native Simulator Screenshot - iPhone 17 - 2026-08-26 at 12 15 18 Simulator Screenshot - iPhone 17 - 2026-08-26 at 12 15 37 Simulator Screenshot - iPhone 17 - 2026-08-26 at 12 16 11
iOS: mWeb Safari
MacOS: Chrome / Safari Screenshot 2026-08-26 at 12 32 48 Screenshot 2026-08-26 at 12 32 58 ; web builds still use Rsbuild and are unchanged. Screenshot 2026-08-26 at 12 33 09

Test and others added 27 commits July 21, 2026 09:18
# Conflicts:
#	ios/Podfile.lock
# Conflicts:
#	ios/Podfile.lock
#	package-lock.json
# Conflicts:
#	ios/Podfile.lock
hermes-parser takes ~95s to parse this minified single-line browser
bundle, serializing the whole cold build. It is plain ESM with no
RN-specific syntax, so rspack parses it natively. Cold prod bundle
drops from ~120s to ~48s; dev server cold start from 146s to 78s.
Split the node_modules rule in two: packages that genuinely need babel +
hermes-parser (Flow-typed RN core, codegenNativeComponent libs, Re.Pack's
own runtime) stay on babel-swc-loader; everything else goes through the
same OXC chain as app source (oxc -> worklets -> CJS lowering), with
parallel workers and Fast Refresh disabled for third-party code.

The cjs-inline-requires loader gains two options: sourcemap (prebuilt
bundles ship multi-source maps that remapping() rejects) and
hermesLowering (Hermes cannot parse async generators).

Same-day numbers vs Metro: prod cold 85s -> 50s, dev cold (--platform
ios) 54s -> 53s, dev warm 8s -> 4s, minified JS -3.5%. Boot-verified on
iOS standalone, Android emulator, and HybridApp simulator builds.
…ie-hermes-parse

# Conflicts:
#	ios/Podfile.lock
#	tsconfig.json
@github-actions

ghost commented Aug 25, 2026

Copy link
Copy Markdown
Contributor

⚠️ This PR is possibly changing native code and/or updating libraries, it may cause problems with HybridApp. Please check if any patch updates are required in the HybridApp repo and run an AdHoc build to verify that HybridApp will not break. Ask Contributor Plus for help if you are not sure how to handle this. ⚠️

* Flow) and packages calling `codegenNativeComponent` in shipped JS, which needs the RN preset's
* codegen plugin to register Fabric view configs — without it the app crashes on boot.
*/
const BABEL_PACKAGES = [

ghost Aug 25, 2026

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is why the CI script in the post merge pr is crucial - because when there will be deps or new packages that meet those conditions in the comment and won't added to this allowlist if will crush on boot

Comment thread scripts/run-build.sh

ghost Sep 17, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@elirangoshen Can you please restore --verbose flag here?

@shubham1206agra

ghost commented Sep 18, 2026 •

Copy link
Copy Markdown
Contributor

@elirangoshen Please resolve conflicts so that I can test on xcode 27

eliran goshen added 2 commits September 18, 2026 09:58
…ie-hermes-parse

# Conflicts:
#	ios/Podfile.lock
Keeps build logs verbose as before; this PR should not change run-build.sh.
@elirangoshen

ghost commented Sep 18, 2026

Copy link
Copy Markdown
Contributor Author

@elirangoshen Please resolve conflicts so that I can test on xcode 27

done

@shubham1206agra

ghost commented Sep 18, 2026

Copy link
Copy Markdown
Contributor
Screen.Recording.2026-09-18.at.3.46.58.PM.mov

@elirangoshen App crashes on launch

@elirangoshen

ghost commented Sep 18, 2026

Copy link
Copy Markdown
Contributor Author

Screen.Recording.2026-09-18.at.3.46.58.PM.mov
@elirangoshen App crashes on launch

ok following our discussion I'm investigating it.

@elirangoshen

ghost commented Sep 18, 2026

Copy link
Copy Markdown
Contributor Author

So app is crashing on main too with the same stack trace you sent tome. so issue doesn't seems to be in the pr but in app with xcode 27 and latest main.

maybe we can test it with xcode 26 until main will be fix ? @shubham1206agra
(or wait until fix will be deployed)

@shubham1206agra

ghost commented Sep 20, 2026

Copy link
Copy Markdown
Contributor

Reviewer Checklist

  • I have verified the author checklist is complete (all boxes are checked off).
  • I verified the correct issue is linked in the ### Fixed Issues section above
  • I verified testing steps are clear and they cover the changes made in this PR
    • I verified the steps for local testing are in the Tests section
    • I verified the steps for Staging and/or Production testing are in the QA steps section
    • I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
    • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
  • I checked that screenshots or videos are included for tests on all platforms
  • I included screenshots or videos for tests on all platforms
  • I verified that the composer does not automatically focus or open the keyboard on mobile unless explicitly intended. This includes checking that returning the app from the background does not unexpectedly open the keyboard.
  • I verified tests pass on all platforms & I tested again on:
    • Android: HybridApp
    • Android: mWeb Chrome
    • iOS: HybridApp
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
  • If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
  • I verified proper code patterns were followed (see Reviewing the code)
    • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
    • I verified that comments were added to code that is not self explanatory
    • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
    • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
  • I verified that this PR follows the guidelines as stated in the Review Guidelines
  • I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
  • If a new component is created I verified that:
    • A similar component doesn't exist in the codebase
    • All props are defined accurately and each prop has a /** comment above it */
    • The file is named correctly
    • The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
    • The only data being stored in the state is data necessary for rendering and nothing else
    • For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
    • Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
    • All JSX used for rendering exists in the render method
    • The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
  • If any new file was added I verified that:
    • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
  • If a new CSS style is added I verified that:
    • A similar style doesn't already exist
    • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)
  • If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
  • If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
  • If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
  • If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
  • If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
    • I verified that all the inputs inside a form are aligned with each other.
    • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
  • For any bug fix or new feature in this PR, I verified that sufficient unit tests are included to prevent regressions in this flow.
  • If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
  • I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Screen.Recording.2026-09-18.at.10.25.07.PM.mov
Screen.Recording.2026-09-18.at.10.27.35.PM.mov
Screen.Recording.2026-09-20.at.6.25.19.PM.mov

@melvin-bot
melvin-bot Bot requested a review from roryabraham September 20, 2026 13:22

ghost left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@MelvinBot create a follow-up issues to remove Metro and consolidate on a single Rust-based React Compiler. Simplify surrounding tooling / CI checks. Note that this locks us into Re.Pack, but greatly simplifies repo configs and saves time in CI (including lint).

ghost Sep 20, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

by convention, ID should be capitalized:

sentryDebugIDPlugin

ghost Sep 20, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Did you look at how much we could potentially DRY between the web/rsbuild config and the repack rspack config

@roryabraham
roryabraham merged commit 1678a55 into Expensify:main Sep 20, 2026
@github-actions

ghost commented Sep 20, 2026

Copy link
Copy Markdown
Contributor

🚧 roryabraham has triggered a test Expensify/App build. You can view the workflow run here.

@MelvinBot

ghost commented Sep 20, 2026

Copy link
Copy Markdown
Contributor

Created two follow-ups. I split them because they have different blockers — the compiler consolidation can start now, Metro removal can't.

  • [DX] Consolidate on the OXC React Compiler and delete the Babel one — Jest is the last babel-plugin-react-compiler consumer (jest.config.js:24; the OXC transformer already exists and is used for Reassure runs). Switching it over lets us delete checkBoth.mjs, checkWithBabel.mjs, the divergence audit, the divergence rule in the compliance check, and the second compiler pass that ReactCompilerWorker runs on every linted file. That's the lint saving. Unblocked.
  • [DX] Remove Metro from the repo — metro.config.js, pluginMetro, the BUNDLER=metro switch, the metro / repack split in babel.config.js, and six Metro packages. Blocked: per the comment in rock.config.mjs, HybridApp release builds still bundle via the Gradle plugin's own Metro task, so hybrid bundling has to move onto Rock in Mobile-Expensify first. symbolicate:android / symbolicate:ios also shell out to metro-symbolicate and need a replacement.

Both note the Re.Pack lock-in explicitly. Both are assigned to elirangoshen and linked back to [DX] Replace Metro with Re.Pack + a Rust transform pipeline for native builds.

One sequencing call I left to whoever picks these up: babel.config.js still applies the Babel React Compiler on the BUNDLER=metro path, so deleting the plugin before Metro means a Metro fallback build runs unmemoized. Probably fine — it's a debug escape hatch — but it's a deliberate choice, not an accident.

@OSBotify

ghost commented Sep 20, 2026

Copy link
Copy Markdown
Contributor

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

@github-actions

ghost commented Sep 20, 2026

Copy link
Copy Markdown
Contributor

@OSBotify

ghost commented Sep 21, 2026

Copy link
Copy Markdown
Contributor

🚀 Deployed to staging by https://github.com/roryabraham in version: 9.4.91-0 🚀

platform result
🕸 web 🕸 success ✅
🤖 android 🤖 success ✅
🍎 iOS 🍎 success ✅

@MelvinBot

ghost commented Sep 21, 2026

Copy link
Copy Markdown
Contributor

🤖 No help site changes are required for this PR. I did not create a docs PR.

This is a build-tooling change only. It swaps the native JS bundler from Metro to Re.Pack + OXC and changes how node_modules are transformed. Nothing here changes what a customer sees or does in Expensify, so no article under docs/articles needs an update.

How I checked

The diff has no user-facing surface. Of the 25 changed files, 24 are build config, patches, or lockfiles (config/repack/*, rock.config.mjs, rspack.config.mjs, babel.config.js, package.json, package-lock.json, ios/Podfile.lock, android/app/build.gradle, patches/@callstack/repack/*, knip.json).

The single src/ change is a one-line export of an existing constant:

+export {GUTTER_WIDTH};

in src/styles/utils/generators/TooltipStyleUtils/computeHorizontalShift/index.native.ts:44. It adds no behavior and renders nothing new.

No feature, label, or flow changed. The help site documents product behavior — workspace settings, expense flows, integrations, billing. This PR touches none of them. There are no new or renamed settings, tabs, buttons, or menu items to document, and no changed steps for any existing article.

No article references bundling. I searched docs/articles for metro, bundler, repack, and hermes. The 16 files that matched are all NetSuite articles referring to SuiteBundler and the Expensify Connect bundle — unrelated to the JS bundler.

The performance gains are developer-only. The faster cold and warm bundle times in the PR description describe local and CI build speed, not app startup or runtime performance for customers. Hermes bytecode actually grew 3.5%, and the PR notes staging telemetry will show whether that affects startup. Neither number is something the help site claims or should claim.

@elirangoshen, please review the linked help site PR and confirm it reflects the current behavior. Then mark the linked help site PR Ready for review


view run

@collectioneur

ghost commented Sep 22, 2026

Copy link
Copy Markdown
Contributor

Hey! On an iOS dev build, opening Create expense via the FAB throws View config not found for component RNCViewPager and shows "page not found". It's a gap in the Re.Pack BABEL_PACKAGES allowlist: packages outside it skip babel codegen, so codegenNativeComponent() runs at runtime and falls back to the legacy path, which has no view config in bridgeless mode.

Four packages with codegen specs are missing:

react-native-pager-view
react-native-gesture-handler
@rnmapbox/maps
@ua/react-native-airship
I scanned the iOS and Android bundles from the dev server: these four have surviving codegenNativeComponent( after adding them the count is zero).

Anything bundled by Re.Pack is likely affected, so dev builds (npm run ios / npm run android, standalone and HybridApp) and standalone release bundles. HybridApp release still uses Metro, so production should be fine

Screen.Recording.2026-09-22.at.13.22.09.mov

@OSBotify

ghost commented Sep 23, 2026

Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/lakchote in version: 9.4.91-3 🚀

platform result
🕸 web 🕸 success ✅
🤖 android 🤖 success ✅
🍎 iOS 🍎 success ✅

Bundle Size Analysis (Sentry):

@suneox

ghost commented Oct 14, 2026

Copy link
Copy Markdown
Contributor

Coming from #102623 checklist

This PR added config/repack/cjs-inline-requires-loader.mjs, which lowers node_modules to CommonJS through SWC. SWC injects "use strict" by default, while Metro's @react-native/babel-preset compiles with strictMode: false. That turned a silent no-op into a throw: expo's FormData patch (normalizeArgs) assigns name onto a React Native File, which only has a getter for it. The TypeError: Cannot assign to property 'name' which has only a getter killed every file-upload write (tag imports, ...) and SequentialQueue kept retrying, so the UI spun forever.

Fixed in #102681 by setting strictMode: false to match @react-native/babel-preset.

@elirangoshen

ghost commented Oct 14, 2026

Copy link
Copy Markdown
Contributor Author

Coming from #102623 checklist

This PR added config/repack/cjs-inline-requires-loader.mjs, which lowers node_modules to CommonJS through SWC. SWC injects "use strict" by default, while Metro's @react-native/babel-preset compiles with strictMode: false. That turned a silent no-op into a throw: expo's FormData patch (normalizeArgs) assigns name onto a React Native File, which only has a getter for it. The TypeError: Cannot assign to property 'name' which has only a getter killed every file-upload write (tag imports, ...) and SequentialQueue kept retrying, so the UI spun forever.

Fixed in #102681 by setting strictMode: false to match @react-native/babel-preset.

yes we know it should be ok now

@jmusial jmusial mentioned this pull request Nov 17, 2026
36 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

9 participants