@opendatalabs/connect 0.8.1-canary.ee85681 → 0.8.1-canary.f3d3fed

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 (82) hide show
  1. package/README.md +5 -72
  2. package/dist/cli/bin.js +0 -8
  3. package/dist/cli/bin.js.map +1 -1
  4. package/dist/cli/index.d.ts.map +1 -1
  5. package/dist/cli/index.js +487 -385
  6. package/dist/cli/index.js.map +1 -1
  7. package/dist/cli/render/format.d.ts +13 -19
  8. package/dist/cli/render/format.d.ts.map +1 -1
  9. package/dist/cli/render/format.js +30 -55
  10. package/dist/cli/render/format.js.map +1 -1
  11. package/dist/connectors/registry.d.ts +22 -1
  12. package/dist/connectors/registry.d.ts.map +1 -1
  13. package/dist/connectors/registry.js +53 -30
  14. package/dist/connectors/registry.js.map +1 -1
  15. package/dist/core/cli-types.d.ts +9 -13
  16. package/dist/core/cli-types.d.ts.map +1 -1
  17. package/dist/core/cli-types.js +5 -3
  18. package/dist/core/cli-types.js.map +1 -1
  19. package/dist/core/index.d.ts +1 -1
  20. package/dist/core/index.d.ts.map +1 -1
  21. package/dist/core/index.js +1 -1
  22. package/dist/core/index.js.map +1 -1
  23. package/dist/core/paths.d.ts +1 -0
  24. package/dist/core/paths.d.ts.map +1 -1
  25. package/dist/core/paths.js +3 -0
  26. package/dist/core/paths.js.map +1 -1
  27. package/dist/core/state-store.d.ts +4 -1
  28. package/dist/core/state-store.d.ts.map +1 -1
  29. package/dist/core/state-store.js.map +1 -1
  30. package/dist/runtime/index.d.ts +0 -1
  31. package/dist/runtime/index.d.ts.map +1 -1
  32. package/dist/runtime/index.js.map +1 -1
  33. package/dist/runtime/managed-playwright.d.ts +2 -2
  34. package/dist/runtime/managed-playwright.d.ts.map +1 -1
  35. package/dist/runtime/managed-playwright.js +187 -59
  36. package/dist/runtime/managed-playwright.js.map +1 -1
  37. package/dist/runtime/repo-paths.d.ts.map +1 -1
  38. package/dist/runtime/repo-paths.js +7 -24
  39. package/dist/runtime/repo-paths.js.map +1 -1
  40. package/package.json +8 -19
  41. package/runtime-assets/playwright-runner/entitlements.plist +12 -0
  42. package/runtime-assets/playwright-runner/index.cjs +1243 -0
  43. package/runtime-assets/playwright-runner/package-lock.json +1242 -0
  44. package/runtime-assets/playwright-runner/package.json +29 -0
  45. package/runtime-assets/playwright-runner/scripts/build.js +182 -0
  46. package/runtime-assets/run-connector.cjs +355 -0
  47. package/dist/cli/render/capabilities.d.ts +0 -9
  48. package/dist/cli/render/capabilities.d.ts.map +0 -1
  49. package/dist/cli/render/capabilities.js +0 -24
  50. package/dist/cli/render/capabilities.js.map +0 -1
  51. package/dist/cli/render/index.d.ts +0 -5
  52. package/dist/cli/render/index.d.ts.map +0 -1
  53. package/dist/cli/render/index.js +0 -5
  54. package/dist/cli/render/index.js.map +0 -1
  55. package/dist/cli/render/symbols.d.ts +0 -11
  56. package/dist/cli/render/symbols.d.ts.map +0 -1
  57. package/dist/cli/render/symbols.js +0 -21
  58. package/dist/cli/render/symbols.js.map +0 -1
  59. package/dist/cli/render/theme.d.ts +0 -15
  60. package/dist/cli/render/theme.d.ts.map +0 -1
  61. package/dist/cli/render/theme.js +0 -17
  62. package/dist/cli/render/theme.js.map +0 -1
  63. package/dist/runtime/core/contracts.d.ts +0 -69
  64. package/dist/runtime/core/contracts.d.ts.map +0 -1
  65. package/dist/runtime/core/contracts.js +0 -2
  66. package/dist/runtime/core/contracts.js.map +0 -1
  67. package/dist/runtime/core/index.d.ts +0 -2
  68. package/dist/runtime/core/index.d.ts.map +0 -1
  69. package/dist/runtime/core/index.js +0 -2
  70. package/dist/runtime/core/index.js.map +0 -1
  71. package/dist/runtime/playwright/browser.d.ts +0 -11
  72. package/dist/runtime/playwright/browser.d.ts.map +0 -1
  73. package/dist/runtime/playwright/browser.js +0 -208
  74. package/dist/runtime/playwright/browser.js.map +0 -1
  75. package/dist/runtime/playwright/in-process-run.d.ts +0 -6
  76. package/dist/runtime/playwright/in-process-run.d.ts.map +0 -1
  77. package/dist/runtime/playwright/in-process-run.js +0 -534
  78. package/dist/runtime/playwright/in-process-run.js.map +0 -1
  79. package/dist/runtime/playwright/index.d.ts +0 -3
  80. package/dist/runtime/playwright/index.d.ts.map +0 -1
  81. package/dist/runtime/playwright/index.js +0 -3
  82. package/dist/runtime/playwright/index.js.map +0 -1
