Packages Overview
VUP packages are incremental capabilities. Start with templates, then add only what you need.
How to Add Packages
bash
vup package add <packageName>Available Packages
| Package | Purpose | Typical Use Case | Doc |
|---|---|---|---|
@vup/ui | Desktop UI abstraction | Admin systems and desktop web apps | UI |
@vup/ui-mobile | Mobile UI abstraction | Mobile-first and hybrid projects | UI Mobile |
@vup/http | Shared request layer | Unified interceptors, error handling, request base | HTTP |
@vup/mock | Mock capability based on MSW | Frontend-first development, pre-backend integration | Mock |
@vup/pwa | PWA preset and runtime | Web app installability and offline capability | PWA |
@vup/iconfont | Icon asset integration | Team-managed icon set and icon font delivery | Iconfont |
@vup/richeditor | Rich text capability | CMS/editor-like content input | RichEditor |
@vup/nest-upload | File upload module for Nest | Upload pipelines and file metadata handling | Nest Upload |
Capability Examples
Examples are documented separately because they are added with vup example add, not vup package add. See Examples Overview.
Recommended Adoption Path
- Initialize project and apps first (
vup init+vup app add). - Add one package at a time around real requirements.
- Keep package usage minimal and composable.