Bug description

As per #27192 with v6.8.0. I had the same problem and even with the v6.8.1 the issue still exists.

npx prisma init
Error: Only URLs with a scheme in: file, data, and node are supported by the default ESM loader. On Windows, absolute paths must be valid file:// URLs. Received protocol 'c:'

Is this a nextjs issue? or something else?

node -v 22.15.1
npm -v 11.3.0

Severity

🚨 Critical: Data loss, app crash, security issue

Reproduction

npx create-next-app@latest
npm -D i prisma
npx prisma init

Expected vs. Actual Behavior

Unable to init. Even manually creating the folder and schema it still get's error when trying to migrate.

Frequency

Consistently reproducible

Does this occur in development or production?

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

Is this a regression?

Just this one and 6.8.0

Workaround

Prisma Schema & Queries

// Add relevant schema.prisma snippet

// Add relevant Prisma Client query

Prisma Config

// Add your `prisma.config.ts`

Logs & Debug Info

// Debug logs here

Environment & Setup

• OS:
• Database:
• Node.js version:

Prisma Version

// Prisma version output