Prisma generate step friction in development workflow

5/10 Medium

Developers must run `prisma generate` after schema changes to regenerate types. Forgetting this step causes IDE type errors and is reported as the most common support question. The step blocks the development workflow when running concurrent processes.

Category
dx
Workaround
solid
Stage
build
Freshness
persistent
Scope
single_lib
Recurring
Yes
Buyer Type
team
Maintainer
active

Sources

Collection History

Query: “What are the most common pain points with Prisma for developers in 2025?4/4/2026

The `prisma generate` step adds friction during development. In my experience, the most common support question from MakerKit customers is 'why are my types wrong?' — almost always because they edited the schema and forgot to regenerate...If the client needs to be updated, any app specific processes need to be stopped first before regenerating the types.

Created: 4/4/2026Updated: 4/4/2026