This version has breaking changes — APIs, conventions, and file structure may all differ from your training data. Read the relevant guide in node_modules/next/dist/docs/ before writing any code. Heed deprecation notices.
Single Next.js 16 app (not a monorepo) with PostgreSQL via Prisma. See README.md for full feature list and scripts table.
- Node 20.x is required (
.nvmrc). The VM uses nvm:source ~/.nvm/nvm.sh && nvm use 20. - PostgreSQL 16 runs locally. Start with
sudo pg_ctlcluster 16 main start. - Database:
taskhub_devon localhost, userubuntu/devpass. The.envfile hasDATABASE_URLpointing to it. - After install:
npx prisma migrate devapplies migrations. Thepostinstallscript auto-runsprisma generate. - Dev server:
npm run dev→ http://localhost:3000.
- Prisma config (
prisma.config.ts) loads.envviadotenv/config. IfDATABASE_URLin.envis wrong, Prisma commands will silently connect to the wrong DB. Always verify.envhas the local URL. - ESLint reports errors in
src/generated/prisma/(auto-generated code). These are expected and not fixable. The ESLint config does not ignore this directory — when checking lint results, filter outsrc/generated/lines. There are also 4 pre-existing lint errors insrc/components/playbooks/PlaybookGuideModal.tsx(react-hooks/immutability). - AI features require
OPENAI_API_KEYin.envor a user-provided BYOK key in the browser. Without it, only CRUD task management works. - The app has no automated test suite (no
testscript inpackage.json). Verification is via lint + dev server + manual API/UI testing.