@tokenoftrust/cli 2.0.17 → 2.0.19

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tokenoftrust/cli",
-  "version": "2.0.17",
+  "version": "2.0.19",
   "description": "Token of Trust developer CLI — clone a tenant store, run it locally with save→reload, and submit it for preview. Installs the `tot` command.",
   "license": "Apache-2.0",
   "author": "Token of Trust",

package/src/commands/dev.mjs

@@ -66,7 +66,7 @@ export function parseArgs(argv) {
   const a = {
     workspace: null, port: "4321", mcp: null,
     noLogin: false, noOpen: false, sample: false, help: false,
-    rendererVersion: null,
+    rendererVersion: null, resetCache: false,
   };
   for (let i = 0; i < argv.length; i++) {
     const t = argv[i];
@@ -77,12 +77,34 @@ export function parseArgs(argv) {
     else if (t === "--no-open") a.noOpen = true;
     else if (t === "--sample") a.sample = true;
     else if (t === "--renderer-version") a.rendererVersion = argv[++i];
+    else if (t === "--reset-cache") a.resetCache = true;
     else if (t === "--help" || t === "-h") a.help = true;
   }
   return a;
 }
 
-const USAGE = `tot dev — run your store locally with save→reload
+/**
+ * Delete the cached preview engines so the next run downloads and installs fresh.
+ *
+ * The recovery path this replaces was "hand-delete a directory under ~/.tot/cache" —
+ * which agent guidance forbids and no developer should have to know
+ * (fb-1789008798249-sc4tgy: the reporter had no way back to a working dev loop
+ * without it). A first-class flag makes the supported recovery discoverable in
+ * `tot dev --help`.
+ *
+ * Scoped deliberately to the renderer cache: it is a pure download+install artifact,
+ * rebuilt on demand, so removing it can only cost time. It never touches the
+ * tenant checkout, the login session, or anything else under ~/.tot.
+ * @param {{cacheRoot?: string, rm?: (p: string, o: object) => void}} [deps]
+ * @returns {{removed: boolean, path: string}}
+ */
+export function resetRendererCache({ cacheRoot = RENDERER_CACHE_ROOT, rm = rmSync } = {}) {
+  const existed = existsSync(cacheRoot);
+  rm(cacheRoot, { recursive: true, force: true });
+  return { removed: existed, path: cacheRoot };
+}
+
+export const USAGE = `tot dev — run your store locally with save→reload
 
   tot dev <tenant>              (in the monorepo) run tenants/<tenant>/
   tot dev                       (in a checkout) run this store natively (no Docker)
@@ -91,6 +113,7 @@ const USAGE = `tot dev — run your store locally with save→reload
   tot dev --workspace <dir>     run a specific checkout directory
   tot dev --port <n>            host port (default 4321)
   tot dev --no-open             don't auto-open the browser when the server is up
+  tot dev --reset-cache         delete the downloaded preview engines and re-fetch
 
 Edit content/*.html or the theme + save → the browser reloads. Private local
 preview — nothing is published. Prerequisites: Node.js and an invite (or just
@@ -104,6 +127,16 @@ export async function run(argv, ctx) {
     return 0;
   }
 
+  // Before anything else, so a wedged cache cannot break the very run meant to clear
+  // it. Then fall through and start normally: the flag is a modifier, not a separate
+  // command, because "clear it and go" is what a stuck developer actually wants.
+  if (args.resetCache) {
+    const { removed, path } = resetRendererCache();
+    console.error(removed
+      ? `~ cleared the preview-engine cache (${path}) — this run re-downloads it.`
+      : `~ no preview-engine cache to clear (${path}).`);
+  }
+
   // Resolve a free port up front so the URL we derive/open/print matches the port
   // the runner actually binds — Vite's strictPort is off, so a busy default would
   // silently drift and strand the browser/liveness poll on the wrong port. No-op
@@ -1039,6 +1072,36 @@ function sourceVersionKey(source) {
  * @param {{ log?: (m: string) => void, cacheRoot?: string }} [opts]
  * @returns {Promise<string>} the cached, installed runner tree's root directory.
  */
+/**
+ * Rename the runner's shipped lockfile back to the name pnpm reads, so a pinned runner
+ * version pins the graph it RUNS rather than just its own source.
+ *
+ * npm strips `pnpm-lock.yaml` from published tarballs unconditionally (the same
+ * always-excluded list as package-lock.json / yarn.lock), so build-runner.mjs emits a
+ * second copy as `pnpm-lock.runner.yaml`, which survives the publish. Verified both
+ * directions: the published 2.0.33 tarball carries pnpm-workspace.yaml and no lock,
+ * and a packed 2.0.34 tree delivers only the alias.
+ *
+ * Why it matters: without the restore, every developer resolves their own graph. Runner
+ * 2.0.33 was built against vite 8.1.0 / rolldown 1.1.3 and installed as 8.2.2 / 1.2.8,
+ * where an .astro parse regression failed the dependency scan — and Vite answers a
+ * failed scan by skipping pre-bundling for the whole app rather than erroring, silently
+ * disabling the SSR prebundle the renderer's own config depends on. Pages still
+ * rendered, so nothing caught it.
+ *
+ * Never clobbers an existing `pnpm-lock.yaml`: the entitled .tar.gz path is a plain
+ * tarball rather than an npm publish, so it already carries the real name.
+ * @param {string} dir the extracted runner tree
+ * @returns {boolean} whether a lock was restored
+ */
+export function restoreShippedLock(dir) {
+  const alias = join(dir, "pnpm-lock.runner.yaml");
+  const real = join(dir, "pnpm-lock.yaml");
+  if (!existsSync(alias) || existsSync(real)) return false;
+  renameSync(alias, real);
+  return true;
+}
+
 export async function installRunnerTarball(
   { source, version, isUrl = true, strip = 0, integrity = null },
   { log = (m) => console.error(m), cacheRoot = RENDERER_CACHE_ROOT } = {},
@@ -1137,6 +1200,8 @@ export async function installRunnerTarball(
         /** @type {any} */ (err).permanent = true;
         throw err;
       }
+      // Must run BEFORE the install, or it has no effect at all.
+      restoreShippedLock(stagingDir);
       // Pin the runner install to PUBLIC npm. The moat-free runner has only public
       // deps, but the HOST's global ~/.npmrc may point `registry` at a private
       // mirror (an internal proxy that 502s, or one an invited developer can't