web

Wickra Terminal — Web renderer

The browser renderer of the Wickra trading terminal: a Vue 3 + Vite front-end over the WASM binding (bindings/wasm). It runs the exact same wickra-terminal-core as the native TUI, compiled to WebAssembly, and renders the identical frame view-models — the chart to a canvas, the book/tape/watchlist to the DOM.

Web and TUI are two renderers of one core, not two products.

Prerequisites

Build the WASM binding first (the web app depends on its pkg/ via a file: dependency):

( cd ../bindings/wasm && wasm-pack build --target web )

Develop

npm install
npm run dev        # http://localhost:5173

Test

npm test           # vitest, no browser and no WASM needed

The suite covers the pure mappings: config rects to CSS placement, and Binance stream messages to the core's event JSON. Anything that needs the real core is tested in the WASM binding's own suite, which drives the module through the same JSON boundary every other language uses.

Build

npm run build      # vue-tsc typecheck + vite build -> dist/
npm run preview

Notes

• The default source is the deterministic Synth feed; the layout is persisted in localStorage.
• A live source runs over the browser's own WebSocket (the native exchange client cannot run in a sandbox); real order execution needs a backend and is gated separately.
• package.json carries one overrides entry, forcing uuid to ^11.1.1. vite-plugin-top-level-await depends on exactly uuid@10.0.0 and has no release that does otherwise, so the advisory against uuid 10 (GHSA-w5hq-g745-h8pq) cannot be cleared by upgrading the plugin. The plugin is not actually affected -- its only call is v5(seed, namespace) and the advisory needs the optional buf argument -- so the override exists to satisfy the scanners rather than to fix a live bug, and the plugin's identifier generator was checked under uuid 11. Drop the override once the plugin ships a release that depends on a patched uuid; keeping it after that point only pins a version nothing asks for.