cascivo 1.2.1 → 1.3.0
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.
- package/README.md +2 -1
- package/dist/generated/audit-contract.json +1 -1
- package/dist/index.mjs +257 -55
- package/dist/index.mjs.map +1 -1
- package/package.json +2 -2
- package/readme.body.md +2 -1
package/README.md
CHANGED
|
@@ -22,6 +22,7 @@ The `cascivo` CLI drives the copy-paste workflow — it scaffolds config, copies
|
|
|
22
22
|
|
|
23
23
|
```sh
|
|
24
24
|
npx cascivo create my-app # scaffold a full app — Vite + React, app shell, side nav, theme
|
|
25
|
+
npx cascivo create my-app --framework astro # …as an Astro site instead (file routing, zero-JS pages)
|
|
25
26
|
npx cascivo create my-app --template owner/repo/dashboard # …and start from a template
|
|
26
27
|
npx cascivo init # scaffold cascivo.config.ts + tokens; detects your package manager
|
|
27
28
|
cascivo add button card # copy component source from the registry into your project
|
|
@@ -47,7 +48,7 @@ A **template** is a registry item (`type: "template"`) that bundles a working pa
|
|
|
47
48
|
|
|
48
49
|
## How it works
|
|
49
50
|
|
|
50
|
-
`create` scaffolds a complete Vite + React + TypeScript app — pre-wired with the cascivo app shell, side navigation, header, and your chosen theme. It asks for a project name, theme, and the nav sections you want, then generates a section component for each. Pass `--theme`, `--sections "Dashboard, Reports"`, or `--yes` to skip the prompts. `init` detects npm / pnpm / yarn / bun, writes `cascivo.config.ts`, and wires up the token and theme imports. `add` resolves each component from [`registry.json`](https://github.com/cascivo/cascivo/blob/main/registry.json), fetches its source (TSX + CSS module + manifest) from GitHub raw URLs, and drops it into the path from your config — pulling in any dependencies it needs.
|
|
51
|
+
`create` scaffolds a complete app in one of two shapes. The default, `--framework react-vite`, is a Vite + React + TypeScript SPA; `--framework astro` emits an Astro site where pages are real file routes, page content renders to static HTML with no JavaScript, and only the app shell hydrates — including the `vite.resolve.noExternal` line Astro requires for cascivo's component CSS to be emitted at all. Both come pre-wired with the cascivo app shell, side navigation, header, and your chosen theme. It asks for a project name, framework, theme, and the nav sections you want, then generates a section component for each. Pass `--theme`, `--sections "Dashboard, Reports"`, or `--yes` to skip the prompts. `init` detects npm / pnpm / yarn / bun, writes `cascivo.config.ts`, and wires up the token and theme imports. `add` resolves each component from [`registry.json`](https://github.com/cascivo/cascivo/blob/main/registry.json), fetches its source (TSX + CSS module + manifest) from GitHub raw URLs, and drops it into the path from your config — pulling in any dependencies it needs.
|
|
51
52
|
|
|
52
53
|
Because the registry model is open, `add owner/repo/component` installs from any compatible registry, not just the first-party one. See the [registry starter](https://github.com/cascivo/cascivo/tree/main/apps/examples/registry-starter) to publish your own.
|
|
53
54
|
|