vite-plus 0.1.20-alpha.3 → 0.1.20

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -1,35 +0,0 @@
1
- # Create Config
2
-
3
- `vp create` reads the `create` block in `vite.config.ts` to set per-repo defaults. See the [Creating a Project guide](/guide/create#organization-templates) for the full `@org` template workflow.
4
-
5
- ## `create.defaultTemplate`
6
-
7
- When `vp create` is invoked with no `TEMPLATE` argument, Vite+ uses this value as if the user had typed it. Typically set to an npm scope whose `@scope/create` package publishes a `createConfig.templates` manifest — so bare `vp create` drops into the org picker.
8
-
9
- ```ts
10
- import { defineConfig } from 'vite-plus';
11
-
12
- export default defineConfig({
13
- create: {
14
- defaultTemplate: '@your-org',
15
- },
16
- });
17
- ```
18
-
19
- Any value accepted by `vp create` as a first argument works here — `@your-org` for an org picker, `@your-org:web` for a direct manifest entry, `vite:application` for a built-in, etc.
20
-
21
- ## Precedence
22
-
23
- CLI argument > `create.defaultTemplate` > the standard built-in picker.
24
-
25
- Explicit specifiers always win, so scripts and CI can bypass the configured default:
26
-
27
- ```bash
28
- # Uses create.defaultTemplate
29
- vp create
30
-
31
- # Explicitly ignores the default
32
- vp create vite:library
33
- ```
34
-
35
- The org picker also appends a trailing "Vite+ built-in templates" entry — selecting it routes to the `vite:monorepo` / `vite:application` / `vite:library` / `vite:generator` flow, so built-ins stay reachable interactively even when a default is configured.