Hey @gabrieljun56! This is a common issue when working with Prisma. The error message is telling you exactly what to do — the Prisma Client hasn't been generated yet.

Quick fix:

Run this command before seeding:

npx prisma generate

Then run your seed command:

npx prisma db seed

Why this happens:

Since you have a custom output path ("../app/src/generated/prisma"), make sure you're importing from that exact location in your seed.ts file:

import { PrismaClient } from '../app/src/generated/prisma'

Pro tip for your workflow:

You can combine commands in your package.json:

"prisma": {
  "seed": "npx prisma generate && ts-node prisma/seed.ts"
}

This ensures generate always runs before seed.

Also, if you're writing complex SQL queries alongside Prisma, tools like ai2sql.io can help you convert natural language to SQL — useful for debugging or creating raw queries when needed.

Let me know if this helps! 🚀

Solution

The error @prisma/client did not initialize yet happens because you have a custom output path but are importing from the wrong location.

Fix 1: Import from your custom output path

Your schema has:

output = "../app/src/generated/prisma"

So in seed.ts, import from there:

// ❌ Wrong
import { PrismaClient } from "@prisma/client";

// ✅ Correct - use your custom output path
import { PrismaClient } from "../app/src/generated/prisma";

Fix 2: Run generate first

npx prisma generate
npx prisma db seed

Fix 3: Use tsx instead of node for TypeScript

Update package.json:

{
  "prisma": {
    "seed": "tsx prisma/seed.ts"
  }
}

Then install tsx:

npm install -D tsx

Why this happens

When you use a custom output path, @prisma/client is just a stub. The actual generated client lives in your specified folder. You must import from that path instead.

Please feel free to mark one the solutions as answers if your question is resolved.