@velarscript/cli 0.24.0 → 0.25.0

package/dist/surface-versions.js

@@ -0,0 +1,72 @@
+import { VELAR_CORE_API_VERSION } from "@velarscript/compiler";
+/**
+ * D110 — one installation number, five surface versions.
+ *
+ * `VELAR_VERSION` is the number you install. It steps for every package at
+ * once, so it cannot say which of the five observable surfaces actually moved:
+ * Desktop's surface sat still for several releases while its package climbed
+ * with everybody else's. The surface versions answer the question an upgrade
+ * really raises — *which code do I have to re-read?*
+ *
+ * Every number here is read from the package that owns the surface. None of
+ * them is written down twice: D110's background is a website that accumulated
+ * two dozen hand-typed release numbers and had every one of them go stale in a
+ * single release, and a hand-typed number is the failure this whole mechanism
+ * exists to remove. `scripts/check-surface-versions.mjs` hashes each surface
+ * and refuses a change that leaves its number behind.
+ *
+ * `0.N`'s `N` counts how many times that surface has changed since counting
+ * began, and it is not a maturity grade: a low number beside a high one means
+ * that surface started counting later, and nothing else.
+ *
+ * The four target constants are imported *lazily*, and that is not an
+ * optimization detail — it is the difference between this file costing one
+ * command and costing all of them. Reading Web's, Server's and Desktop's
+ * numbers means loading three compiler extensions the CLI otherwise touches
+ * only when a project activates them, and a static import here would put that
+ * on the start of `velar check` and every other command for the sake of a
+ * banner almost none of them print. Core's constant is already loaded, because
+ * the compiler always is.
+ *
+ * Three of those four are also optional now (D111): a project installs the
+ * targets it declares, so a Core project has no Web, Server or Desktop package
+ * to read a number out of. The banner answers for the installation it is in —
+ * the same reading `velar.json`'s `surfaces` check already takes, where the
+ * installed packages, not the CLI's own pins, decide what a project activates.
+ * A surface with nothing installed to speak for it is left out rather than
+ * printed from a number written down here, which is exactly the second copy
+ * this file exists to avoid.
+ */
+export async function readSurfaceVersions() {
+    const [web, node, server, desktop] = await Promise.all([
+        installedSurface(() => import("@velarscript/web/compiler")),
+        import("@velarscript/node/compiler"),
+        installedSurface(() => import("@velarscript/server/compiler")),
+        installedSurface(() => import("@velarscript/desktop")),
+    ]);
+    // Declaration order is the order the surface table is printed in (D110 rule 6).
+    const versions = { core: VELAR_CORE_API_VERSION };
+    if (web)
+        versions.web = web.VELAR_WEB_API_VERSION;
+    versions.node = node.VELAR_NODE_API_VERSION;
+    if (server)
+        versions.server = server.VELAR_SERVER_API_VERSION;
+    if (desktop)
+        versions.desktop = desktop.VELAR_DESKTOP_API_VERSION;
+    return Object.freeze(versions);
+}
+/** One optional target's module, or null when this project did not install it. */
+async function installedSurface(load) {
+    try {
+        return await load();
+    }
+    catch {
+        return null;
+    }
+}
+/** One line, three spaces between entries: `core@<n>   web@<n>   …`. */
+export async function formatSurfaceVersions() {
+    const versions = await readSurfaceVersions();
+    return Object.entries(versions).map(([surface, version]) => `${surface}@${version}`).join("   ");
+}
+//# sourceMappingURL=surface-versions.js.map

