[Blocker] Fix: Unify Prisma client with connection pooling across all files
Published on February 7, 2026
## GitHub Update
**Repository:** [MKWcorp/berkomunitas](https://github.com/MKWcorp/berkomunitas)
**Author:** multimediadrw
**Date:** 2/7/2026, 10:16:33 AM
**Commit:** [`32c99e4`](https://github.com/MKWcorp/berkomunitas/commit/32c99e45f16cbb9544993c8bf2891958aee62092)
### Commit Message
Fix: Unify Prisma client with connection pooling across all files
- Update src/utils/prisma.js to use same connection pooling as lib/prisma.js
- Add connection_limit parameter (5 for production, 10 for dev)
- Update imports in privilegeChecker.js and generateUsername.js to use lib/prisma
- Remove duplicate Prisma client instances
- This should fix 'too many clients already' error in production
Root cause: Multiple Prisma client files without proper connection pooling were creating too many connections to PostgreSQL.
---
_This story was imported from historical commits._