@opendatalabs/connect 0.8.1-canary.e3412ff → 0.8.1-canary.e9ef508

package/README.md

@@ -2,6 +2,54 @@
 
 Let your users bring their own data to your app.
 
+## CLI preview
+
+This branch also carries the new `vana` collection CLI preview.
+
+Start with the dedicated CLI README:
+
+- [CLI README](./docs/CLI-README.md)
+- [CLI review surface](./docs/CLI-REVIEW-SURFACE.md)
+
+Install the current canary on macOS with Homebrew:
+
+```bash
+brew tap vana-com/vana
+brew install vana
+vana status
+```
+
+Or use the hosted prerelease installer on macOS/Linux:
+
+```bash
+curl -fsSL https://raw.githubusercontent.com/vana-com/vana-connect/feat/connect-cli-v1/install/install.sh | sh -s -- --version canary-feat-connect-cli-v1
+```
+
+Branch prerelease:
+
+- `https://github.com/vana-com/vana-connect/releases/tag/canary-feat-connect-cli-v1`
+
+Once installed, the best way to evaluate the CLI quickly is:
+
+```bash
+vana --version
+vana doctor
+vana status
+vana sources
+vana connect github
+vana data list
+vana data show github
+vana logs github
+```
+
+Key demo media:
+
+<img src="https://github.com/vana-com/vana-connect/releases/download/canary-feat-connect-cli-v1/status.gif" width="800" alt="vana status" />
+
+<img src="https://github.com/vana-com/vana-connect/releases/download/canary-feat-connect-cli-v1/connect-github-success.gif" width="800" alt="vana connect github" />
+
+<img src="https://github.com/vana-com/vana-connect/releases/download/canary-feat-connect-cli-v1/data-show-github.gif" width="600" alt="vana data show github" />
+
 ## What problem this solves
 
 Your users already have rich personal data — ChatGPT conversations, Instagram activity, Gmail, purchase history — but it's locked inside the platforms that collected it. As a builder, you can't easily use that data to personalize onboarding, tailor recommendations, or skip lengthy signup forms.
@@ -76,57 +124,13 @@ If you prefer to integrate the SDK into an existing project, follow the steps be
 
 `vana-connect` now also ships a local collection CLI for connector setup and data export flows.
 
-### Install
-
-macOS and Linux:
+If you only care about the CLI, start with [docs/CLI-README.md](./docs/CLI-README.md).
 
-```bash
-curl -fsSL https://raw.githubusercontent.com/vana-com/vana-connect/main/install/install.sh | sh
-```
-
-Windows PowerShell:
-
-```powershell
-iwr https://raw.githubusercontent.com/vana-com/vana-connect/main/install/install.ps1 -useb | iex
-```
-
-Both installers fetch the latest GitHub release asset for your platform, verify its checksum, and install `vana` without requiring Node or npm.
-
-If you want the npm package path as a fallback:
+For the full CLI review surface, use:
 
-```bash
-npx -y @opendatalabs/connect status
-```
-
-### Commands
-
-```bash
-vana sources
-vana connect github
-vana status
-vana setup
-```
-
-### Local development
-
-From this repo:
-
-```bash
-pnpm install
-pnpm build
-node dist/cli/bin.js status
-```
-
-The CLI installs its local browser runtime under `~/.dataconnect/`.
-That runtime is bundled from `vana-connect` itself, so `vana setup` does not require a separate `data-connect` checkout.
-
-To build a standalone launcher plus app payload locally:
-
-```bash
-pnpm build
-pnpm build:sea
-./artifacts/sea/vana-linux-x64/vana status --json
-```
+- [CLI review surface](./docs/CLI-REVIEW-SURFACE.md)
+- [CLI transcripts](./docs/transcripts/README.md)
+- [CLI demos](./docs/vhs/README.md)
 
 `pnpm build:sea` uses Node 25's `--build-sea` flow to create a small `vana` launcher and packages the real app payload next to it under `app/`.
 It produces a platform-specific release directory plus a release archive and matching checksum file under `artifacts/sea/`.

package/dist/cli/bin.d.ts

@@ -0,0 +1,3 @@
+#!/usr/bin/env node
+export {};
+//# sourceMappingURL=bin.d.ts.map

package/dist/cli/bin.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"bin.d.ts","sourceRoot":"","sources":["../../src/cli/bin.ts"],"names":[],"mappings":""}

package/dist/cli/bin.js

@@ -0,0 +1,15 @@
+#!/usr/bin/env node
+import { runCli } from "./index.js";
+for (const stream of [process.stdout, process.stderr]) {
+    stream.on("error", (error) => {
+        if (error.code === "EPIPE") {
+            process.exit(0);
+        }
+        throw error;
+    });
+}
+const exitCode = await runCli(process.argv);
+if (typeof exitCode === "number") {
+    process.exitCode = exitCode;
+}
+//# sourceMappingURL=bin.js.map

package/dist/cli/bin.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"bin.js","sourceRoot":"","sources":["../../src/cli/bin.ts"],"names":[],"mappings":";AAEA,OAAO,EAAE,MAAM,EAAE,MAAM,YAAY,CAAC;AAEpC,KAAK,MAAM,MAAM,IAAI,CAAC,OAAO,CAAC,MAAM,EAAE,OAAO,CAAC,MAAM,CAAC,EAAE,CAAC;IACtD,MAAM,CAAC,EAAE,CAAC,OAAO,EAAE,CAAC,KAA4B,EAAE,EAAE;QAClD,IAAI,KAAK,CAAC,IAAI,KAAK,OAAO,EAAE,CAAC;YAC3B,OAAO,CAAC,IAAI,CAAC,CAAC,CAAC,CAAC;QAClB,CAAC;QACD,MAAM,KAAK,CAAC;IACd,CAAC,CAAC,CAAC;AACL,CAAC;AAED,MAAM,QAAQ,GAAG,MAAM,MAAM,CAAC,OAAO,CAAC,IAAI,CAAC,CAAC;AAC5C,IAAI,OAAO,QAAQ,KAAK,QAAQ,EAAE,CAAC;IACjC,OAAO,CAAC,QAAQ,GAAG,QAAQ,CAAC;AAC9B,CAAC"}

package/dist/cli/index.d.ts

@@ -0,0 +1,2 @@
+export declare function runCli(argv?: string[]): Promise<number>;
+//# sourceMappingURL=index.d.ts.map

package/dist/cli/index.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../src/cli/index.ts"],"names":[],"mappings":"AAqIA,wBAAsB,MAAM,CAAC,IAAI,WAAe,GAAG,OAAO,CAAC,MAAM,CAAC,CA0UjE"}