You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 5663ab6
Browse filesBrowse the repository at this point in the historyBrowse files
refactor(config-generator): rewrite the frontend around layered Svelte stores
Replace the controller god-object with a WASM bridge, a session store with
derived selectors, and dedicated workbench, theme, viewport, URL, and DOM
modules shared through Svelte context. Split components under ui/components
and restyle with design tokens, preserving the existing DOM contract. Add
Vitest unit tests and wire them into the build, check recipe, and docs.
Assisted-by: opencode:deepseek-flash
Copy file name to clipboardExpand all lines: AGENTS.md
+4-3Lines changed: 4 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -38,7 +38,7 @@ Standalone build:
38
38
npm run build --prefix config-generator
39
39
```
40
40
41
-
`npm run build` compiles the Rust library with the locked wasm-pack, runs the Svelte/TypeScript checks, and then bundles the local JS/CSS/WASM with Vite. The first build downloads the wasm-bindgen tool matching the Cargo lock file. `npm run dev` compiles WASM first and then starts Vite; Svelte/CSS supports hot reloading. After changing Rust or XML, run `npm run wasm --prefix config-generator` in another terminal and refresh the browser.
41
+
`npm run build` compiles the Rust library with the locked wasm-pack, runs the Svelte/TypeScript checks and the frontend unit tests, and then bundles the local JS/CSS/WASM with Vite. The first build downloads the wasm-bindgen tool matching the Cargo lock file. `npm run dev` compiles WASM first and then starts Vite; Svelte/CSS supports hot reloading. After changing Rust or XML, run `npm run wasm --prefix config-generator` in another terminal and refresh the browser.
42
42
43
43
The default build embeds every application schema listed in `config-generator/schema/schemas.txt`; the browser switches between them without fetching XML. `CONFIG_SCHEMA` still selects one XML for isolated reuse tests; paths are relative to `config-generator/` (or absolute). Alternative builds should output to a separate directory, and the environment and default WASM must be restored afterward; see the generator's DSL guide.
0 commit comments