Alapinstalláció a Payload CMS-re való áttéréshez (EPIC MITHOME-85):
- payload@3.88.0, @payloadcms/next, @payloadcms/db-mongodb,
@payloadcms/richtext-lexical, graphql, sharp telepítve
- src/payload.config.ts: mongooseAdapter a meglévő MONGODB_URI-ra
(ugyanaz az adatbázis, mint a Mongoose/mongodb rétegnek), lexical
editor, PAYLOAD_SECRET env-ből
- src/collections/Users.ts: minimális auth collection — Payload nem
tud admin felületet renderelni auth collection nélkül. Ez csak a
bootstraphez kell; a valódi access control/jelszó-politika MITHOME-90
feladata.
- App Router route group (src/app/(payload)/): admin UI
([[...segments]]), REST (api/[...slug]), GraphQL + playground route-ok,
root layout — a szokásos Payload v3 Next.js integrációs minta szerint
- next.config.ts: withPayload() wrapper a route handler bundling-hoz
- tsconfig.json: @payload-config path alias -> src/payload.config.ts
(ez oldja fel a webpack/turbopack importot is, nem csak a type-checket)
- PAYLOAD_SECRET env var: generált dev érték a .env.local-ban
(gitignore-olt), changeme placeholder + generálási megjegyzés a
staging/production .env példafájlokban, dokumentálva a CLAUDE.md
env-lista részében
Ismert, még nem javított biztonsági advisory a felvett payload@3.88.0-ban
(GHSA-jg8r-5jh2-v2xj, moderate, CWE-307: az admin account-unlock alapból
más fiókok lockoutját is felold hitelesített usernek) — nincs újabb
patch-elt verzió jelenleg, nyomon követve MITHOME-90 alatt.
Ellenőrizve ezen a commiton: npm run build, npm run lint, tsc --noEmit,
npm test (58 passed) — mind zöld. Az admin bejelentkezés/DB-kapcsolat
élő tesztje MongoDB-t igényel (jelen környezetben Docker daemon nem fut,
ez lokálisan `docker compose -f docker-compose.dev.yml up -d mongodb`
után `npm run dev` + http://localhost:3000/admin-mal ellenőrizhető).
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Payload 3.88.0's peer range for `next` is >=15.2.9 <15.3.0 ||
>=15.3.9 <15.4.0 || >=15.4.11 <15.5.0 || >=16.2.6 <17.0.0 — the
project's previous 15.5.23 fell in the unsupported gap between the
15.4.x and 16.2.x ranges. Upgrading to 16.3.4 (React 19.1.0 stays
compatible) unblocks MITHOME-86.
- next.config.ts: drop the removed `eslint.ignoreDuringBuilds` option
(Next 16 no longer runs ESLint during `next build`)
- eslint.config.mjs: import eslint-config-next's native flat-config
arrays directly instead of bridging through FlatCompat, which threw
"Converting circular structure to JSON" under ESLint 9 with the
upgraded config
- tsconfig.json: Next 16's own migration set `jsx: react-jsx` and added
`.next/dev/types/**/*.ts` to `include`
- ThemeProvider.tsx: suppress two react-hooks/set-state-in-effect
false positives (new rule shipped with eslint-config-next 16) —
these effects intentionally sync state from localStorage/DOM on
mount, there is no subscription to move the setState into
Verified: npm run build, npm run lint, tsc --noEmit, npm test (58
passed) all clean on this change alone, before installing Payload.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
- Updated README.md with project details, quick start instructions, and tech stack.
- Expanded TODO.md to reflect current project status and backlog items, including Linear ticket synchronization.
- Added mobile menu toggle functionality in Header component with corresponding tests for user interactions.
- Configured Next.js for Docker deployment and optimized build settings.
