@samva/cli 0.6.0 → 0.7.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/AGENTS.md +5 -1
- package/README.md +8 -0
- package/dist/bin.mjs +4483 -3814
- package/package.json +13 -12
package/AGENTS.md
CHANGED
|
@@ -38,7 +38,7 @@ image or font as unsaved bytes at `assets/<file name>` unless `--path` names ano
|
|
|
38
38
|
`--replace` is required to change a path that already holds a file. The Git commands remain the way
|
|
39
39
|
to author a project you have cloned.
|
|
40
40
|
|
|
41
|
-
`samva brands pull [slug]` writes the brand snapshot `.samva/brands/<slug>.json` that
|
|
41
|
+
`samva brands pull [slug]` writes the brand snapshot `.samva/brands/<slug>.json` that the CLI
|
|
42
42
|
resolves `samva:brand` from offline; bare `pull` snapshots the default brand, and `theme.css` is
|
|
43
43
|
never written. Keep `.samva` gitignored. `samva brands push <file>` validates brand CSS locally,
|
|
44
44
|
exits `1` with located findings when it is outside the brand grammar, and otherwise replaces the
|
|
@@ -74,3 +74,7 @@ when it is missing; other CLI commands are self-contained.
|
|
|
74
74
|
the matching platform-specific `@samva/cli-*` executable and falls back to the packaged JavaScript
|
|
75
75
|
CLI through Bun when npm omits optional dependencies. Depend on `@samva/cli`, never a native
|
|
76
76
|
artifact directly.
|
|
77
|
+
|
|
78
|
+
Keep Samva brand resolution in the CLI and pass `samvaBrandPlugin` to the project's authoring
|
|
79
|
+
toolchain, so standalone `@samva/vite` stays independent of Samva authentication and storage.
|
|
80
|
+
Standalone callers supply their own resolver. The README owns resolution order and configuration.
|
package/README.md
CHANGED
|
@@ -221,6 +221,14 @@ automation path.
|
|
|
221
221
|
editor from the project's `@samva/vite/dev` under Node.js, with no `vite.config.ts`. It prints the
|
|
222
222
|
editor URL and runs until interrupted; `SIGINT` and `SIGTERM` close the server.
|
|
223
223
|
|
|
224
|
+
The CLI supplies Samva brand resolution to `dev`, `check`, `build`, `render`, `snapshot` and
|
|
225
|
+
`export`. An imported `samva:brand` uses `SAMVA_API_KEY` from the environment or project `.env`
|
|
226
|
+
(and `SAMVA_API_URL` for another endpoint), or `samva brands get --json` on `PATH` with your login
|
|
227
|
+
session. Live answers refresh `.samva/brands/<slug>.json`; an unavailable live brand falls back to
|
|
228
|
+
that snapshot with `brand-offline`. A changed live digest reports `brand-snapshot-stale`. With
|
|
229
|
+
neither a live answer nor a snapshot, the command fails with `brand-unavailable`. Keep `.samva/`
|
|
230
|
+
gitignored. Standalone `@samva/vite` callers configure a resolver themselves.
|
|
231
|
+
|
|
224
232
|
`samva templates check` runs the project's TypeScript configuration, then uses the project's
|
|
225
233
|
`@samva/vite/build` to compile every template, render every fixture, and report located findings
|
|
226
234
|
plus email-client compatibility findings. It writes no files and exits non-zero on TypeScript,
|