@xiaou66/vite-plugin-vue-mcp-next 1.1.0 → 1.2.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.
- package/README.md +20 -0
- package/dist/index.cjs +449 -17
- package/dist/index.cjs.map +1 -1
- package/dist/index.d.cts +77 -0
- package/dist/index.d.ts +77 -0
- package/dist/index.js +449 -17
- package/dist/index.js.map +1 -1
- package/dist/runtime/client.cjs +404 -1
- package/dist/runtime/client.cjs.map +1 -1
- package/dist/runtime/client.js +404 -1
- package/dist/runtime/client.js.map +1 -1
- package/package.json +1 -1
- package/skills/vite-mcp-next/SKILL.md +7 -2
package/package.json
CHANGED
|
@@ -33,6 +33,8 @@ Do not use it for static code-only questions where reading files is enough.
|
|
|
33
33
|
| Inspect requests | `get_network_requests` |
|
|
34
34
|
| Inspect one request deeply | `get_network_request_detail` |
|
|
35
35
|
| Reset old request records | `clear_network_requests` |
|
|
36
|
+
| Inspect browser storage | `list_storage`, `get_storage_item` |
|
|
37
|
+
| Mutate browser storage | `set_storage_item`, `delete_storage_item`, `clear_storage` |
|
|
36
38
|
| Inspect Vue component tree | `get_component_tree` |
|
|
37
39
|
| Inspect one component state | `get_component_state` |
|
|
38
40
|
| Edit runtime component state | `edit_component_state` |
|
|
@@ -48,12 +50,14 @@ Do not use it for static code-only questions where reading files is enough.
|
|
|
48
50
|
3. For visual verification, call `take_screenshot` and report whether `source` is `cdp` or `snapdom`.
|
|
49
51
|
4. For browser errors, call `get_console_logs`.
|
|
50
52
|
5. For API behavior, call `get_network_requests`, then `get_network_request_detail` for the relevant id.
|
|
51
|
-
6. For
|
|
53
|
+
6. For storage questions, call `list_storage` first, then `get_storage_item`, `set_storage_item`, `delete_storage_item`, or `clear_storage` for the selected scope.
|
|
54
|
+
7. For Vue-specific behavior, call `get_component_tree`, `get_component_state`, `get_router_info`, `get_pinia_tree`, or `get_pinia_state`.
|
|
52
55
|
|
|
53
56
|
## Channel Boundaries
|
|
54
57
|
|
|
55
58
|
- DOM, Console, Network, and Screenshot should use CDP when available.
|
|
56
|
-
- Without CDP, DOM, Console, and
|
|
59
|
+
- Without CDP, DOM, Console, Network, and same-origin storage fall back to Runtime Hook; screenshots fall back to snapdom.
|
|
60
|
+
- Cookie storage is CDP-only. `HttpOnly` cookies can be read through CDP, but deletion and clear operations skip them.
|
|
57
61
|
- Vue component, Router, and Pinia tools always use Vue Runtime Bridge. Do not replace them with CDP DOM inspection when Vue semantic state is needed.
|
|
58
62
|
|
|
59
63
|
## Risk Boundaries
|
|
@@ -61,6 +65,7 @@ Do not use it for static code-only questions where reading files is enough.
|
|
|
61
65
|
- `evaluate_script` is disabled unless the project sets `runtime.evaluate.enabled: true`.
|
|
62
66
|
- Prefer `evaluate_script` for read-only diagnosis. Do not mutate page state unless the user asked for it.
|
|
63
67
|
- `edit_component_state` mutates runtime Vue state. Use it only when state editing is the explicit goal.
|
|
68
|
+
- Storage mutation tools change browser state. Use them only when the user explicitly asks to write, delete, or clear storage.
|
|
64
69
|
- Network data can include token, cookie, or authorization values. Do not write sensitive values into source code, docs, commits, or final replies.
|
|
65
70
|
|
|
66
71
|
## Failure Handling
|