@vp-demo/create

Demo organization templates for Vite+. Showcases the createConfig.templates manifest by routing each entry to a different specifier type — bundled paths, external npm packages, and Vite+ builtins — all from a single picker.

Try it

# Interactive picker over the templates below
vp create @vp-demo

# Or pick a specific template directly
vp create @vp-demo:webapp
vp create @vp-demo:nuxt
vp create @vp-demo:vue
vp create @vp-demo:svelte
vp create @vp-demo:library
vp create @vp-demo:monorepo

What's inside

| Template | Specifier type | Scaffolds | | ---------- | --------------------- | ----------------------------------------------------------- | | webapp | bundled subdirectory | Opinionated Vite+ web app (TypeScript, oxlint, CI workflow) | | nuxt | external npm package | Nuxt application via create-nuxt | | vue | external npm package | Vue application via create-vue | | svelte | external npm package | SvelteKit application via create-svelte | | library | Vite+ builtin | TypeScript library via vite:library | | monorepo | bundled subdirectory | Vite+ monorepo with shared defaults |

The mix is intentional. An org-template manifest doesn't have to bundle every template — it can route to whatever already exists (npm package, Vite+ builtin, GitHub repo) and add bundled subdirectories only where you actually want custom opinions.

Authoring reference

See the Vite+ docs for the full manifest schema and authoring guide.