@prisma/client-common 7.2.0 → 7.3.0-integration-fix-6-19-0-cloudflare-accelerate-engine.1

package/dist/QueryEngine.d.ts

@@ -1,4 +1,21 @@
 import { ErrorCapturingSqlDriverAdapter } from '@prisma/driver-adapter-utils';
+export type EngineWasmLoadingConfig = {
+    /**
+     * WASM-bindgen runtime for corresponding module
+     */
+    getRuntime: () => Promise<{
+        __wbg_set_wasm(exports: unknown): void;
+        QueryEngine: QueryEngineConstructor;
+    }>;
+    /**
+     * Loads the raw wasm module for the wasm query engine. This configuration is
+     * generated specifically for each type of client, eg. Node.js client and Edge
+     * clients will have different implementations.
+     * @remarks this is a callback on purpose, we only load the wasm if needed.
+     * @remarks only used by LibraryEngine
+     */
+    getQueryEngineWasmModule: () => Promise<unknown>;
+};
 export type QueryEngineInstance = {
     connect(headers: string, requestId: string): Promise<void>;
     disconnect(headers: string, requestId: string): Promise<void>;
@@ -16,6 +33,8 @@ export type QueryEngineInstance = {
     startTransaction(options: string, traceHeaders: string, requestId: string): Promise<string>;
     commitTransaction(id: string, traceHeaders: string, requestId: string): Promise<string>;
     rollbackTransaction(id: string, traceHeaders: string, requestId: string): Promise<string>;
+    metrics?(options: string): Promise<string>;
+    applyPendingMigrations?(): Promise<void>;
     trace(requestId: string): Promise<string | null>;
 };
 export interface QueryEngineConstructor {

package/dist/client-config.d.ts

@@ -1,5 +1,7 @@
-import { ActiveConnectorType } from '@prisma/generator';
+import { ActiveConnectorType, EnvValue, GeneratorConfig } from '@prisma/generator';
+import { LoadedEnv } from '@prisma/internals';
 import { CompilerWasmLoadingConfig } from './QueryCompiler';
+import { EngineWasmLoadingConfig } from './QueryEngine';
 import { RuntimeDataModel } from './runtimeDataModel';
 /**
  * Config that is stored into the generated client. When the generated client is
@@ -8,16 +10,73 @@ import { RuntimeDataModel } from './runtimeDataModel';
  */
 export type GetPrismaClientConfig = {
     runtimeDataModel: RuntimeDataModel;
-    previewFeatures: string[];
+    generator?: GeneratorConfig;
+    relativeEnvPaths?: {
+        rootEnvPath?: string | null;
+        schemaEnvPath?: string | null;
+    };
+    relativePath: string;
+    dirname: string;
     clientVersion: string;
     engineVersion: string;
+    datasourceNames: string[];
     activeProvider: ActiveConnectorType;
     /**
      * The contents of the schema encoded into a string
+     * @remarks only used for the purpose of data proxy
      */
     inlineSchema: string;
+    /**
+     * A special env object just for the data proxy edge runtime.
+     * Allows bundlers to inject their own env variables (Vercel).
+     * Allows platforms to declare global variables as env (Workers).
+     * @remarks only used for the purpose of data proxy
+     */
+    injectableEdgeEnv?: () => LoadedEnv;
+    /**
+     * The contents of the datasource url saved in a string.
+     * This can either be an env var name or connection string.
+     * It is needed by the client to connect to the Data Proxy.
+     * @remarks only used for the purpose of data proxy
+     */
+    inlineDatasources: {
+        [name in string]: {
+            url: EnvValue;
+        };
+    };
+    /**
+     * The string hash that was produced for a given schema
+     * @remarks only used for the purpose of data proxy
+     */
+    inlineSchemaHash: string;
+    /**
+     * A marker to indicate that the client was not generated via `prisma
+     * generate` but was generated via `generate --postinstall` script instead.
+     * @remarks used to error for Vercel/Netlify for schema caching issues
+     */
+    postinstall?: boolean;
+    /**
+     * Information about the CI where the Prisma Client has been generated. The
+     * name of the CI environment is stored at generation time because CI
+     * information is not always available at runtime. Moreover, the edge client
+     * has no notion of environment variables, so this works around that.
+     * @remarks used to error for Vercel/Netlify for schema caching issues
+     */
+    ciName?: string;
+    /**
+     * Information about whether we have not found a schema.prisma file in the
+     * default location, and that we fell back to finding the schema.prisma file
+     * in the current working directory. This usually means it has been bundled.
+     */
+    isBundled?: boolean;
+    /**
+     * A boolean that is `false` when the client was generated with --no-engine. At
+     * runtime, this means the client will be bound to be using the Data Proxy.
+     */
+    copyEngine?: boolean;
     /**
      * Optional wasm loading configuration
      */
+    engineWasm?: EngineWasmLoadingConfig;
     compilerWasm?: CompilerWasmLoadingConfig;
 };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@prisma/client-common",
-  "version": "7.2.0",
+  "version": "7.3.0-integration-fix-6-19-0-cloudflare-accelerate-engine.1",
   "description": "This package is intended for Prisma's internal use",
   "main": "dist/index.js",
   "module": "dist/index.mjs",
@@ -24,11 +24,11 @@
   },
   "license": "Apache-2.0",
   "dependencies": {
-    "@prisma/client-engine-runtime": "7.2.0",
-    "@prisma/dmmf": "7.2.0",
-    "@prisma/generator": "7.2.0",
-    "@prisma/internals": "7.2.0",
-    "@prisma/driver-adapter-utils": "7.2.0"
+    "@prisma/client-engine-runtime": "7.3.0-integration-fix-6-19-0-cloudflare-accelerate-engine.1",
+    "@prisma/dmmf": "7.3.0-integration-fix-6-19-0-cloudflare-accelerate-engine.1",
+    "@prisma/driver-adapter-utils": "7.3.0-integration-fix-6-19-0-cloudflare-accelerate-engine.1",
+    "@prisma/generator": "7.3.0-integration-fix-6-19-0-cloudflare-accelerate-engine.1",
+    "@prisma/internals": "7.3.0-integration-fix-6-19-0-cloudflare-accelerate-engine.1"
   },
   "files": [
     "dist"