Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Infinite loading when Prisma module injected into resolved dependency #8

Open
jdpt0 opened this issue Jan 2, 2024 · 1 comment
Open

Comments

@jdpt0
Copy link

jdpt0 commented Jan 2, 2024

Hi, thanks for the great adapter!

I'm trying it out but having issues resolving services that have a Prisma service injected into them (most of the services in the application), which is very similar to the example in the Nest docs: https://docs.nestjs.com/recipes/prisma#use-prisma-client-in-your-nestjs-services. I just get an infinite loading spinner when I try to access any of the trpc endpoints. It seems to work when I use a service in tRPC that doesn't have any injected dependencies.

Does anyone have any ideas why this isn't resolving? Is there any more information I can provide to help debug this? Would love to be able to use this properly!

EDIT: Tried nestjs-prisma too and this exhibits the same behavior. NodeJS ran out of memory after hitting the tRPC endpoint.

@medv
Copy link

medv commented Jan 27, 2024

You might need to provide a reproduction, my own PrismaModule as well as a nestjs-prisma module work without this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants