`InvalidDatasourceError` of Data Proxy Client outputs a code snippet

C:\Users\Jan\Documents\throwaway\dataProxyTest>node script.js
C:\Users\Jan\Documents\throwaway\dataProxyTest\node_modules\@prisma\client\runtime\proxy.js:27
`)}`});let i={batch:e.map(o=>({query:o,variables:{}})),transaction:r},{batchResult:a}=await this.requestInternal(i,t,n);return a}async requestInternal(e,t,r){var n;await this.pushPromise;try{this.logEmitter.emit("info",{message:`Calling ${this.url("graphql")} (n=${r})`});let i=await Sr(this.url("graphql"),{method:"POST",headers:{...t,...this.headers},body:JSON.stringify(e)}),a=await Kr(i,this.clientVersion);if(a instanceof Yr)throw await this.uploadSchema(),new Wr({clientVersion:this.clientVersion,c                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        

InvalidDatasourceError: Datasource URL should use prisma:// protocol. If you are not using the Data Proxy, remove the `dataProxy` from the `previewFeatures` in your schema and ensure that `PRISMA_CLIENT_ENGINE_TYPE` environment variable is not set to `dataproxy`.    at Object.extractHostAndApiKey (C:\Users\Jan\Documents\throwaway\dataProxyTest\node_modules\@prisma\client\runtime\proxy.js:27:1513)    at new DataProxyEngine (C:\Users\Jan\Documents\throwaway\dataProxyTest\node_modules\@prisma\client\runtime\proxy.js:25:14740)    at t.getEngine (C:\Users\Jan\Documents\throwaway\dataProxyTest\node_modules\@prisma\client\runtime\proxy.js:104:3039)    at new PrismaClient (C:\Users\Jan\Documents\throwaway\dataProxyTest\node_modules\@prisma\client\runtime\proxy.js:104:2583)    at file:///C:/Users/Jan/Documents/throwaway/dataProxyTest/script.js:2:16    at ModuleJob.run (node:internal/modules/esm/module_job:183:25)
    at async Loader.import (node:internal/modules/esm/loader:178:24)
    at async Object.loadESM (node:internal/process/esm_loader:68:5)
    at async handleMainPromise (node:internal/modules/run_main:63:12) {
  clientVersion: '3.14.0',
  cause: undefined,
  isRetryable: false,
  code: 'P5002'
}

This error output is unexpected.

Reproduction

• Create new folder with Prisma project via npx prisma init
• Modify schema:

  generator client {
    provider        = "prisma-client-js"
    previewFeatures = ["dataProxy"]
  }
  
  datasource db {
    provider = "postgresql"
    url      = env("DATABASE_URL")
  }
  
  model foo {
    id Int @id
  }
  

• Generate Data Proxy Client: https://www.prisma.io/docs/concepts/data-platform/data-proxy#step-3-enable-the-feature-flag-in-the-prisma-schema-file and following
• Minimal scripts.js:

  import { PrismaClient } from '@prisma/client'
  const prisma = new PrismaClient()
  

• Add "type": "module" to package.json
• node script.js
• Observe error

[janpio]

Now I can confirm this is fixed with 3.15.0:

PS C:\Users\Jan\Documents\throwaway\3150> node .\scripts.js
C:\Users\Jan\Documents\throwaway\3150\node_modules\@prisma\client\runtime\index.js:44543
      throw new InvalidDatasourceError("No valid API key found in the datasource URL", {
            ^

InvalidDatasourceError: No valid API key found in the datasource URL
    at DataProxyEngine.extractHostAndApiKey (C:\Users\Jan\Documents\throwaway\3150\node_modules\@prisma\client\runtime\index.js:44543:13)
    at new DataProxyEngine (C:\Users\Jan\Documents\throwaway\3150\node_modules\@prisma\client\runtime\index.js:44399:33)
    at PrismaClient.getEngine (C:\Users\Jan\Documents\throwaway\3150\node_modules\@prisma\client\runtime\index.js:49538:16)
    at new PrismaClient (C:\Users\Jan\Documents\throwaway\3150\node_modules\@prisma\client\runtime\index.js:49512:29)
    at file:///C:/Users/Jan/Documents/throwaway/3150/scripts.js:2:16
    at ModuleJob.run (node:internal/modules/esm/module_job:183:25)
    at async Loader.import (node:internal/modules/esm/loader:178:24)
    at async Object.loadESM (node:internal/process/esm_loader:68:5)
    at async handleMainPromise (node:internal/modules/run_main:63:12) {
  clientVersion: '3.15.0',
  cause: undefined,
  isRetryable: false,
  code: 'P5002'
}

[millsp]

Sorry, let me correct myself, I meant that I cannot reproduce this with the latest changes in the chore/data-proxy-ga-3 branch.