Remove the implicit "native" binaryTarget

Bug description

I want to leave out my “native” binaryTarget, and build the client explicitly for the targets I declard in schema.prisma.

This is a problem because when multiple people (with different Operating Systems) are working on the same codebase will generate different clients - but they should be exactly the same.

Doc links: https://www.prisma.io/docs/reference/api-reference/prisma-schema-reference#specify-custom-binarytargets-to-ensure-compatibility-with-the-os

How to reproduce

For example, in this case:

generator client {
  provider      = "prisma-client-js"
  binaryTargets = ["rhel-openssl-1.0.x"]
}

I want the client built ONLY for "rhel-openssl-1.0.x" and not for my "native" target as well.

The "native" target is added implicitly for some reason.

Expected behavior

No response

Prisma information

schema.prisma:

generator client {
  provider      = "prisma-client-js"
  binaryTargets = ["rhel-openssl-1.0.x"]
}

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

model User {
  uuid      String   @id @db.Uuid
  createdAt DateTime @default(now())
}

Environment & setup

• OS: Mac/Ubuntu/Windows
• Database: PostgreSQL (not relevant)
• Node.js version: v16.13.2

Prisma Version

package.json:

    ...
    "@prisma/client": "^3.12.0",
    "prisma": "^3.12.0",
    ...

[janpio]

That’s a pretty good suggestion. Can you turn it into a new feature request issue please @dejanvasic85? Thanks.

[janpio]

Yes, that is what I confirmed (or tried to at least) with my comment above 😆 We’ll look into this. Changing this of course would not be that easy, as quite a few setups out there of course could rely on this current behavior - accidentally or by design.