@opendatalabs/connect 0.8.1-canary.32c01c1 → 0.8.1-canary.38ea4e7

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 (41) hide show
  1. package/README.md +198 -1
  2. package/dist/cli/index.d.ts.map +1 -1
  3. package/dist/cli/index.js +1966 -160
  4. package/dist/cli/index.js.map +1 -1
  5. package/dist/cli/render/format.d.ts +2 -0
  6. package/dist/cli/render/format.d.ts.map +1 -1
  7. package/dist/cli/render/format.js +24 -5
  8. package/dist/cli/render/format.js.map +1 -1
  9. package/dist/cli/render/index.d.ts +1 -0
  10. package/dist/cli/render/index.d.ts.map +1 -1
  11. package/dist/cli/render/index.js +1 -0
  12. package/dist/cli/render/index.js.map +1 -1
  13. package/dist/cli/render/progress.d.ts +11 -0
  14. package/dist/cli/render/progress.d.ts.map +1 -0
  15. package/dist/cli/render/progress.js +56 -0
  16. package/dist/cli/render/progress.js.map +1 -0
  17. package/dist/cli/render/theme.d.ts.map +1 -1
  18. package/dist/cli/render/theme.js +26 -2
  19. package/dist/cli/render/theme.js.map +1 -1
  20. package/dist/core/cli-types.d.ts +473 -1
  21. package/dist/core/cli-types.d.ts.map +1 -1
  22. package/dist/core/cli-types.js +221 -1
  23. package/dist/core/cli-types.js.map +1 -1
  24. package/dist/core/state-store.d.ts +5 -0
  25. package/dist/core/state-store.d.ts.map +1 -1
  26. package/dist/core/state-store.js +68 -4
  27. package/dist/core/state-store.js.map +1 -1
  28. package/dist/runtime/core/contracts.d.ts +15 -1
  29. package/dist/runtime/core/contracts.d.ts.map +1 -1
  30. package/dist/runtime/managed-playwright.d.ts +5 -0
  31. package/dist/runtime/managed-playwright.d.ts.map +1 -1
  32. package/dist/runtime/managed-playwright.js +69 -10
  33. package/dist/runtime/managed-playwright.js.map +1 -1
  34. package/dist/runtime/playwright/browser.d.ts +1 -0
  35. package/dist/runtime/playwright/browser.d.ts.map +1 -1
  36. package/dist/runtime/playwright/browser.js +14 -4
  37. package/dist/runtime/playwright/browser.js.map +1 -1
  38. package/dist/runtime/playwright/in-process-run.d.ts.map +1 -1
  39. package/dist/runtime/playwright/in-process-run.js +52 -10
  40. package/dist/runtime/playwright/in-process-run.js.map +1 -1
  41. package/package.json +11 -1
package/README.md CHANGED
@@ -2,6 +2,65 @@
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 list
39
+ vana data show github
40
+ vana logs github
41
+ ```
42
+
43
+ Current reviewable transcripts:
44
+
45
+ - [`status`](./docs/transcripts/status.txt)
46
+ - [`doctor`](./docs/transcripts/doctor.txt)
47
+ - [`logs`](./docs/transcripts/logs.txt)
48
+ - [`setup`](./docs/transcripts/setup.txt)
49
+ - [`sources`](./docs/transcripts/sources.txt)
50
+ - [`data list`](./docs/transcripts/data-list.txt)
51
+ - [`data help`](./docs/transcripts/data-help.txt)
52
+ - [`data list (empty)`](./docs/transcripts/data-list-empty.txt)
53
+ - [`data show github`](./docs/transcripts/data-show-github.txt)
54
+ - [`data show github (missing)`](./docs/transcripts/data-show-github-missing.txt)
55
+ - [`data path github`](./docs/transcripts/data-path-github.txt)
56
+ - [`connect github`](./docs/transcripts/connect-github-success.txt)
57
+ - [`connect github --no-input`](./docs/transcripts/connect-github-no-input.txt)
58
+ - [`connect github session reuse --no-input`](./docs/transcripts/connect-github-session-reuse-no-input.txt)
59
+ - [`connect shop`](./docs/transcripts/connect-shop.txt)
60
+ - [`connect shop --no-input`](./docs/transcripts/connect-shop-no-input.txt)
61
+ - [`connect steam`](./docs/transcripts/connect-steam.txt)
62
+ - [`connect steam --no-input`](./docs/transcripts/connect-steam-no-input.txt)
63
+
5
64
  ## What problem this solves
6
65
 
7
66
  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,19 +202,157 @@ npx -y @opendatalabs/connect status
143
202
  ### Commands
144
203
 
145
204
  ```bash
