@opendatalabs/connect 0.8.1-canary.c921264 → 0.8.1-canary.ce3d7cd

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.
package/README.md CHANGED
@@ -2,6 +2,58 @@
2
2
 
3
3
  Let your users bring their own data to your app.
4
4
 
5
+ ## CLI preview
6
+
7
+ This branch also carries the new `vana` collection CLI preview.
8
+
9
+ - install the current canary on macOS with Homebrew:
10
+
11
+ ```bash
12
+ brew tap vana-com/vana
13
+ brew install vana
14
+ vana status
15
+ ```
16
+
17
+ - or use the hosted prerelease installer on macOS/Linux:
18
+
19
+ ```bash
20
+ 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
21
+ ```
22
+
23
+ - branch release page:
24
+ `https://github.com/vana-com/vana-connect/releases/tag/canary-feat-connect-cli-v1`
25
+ - demo media:
26
+ [`status-and-sources.gif`](https://github.com/vana-com/vana-connect/releases/download/canary-feat-connect-cli-v1/status-and-sources.gif),
27
+ [`data-inspection.gif`](https://github.com/vana-com/vana-connect/releases/download/canary-feat-connect-cli-v1/data-inspection.gif),
28
+ [`connect-success.gif`](https://github.com/vana-com/vana-connect/releases/download/canary-feat-connect-cli-v1/connect-success.gif)
29
+
30
+ Once installed, the best way to evaluate the CLI quickly is:
31
+
32
+ ```bash
33
+ vana --version
34
+ vana doctor
35
+ vana status
36
+ vana sources
37
+ vana connect github
38
+ vana data show github
39
+ ```
40
+
41
+ Current reviewable transcripts:
42
+
43
+ - [`status`](./docs/transcripts/status.txt)
44
+ - [`doctor`](./docs/transcripts/doctor.txt)
45
+ - [`setup`](./docs/transcripts/setup.txt)
46
+ - [`sources`](./docs/transcripts/sources.txt)
47
+ - [`data list`](./docs/transcripts/data-list.txt)
48
+ - [`data list (empty)`](./docs/transcripts/data-list-empty.txt)
49
+ - [`data show github`](./docs/transcripts/data-show-github.txt)
50
+ - [`data show github (missing)`](./docs/transcripts/data-show-github-missing.txt)
51
+ - [`data path github`](./docs/transcripts/data-path-github.txt)
52
+ - [`connect github`](./docs/transcripts/connect-github-success.txt)
53
+ - [`connect github --no-input`](./docs/transcripts/connect-github-no-input.txt)
54
+ - [`connect shop --no-input`](./docs/transcripts/connect-shop-no-input.txt)
55
+ - [`connect steam --no-input`](./docs/transcripts/connect-steam-no-input.txt)
56
+
5
57
  ## What problem this solves
6
58
 
7
59
  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.
@@ -143,6 +195,9 @@ npx -y @opendatalabs/connect status
143
195
  ### Commands
144
196
 
145
197
  ```bash
198
+ vana --version
199
+ vana version
200
+ vana doctor
146
201
  vana connect
147
202
  vana sources
148
203
  vana connect github
@@ -159,19 +214,134 @@ vana data show github --json | jq '.summary.lines'
159
214
  - `vana connect <source> --json --no-input` is the strict machine-safe path for agents and shell automation.
160
215
  - `vana sources` groups sources into ready-now vs manual-step flows.
161
216
  - `vana status` prioritizes sources that need attention before already-connected sources.
217
+ - `vana doctor` checks the local install, browser runtime, and state directories.
162
218
  - `vana data ...` lets you inspect collected local datasets without opening the raw JSON file yourself.
163
219
 
220
+ ### Shell contract
221
+
222
+ - `--json` mode writes machine-readable output to stdout without human narration.
223
+ - Successful command completion returns exit code `0`.
224
+ - Actionable failures like missing source selection, unavailable connectors, or disabled prompting return exit code `1`.
225
+ - `vana --version`, `vana version`, and `vana --help` return exit code `0`.
226
+ - `vana doctor --json` includes `installMethod`, `channel`, and upgrade/uninstall commands so scripts can surface the right lifecycle guidance.
227
+
228
+ ### Shell examples
229
+
230
+ ```bash
231
+ vana status --json | jq '.channel, .installMethod, .summary | {connectedCount, localCount, syncedCount}'
232
+ vana sources --json | jq '.summary, .recommendedSource'
233
+ vana data list --json | jq '.summary, .datasets[] | {source, dataState, path}'
234
+ vana doctor --json | jq '.paths.executable, .paths.appRoot, .lifecycle'
235
+ ```
236
+
237
+ ### Upgrade, channels, and uninstall
238
+
239
+ Upgrade with the same channel you installed from:
240
+
241
+ You can always confirm the current install method and exact lifecycle commands with:
242
+
243
+ ```bash
244
+ vana doctor
245
+ ```
246
+
247
+ - Homebrew:
248
+ ```bash
249
+ brew update
250
+ brew upgrade vana
251
+ ```
252
+ - macOS/Linux installer:
253
+ ```bash
254
+ curl -fsSL https://raw.githubusercontent.com/vana-com/vana-connect/main/install/install.sh | sh
255
+ ```
256
+ - Windows PowerShell installer:
257
+ ```powershell
258
+ iwr https://raw.githubusercontent.com/vana-com/vana-connect/main/install/install.ps1 -useb | iex
259
+ ```
260
+
261
+ Current channels:
262
+
263
+ - `stable`: install from `main` or the eventual stable Homebrew tap state
264
+ - `canary`: install from the latest prerelease assets while this CLI is still rolling out
265
+
266
+ To remove the installed CLI:
267
+
268
+ - Homebrew:
269
+ ```bash
270
+ brew uninstall vana
271
+ ```
272
+ - macOS/Linux installer:
273
+ ```bash
274
+ rm -f ~/.local/bin/vana
275
+ rm -rf ~/.local/share/vana
276
+ ```
277
+ - Windows PowerShell installer:
278
+ - remove `%USERPROFILE%\AppData\Local\Microsoft\WinGet\Links\vana.cmd`
279
+ - remove `%USERPROFILE%\AppData\Local\Vana`
280
+
281
+ To remove local runtime and collected state as well:
282
+
283
+ ```bash
284
+ rm -rf ~/.dataconnect
285
+ ```
286
+
164
287
  ### CLI demos
165
288
 
166
289
  The branch also includes deterministic VHS demo scaffolding under
167
290
  [`docs/vhs/`](./docs/vhs/README.md).
168
291
 
292
+ Branch prerelease preview media:
293
+
294
+ - [`status-and-sources.gif`](https://github.com/vana-com/vana-connect/releases/download/canary-feat-connect-cli-v1/status-and-sources.gif)
295
+ - [`data-inspection.gif`](https://github.com/vana-com/vana-connect/releases/download/canary-feat-connect-cli-v1/data-inspection.gif)
296
+ - [`connect-success.gif`](https://github.com/vana-com/vana-connect/releases/download/canary-feat-connect-cli-v1/connect-success.gif)
297
+
298
+ ![Vana status and sources demo](https://github.com/vana-com/vana-connect/releases/download/canary-feat-connect-cli-v1/status-and-sources.gif)
299
+
300
+ ![Vana data inspection demo](https://github.com/vana-com/vana-connect/releases/download/canary-feat-connect-cli-v1/data-inspection.gif)
301
+
302
+ ![Vana successful connect demo](https://github.com/vana-com/vana-connect/releases/download/canary-feat-connect-cli-v1/connect-success.gif)
303
+
304
+ Current reviewable transcripts:
305
+
306
+ - [`status`](./docs/transcripts/status.txt)
307
+ - [`doctor`](./docs/transcripts/doctor.txt)
308
+ - [`setup`](./docs/transcripts/setup.txt)
309
+ - [`sources`](./docs/transcripts/sources.txt)
310
+ - [`data list`](./docs/transcripts/data-list.txt)
311
+ - [`data list (empty)`](./docs/transcripts/data-list-empty.txt)
312
+ - [`data show github`](./docs/transcripts/data-show-github.txt)
313
+ - [`data show github (missing)`](./docs/transcripts/data-show-github-missing.txt)
314
+ - [`data path github`](./docs/transcripts/data-path-github.txt)
315
+ - [`connect github`](./docs/transcripts/connect-github-success.txt)
316
+ - [`connect github --no-input`](./docs/transcripts/connect-github-no-input.txt)
317
+ - [`connect shop --no-input`](./docs/transcripts/connect-shop-no-input.txt)
318
+ - [`connect steam --no-input`](./docs/transcripts/connect-steam-no-input.txt)
319
+
169
320
  To seed the fixture home used by the first tapes:
170
321
 
171
322
  ```bash
172
323
  pnpm demo:vhs:fixtures
173
324
  ```
174
325
 
326
+ To render the checked-in tapes once `vhs` or Docker is available:
327
+
328
+ ```bash
329
+ pnpm demo:vhs
330
+ ```
331
+
332
+ To capture deterministic human-mode transcripts for review:
333
+
334
+ ```bash
335
+ pnpm demo:transcripts
336
+ ```
337
+
338
+ To watch the branch release lane, trigger Homebrew sync, and verify the
339
+ published installer automatically:
340
+
341
+ ```bash
342
+ pnpm release:watch
343
+ ```
344
+
175
345
  ### Local development
176
346
 
177
347
  From this repo:
@@ -1 +1 @@
1
- {"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../src/cli/index.ts"],"names":[],"mappings":"AAwEA,wBAAsB,MAAM,CAAC,IAAI,WAAe,GAAG,OAAO,CAAC,MAAM,CAAC,CAuEjE"}
1
+ {"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../src/cli/index.ts"],"names":[],"mappings":"AA+FA,wBAAsB,MAAM,CAAC,IAAI,WAAe,GAAG,OAAO,CAAC,MAAM,CAAC,CAqMjE"}