Option to skip creation of lib/prisma.ts

[lewebsimple]

When only using the usePrismaClient composable, it would be nice to disable generation of the global instance in lib/prisma.ts

[saurlax]

I hope the Prisma instance is located in server/utils/prisma.ts instead of lib/prisma.ts, so it can be automatically imported in server route endpoints. Is this approach reliable? Unfortunately, I haven't found a way to skip generating lib/prisma.ts or change its location.

Currently, I am adding the following content to server/utils/prisma.ts to solve this problem:

export { default } from "~/lib/prisma";

[Yariandres]

@saurlax thanks for posting your workaround as this also causes the:

Uncaught TypeError: Failed to resolve module specifier ".prisma/client/index-browser". Relative references must start with either "/", "./", or "../".

on Netlify.

[saurlax]

Hi @Yariandres , you can follow this instruction to address this error: https://www.prisma.io/docs/orm/more/help-and-troubleshooting/prisma-nuxt-module#resolving-typeerror-failed-to-resolve-module-specifier-prismaclientindex-browser

[Yariandres]

@saurlax Thanks, I was looking everywhere... Indeed solved it! 👍

[ankur-arch]

I hope the Prisma instance is located in server/utils/prisma.ts instead of lib/prisma.ts, so it can be automatically imported in server route endpoints. Is this approach reliable? Unfortunately, I haven't found a way to skip generating lib/prisma.ts or change its location.

Thanks @saurlax . I'll try to to make that happen in the next release.

[AmanVarshney01]

Sadly, we are deprecating this module. You can read more about the explanation here

How to use Nuxt with Prisma 7 - https://www.prisma.io/docs/guides/nuxt