Query engine library for current platform "windows" could not be found

Suddenly, for no apparent reason:

    Query engine library for current platform "windows" could not be found.
    You incorrectly pinned it to windows

    This probably happens, because you built Prisma Client on a different platform.
    (Prisma Client looked in "L:\src\foaf\node_modules\@prisma\client\runtime\query_engine-windows.dll.node")

    Searched Locations:

      L:\src\foaf\node_modules\.prisma\client
      L:\src\foaf\node_modules\@prisma\client
      L:\src\foaf\node_modules\@prisma\client
      L:\src\foaf\node_modules\.prisma\client
      L:\src\foaf\prisma
      /tmp/prisma-engines
      L:\src\foaf\node_modules\.prisma\client

    You already added the platform "windows" to the "generator" block
    in the "schema.prisma" file as described in https://pris.ly/d/client-generator,
    but something went wrong. That's suboptimal.

    Please create an issue at https://github.com/prisma/prisma/issues/new

      at Object.getLibQueryEnginePath (node_modules/@prisma/client/runtime/index.js:36461:13)
      at Object.loadEngine (node_modules/@prisma/client/runtime/index.js:36129:33)
      at Object.instantiateLibrary (node_modules/@prisma/client/runtime/index.js:36095:5)

$ grep 'prisma'  package.json
    "prisma": "^3.6.0",

$ node -v
v16.10.0

$ npm -v
7.24.1

Shell is git-bash.

What can I tell you?

[janpio]

Yeah, we are aware that this is kinda messy and your problem shows exactly how this then can go wrong even when you try to do the right thing. Thanks for the explanation!

[appurist]

@janpio Okay, the problem seemed to just be that I was using esbuild to produce the output folder and the includes/excludes were copying the linux version only. Our build is eventually for AWS Lambda, built from a Docker image has a different distro, so we specifically build the “rhel-openssl-1.0.x” version for AWS Lambda. But none of that is too relevant here, I just mention it because you asked about multiple targets:

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

This problem was on Windows and our .esbuild didn’t include the .node engine file for Windows, because it was excluded in the serverless.yml file. I added a *.node wildcard instead of the rhel-specific path that was there and it’s fine:

package:
  excludeDevDependencies: false
  patterns:
    - '!node_modules/.prisma/client/libquery_engine-*'
    - '!node_modules/prisma/libquery_engine-*'
    - '!node_modules/@prisma/engines/**'
    - 'node_modules/.prisma/client/schema.prisma'
    - 'node_modules/.prisma/client/*.node'

That last line ensures these are included. We originally had a problem with the size of prisma in the Lambda image so we started filtering down files that weren’t needed at runtime. I don’t think the others are still needed but the last line ensures we have the native engine, whatever that is.