problem when deploying prisma

hello guys , i just completed my portfolio and i'm trying to deploy my app to vercel but i'm always having this error

You can mark the path "mock-aws-s3" as external to exclude it from the bundle, which will remove this error and leave the unresolved path in the bundle. You can also surround this "require" call with a try/catch block to handle this failure at run-time instead of bundle-time.

You can mark the path "mock-aws-s3" as external to exclude it from the bundle, which will remove this error and leave the unresolved path in the bundle. You can also surround this "require" call with a try/catch block to handle this failure at run-time instead of bundle-time.

, the problem is i never used the path that he is talking about , i started getting the error when i added prisma to my code , any idea how to solve it ?

Solution

you are right , i found that there is a part of the project that uses Lucia auth i forgot to delete it , it's the source of this error

Jump to solution

Prisma•2y ago•

7 replies

adam boukhris

problem when deploying prisma

hello guys , i just completed my portfolio and i'm trying to deploy my app to vercel but i'm always having this error

You can mark the path "mock-aws-s3" as external to exclude it from the bundle, which will remove this error and leave the unresolved path in the bundle. You can also surround this "require" call with a try/catch block to handle this failure at run-time instead of bundle-time.

You can mark the path "mock-aws-s3" as external to exclude it from the bundle, which will remove this error and leave the unresolved path in the bundle. You can also surround this "require" call with a try/catch block to handle this failure at run-time instead of bundle-time.

, the problem is i never used the path that he is talking about , i started getting the error when i added prisma to my code , any idea how to solve it ?

Solution

you are right , i found that there is a part of the project that uses Lucia auth i forgot to delete it , it's the source of this error

Jump to solution

problem when deploying prisma

Similar Threads

problem when deploying prisma

Similar Threads

Similar Threads

Similar Threads