Skip to content

chore(db): run prisma generate on postinstall so fresh clones typecheck #499

Description

@joryirving

Problem: a fresh checkout / any schema change leaves a stale generated client, so tsc --noEmit, tests and dev fail with Property 'groomingRun' is missing on PrismaClient (9 errors) until you manually npm run db:generate. CI/Docker hide it by generating explicitly.

Fix: add "postinstall": "prisma generate" to package.json. prisma generate needs only the schema, but prisma.config.ts:4 throws when DATABASE_URL is unset — drop the datasource url from the generate path or gate the throw so generate works without env. Document the ordering in AGENTS.md.

Effort: Low. Impact: High (unblocks every fresh clone).


Part of #498 (dispatch audit).

Metadata

Metadata

Assignees

No one assigned

    Labels

    priority/p1High priority.status/readyReady for Dispatch worker pickup.type/choreRoutine tasks and maintenance

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions