Naming coflict after client generation in 6.6.0

[isfan14]

Bug description

Language tools does not seem to ignore generated/compiled schema.prisma file in the defined output dir on 6.6.0 using prisma.config.ts with multiple schema file. This behavior raising some naming conflict error as shown below.

How to reproduce

1. Set schema dir in prisma.config.ts to prisma/schema
2. Set output dir in main schema.prisma to output = "../generated/client"
3. Generate prisma client npx prisma generate
4. Open source .prisma files and the schema.prisma in prisma/generated/client
5. See error raised in the PROBLEMS tab

Expected behavior

Language tool should ignore schema.prisma file in the defined output dir.

Prisma information

• Using Prisma 6.6.0
• Using preview feature prisma.config.ts

import path from 'node:path';
import { defineConfig } from 'prisma/config';

import 'dotenv/config';

export default defineConfig({
  earlyAccess: true,
  schema: path.join('prisma', 'schema'),
});

• Client generator in schema.prisma

generator client {
  provider        = "prisma-client-js"
  previewFeatures = ["multiSchema", "postgresqlExtensions", "relationJoins", "prismaSchemaFolder", "fullTextSearchPostgres", "typedsql"]
  output          = "../generated/client"
  moduleFormat    = "esm"
}

Environment & setup

• OS: Ubuntu 24.04.1 LTS in WSL in Windows 11
• Editor: VS Code
• Editor version: 1.99.3
• Extension version: 6.6.0

[bshearrer]

I am also having this issue

[favna]

We are also facing this problem at work project with extension version 6.7.0.

[jusemon]

Same issue here

[bshearrer]

Looks like this issue is similar/related to https://github.com/prisma/language-tools/issues/1803 which has a comment potential workaround solution https://github.com/prisma/prisma/discussions/24413#discussioncomment-9670600

[wowtah]

I have the same issue, Prisma 6.13.0. Very annoying.

[fornaeffe]

Same issue. I'm using Prisma 6.15.0, without preview features.