local-expo-build 0.2.0 → 0.4.1

package/CHANGELOG.md

@@ -5,6 +5,126 @@ All notable changes to `local-expo-build` are documented here.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [0.4.1] — 2026-06-28
+
+### Added
+
+- **Interactive `--clean` prompt.** When you run `build android` / `build
+  ios` (runner mode) or `npm run build:android:*` (scaffold mode) in an
+  interactive terminal, the build asks once at the top whether to clean.
+  Hint text explains when to say yes (Expo SDK upgrade, plugin change,
+  "android project is malformed" / "MainActivity not found" errors).
+  Default is **No** — most builds don't need clean, and forgetting to
+  clean fails loud (errors) while forgetting NOT to clean wastes 1-2 min
+  silently every time.
+- **`--no-clean` flag** to skip the prompt and force no-clean. Useful when
+  scripting / aliasing the build invocation.
+- **Scaffold mode now honors `--clean` / `--no-clean`.** Previously these
+  flags only worked in runner mode; the templated `scripts/build.js`
+  silently ignored them. Now they're parsed from argv and propagated to
+  `expo prebuild`. Pass via `npm run build:android:aab -- --clean`.
+
+### Changed
+
+- All templated scripts bumped to `v0.4.1` version stamp. Users on v0.4.0
+  will see them as outdated when running `npx local-expo-build update-scripts`.
+
+### Behavior in non-interactive environments
+
+- CI / non-TTY: defaults to no-clean (unchanged from v0.4.0).
+- `--dry-run`: defaults to no-clean (so the dry-run output is deterministic).
+- Explicit `--clean` or `--no-clean` always wins, no prompt.
+
+## [0.4.0] — 2026-06-28
+
+### Added
+
+- **iOS build support (EXPERIMENTAL, macOS only).** New `local-expo-build
+  build ios` subcommand orchestrates `expo prebuild --platform ios` →
+  `xcodebuild archive` → `xcodebuild -exportArchive` → signed `.ipa`. Five
+  steps with the same numbered progress + dry-run support as the Android
+  pipeline. Flags: `--method app-store|ad-hoc|development|enterprise`,
+  `--scheme`, `--configuration`, `--team-id`, `--bundle-id`,
+  `--profile-name`, `--clean`, `--no-bump`, `--no-prebuild`.
+- **`src/core/ios/` module suite.** `xcodebuild.ts` (archive + export
+  wrappers), `exportOptions.ts` (generates `export-options.plist` per
+  build), `credentials.ts` (reads the `ios` section of `credentials.json`),
+  `detect.ts` (auto-detects `ios/<Workspace>.xcworkspace`).
+- **`assertMacOS` guard.** Every iOS code path hard-throws on non-Darwin
+  hosts with an actionable message (no cryptic `command not found` for
+  `xcodebuild`).
+- **Loud experimental banner.** iOS commands print a yellow warning line
+  before doing anything so users know to expect rough edges and to file
+  issues. No opt-in flag required (would be annoying after the first run).
+- **Doctor adds iOS prerequisite checks** on macOS (`xcodebuild`,
+  `xcrun`). Non-macOS hosts get a single dim "skipped — iOS builds require
+  macOS" row instead of failures.
+- **14 new `node:test` cases** for the iOS-testable bits: plist
+  generation, credentials.json parsing, workspace detection,
+  `assertMacOS` guard. Total: 37 tests across 7 suites.
+
+### Changed
+
+- **README restructured** with platform-tab sections — Android (stable)
+  and iOS (experimental) have separate Quick Start blocks, "Bringing your
+  own credentials" walkthroughs, and file tables.
+- **Comparison table + Roadmap updated** to reflect iOS support and to
+  retire the closed items (iOS basic, remote `GRADLE_PIN` manifest).
+- **Package keywords + description** now mention iOS / `.ipa` /
+  `xcodebuild`.
+
+### Known limitations of iOS support (read before reporting)
+
+The iOS pipeline was implemented from Apple's documented `xcodebuild`
+interface but **not validated on macOS by the maintainer** (Windows-only
+dev environment). Code is correct in theory; please file issues with
+your `eas-cli` version, `xcodebuild -version` output, and the failing
+command if something doesn't work. Specifically not yet supported:
+
+- Automated `.p12` keychain import (you double-click the file).
+- Automated provisioning profile install (you double-click the file).
+- TestFlight / App Store upload (use `xcrun altool` manually after the build).
+- iOS-specific `CFBundleVersion` (buildNumber) bump.
+- Multi-bundle apps (extensions / widgets / watch apps).
+
+All of the above are on the roadmap for future releases.
+
+## [0.3.0] — 2026-06-28
+
+### Added
+
+- **Live `GRADLE_PIN` manifest.** `pinGradle` now fetches the latest pin table
+  from `manifest/gradle-pins.json` in the GitHub repo (3 s timeout, silent
+  fallback to the bundled table). New Expo SDK shipping a problematic Gradle
+  default → edit the manifest, commit, and every existing CLI user gets the
+  new pin on their next build. No `npm publish` required.
+- **`local-expo-build update-scripts` subcommand.** Diffs scaffolded
+  `scripts/*.js` against the bundled templates by version stamp + content.
+  Shows a table of up-to-date / outdated / missing scripts. Prompts before
+  overwriting (or pass `--yes`). Honors `--dry-run`. Every scaffolded script
+  now carries a `// Generated by local-expo-build vX.Y.Z` header.
+- **Multi-strategy `signingConfigs.release` injection.** `setupSigning` now
+  tries three strategies in order: exact-match → tolerant block-inject →
+  synthesize new block inside `android { }`. Survives whitespace drift,
+  comments, and even Expo dropping the default debug signing block from
+  prebuild output.
+- **`local-expo-build` test suite.** 23 tests across 5 suites using
+  `node:test` (no new devDep). Covers gradle injection, buildType rewiring,
+  EAS link detection, and rehydrate candidate matching — the bits that
+  break first when Expo shifts. Run with `npm test`.
+- **CI matrix:** 3 OS × 2 Node versions = 6 jobs per PR
+  (ubuntu/macos/windows × Node 20/22). Catches Windows-specific regressions
+  before users do.
+
+### Changed
+
+- **Node 20 minimum** (`engines.node`). Node 18 reached EOL in April 2025;
+  bumping the floor lets us use native `fetch` for the manifest and
+  `node:test` for the test suite without polyfills.
+- Doctor's `Node` check now requires `>= 20` instead of `>= 18`.
+- `pinGradle` is now async (was sync). The single internal caller in
+  `build.ts` was updated.
+
 ## [0.2.0] — 2026-06-28
 
 ### Added

