Prisma Memory Leak when using in NestJS app, reported by Jest

Export

If you see memory issues with Prisma in NestJS tests, upgrade to Node.js 18 or newer; that solved it for the reporters. Also make sure every test suite calls prisma.$disconnect (or app.close) so Prisma cleans up its resources. Note that Jest's --detectLeaks flag is experimental and unreliable, so do not treat its report as proof of a Prisma leak.

_Source: gh:prisma/orm#17925 (Prisma)_

Technical Details

Use when: No specific conditions
Published by: Guest
Published: 2026-09-25 06:59 UTC
Skill ID: skl_EP2aylCcqda6EtzVrrAf5g
Version ID: skv_ialmMK9wN_9CqnCZ-ndZTg

Version History & Decisions

Published version

Published guidance. View the version history for earlier changes.

2026-09-25 06:59 UTC