* ui: import Lucide icons by path in modules that run in Node Assisted-by: Claude (Opus 5.5 Medium) * ui: register highlight.js languages once, from lowlight's modules Assisted-by: Claude (Opus 5.5 Medium) * ui: load the pdf.js worker and nerdamer as files of their own Assisted-by: Claude (Opus 5.5 Medium) * ui: draw Mermaid diagrams with Pele Assisted-by: Claude (Opus 5.5 Medium) * ui: pin dependency versions and use one Svelte across the UI packages Assisted-by: Claude (Opus 5.5 Medium) * ui: build Llama Chat as split chunks Assisted-by: Claude (Opus 5.5 Medium) * ui: load KaTeX and pdf.js on first use Assisted-by: Claude (Opus 5.5 Medium)
ui
The UI of llama.cpp: the packages in lib and the apps built on them.
ui/
├── lib/
│ └── ui/ @ggml-org/llama-ui: design tokens, fonts, surfaces and components
└── apps/
└── chat/ Llama Chat, the chat app that llama-server serves
lib/uidraws the parts and handles interaction, with no business logic. It is built with@sveltejs/packageand published to npm as@ggml-org/llama-ui. Apps in this repo skip the package: they compile its sources as part of their own build, so they hold no copy of a component, a token or a font.apps/chattalks to llama-server, stores conversations and runs the agentic loop. CMake builds it into llama-server (seescripts/ui-assets.cmake), and it is published to npm as@ggml-org/llama-chat(withllama-chatas its short name), sonpx llama-chatruns it against any llama-server.
Each folder is its own npm package with its own package-lock.json: run npm ci in the one you work on. Building,
checking and testing apps/chat needs no install in lib/ui.
Releases
The npm packages are versioned by hand, with semver, and published by CI:
| Package | Version in | Published by |
|---|---|---|
@ggml-org/llama-ui |
lib/ui/package.json |
ui-lib-publish.yml |
@ggml-org/llama-chat and llama-chat |
apps/chat/package.json and apps/chat/alias/package.json, always the same |
ui-chat-publish.yml |
To release, bump the version in the PR that should ship the change: a patch for fixes, a minor for new or changed
features or API while the version is 0.x. When that PR reaches master with a version npm does not have yet, the
workflow builds the package and publishes it; any other commit publishes nothing. A version lower than the one on npm
fails the run.
Llama Chat as bundled in llama-server is not versioned this way: it ships in every llama.cpp release, as b<build>.