Fix Prisma Client ESM import paths so Webpack bundles reliably

Fix Prisma Client ESM import paths so Webpack bundles reliably targets a $1.2B = 200K backend engineering teams × $6K ACV total addressable market with medium saturation and a year-over-year growth rate of 12% YoY — based on growth of JS/TS server adoption and tooling demand (GitHub Octoverse and Stack Overflow surveys indicate steady backend JS growth).

Key trends driving demand: Migration to ESM and stricter module resolution — this increases the frequency of generator-to-bundler mismatch bugs and creates demand for tooling that standardizes codegen outputs.; Rising adoption of code generation (ORMs, GraphQL codegen, API clients) — more generated sources means more surface area for integration issues and higher value for automated compatibility fixes.; Shift to CI-first developer workflows — teams want deterministic CI checks to catch bundling and runtime import issues before release, creating an opening for CI-integrated validation tools.; Plugin ecosystems for bundlers are maturing — standardized plugin interfaces let small teams ship cross-bundler solutions faster and reach many users via package registries..