@joystack/cli 0.1.43 → 0.1.44

package/CHANGELOG.md

@@ -14,6 +14,14 @@ Versions: [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
 ## [Unreleased]
 
+## [0.1.44] - 2026-10-09
+
+### Added
+
+- When `joystack update` moves a game made before the rename, it ends with a
+  short checklist for your agent: the links, tests and publishing tokens in
+  your game's own files that the update cannot move itself.
+
 ### Removed
 
 - `joystack dev` no longer starts a services proxy on port 8788. Nothing in the
@@ -22,6 +30,9 @@ Versions: [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
 ### Changed
 
+- `joystack create` marks the new game as ES modules (`"type": "module"` in
+  package.json), so `joystack publish` no longer prints Node's
+  `MODULE_TYPELESS_PACKAGE_JSON` warning.
 - **The CLI is `@joystack/cli`, and its command is `joystack`** (`npx joystack
   dev`, `npx joystack test`, `npx joystack publish`, …). Nothing in your game has
   to change: the previous command name runs the same CLI, so the scripts in your

package/lib/create.mjs

@@ -112,6 +112,8 @@ async function scaffold({ dir, name, install, cliSpec, apiBase, log, ensure, rec
       {
         name,
         private: true,
+        // Every file a game is made of is an ES module.
+        type: 'module',
         description: `A Joystack game. Play at https://${name}.joystack.games/`,
         // The scaffold is a framework-v2 game (entities + traits + a world root,
         // lowered to the engine runtime on this machine). This flag is what makes

package/lib/legacy-names.mjs

@@ -244,3 +244,32 @@ export const LEGACY_MANAGED_MARKERS = Object.freeze({
   start: `<!-- ${OLD}:managed:start -->`,
   end: `<!-- ${OLD}:managed:end -->`,
 });
+
+// Whether this update moved a game made under the old name: the CLI dependency
+// was switched over, or the old update skill was retired. `cli` and `surface`
+// are what update.mjs got from syncCli and the agent-surface reconcile.
+export function movedFromLegacy(cli, surface) {
+  return Boolean(cli?.switched) || (surface?.removed ?? []).some((f) => /(^|\/)skills\/update-looop(\/|$)/.test(f));
+}
+
+// What `joystack update` prints after such a move, once. It is addressed to
+// the creator's agent, which reads the update's output: the update moved what
+// is Joystack's, and these are what the game itself may still say about Looop.
+export const MOVED_FROM_LEGACY_NOTE = [
+  'This game just moved from Looop to Joystack. The update moved what is',
+  "Joystack's; check the game's own files for what it could not move, and",
+  'fix what you find before calling the update done:',
+  '  • Links to play.looop.games/g/<slug>: the game lives at',
+  '    https://<slug>.joystack.games/ from its first `npx joystack publish`.',
+  '    The Looop copy stays as it was.',
+  '  • Tests or scripts matching `[looop]`, `looop:` keys or `.looop/`: the',
+  '    engine now writes `[joystack]`, `joystack:` and `.joystack/`.',
+  '  • Automation that publishes (GitHub Actions, scripts) with a Looop token:',
+  '    Joystack does not accept it. Make one for the job by signing in with an',
+  '    empty folder (mktemp -d) as the home: `JOYSTACK_HOME=<folder> npx joystack login`.',
+  '    With the creator\'s OK, store it without ever displaying it:',
+  '      node -e "process.stdout.write(require(\'<folder>/config.json\').token)" | gh secret set <NAME>',
+  '    Without gh, pipe the same into pbcopy (Mac) and walk them through',
+  '    GitHub → Settings → Secrets and variables → Actions → <NAME> → Update.',
+  '    Then delete the folder.',
+];

package/lib/update.mjs

@@ -16,6 +16,7 @@ import { login } from './login.mjs';
 import { compareVersions, renderReleases } from './changelog.mjs';
 import { syncCli, reportCli } from './self-update.mjs';
 import { fetchStatus, landedIn } from './feedback-sync.mjs';
+import { MOVED_FROM_LEGACY_NOTE, movedFromLegacy } from './legacy-names.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.
@@ -69,6 +70,20 @@ function report(log, engineVersion, surface) {
   log("   changes you didn't make. Review them and save them with your next commit.");
 }
 
+// A game made before the rename moves over in this update. What is Joystack's
+// has moved; what the game itself says (its links, its tests, a token its
+// automation publishes with) has not, and the note lists it for the agent
+// reading this output. Neither condition holds on a later update, so it is
+// printed this once only.
+function noteMove(log, cli, surface) {
+  const moved = movedFromLegacy(cli, surface);
+  if (moved) {
+    log('');
+    for (const line of MOVED_FROM_LEGACY_NOTE) log(`   ${line}`);
+  }
+  return moved;
+}
+
 export async function update({
   cwd = process.cwd(),
   apiBase = getApiBase(DEFAULT_API_BASE),
@@ -146,7 +161,8 @@ export async function update({
     log('   This is a pre-release candidate — its changelog and any migration');
     log('   notes ship inside the engine (read the handbook / engine docs), not');
     log('   via `joystack changelog`. Republish (`npx joystack publish`) when ready.');
-    return { from, to: engine.version, updated: from !== engine.version, surface, crossed: null, cli, candidate: true };
+    const movedIn = noteMove(log, cli, surface);
+    return { from, to: engine.version, updated: from !== engine.version, surface, crossed: null, cli, candidate: true, movedIn };
   }
 
   const res = await fetchImpl(`${apiBase}/api/creator/engine`, {
@@ -295,5 +311,6 @@ export async function update({
     log('');
     log('   Republish (`npx joystack publish`) when you want the live game on it.');
   }
-  return { from, to: latest, updated, surface, crossed, cli, landed };
+  const movedIn = noteMove(log, cli, surface);
+  return { from, to: latest, updated, surface, crossed, cli, landed, movedIn };
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@joystack/cli",
-  "version": "0.1.43",
+  "version": "0.1.44",
   "description": "Joystack game development CLI \u2014 dev server, login, and publishing for standalone Joystack games.",
   "type": "module",
   "license": "Apache-2.0",