CLI supports ordering of tasks

Summary:
This gives Frameworks more control in selecting specific tasks and integrating the return types data in their UI.  For example piping `stdout` to the user or using packages like [Listr2](https://www.npmjs.com/package/listr2) to run tasks in parallel and show progress.

The ordering is suggestive (but also enforced by some assertions).  Frameworks are free to do what they want.

The order was implicit in the previous data structure with lists of Tasks, but made it difficult to tap into each async task.

I've also had to rework how we transpile the code if directly executed from the monorepo.  This keeps our:
- flow types valid,
- allows the core-cli-utils package to be built (to generate TypeScript types and a valid npm module), and
- allows direct transpiled execution as a yarn script.

Changelog: [Internal]

Reviewed By: cipolleschi

Differential Revision: D56242487

fbshipit-source-id: a1a18f14a4aef53a98770462c8ebdef4111f0ab4

Author: blakef

.eslintrc.js

@@ -24,7 +24,7 @@ module.exports = {
     // overriding the JS config from @react-native/eslint-config to ensure
     // that we use hermes-eslint for all js files
     {
-      files: ['*.js', '*.js.flow'],
+      files: ['*.js', '*.js.flow', '*.jsx'],
       parser: 'hermes-eslint',
       rules: {
         // These rules are not required with hermes-eslint

packages/community-cli-plugin/src/commands/start/runServer.js

@@ -38,7 +38,7 @@ export type StartCommandArgs = {
   https?: boolean,
   maxWorkers?: number,
   key?: string,
-  platforms?: string[],
+  platforms: string[],
   port?: number,
   resetCache?: boolean,
   sourceExts?: string[],

packages/core-cli-utils/package.json

@@ -2,19 +2,19 @@
   "name": "@react-native/core-cli-utils",
   "version": "0.75.0-main",
   "description": "React Native CLI library for Frameworks to build on",
-  "main": "./src/index.js",
+  "main": "./src/index.flow.js",
   "license": "MIT",
   "repository": {
     "type": "git",
     "url": "git+https://github.com/facebook/react-native.git",
     "directory": "packages/core-cli-utils"
   },
   "exports": {
-    ".": "./src/index.js",
+    ".": "./src/index.flow.js",
     "./package.json": "./package.json",
     "./version.js": "./src/public/version.js"
   },
-  "types": "./dist/index.d.ts",
+  "types": "./dist/index.flow.d.ts",
   "homepage": "https://github.com/facebook/react-native/tree/HEAD/packages/core-cli-utils#readme",
   "keywords": [
     "cli-utils",
@@ -25,8 +25,8 @@
     "node": ">=18"
   },
   "files": [
-    "dist"
+    "src"
   ],
   "dependencies": {},
   "devDependencies": {}
-}
+}

packages/core-cli-utils/src/index.js

@@ -0,0 +1,23 @@
+/**
+ * Copyright (c) Meta Platforms, Inc. and affiliates.
+ *
+ * This source code is licensed under the MIT license found in the
+ * LICENSE file in the root directory of this source tree.
+ *
+ * @format
+ * @oncall react_native
+ */
+
+// Should only used when called in the monorepo when we don't want to use the `yarn run build`
+// step to transpile to project. When used as a vanilla npm package, it should be built and
+// exported with `dist/index.flow.js` as main.
+//
+// The reason for this workaround is that flow-api-translator can't understand ESM and CJS style
+// exports in the same file.  Throw in a bit of Flow in the mix and it all goes to hell.
+//
+// See packages/helloworld/cli.js for an example of how to swap this out in the monorepo.
+if (process.env.BUILD_EXCLUDE_BABEL_REGISTER == null) {
+  require('../../../scripts/build/babel-register').registerForMonorepo();
+}
+
+module.exports = require('./index.flow.js');

packages/core-cli-utils/src/monorepo.js

@@ -24,12 +24,8 @@ type AndroidBuild = {
   gradleArgs?: Array<string>,
 };
 
-async function gradle(
-  cwd: string,
-  ...args: string[]
-): ReturnType<typeof execa> {
+function gradle(cwd: string, ...args: string[]): ExecaPromise {
   const gradlew = isWindows ? 'gradlew.bat' : './gradlew';
-  // $FlowFixMe[incompatible-return] Mismatch between flow and TypeScript types
   return execa(gradlew, args, {
     cwd,
     stdio: 'inherit',

packages/core-cli-utils/src/private/android.js

@@ -39,6 +39,7 @@ type AppleInstallApp = {
   // `xcrun simctl list devices`
   device: string,
   appPath: string,
+  bundleId: string,
   ...AppleOptions,
 };
 

packages/core-cli-utils/src/private/apple.js

@@ -41,6 +41,7 @@ type PathCheckResult = {
 export function isOnPath(dep: string, description: string): PathCheckResult {
   const cmd = isWindows ? ['where', [dep]] : ['command', ['-v', dep]];
   try {
+    const args = isWindows ? ['where', [dep]] : ['command', ['-v', dep]];
     return {
       dep,
       description,

packages/core-cli-utils/src/private/utils.js

@@ -1,9 +1,7 @@
 # OSX
-#
 .DS_Store
 
 # Xcode
-#
 build/
 *.pbxuser
 !default.pbxuser
@@ -23,7 +21,6 @@ DerivedData
 **/.xcode.env.local
 
 # Android/IntelliJ
-#
 build/
 .idea
 .gradle
@@ -35,36 +32,20 @@ local.properties
 !debug.keystore
 
 # node.js
-#
 node_modules/
 npm-debug.log
 yarn-error.log
 
-# fastlane
-#
-# It is recommended to not store the screenshots in the git repo. Instead, use fastlane to re-generate the
-# screenshots whenever they are needed.
-# For more information about the recommended setup visit:
-# https://docs.fastlane.tools/best-practices/source-control/
-
-**/fastlane/report.xml
-**/fastlane/Preview.html
-**/fastlane/screenshots
-**/fastlane/test_output
-
 # Bundle artifact
 *.jsbundle
 
 # Ruby / CocoaPods
-**/Pods/
-/vendor/bundle/
+ios/Pods/
+vendor/bundle/
 
 # Temporary files created by Metro to check the health of the file watcher
 .metro-health-check*
 
-# testing
-/coverage
-
 # Yarn
 .yarn/*
 !.yarn/patches