package/README.md

@@ -1,13 +1,15 @@
 # local-expo-build
 
-> One-stop CLI for **local** Expo Android APK / AAB builds. Bypass EAS cloud builds, keep full control of signing, and stop waiting in queues.
+> One-stop CLI for **local** Expo Android APK / AAB builds — **works on Windows, macOS, and Linux** (unlike `eas build --local`, which rejects Windows). Own your signing, skip the EAS cloud queue, no eas.json required.
 
 [![npm version](https://img.shields.io/npm/v/local-expo-build.svg)](https://www.npmjs.com/package/local-expo-build)
 [![npm downloads](https://img.shields.io/npm/dm/local-expo-build.svg)](https://www.npmjs.com/package/local-expo-build)
 [![license](https://img.shields.io/npm/l/local-expo-build.svg)](https://github.com/nikhild64/local-expo-build/blob/main/LICENSE)
 [![node](https://img.shields.io/node/v/local-expo-build.svg)](https://nodejs.org/)
 
-`local-expo-build` automates the painful parts of running `expo prebuild` + `gradlew bundleRelease` yourself:
+`local-expo-build` automates the painful parts of running `expo prebuild` + `gradlew bundleRelease` (or `xcodebuild archive`) yourself:
+
+**Android (stable):**
 
 - Detects your Expo SDK and pins the Gradle wrapper to a version that actually works (e.g. SDK 55 → Gradle 8.13, working around the `expo-manifests` `components.release` bug).
 - Bumps your app version and pulls the next `versionCode` from EAS so Play Store ingest doesn't reject the upload.
@@ -17,6 +19,13 @@
 - Runs `gradlew assembleRelease` / `bundleRelease` and prints the absolute path + size of the produced artifact.
 - Pushes the new `versionCode` back to EAS via GraphQL so `eas build` / `eas submit` stay in sync.
 
+**iOS (experimental, macOS only — community-tested):**
+
+- Orchestrates `xcodebuild archive` + `-exportArchive` for `.ipa` output.
+- Auto-detects the workspace + scheme produced by `expo prebuild --platform ios`.
+- Generates `export-options.plist` per build with sensible defaults for `app-store` / `ad-hoc` / `development` / `enterprise` distribution methods.
+- Reads `.p12` + provisioning profile paths from `credentials.json` (same file format EAS downloads).
+
 **`doctor` is a setup wizard, not just a health check.** It detects missing pieces (`expo.android.package`, EAS link, `eas.json`, keystore) and offers to fix each one interactively — `eas init`, `eas build:configure`, keystore picker (with one-prompt `rehydrate` from `credentials.json` when possible), all chained.
 
 ![local-expo-build init: doctor pre-flight + scaffolding in one command](https://raw.githubusercontent.com/nikhild64/local-expo-build/main/assets/screenshots/setup_init.png)
@@ -68,14 +77,15 @@ local-expo-build init [--force] [--no-keystore] [--no-doctor]
                                             Scaffold scripts + package.json entries
                                             (runs `doctor` first by default)
 
-local-expo-build build android [--apk|--aab] [--profile <name>]
-                               [--clean] [--no-bump] [--no-sync] [--no-prebuild]
-                                            Run the full pipeline → .aab|.apk
-
 local-expo-build doctor                     Env check + interactive auto-fix wizard
                                             (eas init → eas build:configure →
                                              keystore setup)
 
+# ── Android (stable) ──
+local-expo-build build android [--apk|--aab] [--profile <name>]
+                               [--clean] [--no-bump] [--no-sync] [--no-prebuild]
+                                            Run the full Android pipeline → .aab|.apk
+
 local-expo-build keystore setup             Interactive picker:
                                             rehydrate | existing | generate | EAS
 local-expo-build keystore import            Register an existing .jks
@@ -84,7 +94,19 @@ local-expo-build keystore fetch             Open `eas credentials` to download a
 local-expo-build keystore rehydrate [--move]
                                             Bind credentials.json + .jks into
                                             keystore.properties (no password re-entry).
-                                            --move deletes the source .jks after copy.
+
+# ── iOS (experimental, macOS only) ──
+local-expo-build build ios [--method <m>] [--scheme <s>] [--configuration <c>]
+                            [--team-id <id>] [--profile-name <n>] [--bundle-id <id>]
+                            [--clean] [--no-bump] [--no-prebuild]
+                                            Run the full iOS pipeline → .ipa
+                                            --method = app-store | ad-hoc |
+                                                       development | enterprise
+
+# ── Shared ──
+local-expo-build update-scripts [-y|--yes]
+                                            Refresh scaffolded scripts/*.js to the
+                                            version bundled with this CLI.
 ```
 
 Global flags: `--cwd <path>`, `--verbose`, `--dry-run`.
@@ -95,22 +117,52 @@ Global flags: `--cwd <path>`, `--verbose`, `--dry-run`.
 > npx local-expo-build --dry-run build android --aab    # runner mode
 > npm run build:android:aab -- --dry-run                # scaffold mode (or: node scripts/build.js aab --dry-run)
 > ```
+>
+> **`--clean`** prompts interactively when neither `--clean` nor `--no-clean` is passed. Default is **No** (faster). Say yes after an Expo SDK upgrade, plugin change, or `MainActivity not found` / "android project is malformed" errors. Pass `--clean` or `--no-clean` explicitly to skip the prompt.
 
 ![Dry-run output: the full 7-step build pipeline with no side effects](https://raw.githubusercontent.com/nikhild64/local-expo-build/main/assets/screenshots/dryrun-build.png)
 
 ## How it compares
 
-|  | `eas build` (cloud) | `npx expo run:android` | `local-expo-build` |
-| --- | --- | --- | --- |
-| Runs locally | No | Yes | **Yes** |
-| Produces a signed release `.aab` / `.apk` | Yes | No (debug) | **Yes** |
-| Manages release `signingConfig` for you | Yes | No | **Yes** |
-| Bumps `versionCode` from EAS automatically | Yes | No | **Yes** |
-| Wait in cloud queue | Sometimes | Never | Never |
-| Works offline | No | Yes | **Yes** (after first prebuild) |
-| Needs `eas-cli` | Yes | No | Optional (only for version sync / EAS keystore) |
+|  | `eas build` (cloud) | `eas build --local` | `npx expo run:android/ios` | `local-expo-build` |
+| --- | --- | --- | --- | --- |
+| Runs locally | No | Yes | Yes | **Yes** |
+| **Works on Windows** | Yes (cloud) | **No** ¹ | Yes (debug only) | **Yes** |
+| Works on macOS / Linux | Yes (cloud) | Yes | Yes | **Yes** |
+| Produces a signed release `.aab` / `.apk` | Yes | Yes | No (debug) | **Yes (Android)** |
+| Produces a signed release `.ipa` | Yes | Yes | No (debug) | **Yes (iOS, experimental)** |
+| Counts against EAS free build quota | **Yes** | No | No | No |
+| Manages release signing config for you | Yes | Yes | No | **Yes** |
+| Bumps `versionCode` from EAS automatically | Yes | Yes | No | **Yes (Android)** |
+| Wait in cloud queue | Sometimes | Never | Never | Never |
+| Needs `eas-cli` installed | Yes | **Yes** | No | Optional ² |
+| Needs `eas.json` set up | Yes | **Yes** | No | No |
+| Needs EAS account / login | Yes | **Yes** | No | Optional ² |
+| Pipeline editable per-project | No | No | No | **Yes** (scaffold mode) |
+
+¹ `eas build --platform android --local` errors with `"Unsupported platform, macOS or Linux is required to build apps for Android"` on Windows — EAS's local build infrastructure uses Unix-only tooling.
+
+² Only needed for: EAS keystore fetch, versionCode sync back to EAS, or doctor's `eas init` / `eas build:configure` auto-fixes. The build itself runs without any EAS dependency.
+
+**TL;DR:**
 
-If you're happy with cloud builds, use `eas build`. This CLI is for teams who want the EAS workflow (managed signing, synced `versionCode`) but the speed and control of building on their own machine.
+- **On Windows?** `local-expo-build` is the only option in the Expo ecosystem to build Android locally.
+- **On Mac/Linux + happy with EAS?** Use `eas build --local` — it's the official path with managed credentials + `eas submit` integration.
+- **On Mac/Linux + want lightweight / no EAS lock-in?** `local-expo-build` is your fit — no eas.json, no login, fully editable pipeline.
+
+## Why not just use `eas build --local`?
+
+If you're on Mac or Linux **and** already invested in EAS (account, eas.json, profiles, `eas submit` workflow), `eas build --platform android --local` is the official Expo path and you should use it. It integrates seamlessly with `eas submit`, managed credentials, and the rest of the EAS toolbox.
+
+Use `local-expo-build` instead when **any** of these is true:
+
+1. **You're on Windows.** `eas build --local` literally won't run — it errors out with `"Unsupported platform, macOS or Linux is required to build apps for Android"`. This is the killer use case: there's no other path to local Expo Android builds on Windows.
+2. **You don't want an EAS account.** No login, no `eas.json`, no project-link ceremony. Just point at any Expo project and get a signed `.aab`.
+3. **You want to vendor + edit the build pipeline in your repo.** Scaffold mode drops 6 readable JS files into `scripts/` that you can customize per-project (custom version bumping, project-specific signing tweaks, pre/post hooks). `eas build` is a black box by design.
+4. **Your project pre-dates EAS** (SDK 50 era) and you never set up the EAS link. `local-expo-build` works on any Expo SDK ≥ 50 with no migration needed.
+5. **You want to script around predictable artifact paths.** Output always lands at `android/app/build/outputs/{apk,bundle}/release/...`. EAS local copies through temp dirs.
+
+Both tools can coexist. The CLI also writes a `credentials.json` at project root, which `eas submit` (and `eas build` cloud, if you ever want to use it) reads directly — your local-built `.aab` can still be uploaded via `eas submit --path /path/to/app.aab` without re-signing.
 
 ## Keystore sources
 
@@ -180,6 +232,97 @@ npx local-expo-build build android --aab   # runner mode
 
 > Tip: you can skip step 2 entirely — `doctor` detects the rehydrate state automatically and offers the same one-prompt fix inline.
 
+## iOS (experimental, macOS only)
+
+> **Status: community-tested.** The iOS pipeline ships behind an experimental banner because the maintainer develops on Windows and can't validate every build configuration. The code is built on Apple's documented `xcodebuild` interface and follows the same patterns as the Android side, but please [file issues](https://github.com/nikhild64/local-expo-build/issues) when you hit something — and PRs are very welcome.
+
+### Prerequisites
+
+iOS local builds are constrained by Apple and require all of:
+
+- **macOS** (Xcode is macOS-only — Apple does not ship `xcodebuild` for Linux or Windows)
+- **Xcode** 14+ with Command Line Tools (`xcode-select --install`)
+- **Apple Developer account** ($99/yr — required for distribution signing certificates)
+- **A distribution `.p12`** + **provisioning profile** installed in your keychain (drag the `.p12` into Keychain Access; double-click the `.mobileprovision` to install)
+
+`local-expo-build doctor` checks for Xcode / `xcodebuild` automatically on macOS hosts and skips the checks elsewhere.
+
+### Quick start (iOS)
+
+```bash
+# 1. Download credentials from EAS (same flow as Android)
+npx local-expo-build keystore fetch
+# In the EAS menu pick: iOS → Download credentials to credentials.json
+# This produces:
+#   - credentials.json with an `ios` section
+#   - ios/certs/dist.p12  (distribution certificate)
+#   - ios/certs/profile.mobileprovision  (provisioning profile)
+
+# 2. (one-time, manual) Import the .p12 into your login keychain
+#    and double-click the .mobileprovision file. Both go into ~/Library/...
+#    Xcode does this automatically on double-click.
+
+# 3. Build the .ipa
+npx local-expo-build build ios --method app-store \
+  --team-id ABCDE12345 \
+  --bundle-id com.yourcompany.yourapp \
+  --profile-name "Your Profile Name"
+```
+
+The build runs through these 5 steps:
+
+```text
+1/5 expo prebuild (ios)
+2/5 bump version
+3/5 detect Xcode workspace + credentials
+4/5 xcodebuild archive
+5/5 xcodebuild -exportArchive (method=app-store)
+
+Build complete (.ipa, 14.3 MB):
+  /path/to/your/app/ios/build/export/YourApp.ipa
+```
+
+Use `--dry-run` to preview the 5 steps without invoking xcodebuild.
+
+### What the CLI does NOT handle (yet)
+
+By design, the experimental iOS support keeps a tight scope so we don't ship untested Apple-keychain code that could leave your machine in a weird state. You're still responsible for:
+
+- **Keychain `.p12` import.** Double-click the file in Finder, or `security import dist.p12 -k ~/Library/Keychains/login.keychain-db -P <password>`.
+- **Provisioning profile install.** Double-click the `.mobileprovision`, or copy to `~/Library/MobileDevice/Provisioning Profiles/<UUID>.mobileprovision`.
+- **TestFlight / App Store upload.** Use `xcrun altool --upload-app` or Apple's Transporter app after the `.ipa` is built.
+
+These are on the roadmap (full `certs setup` flow + EAS cert fetch + TestFlight upload) for a future release once there's been enough community testing of the core build flow.
+
+### iOS-specific files
+
+| Path | Purpose | Gitignored? |
+| --- | --- | --- |
+| `credentials.json` → `ios` block | EAS local-credentials shape for iOS (`distributionCertificate.path/password`, `provisioningProfilePath`) | Yes (auto via the Android setup) |
+| `ios/build/export-options.plist` | Regenerated per build with the chosen distribution method | No — derived per-build, safe to commit or gitignore as you prefer |
+| `ios/build/<Scheme>.xcarchive` | Intermediate archive produced by `xcodebuild archive` | Yes (recommend adding `ios/build/` to `.gitignore`) |
+| `ios/build/export/<Scheme>.ipa` | The final `.ipa` | Yes (recommend adding `ios/build/` to `.gitignore`) |
+
+### Known caveats
+
+- **Auto-detected scheme is the workspace basename.** Works for Expo's default prebuild output; pass `--scheme MyOtherScheme` if your project has multiple schemes.
+- **Manual signing requires `--team-id`.** Without it, `xcodebuild` falls back to automatic signing, which only works for `development` builds if your Apple ID is logged into Xcode.
+- **Multi-bundle apps not handled.** If your project has app extensions (widgets, watch app, share extension), each needs its own provisioning profile and the current `--profile-name` flag only sets one. File an issue with your `app.json` `extra.eas.build.experimental.ios.appExtensions` setup if you hit this.
+- **No `bumpVersion` for iOS-specific `buildNumber`.** Today the bump step still updates `versionCode` in `android/app/build.gradle` (no-op on iOS-only builds). Expo's prebuild reads `expo.version` from `app.json` and writes it into `Info.plist`'s `CFBundleShortVersionString` — for `CFBundleVersion` (the iOS equivalent of `versionCode`) you currently need to manage that in `app.json` → `ios.buildNumber` manually. PRs to wire this up are welcome.
+
+### How it works (iOS pipeline)
+
+```text
+expo prebuild --platform ios
+  → (you import .p12 + provisioning profile manually, one-time)
+  → bump app.json version                       (src/core/bumpVersion.ts)
+  → detect ios/<Workspace>.xcworkspace          (src/core/ios/detect.ts)
+  → read credentials.json `ios` section         (src/core/ios/credentials.ts)
+  → write ios/build/export-options.plist        (src/core/ios/exportOptions.ts)
+  → xcodebuild archive                          (src/core/ios/xcodebuild.ts)
+  → xcodebuild -exportArchive → .ipa
+```
+
 ## Files this CLI creates / touches
 
 | Path | Purpose | Gitignored? |
@@ -215,13 +358,24 @@ If your SDK isn't pinned, `pinGradle` is a no-op. Add a row + open a PR if a fut
 
 ## Requirements
 
-- Node ≥ 18
+**All platforms:**
+
+- Node ≥ 20 (Node 18 reached EOL in April 2025)
+- `eas-cli` is **optional** — only needed for EAS version sync, EAS credentials fetch, or doctor's `eas init` / `eas build:configure` auto-fixes
+
+**Android builds (cross-platform):**
+
 - JDK 17 (recommended for Expo SDK 55)
 - Android SDK + `ANDROID_HOME` env var
 - `keytool` on `PATH` (ships with the JDK)
-- `eas-cli` is **optional** — only needed for EAS version sync, EAS keystore fetch, or doctor's `eas init` / `eas build:configure` auto-fixes
 
-Run `local-expo-build doctor` to verify all of the above.
+**iOS builds (macOS only):**
+
+- macOS (Apple does not ship `xcodebuild` for Linux or Windows)
+- Xcode 14+ with Command Line Tools (`xcode-select --install`)
+- Apple Developer account ($99/yr — for distribution signing certificates)
+
+Run `local-expo-build doctor` to verify all of the above — iOS-specific checks are auto-skipped on non-macOS hosts.
 
 ## How it works (pipeline)
 
@@ -350,9 +504,12 @@ node /abs/path/local-expo-build/bin/local-expo-build.js doctor --cwd /abs/path/m
 
 ## Roadmap
 
-- [ ] iOS local builds
-- [ ] Auto-update `GRADLE_PIN` table from a hosted manifest
-- [ ] Symbol upload (`mapping.txt` → Play Console / Sentry)
+- [x] iOS local builds (experimental in v0.4.0 — awaiting community testing)
+- [x] Auto-update `GRADLE_PIN` table from a hosted manifest (v0.3.0)
+- [ ] `certs setup` interactive flow for iOS (.p12 import + provisioning profile install via `security` / Keychain Access automation)
+- [ ] iOS `buildNumber` (CFBundleVersion) bump + EAS sync — parity with Android's `versionCode` flow
+- [ ] TestFlight / App Store Connect upload (`xcrun altool` / `notarytool` wrapper)
+- [ ] Symbol upload (`mapping.txt` → Play Console / Sentry; iOS `.dSYM` to Sentry)
 - [ ] CI presets (`init --ci` that scaffolds a GitHub Actions / GitLab CI workflow with base64-encoded secrets)
 
 ## Contributing

package/dist/cli.js

@@ -9,6 +9,7 @@ const build_1 = require("./commands/build");
 const init_1 = require("./commands/init");
 const keystore_1 = require("./commands/keystore");
 const doctor_1 = require("./commands/doctor");
+const update_1 = require("./commands/update");
 const pkg = require('../package.json');
 const program = new commander_1.Command();
 program
@@ -23,6 +24,7 @@ program
 (0, init_1.registerInitCommand)(program);
 (0, keystore_1.registerKeystoreCommand)(program);
 (0, doctor_1.registerDoctorCommand)(program);
+(0, update_1.registerUpdateCommand)(program);
 program
     .parseAsync(process.argv)
     .catch((err) => {

package/dist/cli.js.map

@@ -1 +1 @@
-{"version":3,"file":"cli.js","sourceRoot":"","sources":["../src/cli.ts"],"names":[],"mappings":";;;;;AAAA,yCAAoC;AACpC,kDAA0B;AAC1B,4CAAwD;AACxD,0CAAsD;AACtD,kDAA8D;AAC9D,8CAA0D;AAE1D,MAAM,GAAG,GAAG,OAAO,CAAC,iBAAiB,CAAC,CAAC;AAEvC,MAAM,OAAO,GAAG,IAAI,mBAAO,EAAE,CAAC;AAE9B,OAAO;KACJ,IAAI,CAAC,kBAAkB,CAAC;KACxB,WAAW,CACV,4DAA4D;IAC1D,gFAAgF,CACnF;KACA,OAAO,CAAC,GAAG,CAAC,OAAO,CAAC;KACpB,MAAM,CAAC,cAAc,EAAE,4CAA4C,CAAC;KACpE,MAAM,CAAC,WAAW,EAAE,iBAAiB,CAAC;KACtC,MAAM,CAAC,WAAW,EAAE,mDAAmD,CAAC,CAAC;AAE5E,IAAA,4BAAoB,EAAC,OAAO,CAAC,CAAC;AAC9B,IAAA,0BAAmB,EAAC,OAAO,CAAC,CAAC;AAC7B,IAAA,kCAAuB,EAAC,OAAO,CAAC,CAAC;AACjC,IAAA,8BAAqB,EAAC,OAAO,CAAC,CAAC;AAE/B,OAAO;KACJ,UAAU,CAAC,OAAO,CAAC,IAAI,CAAC;KACxB,KAAK,CAAC,CAAC,GAAG,EAAE,EAAE;IACb,OAAO,CAAC,KAAK,CAAC,eAAK,CAAC,GAAG,CAAC,4BAA4B,CAAC,CAAC,CAAC;IACvD,OAAO,CAAC,KAAK,CAAC,GAAG,EAAE,KAAK,IAAI,GAAG,EAAE,OAAO,IAAI,GAAG,CAAC,CAAC;IACjD,OAAO,CAAC,IAAI,CAAC,CAAC,CAAC,CAAC;AAClB,CAAC,CAAC,CAAC"}
+{"version":3,"file":"cli.js","sourceRoot":"","sources":["../src/cli.ts"],"names":[],"mappings":";;;;;AAAA,yCAAoC;AACpC,kDAA0B;AAC1B,4CAAwD;AACxD,0CAAsD;AACtD,kDAA8D;AAC9D,8CAA0D;AAC1D,8CAA0D;AAE1D,MAAM,GAAG,GAAG,OAAO,CAAC,iBAAiB,CAAC,CAAC;AAEvC,MAAM,OAAO,GAAG,IAAI,mBAAO,EAAE,CAAC;AAE9B,OAAO;KACJ,IAAI,CAAC,kBAAkB,CAAC;KACxB,WAAW,CACV,4DAA4D;IAC1D,gFAAgF,CACnF;KACA,OAAO,CAAC,GAAG,CAAC,OAAO,CAAC;KACpB,MAAM,CAAC,cAAc,EAAE,4CAA4C,CAAC;KACpE,MAAM,CAAC,WAAW,EAAE,iBAAiB,CAAC;KACtC,MAAM,CAAC,WAAW,EAAE,mDAAmD,CAAC,CAAC;AAE5E,IAAA,4BAAoB,EAAC,OAAO,CAAC,CAAC;AAC9B,IAAA,0BAAmB,EAAC,OAAO,CAAC,CAAC;AAC7B,IAAA,kCAAuB,EAAC,OAAO,CAAC,CAAC;AACjC,IAAA,8BAAqB,EAAC,OAAO,CAAC,CAAC;AAC/B,IAAA,8BAAqB,EAAC,OAAO,CAAC,CAAC;AAE/B,OAAO;KACJ,UAAU,CAAC,OAAO,CAAC,IAAI,CAAC;KACxB,KAAK,CAAC,CAAC,GAAG,EAAE,EAAE;IACb,OAAO,CAAC,KAAK,CAAC,eAAK,CAAC,GAAG,CAAC,4BAA4B,CAAC,CAAC,CAAC;IACvD,OAAO,CAAC,KAAK,CAAC,GAAG,EAAE,KAAK,IAAI,GAAG,EAAE,OAAO,IAAI,GAAG,CAAC,CAAC;IACjD,OAAO,CAAC,IAAI,CAAC,CAAC,CAAC,CAAC;AAClB,CAAC,CAAC,CAAC"}