@pugi/cli 1.0.0-alpha.175 → 1.0.0-alpha.177

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pugi/cli",
-  "version": "1.0.0-alpha.175",
+  "version": "1.0.0-alpha.177",
   "description": "Pugi CLI - terminal-native software execution system",
   "license": "MIT",
   "homepage": "https://pugi.io",
@@ -40,11 +40,11 @@
     "LICENSE"
   ],
   "optionalDependencies": {
-    "@pugi/cli-darwin-arm64": "1.0.0-alpha.175",
-    "@pugi/cli-darwin-x64": "1.0.0-alpha.175",
-    "@pugi/cli-linux-arm64": "1.0.0-alpha.175",
-    "@pugi/cli-linux-x64": "1.0.0-alpha.175",
-    "@pugi/cli-windows-arm64": "1.0.0-alpha.175",
-    "@pugi/cli-windows-x64": "1.0.0-alpha.175"
+    "@pugi/cli-darwin-arm64": "1.0.0-alpha.177",
+    "@pugi/cli-darwin-x64": "1.0.0-alpha.177",
+    "@pugi/cli-linux-arm64": "1.0.0-alpha.177",
+    "@pugi/cli-linux-x64": "1.0.0-alpha.177",
+    "@pugi/cli-windows-arm64": "1.0.0-alpha.177",
+    "@pugi/cli-windows-x64": "1.0.0-alpha.177"
   }
 }

package/skills/nestjs-api/SKILL.md

@@ -13,11 +13,12 @@ Generates idiomatic NestJS modules, controllers, services, DTOs.
 
 - Every dependency you import must be in package.json before you import it. A test file is code: importing `@nestjs/testing` without adding it fails the build for the whole project, not just the test.
 - Run the project's own build once before reporting done. `tsc` is the cheapest reviewer you have and it reads the tsconfig the customer will ship with, not the one you assumed.
+- Any `@nestjs/*` package you add must carry the SAME major as the `@nestjs/common` already in package.json. Read it; never write a version from memory. A mismatched major makes `npm install` refuse the whole tree with ERESOLVE, and then nothing installs at all — which surfaces as a missing runtime module, not as a version problem.
 
 
 ## Known failure modes
 
-Read `quirks.md` in this directory BEFORE writing code in this domain. It records 2 failures that reached a customer build, each with the symptom, the cause, and the check that tells them apart.
+Read `quirks.md` in this directory BEFORE writing code in this domain. It records 3 failures that reached a customer build, each with the symptom, the cause, and the check that tells them apart.
 
 
 ## Grounding

package/skills/nestjs-api/quirks.md

@@ -23,4 +23,14 @@ actually observe; the build succeeds in every one of these cases.
 
 **Check.** Before writing a `.test.ts`/`.spec.ts`, check that every module it imports appears in package.json. `@nestjs/testing` is NOT part of the default starter.
 
-**Fix.** Add the package to devDependencies and install it, or do not write the test. A test that cannot compile is worse than no test — it takes the build down with it.
+**Fix.** Add the package to devDependencies and install it, or do not write the test. A test that cannot compile is worse than no test — it takes the build down with it. Pick the version by the rule in the next entry — a wrong one is worse than the missing package.
+
+## nest-package-version-must-match-the-installed-major
+
+**Symptom.** `npm install` ends with `npm error code ERESOLVE` and a "could not resolve dependency" block naming a peer. node_modules is NOT created, so the next command fails on something unrelated-looking — typically `Cannot find module '@nestjs/core'`, which is NOT the problem.
+
+**Cause.** A `@nestjs/*` package was added at a version from a different major than the Nest already in the project. Measured on a live customer preview 2026-09-10: `@nestjs/common@10.4.22` was installed and a generated `@nestjs/testing@4.6.6` demanded `@nestjs/common@"^4.*"`, so npm refused the WHOLE tree. `--omit=dev` does not save you — npm resolves everything before omitting, so one bad dev pin blocks the production install too.
+
+**Check.** Before adding any `@nestjs/*` package, read the version of `@nestjs/common` (or `@nestjs/core`) already in package.json and use the SAME major. Never write a version from memory. When an install fails, read the INSTALL output — the crash you see is several steps downstream.
+
+**Fix.** Match the major — with `@nestjs/common@^10`, write `"@nestjs/testing": "^10"`. If unsure, install without a version (`npm install -D @nestjs/testing`) and let npm pick a compatible one, then confirm the install exited 0.