Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

React Native Windows 0.83 does not support `REACT_EAGER_TURBO_MODULE` (while 0.81 does)

Open
  • Is something wrong?
#16,479 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
cpp, react-native
Domain
build-system, mobile-dev

Research direction

Compare the REACT_EAGER_TURBO_MODULE change in PR #16093 and its 0.81 backport in PR #16095 with the 0.83 stable branch and 0.83.2 release. Start by locating the macro definition and the Windows build project that includes MainRuntimeInstaller.h; the reported compile error is C4430. Done means the macro is available in 0.83 and the supplied usage compiles.

Written by the indexing model from the issue text.

Description

bug Needs: Triage :mag:
Problem Description

It seems #16093 (the PR introducing REACT_EAGER_TURBO_MODULE), which landed on main and was backported to 0.81 in #16095, was never cherry-picked into 0.83 (it's neither on 0.83-stable, nor the current 0.83.2 npm release).

Steps To Reproduce

Try using REACT_EAGER_TURBO_MODULE, as we do in expo-desktop with React Native Windows 0.81.37:

REACT_EAGER_TURBO_MODULE(ExpoMainRuntimeInstaller);
struct ExpoMainRuntimeInstaller {
  using ModuleSpec = ExpoDesktopModulesCoreCodegen::ExpoMainRuntimeInstallerSpec;

We get a compile-time failure:

× Building Solution: ExpoDesktopStubs.vcxproj -> C:\Users\jamie\Downloads\expod-beta\MyApp\windows\ARM64\Debug\E...
- Build failed with message C:\Users\jamie\Downloads\expod-beta\MyApp\node_modules\expo-desktop-modules-core\windows\ExpoModulesCore\MainRuntimeInstaller.h(26,1): error C4430: missing type specifier - int assumed. Note: C++ does not support default-int [C:\Users\jamie\Downloads\expod-beta\MyApp\node_modules\expo-desktop-modules-core\windows\ExpoModulesCore\ExpoModulesCore.vcxproj]. Check your build configuration.
Expected Results

It should compile just fine.

CLI version

Not using RNC-CLI. Directly using @react-native-windows/cli 0.83.2.

Environment
System:
  OS: Windows 11 10.0.26100
  CPU: (4) arm64 Apple Silicon
  Memory: 421.79 MB / 7.99 GB
Binaries:
  Node:
    version: 24.21.0
    path: C:\Users\jamie\AppData\Local\mise\installs\node\24.21.0\node.EXE
  Yarn:
    version: 1.22.22
    path: C:\Program Files (x86)\Yarn\bin\yarn.CMD
  npm:
    version: 12.0.2
    path: C:\Users\jamie\AppData\Local\mise\installs\npm\latest\node_modules\.bin\npm.CMD
  Watchman: Not Found
SDKs:
  Android SDK: Not Found
  Windows SDK:
    AllowDevelopmentWithoutDevLicense: Enabled
    AllowAllTrustedApps: Enabled
    Versions:
      - 10.0.19041.0
      - 10.0.22621.0
      - 10.0.26100.0
IDEs:
  Android Studio: Not Found
  Visual Studio:
    - 17.14.37614.0 (Visual Studio Community 2022)
    - 18.9.12112.369 (Visual Studio Community 2026)
Languages:
  Java: Not Found
  Ruby: Not Found
npmPackages:
  "@react-native-community/cli": Not Found
  react:
    installed: 19.2.0
    wanted: 19.2.0
  react-native:
    installed: 0.83.10
    wanted: 0.83.10
  react-native-windows:
    installed: 0.83.2
    wanted: 0.83.2
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: true
  newArchEnabled: true
iOS:
  hermesEnabled: Not found
  newArchEnabled: Not found

info React Native v0.87.1 is now available (your project is running on v0.83.10).
info Changelog: https://github.com/facebook/react-native/releases/tag/v0.87.1
info Diff: https://react-native-community.github.io/upgrade-helper/?from=0.83.10&to=0.87.1
info For more info, check out "https://reactnative.dev/docs/upgrading?os=windows".

Done in 35.6s using pnpm v12.11.2
Community Modules

No response

Target React Native Architecture

New Architecture (WinAppSDK) Only

Target Platform Version

None

Visual Studio Version

None

Build Configuration

None

Snack, code example, screenshot, or link to a repository

No response

Dominant language
C++
Stars
17.4k
Forks
1.2k
Avg merge
1d 20h
Merged PRs (30d)
37

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/react-native-windows

All issues in microsoft/react-native-windows

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.