@spaethtech/svelte-ui 0.21.1-dev.124.7b5c577 → 0.21.1-dev.125.4911439
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/CLAUDE.md +19 -4
- package/package.json +1 -1
package/CLAUDE.md
CHANGED
|
@@ -148,12 +148,27 @@ for just the library artifact.
|
|
|
148
148
|
**IMPORTANT**: Drive the running demo site when working on UI components — verify behavior in a real
|
|
149
149
|
browser, don't rely on `svelte-check` alone.
|
|
150
150
|
|
|
151
|
-
|
|
151
|
+
**The dev stack is ALWAYS running — you never cold-build the demo.** A Docker container
|
|
152
|
+
(`svelte-ui-demo-1`, `node:24`, cmd `npm run dev:linked`) runs the Vite dev server **continuously
|
|
153
|
+
with HMR**, bind-mounting this repo (`/home/rspaeth/svelte-ui -> /svelte-ui`), so every edit you save
|
|
154
|
+
here hot-reloads into the live site within seconds. So "verify in a browser" needs **no build and no
|
|
155
|
+
memory** on your part — the compile already happened and stays warm. (This sandbox is small — ~1.9 GB
|
|
156
|
+
RAM, 1 vCPU — so a *second*, cold `npm run dev`/`vite build` in here can OOM; that's why you use the
|
|
157
|
+
already-running container, not a fresh build. `npm run package` is light and is fine to run.)
|
|
158
|
+
|
|
159
|
+
Reach it without `localhost` publishing: the container exposes `5173` on the Docker network (not a
|
|
160
|
+
host port). Get its IP with `docker inspect svelte-ui-demo-1 --format '{{range .NetworkSettings.Networks}}{{.IPAddress}}{{end}}'`
|
|
161
|
+
(e.g. `http://172.18.0.2:5173/<route>`), or go through Caddy at `https://svelte-ui.spaethtech.dev`
|
|
162
|
+
(`svelte-ui-caddy-1` proxies to it; `php-svelte.spaethtech.dev` → the host `:5173`). `curl` the route
|
|
163
|
+
first to confirm it serves, then point a browser at it.
|
|
152
164
|
|
|
153
165
|
Use the **`/playwright-cli`** workflow for browser-driven testing (navigation, snapshots/screenshots,
|
|
154
|
-
console inspection, interaction). Point it at the
|
|
155
|
-
|
|
156
|
-
|
|
166
|
+
console inspection, interaction). Point it at the **container IP** `:5173` and the relevant demo route
|
|
167
|
+
(e.g. `/tabstrip`). The old Chrome DevTools MCP (`.mcp.json` + `chrome-devtools-mcp`) has been removed
|
|
168
|
+
in favor of this. **Browser-binary gotcha:** the Playwright in `node_modules` and the cached browser
|
|
169
|
+
revision can mismatch (e.g. it wants `headless_shell-1181` but the cache has `chromium-1229`); pass
|
|
170
|
+
`executablePath` to the installed `~/.cache/ms-playwright/chromium-*/chrome-linux64/chrome` instead of
|
|
171
|
+
re-downloading.
|
|
157
172
|
|
|
158
173
|
### Demo pages (`src/routes/<component>/`)
|
|
159
174
|
|