@opendatalabs/connect 0.8.1-canary.5fa6718 → 0.8.1-canary.609ff8b

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 (49) hide show
  1. package/README.md +53 -153
  2. package/dist/cli/index.d.ts.map +1 -1
  3. package/dist/cli/index.js +1850 -142
  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 +17 -10
  19. package/dist/cli/render/theme.js.map +1 -1
  20. package/dist/core/cli-types.d.ts +488 -1
  21. package/dist/core/cli-types.d.ts.map +1 -1
  22. package/dist/core/cli-types.js +227 -1
  23. package/dist/core/cli-types.js.map +1 -1
  24. package/dist/core/index.d.ts +2 -1
  25. package/dist/core/index.d.ts.map +1 -1
  26. package/dist/core/index.js +1 -1
  27. package/dist/core/index.js.map +1 -1
  28. package/dist/core/state-store.d.ts +11 -0
  29. package/dist/core/state-store.d.ts.map +1 -1
  30. package/dist/core/state-store.js +81 -3
  31. package/dist/core/state-store.js.map +1 -1
  32. package/dist/personal-server/index.d.ts +8 -0
  33. package/dist/personal-server/index.d.ts.map +1 -1
  34. package/dist/personal-server/index.js +40 -10
  35. package/dist/personal-server/index.js.map +1 -1
  36. package/dist/runtime/core/contracts.d.ts +15 -1
  37. package/dist/runtime/core/contracts.d.ts.map +1 -1
  38. package/dist/runtime/managed-playwright.d.ts +5 -0
  39. package/dist/runtime/managed-playwright.d.ts.map +1 -1
  40. package/dist/runtime/managed-playwright.js +69 -10
  41. package/dist/runtime/managed-playwright.js.map +1 -1
  42. package/dist/runtime/playwright/browser.d.ts +1 -0
  43. package/dist/runtime/playwright/browser.d.ts.map +1 -1
  44. package/dist/runtime/playwright/browser.js +14 -4
  45. package/dist/runtime/playwright/browser.js.map +1 -1
  46. package/dist/runtime/playwright/in-process-run.d.ts.map +1 -1
  47. package/dist/runtime/playwright/in-process-run.js +52 -10
  48. package/dist/runtime/playwright/in-process-run.js.map +1 -1
  49. package/package.json +8 -3
package/README.md CHANGED
@@ -2,6 +2,54 @@
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
+ Start with the dedicated CLI README:
10
+
11
+ - [CLI README](./docs/CLI-README.md)
12
+ - [CLI review surface](./docs/CLI-REVIEW-SURFACE.md)
13
+
14
+ Install the current canary on macOS with Homebrew:
15
+
16
+ ```bash
17
+ brew tap vana-com/vana
18
+ brew install vana
19
+ vana status
20
+ ```
21
+
22
+ Or use the hosted prerelease installer on macOS/Linux:
23
+
24
+ ```bash
25
+ 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
26
+ ```
27
+
28
+ Branch prerelease:
29
+
30
+ - `https://github.com/vana-com/vana-connect/releases/tag/canary-feat-connect-cli-v1`
31
+
32
+ Once installed, the best way to evaluate the CLI quickly is:
33
+
34
+ ```bash
35
+ vana --version
36
+ vana doctor
37
+ vana status
38
+ vana sources
39
+ vana connect github
40
+ vana data list
41
+ vana data show github
42
+ vana logs github
43
+ ```
44
+
45
+ Key demo media:
46
+
47
+ <img src="https://github.com/vana-com/vana-connect/releases/download/canary-feat-connect-cli-v1/status.gif" width="800" alt="vana status" />
48
+
49
+ <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" />
50
+
51
+ <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" />
52
+
5
53
  ## What problem this solves
6
54
 
7
55
  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,161 +124,13 @@ If you prefer to integrate the SDK into an existing project, follow the steps be
76
124
 
77
125
  `vana-connect` now also ships a local collection CLI for connector setup and data export flows.
78
126
 
79
- ### Install
80
-
81
- If you are evaluating this branch before it lands on `main`, use the prerelease path in the next section. The stable install commands below are the intended post-merge install path.
82
-
83
- macOS with Homebrew:
84
-
85
- ```bash
86
- brew tap vana-com/vana
87
- brew install vana
88
- ```
89
-
90
- macOS and Linux:
91
-
92
- ```bash
93
- curl -fsSL https://raw.githubusercontent.com/vana-com/vana-connect/main/install/install.sh | sh
94
- ```
95
-
96
- Windows PowerShell:
97
-
98
- ```powershell
99
- iwr https://raw.githubusercontent.com/vana-com/vana-connect/main/install/install.ps1 -useb | iex
100
- ```
101
-
102
- Both installers fetch the latest GitHub release asset for your platform, verify its checksum, and install `vana` without requiring Node or npm.
103
-
104
- ### Canary / prerelease testing
105
-
106
- If you are testing an unreleased branch build, install from the branch installer and pass the prerelease tag explicitly.
107
-
108
- macOS with Homebrew:
109
-
110
- ```bash
111
- brew tap vana-com/vana
112
- brew install vana
113
- ```
114
-
115
- The current Homebrew tap is following the latest `vana-connect` canary while this CLI is still rolling out.
127
+ If you only care about the CLI, start with [docs/CLI-README.md](./docs/CLI-README.md).
116
128
 
