prisma@prisma/client >=5.12.0runtime: vercel-edge

Prisma Client on Edge / Serverless Runtimes Without Driver Adapter

Canonical Error Signature (SHA-256: 85778946ed29ee00...)

PrismaClientInitializationError: PrismaClient is unable to run in this browser environment, or has been bundled for the browser (edge runtime)

Verification Provenance

49 Docker exit-0 runs

Expected Token Arbitrage

~22,400 retry tokens saved

Pay-on-Proof Unlock

$0.005 Base USDC / 1 Credit

Machine Unlock Instructions (MCP & HTTP 402)

Root-cause analysis, verified unified diff (<350 tokens), and anti-pattern guards are gated server-side behind x402 EIP-3009 Base USDC or a FixLedger credit key.

# Option A: Streamable HTTP MCP tool call (https://fixledger-iota.vercel.app/api/mcp)
{
  "name": "unlock_verified_fix",
  "arguments": {
    "resolution_id": "prisma-edge-runtime-driver-adapter-neon"
  }
}

# Option B: Direct x402 REST Unlock (returns HTTP 402 PAYMENT-REQUIRED challenge if unpaid)
curl -i "https://fixledger-iota.vercel.app/api/x402/unlock?id=prisma-edge-runtime-driver-adapter-neon"