@looop-games/cli 0.1.10 → 0.1.12

package/CHANGELOG.md

@@ -14,6 +14,38 @@ Versions: [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
 ## [Unreleased]
 
+## [0.1.12] - 2026-07-12
+
+### Added
+- `looop lint` — check your game against the Looop rules: the mistakes that ship
+  a broken game while every test stays green. `looop lint --fix` applies the ones
+  that can be fixed mechanically.
+- `looop test` now runs the lint first, before it starts a browser. A hardcoded
+  multiplayer host is reported in a second, instead of after a full smoke run
+  that passed for the wrong reason.
+
+  The rules themselves live in the engine (so `looop update` brings you new ones)
+  and your game's `eslint.config.js` imports the same file the gate runs — the
+  editor and the test can't disagree. Nothing changes for an existing game until
+  you install eslint (`npm i -D eslint`); new games get it out of the box.
+
+## [0.1.11] - 2026-07-12
+
+### Fixed
+- `looop update` now updates the **`looop` command itself**, not just the engine.
+  It used to leave the command at whatever version your game had pinned — so an
+  update could hand you an engine whose skills tell you to run a command your
+  `looop` was too old to have (`Unknown command: changelog`). It now moves both,
+  and says which versions it moved you between.
+
+  If you are seeing `Unknown command` today, you are on a `looop` from before
+  this fix and it cannot update itself. Run this once, and it will keep itself
+  current from then on:
+
+  ```bash
+  npm update @looop-games/cli
+  ```
+
 ## [0.1.10] - 2026-07-12
 
 ### Added

package/bin/looop.mjs

@@ -8,6 +8,7 @@ import { login, whoami } from '../lib/login.mjs';
 import { publish } from '../lib/publish.mjs';
 import { create } from '../lib/create.mjs';
 import { testCmd } from '../lib/test-cmd.mjs';
+import { lintCmd } from '../lib/lint.mjs';
 import { update } from '../lib/update.mjs';
 import { changelog } from '../lib/changelog.mjs';
 import { sendFeedback } from '../lib/feedback.mjs';
@@ -26,6 +27,7 @@ Usage:
   looop create <name>        Bootstrap a new game folder (multiplayer works out of the box)
   looop dev [--port <n>]     Run the full dev stack (game + multiplayer + services)
   looop test                 Run the game's tests (*.test.mjs) and smokes (*.smoke.mjs)
+  looop lint [--fix]         Check the game against the Looop rules (runs inside 'looop test')
   looop changelog [<v>]      What changed in the engine (default: everything newer than your pin)
   looop update               Move this game to the latest engine release (re-pins looop.engine)
   looop publish [--slug <s>]  Publish this game to play.looop.games (--slug for an A/B copy)
@@ -59,6 +61,10 @@ try {
       const { ok } = await testCmd();
       process.exit(ok ? 0 : 1);
     }
+    case 'lint': {
+      const { ok } = await lintCmd({ fix: rest.includes('--fix') });
+      process.exit(ok ? 0 : 1);
+    }
     case 'changelog':
       await changelog({
         version: rest.find((a) => !a.startsWith('--')),

package/lib/create.mjs

@@ -67,6 +67,14 @@ const ALLOW_SCRIPTS = { esbuild: true, workerd: true, fsevents: true };
 // what create-time provisioning exists to prevent.
 const PLAYWRIGHT_SPEC = '^1.61.1';
 
+// The Looop rules ship as an ESLint config (the scaffold's eslint.config.js,
+// importing the rules from the installed engine), so they squiggle in the
+// creator's editor as the code is written — a far tighter loop than a failing
+// gate, and the whole reason this is ESLint and not a bespoke scanner. That
+// only works if eslint is actually installed, so it is a scaffold
+// devDependency, exactly like playwright. `looop test` also runs it.
+const ESLINT_SPEC = '^10.7.0';
+
 // Copy the starter game out of the artifact. One rename: `gitignore` →
 // `.gitignore` (npm pack silently strips .gitignore files from a package, so
 // the artifact stores it dot-less).
@@ -105,8 +113,8 @@ async function scaffold({ dir, name, install, cliSpec, apiBase, log, ensure, rec
         name,
         private: true,
         description: `A Looop game. Play at https://play.looop.games/g/${name}`,
-        scripts: { dev: 'looop dev', publish: 'looop publish', test: 'looop test' },
-        devDependencies: { '@looop-games/cli': cliSpec, playwright: PLAYWRIGHT_SPEC },
+        scripts: { dev: 'looop dev', publish: 'looop publish', test: 'looop test', lint: 'looop lint' },
+        devDependencies: { '@looop-games/cli': cliSpec, playwright: PLAYWRIGHT_SPEC, eslint: ESLINT_SPEC },
         allowScripts: ALLOW_SCRIPTS,
       },
       null,

package/lib/lint.mjs

@@ -0,0 +1,125 @@
+// `looop lint` — the hard rules, made executable.
+//
+// A "Never" that lives only in prose is a suggestion. The rules that have
+// actually shipped broken games are enforced here: in the editor as you type
+// (via the game's eslint.config.js) and in the gate (`looop test` runs this
+// first).
+//
+// The rules themselves live in the ENGINE (`<engine>/eslint/`), not in this
+// package — they are something the creator receives, so they have one authoring
+// home and one release lane, and `looop update` brings a game the new ones. This
+// command resolves them out of the game's installed engine, which is the very
+// same file its eslint.config.js imports. One copy: the gate and the editor
+// cannot disagree.
+//
+// Escape hatch: `// eslint-disable-next-line looop/<rule>` — the one every
+// developer already knows. This is mandatory, not a nicety: creators are not
+// developers, and a false positive must never wall someone out of their own
+// test command with no way through.
+import { existsSync } from 'node:fs';
+import { createRequire } from 'node:module';
+import { join, relative } from 'node:path';
+import { pathToFileURL } from 'node:url';
+import { findProject, resolveEngine } from './project.mjs';
+
+const CONFIG_NAMES = ['eslint.config.js', 'eslint.config.mjs', 'eslint.config.cjs'];
+
+// Resolve ESLint from the GAME's node_modules — same preflight shape as
+// playwright in test-cmd.mjs. Games scaffolded before lint existed simply don't
+// have it; they skip rather than break.
+async function loadFromProject(projectDir) {
+  try {
+    const req = createRequire(join(projectDir, 'package.json'));
+    const mod = await import(pathToFileURL(req.resolve('eslint')).href);
+    return mod.ESLint ?? mod.default?.ESLint ?? null;
+  } catch {
+    return null;
+  }
+}
+
+// The shareable config, out of the installed engine artifact.
+async function loadRulesFromEngine(projectDir) {
+  let engineDir;
+  try {
+    ({ dir: engineDir } = resolveEngine(projectDir));
+  } catch {
+    return null; // no engine installed yet — `looop dev` installs it
+  }
+  const entry = join(engineDir, 'eslint', 'index.js');
+  if (!existsSync(entry)) return null; // engine predates the rules
+  const mod = await import(pathToFileURL(entry).href);
+  return mod.configs ?? mod.default?.configs ?? null;
+}
+
+export async function lintCmd({
+  cwd = process.cwd(),
+  fix = false,
+  log = console.log,
+  loadEslint = loadFromProject,
+  loadRules = loadRulesFromEngine,
+} = {}) {
+  const project = findProject(cwd);
+
+  const ESLint = await loadEslint(project.dir);
+  if (!ESLint) {
+    log('⚠️  looop lint: eslint is not installed in this game — skipping the rule checks.');
+    log('   To turn them on (recommended — they catch bugs that silently pass your tests):');
+    log('     npm i -D eslint');
+    return { ok: true, skipped: true, errorCount: 0, warningCount: 0 };
+  }
+
+  const configs = await loadRules(project.dir);
+  if (!configs) {
+    log('⚠️  looop lint: this engine ships no rules yet — skipping.');
+    log('   Get the latest engine (it carries them): looop update');
+    return { ok: true, skipped: true, errorCount: 0, warningCount: 0 };
+  }
+
+  // A game that ships its own eslint.config.js owns its rules — we do not
+  // override it (and the scaffold's config already spreads ours in). Otherwise
+  // lint with the engine's recommended set, so a repo created before lint
+  // existed still gets the checks with zero setup.
+  const hasOwnConfig = CONFIG_NAMES.some((n) => existsSync(join(project.dir, n)));
+  const eslint = new ESLint({
+    cwd: project.dir,
+    fix,
+    ...(hasOwnConfig ? {} : { overrideConfigFile: true, baseConfig: configs.recommended }),
+  });
+
+  const results = await eslint.lintFiles(['.']);
+  if (fix) await ESLint.outputFixes(results);
+
+  let errorCount = 0;
+  let warningCount = 0;
+  for (const r of results) {
+    errorCount += r.errorCount;
+    warningCount += r.warningCount;
+  }
+
+  if (errorCount || warningCount) {
+    // ESLint's own stylish formatter: the creator's agent (and their editor)
+    // already know how to read it.
+    const formatter = await eslint.loadFormatter('stylish');
+    const text = await formatter.format(results);
+    if (text.trim()) log(text.trim());
+  }
+
+  if (errorCount === 0) {
+    log(`✅ looop lint: clean (${results.length} file(s))${fix ? ' — fixes applied' : ''}`);
+  } else {
+    log('');
+    log(`❌ looop lint: ${errorCount} error(s) in ${results.filter((r) => r.errorCount).length} file(s)`);
+    if (results.some((r) => r.messages.some((m) => m.fix))) {
+      log('   Some of these are auto-fixable: `looop lint --fix`');
+    }
+    log('   A rule is wrong about your code? `// eslint-disable-next-line <rule>` above the line.');
+  }
+
+  return {
+    ok: errorCount === 0,
+    skipped: false,
+    errorCount,
+    warningCount,
+    files: results.map((r) => relative(project.dir, r.filePath)),
+  };
+}

package/lib/self-update.mjs

@@ -0,0 +1,120 @@
+// Keep the `looop` command itself up to date — the third lane.
+//
+// THE BUG THIS EXISTS FOR. A game's skills and its engine ride one artifact, so
+// they can't drift. The `looop` command does not: it's an npm devDependency
+// pinned in the game's own lockfile, and `npx looop` runs THAT copy, not npm's
+// latest. `looop update` used to move only the engine — so a real game (riven)
+// ended up on engine 0.1.14, whose skills tell the agent to run
+// `looop changelog`, while its CLI was still 0.1.6:
+//
+//     $ npx looop changelog
+//     Unknown command: changelog
+//
+// The agent surface is shipped BY the engine and can name any `looop` command it
+// likes. Nothing kept the CLI in step with it. So `looop update` must mean
+// "update Looop" — engine, skills, AND the command — or the next skill that
+// mentions a new command breaks the same way.
+//
+// FAIL SOFT, ALWAYS. The engine update is the important half and it has already
+// happened by the time we get here. A CLI bump that cannot be done (offline, npm
+// down, no write access) must warn and step aside — never take the command down
+// with it. Nothing in here throws.
+import { readFileSync } from 'node:fs';
+import { join } from 'node:path';
+import { runNpm } from './npm.mjs';
+
+export const CLI_PKG = '@looop-games/cli';
+
+// What `npx looop` will run NEXT TIME — the copy on disk in this game, which is
+// not necessarily the copy running right now (`npx @looop-games/cli@x update` in
+// a repo pinned to something older runs the newer one but must still fix the
+// repo).
+export function projectCliVersion(projectDir) {
+  try {
+    const pkg = JSON.parse(
+      readFileSync(join(projectDir, 'node_modules', ...CLI_PKG.split('/'), 'package.json'), 'utf8'),
+    );
+    return typeof pkg.version === 'string' ? pkg.version : null;
+  } catch {
+    return null;
+  }
+}
+
+function isOlder(a, b) {
+  const pa = a.split('.').map(Number);
+  const pb = b.split('.').map(Number);
+  for (let i = 0; i < 3; i++) {
+    if ((pa[i] ?? 0) !== (pb[i] ?? 0)) return (pa[i] ?? 0) < (pb[i] ?? 0);
+  }
+  return false;
+}
+
+export async function syncCli({ projectDir, npm = runNpm, log = console.log } = {}) {
+  const from = projectCliVersion(projectDir);
+
+  // Nothing installed: `create` and `dev` own that. There is nothing to bring up
+  // to date, and force-installing here would be a surprise.
+  if (!from) return { from: null, to: null, updated: false, skipped: 'not-installed' };
+
+  let latest;
+  try {
+    const out = npm(['view', CLI_PKG, 'version', '--json'], { cwd: projectDir });
+    latest = JSON.parse(out.stdout.toString());
+  } catch (err) {
+    log('');
+    log(`   Could not check for a newer looop command (npm did not answer). Your engine is`);
+    log(`   up to date; the command stayed at ${from}. Try again later, or run:`);
+    log(`      npm update ${CLI_PKG}`);
+    return { from, to: null, updated: false, error: err };
+  }
+
+  // Never downgrade. A local dev build (or a version newer than the registry
+  // knows about) is deliberate — leave it alone.
+  if (!isOlder(from, latest)) return { from, to: latest, updated: false };
+
+  try {
+    // --save-dev so the DECLARED range moves too. Without it the next plain
+    // `npm install` in that repo happily resolves back down to the old pin, and
+    // the update silently un-does itself.
+    npm(['install', '--save-dev', `${CLI_PKG}@${latest}`], { cwd: projectDir });
+  } catch (err) {
+    log('');
+    log(`   The looop command could not be updated to ${latest} (npm install failed).`);
+    log(`   Your engine is up to date; the command is still ${from}. Run this to retry:`);
+    log(`      npm install --save-dev ${CLI_PKG}@${latest}`);
+    return { from, to: latest, updated: false, error: err };
+  }
+
+  return { from, to: latest, updated: true };
+}
+
+// The version of the CLI EXECUTING right now — which is not always the one the
+// project has installed. `npx looop` runs the local install (so they match), but
+// `npx @looop-games/cli@latest update` runs a newer one against an older repo.
+export function runningCliVersion() {
+  try {
+    return JSON.parse(readFileSync(join(import.meta.dirname, '..', 'package.json'), 'utf8')).version ?? null;
+  } catch {
+    return null;
+  }
+}
+
+// What `update` prints. Separate so the wording is testable.
+//
+// The caveat — "you're still running the old one" — is TRUE only when the process
+// executing is the copy we just replaced. An earlier version asserted it
+// unconditionally and told a `npx @looop-games/cli@latest update` run that it was
+// "still running 0.1.6", which it plainly was not. Caught by reading the output of
+// a real run against riven. Say it only when it's true.
+export function reportCli(log, cli, { running = runningCliVersion() } = {}) {
+  if (!cli?.updated) return;
+  log('');
+  log(`✅ The looop command updated: ${cli.from} → ${cli.to}`);
+  if (running === cli.from) {
+    log(`   You're still running ${cli.from} in this process — any new commands work from`);
+    log(`   your next \`npx looop\`.`);
+  } else {
+    log(`   New commands are available from your next \`npx looop\`.`);
+  }
+  log(`   Its own changes are in node_modules/${CLI_PKG}/CHANGELOG.md.`);
+}

package/lib/test-cmd.mjs

@@ -13,6 +13,7 @@ import { createRequire } from 'node:module';
 import { join, relative, dirname } from 'node:path';
 import { findProject } from './project.mjs';
 import { dev } from './dev.mjs';
+import { lintCmd } from './lint.mjs';
 import { portsFor, portInUse } from './ports.mjs';
 
 const SKIP_DIRS = new Set(['node_modules', 'overrides']);
@@ -56,17 +57,24 @@ async function freeTestPort(base = 8100) {
   throw new Error('no free port triple found for the test dev stack');
 }
 
-export async function testCmd({ cwd = process.cwd(), log = console.log, devFn = dev } = {}) {
+export async function testCmd({ cwd = process.cwd(), log = console.log, devFn = dev, lintFn = lintCmd } = {}) {
   const project = findProject(cwd);
   const { unit, smokes } = discoverTestFiles(project.dir);
 
+  // Lint FIRST — it needs no servers and no browser, and the defects it catches
+  // (a hardcoded multiplayer host, a smoke pointed at the wrong port) are
+  // exactly the ones that make the suite below pass while testing nothing.
+  // Failing here does not skip the tests: the creator should see everything
+  // that is wrong in one run, not peel it one gate at a time.
+  const lint = await lintFn({ cwd: project.dir, log });
+
   if (unit.length + smokes.length === 0) {
     log(`No tests yet in ${project.dir} — nothing to run.`);
     log('(Unit tests are *.test.mjs; browser smokes are *.smoke.mjs. Anything with an assertion is a regression test — keep it.)');
-    return { ok: true, ran: 0 };
+    return { ok: lint.ok, ran: 0 };
   }
 
-  let ok = true;
+  let ok = lint.ok;
 
   // If looop test itself runs under a node --test parent, the inherited
   // NODE_TEST_CONTEXT makes a nested `node --test` exit 0 even on failure —
@@ -130,5 +138,5 @@ export async function testCmd({ cwd = process.cwd(), log = console.log, devFn =
 
   log('');
   log(ok ? `✅ looop test: all green (${unit.length} unit file(s), ${smokes.length} smoke(s))` : '❌ looop test: failures above');
-  return { ok, ran: unit.length + smokes.length };
+  return { ok, ran: unit.length + smokes.length, lint };
 }

package/lib/update.mjs

@@ -16,6 +16,7 @@ import { getToken, getApiBase } from './config.mjs';
 import { login } from './login.mjs';
 import { DEFAULT_API_BASE } from './llm-shim.mjs';
 import { compareVersions, renderReleases } from './changelog.mjs';
+import { syncCli, reportCli } from './self-update.mjs';
 
 // The report is the point. A creator reading this must be able to answer, with
 // no further digging: what changed, was any of it mine, and what do I do now.
@@ -57,6 +58,7 @@ export async function update({
   loginFn = login,
   ensure = ensureEngine,
   reconcile = reconcileAgentSurface,
+  syncCliFn = syncCli,
 } = {}) {
   const project = findProject(cwd);
   const from = readEnginePin(project.dir);
@@ -122,6 +124,24 @@ export async function update({
   const surface = engineDir ? reconcile(project.dir, engineDir, { log }) : { skipped: true };
   if (!surface.skipped) report(log, surface.engineVersion ?? latest, surface);
 
+  // The third lane: the `looop` command itself (see self-update.mjs). The skills
+  // we just reconciled ship WITH the engine and can name any command they like —
+  // riven ended up on an engine whose skills say `looop changelog` while its CLI
+  // was four versions too old to have it. So update moves this too.
+  //
+  // Wrapped: syncCli is already fail-soft, but a bug in it must not undo an
+  // engine update that has already landed on disk.
+  let cli;
+  try {
+    cli = await syncCliFn({ projectDir: project.dir, log });
+    reportCli(log, cli);
+  } catch (err) {
+    cli = { updated: false, error: err };
+    log('');
+    log(`   The looop command could not be updated (${err.message}).`);
+    log('   Your engine and skills are up to date. Retry with: npm update @looop-games/cli');
+  }
+
   if (updated) {
     log('');
     if (crossed === null) {
@@ -133,5 +153,5 @@ export async function update({
     log('');
     log('   Republish (`npx looop publish`) when you want the live game on it.');
   }
-  return { from, to: latest, updated, surface, crossed };
+  return { from, to: latest, updated, surface, crossed, cli };
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@looop-games/cli",
-  "version": "0.1.10",
+  "version": "0.1.12",
   "description": "Looop game development CLI — dev server, login, and publishing for standalone Looop games.",
   "type": "module",
   "license": "Apache-2.0",