117
- macOS and Linux:
129
+ For the full CLI review surface, use:
118
130
 
119
- ```bash
120
- 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
121
- ```
122
-
123
- Windows PowerShell:
124
-
125
- ```powershell
126
- & ([scriptblock]::Create((iwr https://raw.githubusercontent.com/vana-com/vana-connect/feat/connect-cli-v1/install/install.ps1 -useb).Content)) --version canary-feat-connect-cli-v1
127
- ```
128
-
129
- The current hosted prerelease is:
130
-
131
- `canary-feat-connect-cli-v1`
132
-
133
- Release page:
134
-
135
- `https://github.com/vana-com/vana-connect/releases/tag/canary-feat-connect-cli-v1`
136
-
137
- If you want the npm package path as a fallback:
138
-
139
- ```bash
140
- npx -y @opendatalabs/connect status
141
- ```
142
-
143
- ### Commands
144
-
145
- ```bash
146
- vana connect
147
- vana sources
148
- vana connect github
149
- vana connect github --json --no-input
150
- vana status
151
- vana setup
152
- vana data list
153
- vana data path github --json
154
- vana data show github --json | jq '.summary.lines'
155
- ```
156
-
157
- - `vana connect` opens a guided source picker in human mode.
158
- - `vana connect <source>` runs the end-to-end collection flow.
159
- - `vana connect <source> --json --no-input` is the strict machine-safe path for agents and shell automation.
160
- - `vana sources` groups sources into ready-now vs manual-step flows.
161
- - `vana status` prioritizes sources that need attention before already-connected sources.
162
- - `vana data ...` lets you inspect collected local datasets without opening the raw JSON file yourself.
163
-
164
- ### CLI demos
165
-
166
- The branch also includes deterministic VHS demo scaffolding under
167
- [`docs/vhs/`](./docs/vhs/README.md).
168
-
169
- Branch prerelease preview media:
170
-
171
- - [`status-and-sources.gif`](https://github.com/vana-com/vana-connect/releases/download/canary-feat-connect-cli-v1/status-and-sources.gif)
172
- - [`data-inspection.gif`](https://github.com/vana-com/vana-connect/releases/download/canary-feat-connect-cli-v1/data-inspection.gif)
173
- - [`connect-guided.gif`](https://github.com/vana-com/vana-connect/releases/download/canary-feat-connect-cli-v1/connect-guided.gif)
174
-
175
- ![Vana status and sources demo](https://github.com/vana-com/vana-connect/releases/download/canary-feat-connect-cli-v1/status-and-sources.gif)
176
-
177
- ![Vana data inspection demo](https://github.com/vana-com/vana-connect/releases/download/canary-feat-connect-cli-v1/data-inspection.gif)
178
-
179
- ![Vana guided connect demo](https://github.com/vana-com/vana-connect/releases/download/canary-feat-connect-cli-v1/connect-guided.gif)
180
-
181
- Current reviewable transcripts:
182
-
183
- - [`status`](./docs/transcripts/status.txt)
184
- - [`sources`](./docs/transcripts/sources.txt)
185
- - [`data list`](./docs/transcripts/data-list.txt)
186
- - [`data show github`](./docs/transcripts/data-show-github.txt)
187
- - [`connect steam --no-input`](./docs/transcripts/connect-steam-no-input.txt)
188
-
189
- To seed the fixture home used by the first tapes:
190
-
191
- ```bash
192
- pnpm demo:vhs:fixtures
193
- ```
194
-
195
- To render the checked-in tapes once `vhs` or Docker is available:
196
-
197
- ```bash
198
- pnpm demo:vhs
199
- ```
200
-
201
- To capture deterministic human-mode transcripts for review:
202
-
203
- ```bash
204
- pnpm demo:transcripts
205
- ```
206
-
207
- To watch the branch release lane, trigger Homebrew sync, and verify the
208
- published installer automatically:
209
-
210
- ```bash
211
- pnpm release:watch
212
- ```
213
-
214
- ### Local development
215
-
216
- From this repo:
217
-
218
- ```bash
219
- pnpm install
220
- pnpm build
221
- node dist/cli/bin.js status
222
- ```
223
-
224
- The CLI installs its local browser runtime under `~/.dataconnect/`.
225
- That runtime is bundled from `vana-connect` itself, so `vana setup` does not require a separate `data-connect` checkout.
226
-
227
- To build a standalone launcher plus app payload locally:
228
-
229
- ```bash
230
- pnpm build
231
- pnpm build:sea
232
- ./artifacts/sea/vana-linux-x64/vana status --json
233
- ```
131
+ - [CLI review surface](./docs/CLI-REVIEW-SURFACE.md)
132
+ - [CLI transcripts](./docs/transcripts/README.md)
133
+ - [CLI demos](./docs/vhs/README.md)
234
134
 
235
135
  `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/`.
236
136
  It produces a platform-specific release directory plus a release archive and matching checksum file under `artifacts/sea/`.
@@ -1 +1 @@
1
- {"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../src/cli/index.ts"],"names":[],"mappings":"AAyEA,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":"AAoGA,wBAAsB,MAAM,CAAC,IAAI,WAAe,GAAG,OAAO,CAAC,MAAM,CAAC,CA+RjE"}