modern-cms 1.1.6 → 1.1.8
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +2 -0
- package/package.json +1 -1
- package/template/README.md +2 -0
- package/template/apps/api/package.json +1 -1
package/README.md
CHANGED
|
@@ -87,6 +87,8 @@ Then open the web app at the URL you chose (default `http://localhost:3000`) and
|
|
|
87
87
|
> **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.
|
|
88
88
|
>
|
|
89
89
|
> **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.
|
|
90
|
+
>
|
|
91
|
+
> **Public site failing with `ECONNREFUSED` / 404s under `npm run dev` on Windows?** Fixed in v1.1.7 — `apps/api`'s dev script previously used `tsx watch`, which could hang without binding its port when launched through `concurrently` on Windows (the exact same command worked fine on its own). It now uses the equivalent `tsx --watch` flag form, which doesn't hit the issue.
|
|
90
92
|
|
|
91
93
|
## Project layout
|
|
92
94
|
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "modern-cms",
|
|
3
|
-
"version": "1.1.
|
|
3
|
+
"version": "1.1.8",
|
|
4
4
|
"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.",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"bin": {
|
package/template/README.md
CHANGED
|
@@ -263,3 +263,5 @@ No builder-chrome changes needed — the palette, inspector, and drag-and-drop p
|
|
|
263
263
|
|
|
264
264
|
**Dev server "running" but serving stale code** — an orphaned process may still own the port. Verify with `netstat -ano | findstr :3000` (or `:4000`) and kill the listed PID before restarting.
|
|
265
265
|
|
|
266
|
+
**Web app can't reach the API (`ECONNREFUSED` from `serverGet`, homepage 404s) when running `npm run dev`** — on Windows, `tsx watch src/index.ts` (the API's dev script) can hang indefinitely without ever binding its port when spawned through `concurrently`, even though the exact same command works fine run on its own. This is fixed as of the current `apps/api/package.json` (`tsx --watch` instead of `tsx watch` — the flag form doesn't hit the issue), but if you scaffolded a project before this fix, edit `apps/api/package.json`'s `dev` script to `"tsx --watch src/index.ts"` and restart.
|
|
267
|
+
|