[Fabric] run-windows
Script Should Work By Default on Fabric
#12026
Labels
Area: CLI
Area: Fabric
Support Facebook Fabric
bug
New Architecture
Broad category for issues that apply to the RN "new" architecture of Turbo Modules + Fabric
Milestone
Currently when you try to build a Fabric app using the CLI the script will fail with an error message that the app cannot be deployed. This makes sense because Win32 apps do not bundle and are not deployed. We should make a design decision here if Fabric apps should have to explicitly specify
--no-deploy
in order forrun-windows
to succeed, or should the script be adjusted to detect if the app is on the old or new architecture and adjust its behavior accordingly. There are other behavior options here; these are just some examples.The text was updated successfully, but these errors were encountered: