@zalify/cli 0.1.0 → 0.1.2
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 +26 -0
- package/dist/cli.js +11300 -0
- package/package.json +22 -6
- package/bin/cli.js +0 -36
package/README.md
CHANGED
|
@@ -19,3 +19,29 @@ zalify --version # Output current version only
|
|
|
19
19
|
## Commands
|
|
20
20
|
|
|
21
21
|
- **version** – Prints `Zalify CLI version: x.x.x` and, if a newer version exists on npm, suggests running `npm i -g @zalify/cli@latest` to update.
|
|
22
|
+
|
|
23
|
+
## Development
|
|
24
|
+
|
|
25
|
+
Requires [Bun](https://bun.sh).
|
|
26
|
+
|
|
27
|
+
```bash
|
|
28
|
+
bun install
|
|
29
|
+
bun run dev version # Run CLI from source (TypeScript)
|
|
30
|
+
bun run build # Build to dist/
|
|
31
|
+
bun run typecheck # Type-check only
|
|
32
|
+
```
|
|
33
|
+
|
|
34
|
+
## Publishing
|
|
35
|
+
|
|
36
|
+
Publishing requires `NODE_AUTH_TOKEN`. Copy `.env.example` to `.env` and set your token (do not commit `.env`). You can also set `NODE_AUTH_TOKEN` in your shell.
|
|
37
|
+
|
|
38
|
+
Release only bumps the version in `package.json` (no git commit or tag). Commit and tag the version bump yourself if desired. Bun loads `.env` so `NODE_AUTH_TOKEN` is available.
|
|
39
|
+
|
|
40
|
+
```bash
|
|
41
|
+
bun run release # Default: patch (x.x.X)
|
|
42
|
+
bun run release -- -pa # Patch
|
|
43
|
+
bun run release -- -mi # Minor (x.X.0)
|
|
44
|
+
bun run release -- -ma # Major (X.0.0)
|
|
45
|
+
```
|
|
46
|
+
|
|
47
|
+
The release scripts load `.env` and fail with a clear error if `NODE_AUTH_TOKEN` is missing.
|