@kybernesis/create 0.14.0 → 0.14.1

package/dist/upgrade.js

@@ -376,7 +376,17 @@ export async function upgrade(skipEval) {
         return;
     }
     console.log(bold(`\nInstalling: ${toUpgrade.join(", ")}\n`));
-    run("npm", ["install", ...toUpgrade], { cwd });
+    /**
+     * One install, with peers relaxed. Every @kybernesis package peers on a
+     * narrow eve range, and eve moves with them: the installed set demands the
+     * old eve, the new set demands the new one, and npm's resolver refuses
+     * either order — eve first, packages first, or all at once — under strict
+     * peers (seen on Kyber moving 0.38 → 0.49: ERESOLVE all three ways). The
+     * set being installed is exactly the certified combination, so relaxing
+     * peer resolution for this one command changes nothing about what ends up
+     * on disk; the version check above is what guards correctness.
+     */
+    run("npm", ["install", ...toUpgrade, "--legacy-peer-deps"], { cwd });
     /**
      * Repairs run AFTER the install, not before.
      *

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@kybernesis/create",
-  "version": "0.14.0",
-  "description": "The Kybernesis agent scaffolder and FDE toolkit: one command to a governed, remembering, multiplayer, self-testing eve agent \u2014 plus doctor and upgrade.",
+  "version": "0.14.1",
+  "description": "The Kybernesis agent scaffolder and FDE toolkit: one command to a governed, remembering, multiplayer, self-testing eve agent — plus doctor and upgrade.",
   "license": "Apache-2.0",
   "type": "module",
   "homepage": "https://kybernesis.ai",