@turri-dev/cli 0.1.6-next.10e70aa → 0.1.6

package/README.md

@@ -190,7 +190,7 @@ Start at the [documentation index](docs/README.md), or go straight to a page:
 | | |
 | --- | --- |
 | [Installation](docs/installation.md) | doctor, what turri needs of this machine, **turri** and `pi`, environment variables |
-| [Examples](examples/README.md) | projects to build with turri step by step: cognio from an empty folder, a CLI, a backend service with conformance tests, a REST API integration |
+| [Examples](examples/README.md) | projects to build with turri step by step: cognio from an empty folder, guestbook - a backend and a frontend in minutes - a CLI, a backend service with conformance tests, a REST API integration |
 | [Using **turri**](docs/using.md) | the conversation, skills, tools, pulses and regen, choosing models, the command line |
 | [The project config](docs/config.md) | `config.turri.yaml` and each stack's `config.turri.<stack>.yaml`: every key, models and their inheritance, conformance, the testing scripts, stacks and choosing one, the old `config.yaml` |
 | [Deploy](docs/deploy.md) | trying what is built: the last commit in `dist/<module>`, started on your machine, nothing installed without asking |

package/dist/cli.js

@@ -19,7 +19,7 @@ import { dirname, join } from "node:path";
 import { fileURLToPath } from "node:url";
 import { CODING_MODEL_ENV, chatModels } from "./chat-models.js";
 import { readProjectConfig } from "./config.js";
-import { extensionInstalledGlobally, PACKAGE_ROOT, themesInstalledGlobally } from "./environment.js";
+import { extensionInstalledGlobally, PACKAGE_ROOT, themesInstalledGlobally, versionLine } from "./environment.js";
 import { dropNoise } from "./quiet.js";
 /**
  * Start pi with this project's extension and themes already wired in.
@@ -92,6 +92,7 @@ const SETUP_COMMANDS = {
 const USAGE = [
     "usage: turri [options]          open the conversation here: pi, with turri's tools and themes loaded",
     "       turri <command> [args]",
+    "       turri --version          turri's version, and pi's",
     "",
     `  ${"options".padEnd(12)} --harness-model <m>  the model you chat with   --coding-model <m>  the model renders run on`,
     `  ${"".padEnd(12)} --stack <name>  build with config.turri.<name>.yaml over config.turri.yaml - here and in every command`,
@@ -139,6 +140,11 @@ if (command === "-h" || command === "--help") {
     console.log(USAGE);
     process.exit(0);
 }
+// turri's version, not pi's alone: pi's --version would answer for it.
+if (command === "-v" || command === "--version") {
+    console.log(versionLine());
+    process.exit(0);
+}
 // turri alone is the conversation, and so is turri with pi's options - `turri -c`, `turri --harness-model <m>`. A word
 // turri does not know is an error below, not a conversation started on it.
 if (command === undefined || command.startsWith("-"))

package/dist/environment.js

@@ -68,6 +68,32 @@ export function turriOnPath() {
     const found = which.status === 0 ? which.stdout.trim().split("\n")[0] : undefined;
     return found === "" ? undefined : found;
 }
+/** The version of the pi turri runs on, as Node finds it - undefined when it is not installed. */
+export function piVersion() {
+    try {
+        // Its entry point, then up to the package.json that names it.
+        for (let dir = dirname(fileURLToPath(import.meta.resolve("@earendil-works/pi-coding-agent"))); dirname(dir) !== dir; dir = dirname(dir)) {
+            const file = join(dir, "package.json");
+            if (!existsSync(file))
+                continue;
+            const pkg = JSON.parse(readFileSync(file, "utf8"));
+            if (pkg.name === "@earendil-works/pi-coding-agent")
+                return pkg.version;
+        }
+    }
+    catch {
+        /* not installed: left out */
+    }
+    return undefined;
+}
+/**
+ * What `turri --version` prints: turri's version - from a clone, its commit too, as the banner says it - and pi's
+ * beside it. pi's own `--version` says only pi's, which read as turri's.
+ */
+export function versionLine(identity = turriIdentity(), pi = piVersion() ?? null) {
+    const clone = identity.git_commit !== null ? `, from a clone, ${identity.git_commit.slice(0, 7)}${identity.git_dirty === true ? " with changes" : ""}` : "";
+    return `turri ${identity.version ?? "0.0.0"}${clone}${pi !== null ? ` (pi ${pi})` : ""}`;
+}
 /** turri's version, and the commit when it runs from a clone. */
 export function turriIdentity() {
     let version = null;

package/docs/installation.md

@@ -17,7 +17,7 @@ turri init-config   # a config.turri.yaml with the model you talk to and the one
 turri               # pi, with turri's tools, skills and themes loaded
 ```
 
-The package is `@turri-dev/cli` - npm keeps the name `turri` back, as too like another package's - and the command it puts on your PATH is `turri`. `npm install -g @turri-dev/cli@next` gets the latest prerelease instead, built from the last commit on `main`.
+The package is `@turri-dev/cli` - npm keeps the name `turri` back, as too like another package's - and the command it puts on your PATH is `turri`. `npm install -g @turri-dev/cli@next` gets the latest prerelease instead, built from the last commit on `main`. Installed again - `@latest` or `@next` - it replaces the one there. `turri --version` says which turri runs, and the pi under it: `turri 0.1.6 (pi 1.3.0)`, and from a clone its commit too.
 
 ## From a clone
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@turri-dev/cli",
-  "version": "0.1.6-next.10e70aa",
+  "version": "0.1.6",
   "license": "MIT",
   "type": "module",
   "repository": {