modern-cms 1.1.4 → 1.1.5

package/README.md

@@ -84,7 +84,7 @@ npm run dev
 
 Then open the web app at the URL you chose (default `http://localhost:3000`) and log in at `/admin` with the admin email/password from the wizard.
 
-> **Prefer yarn for the scaffolded project too?** `yarn install` works fine, and `dev`/`db:migrate`/`db:seed` all run correctly (they use `tsx`, which doesn't type-check). The one caveat: yarn's dependency hoisting can occasionally produce a duplicate `@types/express`, which shows up as spurious TypeScript errors only if you run `npm run build` or `tsc` directly — running `npm install` once resolves it.
+> **Prefer yarn for the scaffolded project too?** `yarn install` works fine, and `dev`/`build`/`db:migrate`/`db:seed` all run correctly. A stray duplicate `@types/express` (pulled in by `@types/multer`'s unpinned `"*"` dependency range) used to break `tsc`/`npm run build` under both npm and yarn — the generated `package.json` now pins it via `overrides` (npm) and `resolutions` (yarn), so a fresh install with either tool is clean.
 >
 > **Logged in with the wrong password?** The admin user is only created the *first* time `db:seed` runs — editing `.env` afterward doesn't retroactively change it. Run `npm run db:reset-admin && npm run db:seed` to delete and recreate it from the current `.env` values.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "modern-cms",
-  "version": "1.1.4",
+  "version": "1.1.5",
   "description": "Self-hosted, drag-and-drop website CMS (Next.js + Express + Prisma). Interactive installer scaffolds a full project with your choice of PostgreSQL/MySQL and AWS S3/Azure Blob/Cloudinary storage.",
   "type": "module",
   "bin": {

package/template/README.md

@@ -60,7 +60,7 @@ npm run db:seed
 npm run dev
 ```
 
-> **Using yarn to install the scaffolded project itself?** `yarn install` works fine, and `npm run dev` / `db:migrate` / `db:seed` all run correctly under a yarn-installed `node_modules` (they invoke `tsx`, which doesn't type-check). The one thing to watch for: yarn's dependency hoisting can occasionally produce a duplicate `@types/express` in the tree, which shows up as spurious TypeScript errors *only* if you run `npm run build` or `tsc` directly. If that happens, running `npm install` once (even alongside your yarn workflow) resolves it — that's yarn's hoisting, not a bug in the project.
+> **Using yarn to install the scaffolded project itself?** `yarn install` works fine — `npm run dev` / `build` / `db:migrate` / `db:seed` all run correctly under a yarn-installed `node_modules`. (Earlier versions of this README blamed a duplicate `@types/express` type error on "yarn's hoisting" — that diagnosis was wrong. The real cause is that `@types/multer` depends on `@types/express@"*"`, which both npm and yarn will happily resolve to a stray v5 copy alongside the project's pinned v4, breaking `tsc`/`npm run build` under either package manager. The root `package.json`'s `overrides` + `resolutions` fields pin that nested dependency to v4 for both, so this no longer happens with a fresh install.)
 
 See [`packages/modern-cms/README.md`](packages/modern-cms/README.md) for the full prompt-by-prompt reference and configuration details.
 

package/template/package.json

@@ -9,6 +9,14 @@
     "packages/*",
     "apps/*"
   ],
+  "overrides": {
+    "@types/multer": {
+      "@types/express": "^4.17.21"
+    }
+  },
+  "resolutions": {
+    "**/@types/multer/**/@types/express": "^4.17.21"
+  },
   "scripts": {
     "dev": "concurrently -n api,web -c blue,green \"npm run dev -w apps/api\" \"npm run dev -w apps/web\"",
     "dev:api": "npm run dev -w apps/api",