package/dist/surface-versions.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"surface-versions.js","sourceRoot":"","sources":["../src/surface-versions.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,sBAAsB,EAAE,MAAM,uBAAuB,CAAC;AAE/D;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAqCG;AACH,MAAM,CAAC,KAAK,UAAU,mBAAmB;IACvC,MAAM,CAAC,GAAG,EAAE,IAAI,EAAE,MAAM,EAAE,OAAO,CAAC,GAAG,MAAM,OAAO,CAAC,GAAG,CAAC;QACrD,gBAAgB,CAAC,GAAG,EAAE,CAAC,MAAM,CAAC,2BAA2B,CAAC,CAAC;QAC3D,MAAM,CAAC,4BAA4B,CAAC;QACpC,gBAAgB,CAAC,GAAG,EAAE,CAAC,MAAM,CAAC,8BAA8B,CAAC,CAAC;QAC9D,gBAAgB,CAAC,GAAG,EAAE,CAAC,MAAM,CAAC,sBAAsB,CAAC,CAAC;KACvD,CAAC,CAAC;IACH,gFAAgF;IAChF,MAAM,QAAQ,GAA2B,EAAE,IAAI,EAAE,sBAAsB,EAAE,CAAC;IAC1E,IAAI,GAAG;QAAE,QAAQ,CAAC,GAAG,GAAG,GAAG,CAAC,qBAAqB,CAAC;IAClD,QAAQ,CAAC,IAAI,GAAG,IAAI,CAAC,sBAAsB,CAAC;IAC5C,IAAI,MAAM;QAAE,QAAQ,CAAC,MAAM,GAAG,MAAM,CAAC,wBAAwB,CAAC;IAC9D,IAAI,OAAO;QAAE,QAAQ,CAAC,OAAO,GAAG,OAAO,CAAC,yBAAyB,CAAC;IAClE,OAAO,MAAM,CAAC,MAAM,CAAC,QAAQ,CAAC,CAAC;AACjC,CAAC;AAED,kFAAkF;AAClF,KAAK,UAAU,gBAAgB,CAAI,IAAsB;IACvD,IAAI,CAAC;QACH,OAAO,MAAM,IAAI,EAAE,CAAC;IACtB,CAAC;IAAC,MAAM,CAAC;QACP,OAAO,IAAI,CAAC;IACd,CAAC;AACH,CAAC;AAED,wEAAwE;AACxE,MAAM,CAAC,KAAK,UAAU,qBAAqB;IACzC,MAAM,QAAQ,GAAG,MAAM,mBAAmB,EAAE,CAAC;IAC7C,OAAO,MAAM,CAAC,OAAO,CAAC,QAAQ,CAAC,CAAC,GAAG,CAAC,CAAC,CAAC,OAAO,EAAE,OAAO,CAAC,EAAE,EAAE,CAAC,GAAG,OAAO,IAAI,OAAO,EAAE,CAAC,CAAC,IAAI,CAAC,KAAK,CAAC,CAAC;AACnG,CAAC"}

package/dist/version.d.ts

@@ -1,3 +1,3 @@
-export declare const VELAR_VERSION = "0.24.0";
+export declare const VELAR_VERSION = "0.25.0";
 export { VELAR_STANDARD_API_VERSION } from "@velarscript/core";
 //# sourceMappingURL=version.d.ts.map

package/dist/version.js

@@ -1,3 +1,3 @@
-export const VELAR_VERSION = "0.24.0";
+export const VELAR_VERSION = "0.25.0";
 export { VELAR_STANDARD_API_VERSION } from "@velarscript/core";
 //# sourceMappingURL=version.js.map

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@velarscript/cli",
-  "version": "0.24.0",
+  "version": "0.25.0",
   "description": "The VelarScript command-line compiler, dev server, test runner, and language server.",
   "license": "Apache-2.0",
   "type": "module",
@@ -30,14 +30,30 @@
     "velar": "./dist/cli.js"
   },
   "dependencies": {
-    "@velarscript/compiler": "0.24.0",
-    "@velarscript/core": "0.24.0",
-    "@velarscript/desktop": "0.24.0",
-    "@velarscript/node": "0.24.0",
-    "@velarscript/server": "0.24.0",
-    "@velarscript/web": "0.24.0",
-    "create-velar": "0.24.0",
-    "esbuild": "^0.28.1",
+    "@velarscript/compiler": "0.25.0",
+    "@velarscript/core": "0.25.0",
+    "@velarscript/node": "0.25.0",
+    "create-velar": "0.25.0",
+    "esbuild": "^0.28.1"
+  },
+  "peerDependencies": {
+    "@velarscript/desktop": "0.25.0",
+    "@velarscript/server": "0.25.0",
+    "@velarscript/web": "0.25.0",
     "playwright": "^1.58.2"
+  },
+  "peerDependenciesMeta": {
+    "@velarscript/desktop": {
+      "optional": true
+    },
+    "@velarscript/server": {
+      "optional": true
+    },
+    "@velarscript/web": {
+      "optional": true
+    },
+    "playwright": {
+      "optional": true
+    }
   }
 }

package/skill/ai-skill-server.md

@@ -13,7 +13,7 @@ browser application activates `@velarscript/web`:
 ```json
 {
   "dependencies": {
-    "@velarscript/server": "0.24.0"
+    "@velarscript/server": "0.25.0"
   }
 }
 ```

package/skill/ai-skill.md

@@ -88,6 +88,16 @@ Writing the manifest yourself: `formatVersion` is required, `kind` may be
 omitted by a project that loads none, `entry` defaults to `src/main.vel`,
 `outDir` to `dist`, and `publicDir` to `public`.
 
+`surfaces` is optional and records the **surface version** the project was
+written against — `core`, plus one entry per activated extension. `velar create`
+writes it. **Never invent the values**: read them from `velar --version`, which
+prints the five the installed toolchain ships, or leave the key out. A
+declaration that is present must be complete — every activated surface and no
+others — and one that no longer matches what is installed is refused, naming the
+surface, both numbers, and the changelog sections between them. That refusal
+means the surface moved under the project: read those sections, fix the code,
+then write the new number. It is not a range to widen.
+
 A Core project (CLI or library) loads no extensions:
 
 ```json