@radhya/mach 2.0.12 → 2.0.13

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (3) hide show
  1. package/README.md +7 -7
  2. package/dist/index.js +335 -259
  3. package/package.json +1 -1
package/README.md CHANGED
@@ -1,8 +1,8 @@
1
1
  # Mach CLI
2
2
 
3
- **Cloud Build & Delivery for React Native, Expo, and Flutter**
3
+ **Cloud Build & Delivery for Expo, bare React Native, and upcoming Flutter apps**
4
4
 
5
- Mach is a CLI that lets you build, sign, and submit React Native and Expo apps from the cloud. Flutter support is modeled in configuration and documentation so it can be added without changing the command surface.
5
+ Mach is a CLI that lets you build, sign, test, and submit Expo and bare React Native apps from the cloud. Flutter support is planned and already reserved in configuration so the same command surface can support it later.
6
6
 
7
7
  ## Installation
8
8
 
@@ -105,7 +105,7 @@ Installable artifacts are downloaded through Mach public file routes, not raw S3
105
105
 
106
106
  ### Framework Selection
107
107
 
108
- Mach does not auto-detect your app framework during builds. The build framework is declared in `mach.config.json` and is treated as the source of truth:
108
+ Mach supports both Expo apps and vanilla/bare React Native apps. Mach does not auto-detect your app framework during builds. The build framework is declared in `mach.config.json` and is treated as the source of truth:
109
109
 
110
110
  ```json
111
111
  {
@@ -117,11 +117,11 @@ Supported values:
117
117
 
118
118
  | Value | Status | Build behavior |
119
119
  | ---------------- | ------------ | ------------------------------------------------------------------------------ |
120
- | `react-native` | Supported | Uses committed `ios/` and `android/` native projects. No Expo prebuild runs. |
121
- | `expo` | Supported | Runs Expo prebuild before native compilation and applies Expo-specific guards. |
122
- | `flutter` | Planned | Reserved in config/docs. Builds fail clearly until Flutter builders are added. |
120
+ | `react-native` | Supported | For vanilla/bare React Native projects with committed `ios/` and `android/` folders. No Expo prebuild runs. |
121
+ | `expo` | Supported | For Expo projects. Runs Expo prebuild before native compilation and keeps Expo-specific behavior isolated. |
122
+ | `flutter` | Upcoming | Reserved in config/docs. Builds fail clearly until Flutter builders are added. |
123
123
 
124
- `mach init` and `mach link` create `framework: "react-native"` by default. Change it to `"expo"` for Expo projects before running builds. This explicit config prevents a React Native change from affecting Expo projects, and avoids fragile package scanning in CI.
124
+ `mach init` and `mach link` create `framework: "react-native"` by default. Change it to `"expo"` for Expo projects before running builds. Flutter projects should use `"flutter"` only after Flutter builders are released. This explicit config prevents React Native changes from affecting Expo projects, and avoids fragile package scanning in CI.
125
125
 
126
126
  Use the framework guide that matches your app. The command surface stays the same; only `framework` changes the build pipeline:
127
127