gistajs 0.1.2 → 0.1.3
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 +30 -1
- package/dist/bin.cjs +657 -412
- package/dist/index.d.ts +25 -4
- package/dist/index.js +660 -411
- package/package.json +3 -2
package/README.md
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
# gistajs
|
|
2
2
|
|
|
3
|
-
Small CLI for
|
|
3
|
+
Small CLI for scaffolding and managing Gista.js starter projects.
|
|
4
4
|
|
|
5
5
|
## Usage
|
|
6
6
|
|
|
@@ -9,6 +9,9 @@ npx gistajs create my-app
|
|
|
9
9
|
npx gistajs create my-app --starter website --no-install --no-git
|
|
10
10
|
```
|
|
11
11
|
|
|
12
|
+
Today the CLI covers project creation, starter diffs, pin management, and Turso provisioning.
|
|
13
|
+
Vercel provisioning is the next intended provider in the same command family.
|
|
14
|
+
|
|
12
15
|
### Diff
|
|
13
16
|
|
|
14
17
|
Compare the starter changes since your project's pinned release:
|
|
@@ -31,6 +34,32 @@ Advance your project pin after accepting an upgrade:
|
|
|
31
34
|
npx gistajs pin 2026-04-01-001
|
|
32
35
|
```
|
|
33
36
|
|
|
37
|
+
### Pin Model
|
|
38
|
+
|
|
39
|
+
Scaffolded projects carry one base starter lineage for their lifetime.
|
|
40
|
+
That baseline lives in `package.json` as `gistajs.pin`:
|
|
41
|
+
|
|
42
|
+
```json
|
|
43
|
+
{
|
|
44
|
+
"gistajs": {
|
|
45
|
+
"pin": "form:2026-04-01-001"
|
|
46
|
+
}
|
|
47
|
+
}
|
|
48
|
+
```
|
|
49
|
+
|
|
50
|
+
`gistajs diff --latest` uses that pin as the starting point and compares it to the latest published release for the same starter.
|
|
51
|
+
After you accept an upgrade, advance the pin explicitly with `gistajs pin <release-key>`.
|
|
52
|
+
|
|
53
|
+
### Provision
|
|
54
|
+
|
|
55
|
+
Provision a Turso database for the current project and write `DB_URL` plus `DB_AUTH_TOKEN` into `.env`:
|
|
56
|
+
|
|
57
|
+
```bash
|
|
58
|
+
npx gistajs provision turso
|
|
59
|
+
```
|
|
60
|
+
|
|
61
|
+
The command is interactive. It checks Turso login state, lets you choose an org when needed, prompts for a database name and group, and asks before overwriting existing database credentials in `.env`.
|
|
62
|
+
|
|
34
63
|
## Development
|
|
35
64
|
|
|
36
65
|
```bash
|