Repository navigation
Streamline RNW Community Modules Integration & Creation Process #15078
Copy link
Copy link
Open
Copy link
Labels
Area: Native ModulesArea: Turbo ModulesExtensionsTracks issues against community modules and extensionsTracks issues against community modules and extensionsNew ArchitectureBroad category for issues that apply to the RN "new" architecture of Turbo Modules + FabricBroad category for issues that apply to the RN "new" architecture of Turbo Modules + FabricOld ArchitectureBroad category for issues that apply to the RN "old" architecture of Cxx Modules + PaperBroad category for issues that apply to the RN "old" architecture of Cxx Modules + PaperWorkstream: Module SupportModule developers have the requisite tooling and clear path for adding windows support to modules.Module developers have the requisite tooling and clear path for adding windows support to modules.enhancement
Milestone
Description
Activity
- addedNeeds: Triage 🔍New issue that needs to be reviewed by the issue management team (label applied by bot)New issue that needs to be reviewed by the issue management team (label applied by bot)
on Aug 25, 2025 - changed the title
[-]Streamline Community Modules Integration Process[/-][+]Streamline RNW Community Modules Integration Process[/+]on Aug 25, 2025 - changed the title
[-]Streamline RNW Community Modules Integration Process[/-][+]Streamline RNW Community Modules Integration & Creation Process[/+]on Aug 25, 2025 - addedExtensionsTracks issues against community modules and extensionsTracks issues against community modules and extensionsNew ArchitectureBroad category for issues that apply to the RN "new" architecture of Turbo Modules + FabricBroad category for issues that apply to the RN "new" architecture of Turbo Modules + FabricWorkstream: Module SupportModule developers have the requisite tooling and clear path for adding windows support to modules.Module developers have the requisite tooling and clear path for adding windows support to modules.and removedNeeds: Triage 🔍New issue that needs to be reviewed by the issue management team (label applied by bot)New issue that needs to be reviewed by the issue management team (label applied by bot)
on Aug 25, 2025 - addedOld ArchitectureBroad category for issues that apply to the RN "old" architecture of Cxx Modules + PaperBroad category for issues that apply to the RN "old" architecture of Cxx Modules + Paper
on Aug 25, 2025
Metadata
Metadata
Assignees
Labels
Area: Native ModulesArea: Turbo ModulesExtensionsTracks issues against community modules and extensionsTracks issues against community modules and extensionsNew ArchitectureBroad category for issues that apply to the RN "new" architecture of Turbo Modules + FabricBroad category for issues that apply to the RN "new" architecture of Turbo Modules + FabricOld ArchitectureBroad category for issues that apply to the RN "old" architecture of Cxx Modules + PaperBroad category for issues that apply to the RN "old" architecture of Cxx Modules + PaperWorkstream: Module SupportModule developers have the requisite tooling and clear path for adding windows support to modules.Module developers have the requisite tooling and clear path for adding windows support to modules.enhancement
Add some script or AI prompts to speed up integration and API creation of community module in Windows for New Architecture Fabric.
End goal is to automate steps from creation of spec file to C++ API definitions so that we only need to work on API implementation and not spend time debugging or fixing other cases.
The outcome should be to add windows code in any react native module - For example: https://github.com/react-native-webview/react-native-webview
There can be a 1 line command
yarn react-native setup-module-windowsthat would do everything:yarn react-native init-windows --template cpp-lib. Note: This command creates/updates the windows folder and all the relevant files to the latest implementation.The 1 line command can be "
yarn react-native setup-module-windows" which only works for new architecture cpp-lib for now and internally calls init-windows in step 7.Some work is already done here: PR Please fix it with updated point 1 and below feedbacks: