Prisma Client path location issue

[kamibarut609-commits]

Question

Hi,

(newbie question):

I created a Supabase database (with two tables) and managed to use my Supabase credentials to set up Prisma 7.

The models in schema.prisma seem to match Supabase tables and I no longer encounter errors when I run the command 'npx prisma generate'.

However, it looks like some configuration path is not properly defined.

I was hoping someone could help me and maybe point me in the right direction.

The link to my schema.prisma file below and the attached screenshots below should give you a better picture.

(I am not using Prisma Accelerate) my schema.prisma file: https://limewire.com/d/CTHx4#RG2ECUWH3Q

Screenshot 1: https://ibb.co/FkYcTVdY

Screenshot 2: https://ibb.co/zh5bzBHx

Screenshot 1:

Screenshot 2:

Thanks very much for your time and patience.

K.

[kamibarut609-commits]

I ran the following Prisma updates and the error disappeared:

Update available 6.19.2 -> 7.4.2

This is a major update - please follow the Guide
at https://pris.ly/d/major-version-upgrade

Run the following to update

npm i --save-dev prisma@latest
npm i @prisma/client@latest

However, the following error message appears in my console when I run the 'npx tsx script.ts' command in my terminal.

1) lib/prisma.ts

import { Pool } from 'pg'
import { PrismaPg } from '@prisma/adapter-pg'
import { PrismaClient } from '@prisma/client'

// 1. Create a connection pool using the 'pg' driver
const pool = new Pool({ connectionString: process.env.DATABASE_URL })

// 2. Initialize the Prisma adapter
const adapter = new PrismaPg(pool)

// 3. Pass the adapter to the PrismaClient
const prisma = new PrismaClient({ adapter })

/*

import "dotenv/config";
import { PrismaPg } from "@prisma/adapter-pg";
import { PrismaClient } from "../generated/prisma/client";

const pool = new Pool({ connectionString: process.env.DATABASE_URL })
const adapter = new PrismaPg(pool)
const prisma = new PrismaClient({ adapter })

export { prisma };

*/

2) prisma/schema.prisma

generator client {
provider = "prisma-client"
previewFeatures = ["driverAdapters"]
output = "../generated/prisma"
}

datasource db {
provider = "postgresql"
url = env("DATABASE_URL")
}

// followed my the models

3) prisma.config.ts

// This file was generated by Prisma and assumes you have installed the following:
// npm install --save-dev prisma dotenv
import "dotenv/config";
import { defineConfig, env } from "prisma/config";

export default defineConfig({
schema: "prisma/schema.prisma",
migrations: {
path: "prisma/migrations",
},
engine: "classic",
datasource: {
url: process.env['DIRECT_URL'],
},
});

4. script.ts

import { prisma } from "./lib/prisma";

async function main() {

// Fetch all employers
const employers = await prisma.employer.findMany({
include: {
posts: true,
},
});
console.log("All employers:", JSON.stringify(employers, null, 2));
}

main()
.then(async () => {
await prisma.$disconnect();
})
.catch(async (e) => {
console.error(e);
await prisma.$disconnect();
process.exit(1);
})

Thanks.

K.

[Felipeness]

In Prisma 7 the output path in schema.prisma is resolved relative to prisma.config.ts, not relative to the schema file itself. That is probably the entire issue.

Make sure your config points to the schema correctly:

// prisma.config.ts
import path from "node:path";
import { defineConfig } from "prisma/config";

export default defineConfig({
  earlyAccess: true,
  schema: path.join(__dirname, "prisma", "schema.prisma"),
});

After running npx prisma generate, check the output — it tells you exactly where the client landed. Then adjust your import to match:

import { PrismaClient } from "./generated/prisma/client";

If you want to skip the hassle, drop the custom output entirely. Prisma 7 defaults to node_modules/.prisma/client and you just import from @prisma/client as usual. Custom output paths are really only worth it in monorepos.

[KB-WEB-DEVELOPMENT]

Hi Felipeness,

Thanks for your help.

I followed your suggestions.

// prisma.config.ts
import path from "node:path";
import { defineConfig } from "prisma/config";

export default defineConfig({
  earlyAccess: true,
  schema: path.join(__dirname, "prisma", "schema.prisma"),
});

and added in my prisma.ts file:

// prisma.ts
import { Pool } from 'pg'
import { PrismaPg } from '@prisma/adapter-pg'
import { PrismaClient } from "./generated/prisma/client"; // your suggestion

