vertesia-plugin
Framework for building Vertesia plugins with a dual tool-server and UI architecture, featuring Hot Module Replacement, build-tools, and asset management.
Introduction
The Vertesia plugin development environment provides a comprehensive foundation for creating, testing, and deploying modular extensions for the Vertesia platform. By utilizing a dual-architecture approach, developers can simultaneously maintain a robust Hono-based backend (tool server) and a feature-rich React frontend (UI plugin) within a single repository. This structure ensures that server-side logic, such as data processing or external API integrations, remains strictly separated from the client-side user experience while maintaining shared build configurations.
- Dual build system using Rollup for server-side ESM compilation and Vite for optimized React component bundling.
- Advanced import hooks via @vertesia/build-tools that automatically resolve and transform Markdown skill definitions, interaction prompts, and content templates at build time.
- Support for diverse resource types including ToolCollections, SkillCollections, InteractionCollections, and RenderingTemplateCollections.
- Integrated development workflow with pnpm commands for server-side hot-reloading (via start:watch) and frontend HMR.
- Extensible UI component system capable of standalone development or production integration as a Vertesia library.
- Built-in schema validation for tools and interactions, ensuring type safety through TypeScript and JSON Schema interfaces.
Developers should utilize the predefined starter directories in the tool-server to define plugin logic, using the ?skills and ?templates query parameters for auto-discovery of modular components. The tool server acts as the primary execution engine, allowing for custom Hono handlers and MCP provider integrations. When developing the UI, ensure that asset resolution is handled through the project-specific configuration to maintain parity between standalone dev environments and integrated plugin deployment. Practical constraints include the necessity of following the specific directory structure for resource auto-discovery and adhering to the provided Rollup/Vite configuration patterns to ensure successful deployment to the Vertesia host.
Repository Stats
- Stars
- 5
- Forks
- 1
- Open Issues
- 42
- Language
- TypeScript
- Default Branch
- main
- Sync Status
- Idle
- Last Synced
- May 3, 2026, 07:13 PM