package/README.md CHANGED
@@ -78,84 +78,28 @@ If you prefer to integrate the SDK into an existing project, follow the steps be
78
78
 
79
79
  ### Install
80
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:
81
+ Use the published package directly:
109
82
 
110
83
  ```bash
111
- brew tap vana-com/vana
112
- brew install vana
84
+ pnpm dlx @opendatalabs/connect status
113
85
  ```
114
86
 
115
- The current Homebrew tap is following the latest `vana-connect` canary while this CLI is still rolling out.
116
-
117
- macOS and Linux:
87
+ Or install it globally:
118
88
 
119
89
  ```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
90
+ pnpm add -g @opendatalabs/connect
91
+ vana status
141
92
  ```
142
93
 
143
94
  ### Commands
144
95
 
145
96
  ```bash
146
- vana connect
147
97
  vana sources
148
98
  vana connect github
149
99
  vana status
150
100
  vana setup
151
- vana data list
152
- vana data show github --json | jq
153
101
  ```
154
102
 
155
- - `vana connect` opens a guided source picker in human mode.
156
- - `vana connect <source>` runs the end-to-end collection flow.
157
- - `vana data ...` lets you inspect collected local datasets without opening the raw JSON file yourself.
158
-
159
103
  ### Local development
160
104
 
161
105
  From this repo:
@@ -169,17 +113,6 @@ node dist/cli/bin.js status
169
113
  The CLI installs its local browser runtime under `~/.dataconnect/`.
170
114
  That runtime is bundled from `vana-connect` itself, so `vana setup` does not require a separate `data-connect` checkout.
171
115
 
172
- To build a standalone launcher plus app payload locally:
173
-
174
- ```bash
175
- pnpm build
176
- pnpm build:sea
177
- ./artifacts/sea/vana-linux-x64/vana status --json
178
- ```
179
-
180
- `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/`.
181
- It produces a platform-specific release directory plus a release archive and matching checksum file under `artifacts/sea/`.
182
-
183
116
  ### Programmatic runtime access
184
117
 
185
118
  If you are building an app surface like DataConnect Desktop or a hosted orchestration layer, use the SDK modules instead of shelling out to the CLI where possible.
package/dist/cli/bin.js CHANGED
@@ -1,13 +1,5 @@
1
1
  #!/usr/bin/env node
2
2
  import { runCli } from "./index.js";
3
- for (const stream of [process.stdout, process.stderr]) {
4
- stream.on("error", (error) => {
5
- if (error.code === "EPIPE") {
6
- process.exit(0);
7
- }
8
- throw error;
9
- });
10
- }
11
3
  const exitCode = await runCli(process.argv);
12
4
  if (typeof exitCode === "number") {
13
5
  process.exitCode = exitCode;
@@ -1 +1 @@
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"}
1
+ {"version":3,"file":"bin.js","sourceRoot":"","sources":["../../src/cli/bin.ts"],"names":[],"mappings":";AAEA,OAAO,EAAE,MAAM,EAAE,MAAM,YAAY,CAAC;AAEpC,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"}
@@ -1 +1 @@
1
- {"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../src/cli/index.ts"],"names":[],"mappings":"AAuEA,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":"AA0DA,wBAAsB,MAAM,CAAC,IAAI,WAAe,GAAG,OAAO,CAAC,MAAM,CAAC,CA2EjE"}