-
Notifications
You must be signed in to change notification settings - Fork 870
Closed
Description
Bug description
You cannot init Prisma when using Deno
Severity
Reproduction
The step by step guide is literally the guide on the official documentation: Deploy to Deno Deploy.
This command deno run --reload -A npm:prisma@latest init --db
Produces this result:
Error: Relative import path "get-tsconfig" not prefixed with / or ./ or ../ and not in import map from "file:///var/folders/g3/vj3b0pt928gc6vxvlgsghlx80000gn/T/@prisma/cli-init@latest-1748210400000/node_modules/@prisma/cli-init/dist/index.js"
at file:///var/folders/g3/vj3b0pt928gc6vxvlgsghlx80000gn/T/@prisma/cli-init@latest-1748210400000/node_modules/@prisma/cli-init/dist/index.js:23:29
Expected vs. Actual Behavior
Crashing, cannot initiate the app
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 queryPrisma Config
// Add your `prisma.config.ts`Logs & Debug Info
// Debug logs here
Environment & Setup
macOS 15.5, Deno 2.3.3
Prisma Version
using npm:prisma@latest as of 26/05/2025.
Metadata
Metadata
Assignees
Labels
No labels