Files
Adrian Lyjak 758c5cf294 Configure Vite HMR client port via environment variable (#201)
* feat: add LLAMA_DEPLOY_SERVER_PORT HMR clientPort to template vite configs

Set hmr.clientPort to LLAMA_DEPLOY_SERVER_PORT when defined, enabling
Vite HMR websocket connections to work through the server proxy.

https://claude.ai/code/session_01Hq5ZQxquwtyJVJ2qw48bbt

* feat: add LLAMA_DEPLOY_SERVER_PORT HMR support to template vite configs

Add hmr.port and hmr.clientPort to all template vite configs so that
Vite HMR websocket connections work through the server proxy. When
LLAMA_DEPLOY_SERVER_PORT is set, clientPort directs the browser's HMR
websocket to connect via the proxy server port.

Bump patch versions for all affected templates.

https://claude.ai/code/session_01Hq5ZQxquwtyJVJ2qw48bbt

---------

Co-authored-by: Claude <noreply@anthropic.com>
2026-01-27 17:58:46 -05:00
..

Data Extraction UI

This is a simple next.js template that builds on the @llamaindex/agent-app ui component library for showing displaying tables of extracted data.

Ideally run this with llamactl in the parent directory (See README.md), but you can also run it standalone with npm run dev, but workflow integrations will not work