Prisma v7 + Supabase Postgres DB installation : 1) GitHub Codespaces 2) Firebase Studio

[KB-WEB-DEVELOPMENT]

Question

Hello,

Because I am now convinced there is no straightforward way to install Prisma (any version) and have it work with a Supabase Postgres database (#29318) on my machine, I was wondering if someone could share with me a link to a tutorial (or online instructions) which explains properly how to install Prisma v7 (+ Supabase Postgres database) on either

(1) GitHub Codespaces

or / and

(2) Firebase Studio

I have of course already tried both approaches but I would like to meticulously go through every step again and either validate or invalidate the tutorial instructions.

Thanks very much in advance.

KBW.

[Andrew1326]

Here's a step-by-step guide for Prisma v7 + Supabase Postgres in GitHub Codespaces (Firebase Studio steps are nearly identical):

1. Create a new Codespace

Open any repo (or a blank one) in GitHub Codespaces. The default image has Node.js pre-installed.

2. Init your project

mkdir my-app && cd my-app
npm init -y
npm install prisma@latest @prisma/client@latest
npx prisma init

3. Get your Supabase connection string

In your Supabase dashboard → Settings → Database → Connection string → URI.

It looks like: postgresql://postgres.[project-ref]:[password]@aws-0-[region].pooler.supabase.com:6543/postgres

Important: Supabase uses connection pooling (PgBouncer) on port 6543. For Prisma migrations you need the direct connection on port 5432. You can find this under Connection string → Direct connection.

4. Configure .env

# Pooled connection (for queries at runtime)
DATABASE_URL="postgresql://postgres.[ref]:[password]@aws-0-[region].pooler.supabase.com:6543/postgres?pgbouncer=true"

# Direct connection (for migrations)
DIRECT_URL="postgresql://postgres.[ref]:[password]@aws-0-[region].pooler.supabase.com:5432/postgres"

5. Configure prisma/schema.prisma

generator client {
  provider = "prisma-client"
}

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

model Post {
  id        Int      @id @default(autoincrement())
  title     String
  content   String?
  createdAt DateTime @default(now())
}

Key points:

• provider = "prisma-client" is the new Prisma v7 syntax (replaces prisma-client-js)
• directUrl tells Prisma to use the direct connection for migrations (bypassing PgBouncer)

6. Run your first migration

npx prisma migrate dev --name init

This creates the table in your Supabase database. You can verify it in the Supabase Table Editor.

7. Use it in code

Create index.ts:

import { PrismaClient } from '@prisma/client'

const prisma = new PrismaClient()

async function main() {
  const post = await prisma.post.create({
    data: { title: 'Hello from Codespaces!', content: 'It works!' },
  })
  console.log('Created:', post)

  const posts = await prisma.post.findMany()
  console.log('All posts:', posts)
}

main()
  .catch(console.error)
  .finally(() => prisma.$disconnect())

Run it:

npx tsx index.ts

Common issues

• "prepared statement already exists" → Make sure you have ?pgbouncer=true in your DATABASE_URL
• Migration hangs or times out → Make sure DIRECT_URL uses port 5432, not 6543
• SSL errors → Codespaces and Firebase Studio can reach Supabase over SSL by default. If you get SSL errors, add &sslmode=require to both URLs

This should work identically in Firebase Studio — just open the terminal and follow the same steps from step 2 onwards.

[nurul3101]

Did this solution work for you?

[KB-WEB-DEVELOPMENT]

@nurul3101 - Thanks for asking. Because this whole Prisma / Supabase installation and the search for any type of help has been dragging on for so long, I took a little break from the whole thing. I intend to give in another shot in the coming days. Thanks.

[nurul3101]

No worries!

[pranay-dutta]

@nurul3101 prisma7.0.1 does not support DIRECT_URL & DATABASE_URL in schema.prisma file. What about that?

[GitNimay]

The main issue here is probably not Codespaces or Firebase Studio specifically. Prisma can work with Supabase Postgres, but the setup is easy to get wrong because Supabase has multiple connection strings and Prisma uses different connection behavior for runtime versus CLI workflows.

For Prisma 7, I would start from Prisma’s Supabase guide rather than a random tutorial. The important part is to use two URLs:

DATABASE_URL="postgresql://postgres.[project-ref]:[password]@aws-0-[region].pooler.supabase.com:6543/postgres?pgbouncer=true"
DIRECT_URL="postgresql://postgres:[password]@db.[project-ref].supabase.co:5432/postgres"

Then configure the Prisma CLI to use the direct URL:

import "dotenv/config";
import { defineConfig, env } from "prisma/config";

export default defineConfig({
  schema: "prisma/schema.prisma",
  datasource: {
    url: env("DIRECT_URL"),
  },
});

Your Prisma schema should still use PostgreSQL:

datasource db {
  provider = "postgresql"
}

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

For runtime, use the pooled Supabase URL with the PostgreSQL adapter:

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

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

export const prisma = new PrismaClient({ adapter });

Install the relevant packages:

npm install prisma @prisma/client @prisma/adapter-pg pg

Then run:

npx prisma generate
npx prisma db pull

or, for a new schema:

npx prisma migrate dev

In GitHub Codespaces, the setup should be the same as any Linux dev container. The main things to check are that your Supabase project allows the connection, your .env is present in the Codespace, and you are using the direct connection for CLI commands.

In Firebase Studio, I would be a little more careful. Prisma has an official Firebase Studio guide, but that guide is for Prisma Postgres, not necessarily Supabase Postgres. The same Supabase connection principles should still apply, but I would not use a Firebase Studio plus Prisma Postgres tutorial as proof that a Firebase Studio plus Supabase setup is correct.

So the best resources to follow are:

1. Prisma Supabase guide
2. Prisma Firebase Studio guide, only for the Firebase Studio workspace mechanics
3. Supabase dashboard connection string docs, to copy the direct and pooler URLs correctly

The most common mistake is using the Supabase transaction pooler URL for Prisma CLI operations. Use the direct URL for Prisma CLI commands and the pooled URL for the application runtime.

If this still fails, the useful information to post would be the exact Prisma command, the exact error code such as P1001 or P1010, whether the failing URL is direct or pooled, and whether the same connection works from psql inside Codespaces or Firebase Studio.

[logusivam]

This is a reasonable question, but it rests on a premise worth examining before pointing you to tutorials — because "there is no straightforward way to install Prisma with Supabase Postgres" is not accurate as a general statement, and understanding why may save you significant time before going through tutorials again.

---

On the premise from discussion #29318

That discussion describes connection issues that are almost always one of three specific, solvable problems — not a fundamental incompatibility between Prisma and Supabase Postgres. Prisma and Supabase are explicitly designed to work together, and Supabase's own documentation includes a dedicated Prisma integration guide. Before doing a full tutorial walkthrough in Codespaces or Firebase Studio, it is worth confirming which of these three issues you are actually hitting.

---

The three actual causes of Prisma + Supabase failures

1. Wrong connection string type for the wrong Prisma operation

Supabase provides two distinct connection strings and they are not interchangeable:

String type	Port	Use with
Direct connection	5432	prisma migrate, prisma db push, prisma db pull
Transaction pooler (PgBouncer)	6543	Prisma Client runtime queries in serverless environments
Session pooler	5432	Prisma Client runtime queries in long-lived server environments

The single most common failure is using the transaction pooler URL (port 6543) for migrations. PgBouncer in transaction mode does not support the prepared statements that Prisma Migrate requires, so migrations fail. Prisma Client runtime queries using the same pooler URL also require pgbouncer=true appended to the connection string.

The correct setup uses two separate environment variables:

# For migrations and schema operations — direct connection, port 5432
DATABASE_URL="postgresql://postgres:[YOUR-PASSWORD]@db.[YOUR-PROJECT-REF].supabase.co:5432/postgres"

# For Prisma Client at runtime — session pooler, port 5432
DIRECT_URL="postgresql://postgres.[YOUR-PROJECT-REF]:[YOUR-PASSWORD]@aws-0-[REGION].pooler.supabase.com:5432/postgres"

And in your schema.prisma:

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

The directUrl field (available in Prisma v6+, fully supported in v7) tells Prisma to use the direct connection for migrations and the pooled URL for client queries automatically.

2. Prisma v7 requires a driver adapter — the instantiation syntax changed

In Prisma v7, you cannot instantiate PrismaClient without a driver adapter. The old new PrismaClient() with a connection string in the environment variable is no longer valid:

// WRONG in Prisma v7 — will not work
const prisma = new PrismaClient();

// CORRECT in Prisma v7 — driver adapter required
import { PrismaClient } from './generated/prisma/client';
import { PrismaPg } from '@prisma/adapter-pg';

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

And the generator in schema.prisma changed too:

generator client {
  provider = "prisma-client"   // NOT "prisma-client-js" — that is the v6 syntax
}

Most tutorials written before November 2025 will show the v6 syntax and will silently fail in v7 without a clear error message explaining why.

3. SSL certificate validation behavior changed in v7

Prisma v7 changed SSL certificate validation defaults. Supabase connections require SSL, and if your environment doesn't have the right CA bundle, you may hit SSL errors. The fix is to append ?sslmode=require to your connection string, or in some environments ?sslmode=no-verify for development (not production):

DATABASE_URL="postgresql://postgres:[PASSWORD]@db.[REF].supabase.co:5432/postgres?sslmode=require"

---

Minimal working setup for Prisma v7 + Supabase (validated)

npm install prisma@7 @prisma/client@7 @prisma/adapter-pg pg

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

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

// prisma/prisma.config.ts — required in v7
import { defineConfig, env } from "prisma/config";

export default defineConfig({
  schema: "prisma/schema.prisma",
  migrations: {
    path: "prisma/migrations",
  },
  datasource: {
    url: env("DIRECT_URL"),   // migrations use direct connection
  },
});

// src/db.ts
import { PrismaClient } from '../generated/prisma';
import { PrismaPg } from '@prisma/adapter-pg';

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

export const prisma = new PrismaClient({ adapter });

# Run migration
npx prisma migrate dev --config prisma/prisma.config.ts

# Generate client
npx prisma generate --config prisma/prisma.config.ts

---

On Codespaces vs Firebase Studio specifically

Both environments work with this setup. Neither requires a special tutorial beyond the above because the connection issues are not environment-specific — they are Prisma v7 configuration issues that are identical whether you run locally, in Codespaces, or in Firebase Studio. The environment only matters for:

• Port forwarding: Codespaces and Firebase Studio both expose environment variables via their respective secrets/env configuration UI — set DATABASE_URL and DIRECT_URL there rather than in a .env file you might accidentally commit.
• Node.js version: Prisma v7 requires Node.js 18+. Codespaces default images include this. Firebase Studio also supports Node.js 18+. Verify with node -v before starting.

The official Supabase + Prisma guide at supabase.com/docs/guides/database/prisma is the most accurate starting reference, though it may not yet be fully updated for v7's prisma.config.ts requirement and driver adapter syntax — apply the v7 corrections shown above when following it.

If you share the specific error you're hitting (the exact error message from your previous attempts), the root cause can be identified precisely rather than working through every step again from scratch.

Hope this helps — if it answers your question, would you mind clicking "Mark as answer" so others searching for the same thing can find it quickly?