Doc pointing to the wrong import path for Prisma Client

[SkyMarsh14]

Bug description

Hello,

I was following this Prisma get started doc , and I've notice a thing here.
Although it says that I have to import with require('@prisma/client'), this results in the following error.

node:internal/modules/cjs/loader:1252
  throw err;
  ^

Error: Cannot find module '.prisma/client/default'
Require stack:
- /Users/skyaus/Downloads/hello-prisma/node_modules/@prisma/client/default.js
- /Users/skyaus/Downloads/hello-prisma/index.js

This is because, in the docs, it says that I should run the following command.
npx prisma init --datasource-provider postgresql --output ../generated/prisma
If i do this, it generates the module into ../generated/prisma instead of node_modules/@prisma/client/default.js
In fact, it correctly imports by importing with const { PrismaClient } = require("./generated/prisma/default");.

I think there should be an explanation with this in the docs.

Thanks for the consideration.

Expected vs. Actual Behavior

Expected not to throw module not found error.

Frequency

Consistently reproducible

Does this occur in development or production?

Only in development (e.g., CLI tools, migrations, Prisma Studio)

Is this a regression?

Workaround

Prisma Schema & Queries

// Add relevant schema.prisma snippet

// Add relevant Prisma Client query

Logs & Debug Info

// Debug logs here

Environment & Setup

• OS: MacOs
• Database: Postgresql
• Node.js version: 22.11.0

Prisma Version

// Prisma version output

[sovetski]

Same here, the docs should be updated because for now it is very confusing

[mhessdev]

Thanks for brining this to our attention! We will get this sorted ASAP.