@livespace/plugin-cli 0.3.0 → 0.4.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/dist/sdk/range.js +1 -1
- package/package.json +1 -1
- package/skill/livespace-plugin/SKILL.md +24 -6
package/dist/sdk/range.js
CHANGED
|
@@ -26,4 +26,4 @@ export const SDK_LLMS_TXT_CDN_URL = `https://cdn.jsdelivr.net/npm/@livespace/plu
|
|
|
26
26
|
* takes the project's SDK as a peer, so it isn't tied to the SDK's major. A test keeps it in step
|
|
27
27
|
* with `packages/studio`.
|
|
28
28
|
*/
|
|
29
|
-
export const STUDIO_RANGE = "^0.
|
|
29
|
+
export const STUDIO_RANGE = "^0.2";
|
package/package.json
CHANGED
|
@@ -91,12 +91,30 @@ only output is one JSON result, so the guidance it would print in a terminal is
|
|
|
91
91
|
|
|
92
92
|
- Open the page outside Livespace: it shows its loading state and the console is clean.
|
|
93
93
|
- Run **Plugin Studio** with the dev server running: the `studio` script in a project `create`
|
|
94
|
-
made, else `npx @livespace/plugin-studio`. It embeds the page as Livespace does.
|
|
95
|
-
|
|
96
|
-
|
|
97
|
-
|
|
98
|
-
|
|
99
|
-
|
|
94
|
+
made, else `npx @livespace/plugin-studio`. It embeds the page as Livespace does.
|
|
95
|
+
- **Use your own studio.** If port 5190 is taken, start one with `--port <free port>`. Don't
|
|
96
|
+
use the one already running: it's probably the author's, and its saved settings, secrets and
|
|
97
|
+
exchange failures are shared by everyone using it.
|
|
98
|
+
- **With a browser tool, reach every state and mode from step 2**: each record type and no
|
|
99
|
+
record, no viewer, `null` and saved settings, preview and config on its settings page, the
|
|
100
|
+
dialog and fullscreen, and the failures it can switch on. Check each renders what you chose,
|
|
101
|
+
with nothing unexpected in its message log.
|
|
102
|
+
- **Set each state up from the address** rather than by clicking: one URL per state, e.g.
|
|
103
|
+
`http://localhost:5190/#?type=none&viewer=&display=dialog&token=forbidden`, or
|
|
104
|
+
`#settings?preferences=en-US` for the settings page. The studio's README
|
|
105
|
+
(`node_modules/@livespace/plugin-studio/README.md`) lists the params, and the log notes what
|
|
106
|
+
it set and what it ignored.
|
|
107
|
+
- **Saved settings go through the settings page**, never the address: fill in its form and
|
|
108
|
+
Save, or Forget for `null`.
|
|
109
|
+
- **Read the log from the browser console**, not the page: each entry is a line prefixed
|
|
110
|
+
`[studio]`. The studio's notes are warnings, so read those first: anything it refused or
|
|
111
|
+
dropped is a mistake to fix. The messages to and from the plugin are `debug` (with the
|
|
112
|
+
Playwright MCP, `browser_console_messages` with `level: "debug"`); read them when something
|
|
113
|
+
looks wrong.
|
|
114
|
+
- Setting up from the address and the console log need `@livespace/plugin-studio` 0.2 or
|
|
115
|
+
later.
|
|
116
|
+
- **Without a browser tool**, ask the author to do the same, and say what to look for.
|
|
117
|
+
- With a backend, point it at your studio with the env values it prints, and check it verifies
|
|
100
118
|
the plugin's token and reads its secrets.
|
|
101
119
|
- For a catalog plugin, `manifest check` passes.
|
|
102
120
|
|