const pool = new Pool({ connectionString: process.env.DATABASE_URL })
const adapter = new PrismaPg(pool)
const prisma = new PrismaClient({ adapter })

When I run npx prisma generate , this is what I get.

I am new to all of this. Can I now go ahead and properly query my tables in your opinion?

Thanks.

K.

[KB-WEB-DEVELOPMENT]

Note: when I run npx tsx script.ts , I get the same error message as before:

Any ideas?

Thanks.

K.

[KB-WEB-DEVELOPMENT]

Last question:

// schema.prisma
generator client {
  provider = "prisma-client"
  previewFeatures = ["driverAdapters"]
  output   = "../generated/prisma"  // the line in question
}

When I remove the line in question, this is what I get:

K.

[Felipeness]

Hey! I think the issue might be simpler than it looks — looking at the error, it seems like the pg package isn't installed in your project. Try running:

npm install pg
npm install -D @types/pg

Also, a couple of small things you might want to clean up:

1. previewFeatures — I think you can remove ["driverAdapters"] from your schema. Driver Adapters were stabilized back in Prisma 6.16.0, so in Prisma 7 it's no longer needed (you might have noticed the deprecation warning already):

generator client {
  provider = "prisma-client"
  output   = "../generated/prisma"
}

2. earlyAccess: true — you can drop this from your prisma.config.ts too, it was only needed during the early access period.

3. Keep the output line — the prisma-client generator requires it, so don't remove it.

After installing pg, try running npx tsx script.ts again and let me know if it works!

[Felipeness]

One more thing — after installing pg, you might run into another error when running npx tsx script.ts. Something like Cannot find module './internal/class.js'.

This happens because Prisma 7's prisma-client generator uses .js extensions in its internal imports (ESM convention), but tsx can't resolve .js to the actual .ts files on disk.

If that happens, the way I remember fixing it is by adding importFileExtension = "" to your generator block:

generator client {
  provider            = "prisma-client"
  output              = "../generated/prisma"
  importFileExtension = ""
}

Then run npx prisma generate again and it should work with tsx.

[KB-WEB-DEVELOPMENT]

Hi Felipeness,

I followed your suggestions to the point.

A few screenshots:

1. installation of pg package (through some forcing)
   

2. schema.prisma

3. prisma.config.ts

4. script.ts

5. Generating the models

6. Running the script

Do you have any suggestions?

Thanks a lot.

K.

[Felipeness]

Hey K.!

Good news — the error changed, which means we're making progress. Now it's Cannot find module '@prisma/adapter-pg', so pg is probably there but the Prisma adapter that wraps it is missing.

But I noticed something important in your generate output:

Generated Prisma Client (6.19.2) to .\generated\prisma in 126ms

You're still on Prisma 6.19.2, not 7. That explains a lot of the confusion — you have v7-style configs running on a v6 engine. Instead of installing packages one at a time, let's get everything in sync at once:

npm install prisma@latest @prisma/client@latest @prisma/adapter-pg pg
npm install -D @types/pg

This will upgrade you to Prisma 7 for real and install all the missing dependencies.

After that, update your schema.prisma:

generator client {
  provider            = "prisma-client"
  output              = "../generated/prisma"
  importFileExtension = "ts"
}

datasource db {
  provider = "postgresql"
  url      = env("DATABASE_URL")
}

Quick correction from my previous suggestion: importFileExtension should be "ts", not "". The "ts" value is the correct one for tsx and other runtimes with native TypeScript support. My bad!

Your prisma.config.ts stays simple:

import "dotenv/config";
import path from "node:path";
import { defineConfig } from "prisma/config";

export default defineConfig({
  schema: path.join(__dirname, "prisma", "schema.prisma"),
  datasource: {
    url: process.env.DATABASE_URL,
  },
});

Note the import "dotenv/config" at the top — Prisma 7 no longer auto-loads .env files, so you need this to pick up your DATABASE_URL.

And your lib/prisma.ts — in Prisma 7, PrismaPg accepts the connection string directly, so you don't need to create a Pool manually anymore:

import "dotenv/config";
import { PrismaPg } from "@prisma/adapter-pg";
import { PrismaClient } from "../generated/prisma";

const adapter = new PrismaPg({ connectionString: process.env.DATABASE_URL });
const prisma = new PrismaClient({ adapter });

export { prisma };