205
+ vana --version
206
+ vana version
207
+ vana doctor
208
+ vana logs
146
209
  vana connect
147
210
  vana sources
148
211
  vana connect github
212
+ vana connect github --json --no-input
149
213
  vana status
150
214
  vana setup
151
215
  vana data list
152
- vana data show github --json | jq
216
+ vana data path github --json
217
+ vana data show github --json | jq '.summary.lines'
153
218
  ```
154
219
 
155
220
  - `vana connect` opens a guided source picker in human mode.
156
221
  - `vana connect <source>` runs the end-to-end collection flow.
222
+ - `vana connect <source> --json --no-input` is the strict machine-safe path for agents and shell automation.
223
+ - `vana sources` groups sources into ready-now vs manual-step flows.
224
+ - `vana status` prioritizes sources that need attention before already-connected sources.
225
+ - `vana doctor` checks the local install, browser runtime, and state directories.
226
+ - `vana logs` lets you inspect the latest stored connector run logs without hunting through `~/.dataconnect/logs`.
157
227
  - `vana data ...` lets you inspect collected local datasets without opening the raw JSON file yourself.
158
228
 
229
+ ### Shell contract
230
+
231
+ - `--json` mode writes machine-readable output to stdout without human narration.
232
+ - Successful command completion returns exit code `0`.
233
+ - Actionable failures like missing source selection, unavailable connectors, or disabled prompting return exit code `1`.
234
+ - `vana --version`, `vana version`, and `vana --help` return exit code `0`.
235
+ - `vana doctor --json` includes `installMethod`, `channel`, and upgrade/uninstall commands so scripts can surface the right lifecycle guidance.
236
+
237
+ ### Shell examples
238
+
239
+ ```bash
240
+ vana status --json | jq '.channel, .installMethod, .summary | {connectedCount, localCount, syncedCount}'
241
+ vana sources --json | jq '.summary, .recommendedSource'
242
+ vana data list --json | jq '.summary, .datasets[] | {source, dataState, path}'
243
+ vana logs --json | jq '.latestLog, .logs[] | {source, path}'
244
+ vana doctor --json | jq '.paths.executable, .paths.dataHome, .lifecycle'
245
+ ```
246
+
247
+ ### Upgrade, channels, and uninstall
248
+
249
+ Upgrade with the same channel you installed from:
250
+
251
+ You can always confirm the current install method and exact lifecycle commands with:
252
+
253
+ ```bash
254
+ vana doctor
255
+ ```
256
+
257
+ - Homebrew:
258
+ ```bash
259
+ brew update
260
+ brew upgrade vana
261
+ ```
262
+ - macOS/Linux installer:
263
+ ```bash
264
+ curl -fsSL https://raw.githubusercontent.com/vana-com/vana-connect/main/install/install.sh | sh
265
+ ```
266
+ - Windows PowerShell installer:
267
+ ```powershell
268
+ iwr https://raw.githubusercontent.com/vana-com/vana-connect/main/install/install.ps1 -useb | iex
269
+ ```
270
+
271
+ Current channels:
272
+
273
+ - `stable`: install from `main` or the eventual stable Homebrew tap state
274
+ - `canary`: install from the latest prerelease assets while this CLI is still rolling out
275
+
276
+ To remove the installed CLI:
277
+
278
+ - Homebrew:
279
+ ```bash
280
+ brew uninstall vana
281
+ ```
282
+ - macOS/Linux installer:
283
+ ```bash
284
+ rm -f ~/.local/bin/vana
285
+ rm -rf ~/.local/share/vana
286
+ ```
287
+ - Windows PowerShell installer:
288
+ - remove `%USERPROFILE%\AppData\Local\Microsoft\WinGet\Links\vana.cmd`
289
+ - remove `%USERPROFILE%\AppData\Local\Vana`
290
+
291
+ To remove local runtime and collected state as well:
292
+
293
+ ```bash
294
+ rm -rf ~/.dataconnect
295
+ ```
296
+
297
+ ### CLI demos
298
+
299
+ The branch also includes deterministic VHS demo scaffolding under
300
+ [`docs/vhs/`](./docs/vhs/README.md).
301
+
302
+ Branch prerelease preview media:
303
+
304
+ - [`status-and-sources.gif`](https://github.com/vana-com/vana-connect/releases/download/canary-feat-connect-cli-v1/status-and-sources.gif)
305
+ - [`data-inspection.gif`](https://github.com/vana-com/vana-connect/releases/download/canary-feat-connect-cli-v1/data-inspection.gif)
306
+ - [`connect-success.gif`](https://github.com/vana-com/vana-connect/releases/download/canary-feat-connect-cli-v1/connect-success.gif)
307
+
308
+ ![Vana status and sources demo](https://github.com/vana-com/vana-connect/releases/download/canary-feat-connect-cli-v1/status-and-sources.gif)
309
+
310
+ ![Vana data inspection demo](https://github.com/vana-com/vana-connect/releases/download/canary-feat-connect-cli-v1/data-inspection.gif)
311
+
312
+ ![Vana successful connect demo](https://github.com/vana-com/vana-connect/releases/download/canary-feat-connect-cli-v1/connect-success.gif)
313
+
314
+ Current reviewable transcripts:
315
+
316
+ - [`status`](./docs/transcripts/status.txt)
317
+ - [`doctor`](./docs/transcripts/doctor.txt)
318
+ - [`logs`](./docs/transcripts/logs.txt)
319
+ - [`setup`](./docs/transcripts/setup.txt)
320
+ - [`sources`](./docs/transcripts/sources.txt)
321
+ - [`data list`](./docs/transcripts/data-list.txt)
322
+ - [`data list (empty)`](./docs/transcripts/data-list-empty.txt)
323
+ - [`data show github`](./docs/transcripts/data-show-github.txt)
324
+ - [`data show github (missing)`](./docs/transcripts/data-show-github-missing.txt)
325
+ - [`data path github`](./docs/transcripts/data-path-github.txt)
326
+ - [`connect github`](./docs/transcripts/connect-github-success.txt)
327
+ - [`connect github --no-input`](./docs/transcripts/connect-github-no-input.txt)
328
+ - [`connect shop --no-input`](./docs/transcripts/connect-shop-no-input.txt)
329
+ - [`connect steam --no-input`](./docs/transcripts/connect-steam-no-input.txt)
330
+
331
+ To seed the fixture home used by the first tapes:
332
+
333
+ ```bash
334
+ pnpm demo:vhs:fixtures
335
+ ```
336
+
337
+ To render the checked-in tapes once `vhs` or Docker is available:
338
+
339
+ ```bash
340
+ pnpm demo:vhs
341
+ ```
342
+
343
+ To capture deterministic human-mode transcripts for review:
344
+
345
+ ```bash
346
+ pnpm demo:transcripts
347
+ ```
348
+
349
+ To watch the branch release lane, trigger Homebrew sync, and verify the
350
+ published installer automatically:
351
+
352
+ ```bash
353
+ pnpm release:watch
354
+ ```
355
+
159
356
  ### Local development
160
357
 
161
358
  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,CAsEjE"}
1
+ {"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../src/cli/index.ts"],"names":[],"mappings":"AAkGA,wBAAsB,MAAM,CAAC,IAAI,WAAe,GAAG,OAAO,CAAC,MAAM,CAAC,CAiPjE"}