Prisma 6.8.0 init error on Windows - Only URLs with a scheme in: file, data, and node are supported by the default ESM loader #27192
Description
Bug description
on 6.8.0 it is impossible to use prisma:
> npx [email protected] 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:'
but on versions below everything works:
>npx [email protected] init
Need to install the following packages:
[email protected]
Ok to proceed? (y) y
✔ Your Prisma schema was created at prisma/schema.prisma
You can now open it in your favorite editor.
warn Prisma would have added DATABASE_URL but it already exists in .env
warn You already have a .gitignore file. Don't forget to add `.env` in it to not commit any private information.
Next steps:
1. Set the DATABASE_URL in the .env file to point to your existing database. If your database has no tables yet, read https://pris.ly/d/getting-started
2. Set the provider of the datasource block in schema.prisma to match your database: postgresql, mysql, sqlite, sqlserver, mongodb or cockroachdb.
3. Run npx prisma db pull to turn your database schema into a Prisma schema.
4. Run npx prisma generate to generate the Prisma Client. You can then start querying your database.
5. Tip: Explore how you can extend the ORM with scalable connection pooling, global caching, and real-time database events. Read: https://pris.ly/cli/beyond-orm
More information in our documentation:
https://pris.ly/d/getting-started
NodeJS v22.15.1
NPM 11.3.0
Windows 11 24H2 (build 26100.4061)
Severity
🚨 Critical: Data loss, app crash, security issue
Reproduction
> npx [email protected] init
Expected vs. Actual Behavior
instead of an error there should be successful initialize
Frequency
Consistently reproducible
Does this occur in development or production?
Only in development (e.g., CLI tools, migrations, Prisma Studio)
Is this a regression?
Yes, last worked in Prisma 6.7.0, broke in 6.8.0
Workaround
Downgrading to Prisma 6.7.0 fixes it
Prisma Schema & Queries
empty
Prisma Config
empty
Logs & Debug Info
No response
Environment & Setup
- OS: Windows
- Database: any
- Node.js version: 22.12.1
Prisma Version
Environment variables loaded from .env
prisma : 6.8.0
@prisma/client : Not found
Computed binaryTarget : windows
Operating System : win32
Architecture : x64
Node.js : v22.15.1
TypeScript : unknown
Query Engine (Node-API) : libquery-engine 2060c79ba17c6bb9f5823312b6f6b7f4a845738e (at ..\..\Users\vladislav.shinkaruk\AppData\Roaming\npm\node_modules\prisma\node_modules\@prisma\engines\query_engine-windows.dll.node)
Schema Engine : schema-engine-cli 2060c79ba17c6bb9f5823312b6f6b7f4a845738e (at ..\..\Users\vladislav.shinkaruk\AppData\Roaming\npm\node_modules\prisma\node_modules\@prisma\engines\schema-engine-windows.exe)
Schema Wasm : @prisma/prisma-schema-wasm 6.8.0-43.2060c79ba17c6bb9f5823312b6f6b7f4a845738e
Default Engines Hash : 2060c79ba17c6bb9f5823312b6f6b7f4a845738e
Studio : 0.511.0