vibeview 0.7.0 → 0.8.0

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 (8) hide show
  1. package/README.md +105 -0
  2. package/dist/chunk-NZ4G3JKV.js +1990 -0
  3. package/dist/chunk-YD2X6TQV.js +304 -0
  4. package/dist/cli.js +147 -722
  5. package/dist/server-JZAEEHZT.js +367 -0
  6. package/dist/upload-app-GAZVQZYR.js +9 -0
  7. package/package.json +9 -7
  8. package/skills/vibeview-agent/SKILL.md +205 -0
package/README.md ADDED
@@ -0,0 +1,105 @@
1
+ # VibeView CLI
2
+
3
+ Command-line interface for [VibeView](https://vibeview.io) — cloud iOS simulators and Android emulators in your browser. Upload builds, run AI-powered tests from CI, and develop your React Native app live on a cloud device.
4
+
5
+ ## Install
6
+
7
+ ```bash
8
+ npm install -g vibeview
9
+ ```
10
+
11
+ Requires Node.js 20 or later.
12
+
13
+ ## Log in
14
+
15
+ ```bash
16
+ vibeview login
17
+ ```
18
+
19
+ Opens your browser to authenticate. In CI, set a `VIBEVIEW_API_TOKEN` environment variable instead (create one in VibeView under Settings → API Tokens).
20
+
21
+ ## Live Development
22
+
23
+ Edit code locally, see it live on a streamed cloud device — including iOS development without a Mac.
24
+
25
+ ```bash
26
+ # 1. Upload a React Native debug build once
27
+ vibeview upload-app ./app-debug.apk
28
+
29
+ # 2. Start Metro in your project, then:
30
+ vibeview dev
31
+ ```
32
+
33
+ `vibeview dev` starts a cloud device session, installs your latest debug build, connects it to your local Metro bundler, and opens the live stream in your browser. Save a file and Fast Refresh updates the device in about a second. Supports `--platform ios | android | tvos | androidtv`; your choices are remembered per platform in a `vibeview.json` in the project.
34
+
35
+ [Live Development docs →](https://vibeview.io/docs/live-development)
36
+
37
+ ## Let your AI agent drive the device
38
+
39
+ The same session can be driven by a coding agent, so it can verify its own
40
+ changes instead of handing you code to test by hand: it reads the screen,
41
+ taps, types, and checks the result.
42
+
43
+ ```bash
44
+ vibeview ui-tree # what's on screen, with refs like @e5
45
+ vibeview tap @e5 # act — the response says what changed
46
+ vibeview screenshot --out ./check.png
47
+ ```
48
+
49
+ Every command works over MCP too, for agents without shell access:
50
+
51
+ ```bash
52
+ claude mcp add vibeview -- vibeview mcp
53
+ ```
54
+
55
+ Other MCP clients (Cursor, Claude Desktop, VS Code Copilot) run command
56
+ `vibeview` with args `["mcp"]`. The package also ships a ready-made skill at
57
+ `skills/vibeview-agent/SKILL.md` describing the whole workflow.
58
+
59
+ [Agent control docs →](https://vibeview.io/docs/agent-control)
60
+
61
+ ## Testing from CI
62
+
63
+ ```bash
64
+ # Upload the build under test (zipped simulator .app for iOS, .apk for Android)
65
+ vibeview upload-app ./MyApp.zip
66
+
67
+ # Run a single test or a whole suite
68
+ vibeview run-test <test-id> --output json
69
+ vibeview run-suite <suite-id> --output junit
70
+
71
+ # Run several suites with an aggregated exit code
72
+ vibeview run-suites --tag smoke
73
+ ```
74
+
75
+ Output formats: `human`, `json`, and `junit` for any CI system. The exit code reflects pass/fail, and runs can be pinned to a specific build.
76
+
77
+ [CI testing docs →](https://vibeview.io/docs/ci-testing)
78
+
79
+ ## All commands
80
+
81
+ | Command | Purpose |
82
+ | --- | --- |
83
+ | `vibeview login` | Authenticate via browser |
84
+ | `vibeview dev` | Live development on a cloud device |
85
+ | `vibeview build` | Build your app and upload it |
86
+ | `vibeview dev-status` / `dev-stop` | Check on, or stop, a backgrounded dev session |
87
+ | `vibeview mcp` | Run the MCP server so an agent can drive the device |
88
+ | `vibeview ui-tree` | The current screen's elements, each with a ref to act on |
89
+ | `vibeview screenshot` | Capture the screen to a PNG |
90
+ | `vibeview tap` / `type` / `scroll` / `press` | Drive the device |
91
+ | `vibeview scroll-to` / `drag` / `alert` / `find` | Search, precise gestures, iOS system alerts |
92
+ | `vibeview upload-app <file>` | Upload a build (zipped simulator `.app`, or `.apk`) |
93
+ | `vibeview list-apps` | List your apps |
94
+ | `vibeview list-devices` | List available device types |
95
+ | `vibeview list-suites` | List test suites |
96
+ | `vibeview create-test [name]` | Create a test case |
97
+ | `vibeview run-test <test-id>` | Run a single test |
98
+ | `vibeview run-suite <suite-id>` | Run a test suite |
99
+ | `vibeview run-suites` | Run multiple suites |
100
+
101
+ Run any command with `--help` for its options.
102
+
103
+ ## Documentation
104
+
105
+ Full guides at [vibeview.io/docs](https://vibeview.io/docs) — [CLI reference](https://vibeview.io/docs/cli), [Live Development](https://vibeview.io/docs/live-development), [CI testing](https://vibeview.io/docs/ci-testing).