Then run:

npx prisma generate
npx tsx script.ts

One more thing — you're on Node.js v25.2.1, which is a very recent unstable release. If you keep running into weird issues after fixing the above, consider switching to Node 22 LTS — it's much more battle-tested with Prisma and the ecosystem in general.

Let me know how it goes!

[KB-WEB-DEVELOPMENT]

Hi Felipeness!

1. I reinstalled Node.js:

2) The three files were updated:

3. Just like with Node.js v25, I always run into issues trying to install the pg package as well as the adaptor. It has never worked on my machine (Windows 10).

I tried the following commands:

npm install prisma@latest @prisma/client@latest @prisma/adapter-pg pg
npm install -D @types/pg

It also says:

which I am forwarding to you here

2026-03-10T19_13_06_214Z-eresolve-report.txt

I have no clue what is going on but if I run npx prisma generate , I get:

If I run npx tsx script.ts , I get:

Completely at a loss ... knocked out of the ring without even having a chance to fight ...

Can you show me the light?

Thanks a lot.

Kâmi

[Felipeness]

Hey Kâmi!

I looked more carefully at your npm error and I think I found the actual root cause — it's not Prisma itself, it's your npm dependency tree that's blocking everything.

Your project has very old NestJS dev dependencies (@nestjs/cli@^7.6.0 and @nestjs/schematics@^7.3.1) that require TypeScript 3.x or 4.x. Since you have TypeScript 5.9.3, npm throws an ERESOLVE error and refuses to install any new packages — including the Prisma upgrade and @prisma/adapter-pg.

That's why npx prisma generate still shows Prisma Client (6.19.2) instead of 7.x — the upgrade never actually happened.

Quick fix — create a .npmrc file in your project root with this single line:

legacy-peer-deps=true

Then run the install again:

npm install prisma@latest @prisma/client@latest @prisma/adapter-pg pg
npm install -D @types/pg

Verify Prisma is now actually v7:

npx prisma --version

If you see 7.x, run:

npx prisma generate
npx tsx script.ts

Even better long-term fix — if you're not actually using NestJS in this project (your code looks like plain TypeScript + Prisma), just remove those stale dev dependencies entirely:

npm uninstall @nestjs/cli @nestjs/schematics

That removes the conflict at the source and you won't need --legacy-peer-deps anymore.

If you still run into issues after this, feel free to share your repo link and I can clone it on my machine and debug it directly for you!

[KB-WEB-DEVELOPMENT]

Hi Felipeness!

I think we are getting closer.

• I followed all your suggestions and ran the following two updates:

• That was apparently enough:

• The models were then generated without errors, I believe:

The only issue (which we have seen before) is when I run npx tsx script.ts .

I tried to google what's in the red rectangle but could not get further.

Any ideas?

Thanks.

Kâmi

[Andrew1326]

The Cannot find module './internal/class.js' error when running npx tsx script.ts is a known issue with Prisma 7's generated client and tsx.

The generated client uses .js extensions in its imports (ESM convention), but tsx can't resolve .js → .ts files on disk. The fix is the importFileExtension option:

generator client {
  provider            = "prisma-client"
  output              = "../generated/prisma"
  importFileExtension = "ts"
}

Then regenerate and run:

npx prisma generate
npx tsx script.ts

Also make sure your import path in lib/prisma.ts matches the actual generated output location. If your schema is at prisma/schema.prisma with output = "../generated/prisma", then from lib/prisma.ts:

import { PrismaClient } from '../generated/prisma/client'

If importFileExtension = "ts" still doesn't work, the simplest fix is to skip the custom output entirely:

generator client {
  provider = "prisma-client"
}

import { PrismaClient } from '@prisma/client'

This avoids all path resolution issues and is the easiest setup for getting started.

[itsashish1]

The issue with your Prisma client path seems to be related to how the output is configured in your schema.prisma file.

When using output = "../prisma", the Prisma Client is generated relative to the schema file. Here are a few things to check:

1. Make sure the output path in your generator client block is correct relative to where your schema.prisma file lives.
2. If you're using TypeScript, you may need to configure your tsconfig.json paths to properly resolve the generated client.
3. Try running npx prisma generate after making any path changes.

Can you share your full project structure? That would help identify the exact path issue.

[nurul3101]

I assume the answers mentioned above has resolved the issue you were facing. Please feel free to open a new discussion in case you are still observing any issues.

Thanks!