After upgrading to the latest Prisma 8 release, autocomplete and formatting are no longer working for `.prisma` files in VS Code.

[nazzz-infotech]

Package and version

prisma-next

What happened?

Bug description

After upgrading to the latest Prisma 8 release, autocomplete and formatting are no longer working for .prisma files in VS Code.

I am using the official stable Prisma VS Code extension.

The .prisma file is recognized and syntax highlighting works, but:

• IntelliSense/autocomplete suggestions do not appear
• Ctrl + Space does not provide Prisma schema suggestions
• Format Document does not format the schema
• editor.formatOnSave does not format .prisma files

This seems to be related specifically to the VS Code extension / Prisma language server when using Prisma 8.

How to reproduce

1. Create or open a Prisma 8 project.
2. Install the official stable Prisma VS Code extension.
3. Open a .prisma schema file.
4. Try typing something such as:

model User {
  id String
}

Here's a video clip:

5. Trigger autocomplete using Ctrl + Space.
6. Try Format Document or save the file with editor.formatOnSave enabled.

Expected behavior

The Prisma VS Code extension should provide:

• Prisma schema autocomplete
• field/type suggestions
• diagnostics
• schema formatting
• format-on-save support

Actual behavior

Autocomplete suggestions do not appear and the Prisma formatter does not run.
The issue started when using Prisma 8. The same editor functionality was working as expected with previous Prisma versions.

What did you expect to happen?

I expected the official Prisma VS Code extension to provide normal .prisma editor support with Prisma 8, including IntelliSense/autocomplete suggestions, schema diagnostics, and formatting.

Specifically, Ctrl + Space should show Prisma schema suggestions, and Format Document / editor.formatOnSave should format the .prisma file correctly.

I noticed that if the file starts with :

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

generator client {
  provider = "prisma-client-js"
}

Everything is works correctly.
Here's a video clip:

Minimal reproduction

Create a new Prisma 8 project and install the official stable Prisma VS Code extension.

Example:

pnpm dlx prisma@latest init

Open the generated schema.prisma file in VS Code and try:

model User {
  id String @id
  name String?
}

Then:

1. Place the cursor inside the model and press Ctrl + Space.
2. Try adding a field and check whether Prisma type/attribute suggestions appear.
3. Run Format Document.
4. Enable editor.formatOnSave and save the file.

With Prisma 8, autocomplete suggestions do not appear and the VS Code Prisma formatter does not run.

Environment

Environment

• Prisma-next
• VS Code: latest stable
• Prisma VS Code extension: official stable extension
• Package manager: pnpm
• OS: Windows 11
• Node.js: v26.8.1

Additional information

VS Code settings include:

{
  "[prisma]": {
    "editor.defaultFormatter": "Prisma.prisma",
    "editor.formatOnSave": true
  }
}

Full VScode information

Version: 1.136.1 (system setup)
Commit: a44adf7f53e00964ab890f9f8758a334f1fc15bc
Date: 2026-09-03T05:06:41Z
Electron: 42.10.0
ElectronBuildId: 15109253
Chromium: 148.0.7778.280
Node.js: 24.18.1
V8: 14.8.178.38-electron.0
@github/copilot: 1.0.81-0
@github/copilot-sdk: 1.0.11
OS: Windows_NT x64 10.0.22631

Additional context

This has become quite frustrating during normal development because autocomplete and formatting are core parts of the Prisma schema editing experience. Without them, working with .prisma files is noticeably slower and more error-prone, especially when frequently adding or changing models, fields, relations, and attributes.

I also tested the same project with the Prisma Insiders VS Code extension, but the issue still occurs there as well. So this does not appear to be limited to the stable extension.

The Prisma CLI continues to work correctly, while editor autocomplete and formatting remain unavailable.

[SevInf]

I double checked your reproduction instruction, it did work for me. Ensure that the extension is at 31.12.8 version and you have prisma cli as a part of your npm dependencies. If neither works let me know, I'll investigate further. It would help if you could share entire vscode workspace too.

[nazzz-infotech]

I’m closing this issue for now.

After further testing, I think this may be related to my local setup rather than a confirmed Prisma 8 bug. I’ll reopen it or create a new issue if I can reproduce it consistently with a minimal workspace.

Thanks for taking the time to investigate.