New libs created with create-react-native-library > 0.48.9 have a new metro config that we don't support #14634
Labels
bug
Extensions
Tracks issues against community modules and extensions
External
Issue tracked in this repo but change will need to happen in another repo
help wanted
New Architecture
Broad category for issues that apply to the RN "new" architecture of Turbo Modules + Fabric
Workstream: Module Support
Module developers have the requisite tooling and clear path for adding windows support to modules.
Milestone
Problem Description
As part of our
init-windows
script, when applied to a library, we also add windows to any example app present. We mostly use what we're given, but we specifically override the givenmetro.config.js
(as all RN apps, it doesn't work with windows out of the box).Specifically for library example apps (which need to access the library) we incorporate the upstream changes present in
create-react-native-library
's metro config.Starting with
create-react-native-library@^0.49.0
however, they've completely refactored their metro config into some separate packages, and our version doesn't work anymore. Specicially, during bundling, you'll get an error that it can't find the library package anymore.We'll need to figure out how to reconcile the differences.
Steps To Reproduce
create-react-native-library@latest
run-windows
Expected Results
The app runs
CLI version
15.0.0-alpha.2
Environment
Community Modules
No response
Target Platform Version
10.0.22621
Target Device(s)
Desktop
Visual Studio Version
Visual Studio 2022
Build Configuration
ReleaseBundle
Snack, code example, screenshot, or link to a repository
No response
The text was updated successfully, but these errors were encountered: