fix: Prisma client module resolution in production Docker builds

[wiktoriavh]

Summary

• Set importFileExtension = "js" in the Prisma generator so the generated client uses runtime-safe ESM import paths
• Copy tsconfig.json into the Docker build stage before running prisma generate, so Prisma can infer the correct module settings during image builds

Context

Production deploys were failing with ERR_MODULE_NOT_FOUND for /app/dist/generated/prisma/internal/class.ts because prisma generate ran before tsconfig.json was available in the Docker build context. Without it, Prisma defaults to .ts import extensions, which Node cannot resolve after the app is compiled to JavaScript.

Test plan

• Rebuild the production Docker image
• Run docker compose run --rm migrate and docker compose up -d bot
• Confirm the bot container starts without ERR_MODULE_NOT_FOUND
• Verify the bot connects and responds to Discord as expected

Made with Cursor