expo-devbox 0.2.1 → 0.2.2

package/README.md

@@ -70,14 +70,14 @@ Several sessions in one directory help when two agents share a checkout. Each se
 
 ## On the worker
 
-After each change, run `expo-devbox sync`, then run these with `expo-devbox ssh '<command>'`. The `DEVBOX_*` variables are set in every SSH session. After the worker's first build, an incremental build takes a few seconds.
+After each change, run `expo-devbox sync`, then the commands the change needs with `expo-devbox ssh '<command>'`. A JavaScript change needs none: Metro sends it to the running app. A native change needs a build, then install and launch. The rest are for checking the result. The `DEVBOX_*` variables are set in every SSH session. After the worker's first build, an incremental build takes a few seconds.
 
 ```sh
-# Build. Prints errors with file and line, then ** BUILD SUCCEEDED ** or ** BUILD FAILED **, and exits
+# Build, after a native change. Prints errors with file and line, then ** BUILD SUCCEEDED ** or ** BUILD FAILED **, and exits
 # non-zero on failure. The full log is ~/.devbox/build.log.
 set -o pipefail; xcodebuild -workspace "$DEVBOX_WORKSPACE" -scheme "$DEVBOX_SCHEME" -configuration Debug -destination "id=$DEVBOX_SIMULATOR" -derivedDataPath "$DEVBOX_DERIVED_DATA" build 2>&1 | tee ~/.devbox/build.log | grep -E ": (fatal )?error:|\*\* BUILD" | sort -u
 
-# Install and launch the app on the simulator.
+# After a build, install and launch the app on the simulator.
 xcrun simctl install booted "$DEVBOX_APP" && xcrun simctl launch --terminate-running-process booted "$DEVBOX_BUNDLE_ID"
 
 # JavaScript console output and errors (Metro).
@@ -132,7 +132,7 @@ When the user asks for it:
 
 1. Run `bunx expo-devbox help` and follow its "On the worker" section. It has the command for each step: build, install and launch, logs, crash reports and screenshots.
 2. Start a session with `bunx expo-devbox start`. It returns when the worker is ready, and EAS macOS minutes are billed until the session ends.
-3. After each change, run `bunx expo-devbox sync`, then the commands from the help with `bunx expo-devbox ssh '<command>'`.
+3. After each change, run `bunx expo-devbox sync`, then the commands from the help that the change needs, with `bunx expo-devbox ssh '<command>'`.
 4. Commands use the session you started last in this directory. If another agent works in the same directory, pass your session's ID, which `start` prints, to every command: `bunx expo-devbox ssh --session <id> '<command>'`.
 5. When the user is done with the devbox, run `bunx expo-devbox stop`.
 ```
@@ -153,8 +153,7 @@ The workflow runs one custom job on `macos-large` in the `development` environme
 
 `sync` sends what git would track. Patterns from `.gitignore` are excluded, so local secrets such as `.env.local` stay local and files that the worker generated are not deleted. `.gitignore` lines that start with `!` are not supported.
 
-> [!NOTE]
-> SSH support for EAS Workflows is coming soon (`eas workflow:run --ssh` and `eas workflow:ssh`). It will cover about half of what this tool does: the SSH server, the Cloudflare tunnel, finding the worker, and ending idle sessions (steps 1 and 2, and the idle shutdown in step 4). The other half stays: preparing the worker, syncing your files safely, the variables and commands for building and running the app, and the instructions for coding agents. When workflow SSH ships, `expo-devbox` will use it.
+**Coming soon:** SSH support for EAS Workflows (`eas workflow:run --ssh` and `eas workflow:ssh`). It will cover about half of what this tool does: the SSH server, the Cloudflare tunnel, finding the worker, and ending idle sessions (steps 1 and 2, and the idle shutdown in step 4). The other half stays: preparing the worker, syncing your files safely, the variables and commands for building and running the app, and the instructions for coding agents. When workflow SSH ships, `expo-devbox` will use it.
 
 </details>
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "expo-devbox",
-  "version": "0.2.1",
+  "version": "0.2.2",
   "description": "Build and test an Expo app's native iOS code on an EAS macOS worker, from your terminal or a coding agent.",
   "type": "module",
   "bin": {

package/src/cli.ts

@@ -27,14 +27,16 @@ Sessions:
   EXPO_DEVBOX_SESSION=<id>. Any unique prefix of an ID works; expo-devbox sessions lists them.
 
 On the worker:
-  After each change, run expo-devbox sync, then the commands below with expo-devbox ssh '<command>'.
+  After each change, run expo-devbox sync, then the commands below that the change needs with
+  expo-devbox ssh '<command>'. A JavaScript change needs none: Metro sends it to the running app.
+  A native change needs a build, then install and launch. The rest are for checking the result.
   The DEVBOX_* variables are set in every SSH session.
 
-  Build. Prints errors with file and line, then ** BUILD SUCCEEDED ** or ** BUILD FAILED **.
-  The full log is ~/.devbox/build.log.
+  Build, after a native change. Prints errors with file and line, then ** BUILD SUCCEEDED ** or
+  ** BUILD FAILED **. The full log is ~/.devbox/build.log.
     set -o pipefail; xcodebuild -workspace "$DEVBOX_WORKSPACE" -scheme "$DEVBOX_SCHEME" -configuration Debug -destination "id=$DEVBOX_SIMULATOR" -derivedDataPath "$DEVBOX_DERIVED_DATA" build 2>&1 | tee ~/.devbox/build.log | grep -E ": (fatal )?error:|\\*\\* BUILD" | sort -u
 
-  Install and launch the app on the simulator:
+  After a build, install and launch the app on the simulator:
     xcrun simctl install booted "$DEVBOX_APP" && xcrun simctl launch --terminate-running-process booted "$DEVBOX_BUNDLE_ID"
 
   JavaScript console output and errors (Metro):

package/src/init.ts

@@ -14,7 +14,7 @@ When the user asks for it:
 
 1. Run \`bunx expo-devbox help\` and follow its "On the worker" section. It has the command for each step: build, install and launch, logs, crash reports and screenshots.
 2. Start a session with \`bunx expo-devbox start\`. It returns when the worker is ready, and EAS macOS minutes are billed until the session ends.
-3. After each change, run \`bunx expo-devbox sync\`, then the commands from the help with \`bunx expo-devbox ssh '<command>'\`.
+3. After each change, run \`bunx expo-devbox sync\`, then the commands from the help that the change needs, with \`bunx expo-devbox ssh '<command>'\`.
 4. Commands use the session you started last in this directory. If another agent works in the same directory, pass your session's ID, which \`start\` prints, to every command: \`bunx expo-devbox ssh --session <id> '<command>'\`.
 5. When the user is done with the devbox, run \`bunx expo-devbox stop\`.
 `;