Prettier Code Formatting Not Working After Upgrading to Prisma 7

[Safnaj]

Bug description

Identified an issue on code formatting for prisma schema with prettier after upgrading to prisma 7. Not sure whether its a known issue. Previously its worked fine. Due to this the schema looks messy.

How to reproduce

• Tried Format Document with
• Tried Format on Save

Expected behavior

• Prisma VS Code Plugin Should Format the Schema

Prisma information

"@prisma/adapter-pg": "^7.0.0",
"@prisma/client": "^7.0.0",
"prisma": "^7.0.0",

Environment & setup

• OS: macOS
• Editor: VS Code
• Editor version: 1.106.2
• Extension version: 7.0.0

[Mr-Geneo]

After upgrading to version 7, editing the schema and saving with lint() works normally, but format() consumes a lot of CPU and cannot be saved correctly.

[Safnaj]

After upgrading to version 7, editing the schema and saving with lint() works normally, but format() consumes a lot of CPU and cannot be saved correctly.

So what is the solution for this ? It supposed to format with Prettier right ?
And I saw the Prettier Prisma Plugin which seems outdated and not maintained for long time.

[nuintun]

This is a very old issue. It used to occur only in special cases, but now it happens in all situations #1774

[nuintun]

I found the reason why the extension runs slowly.
It frequently re-executes the code in prisma.config.ts.
If that file contains any time-consuming tasks—such as loading env files will be triggered repeatedly and cause significant slowdowns.

If you add a simple condition check, you can greatly reduce or even avoid this issue.

if (!process.env.DATABASE_URL) {
  // load env files
}

I'm not quite sure why the extension re-executes prisma.config.ts so frequently.

[MarcellusStack]

Temporary Workarounds:

Manual: Run npx prisma format for a quick, one-time fix.

On-Save Automation: Temporarily rename prisma.config.ts while working on your schema to restore normal on-save formatting.

[DarkKingpro10]

It is 2026.

I do have the same extension and configs, except that I'm using Windows 10; the bug still continues.
It really makes DX worse.

I cannot understand why the Prisma Team cannot fix this bug