Is anyone familiar with trying to use prisma bindings in a l Prisma #orm-help

Join Slack

Is anyone familiar with trying to use prisma-bindi...

# orm-help

zak.singh

07/28/2018, 10:41 PM

Is anyone familiar with trying to use prisma-bindings in a lambda function?

divyendu

07/29/2018, 3:54 AM

Yes, please let me know if you have a more specific question?

zak.singh

07/29/2018, 3:58 AM

Hi! I've been stuck all day on this issue. I've copied over my generated prisma.ts file to my serverless directory, and instantiated prisma with it normally. However, whenever I try to invoke the lambda, I get an error saying "Cannot find module 'graphql'"

zak.singh

07/29/2018, 4:00 AM

Of course graphql is listed as a direct dependency and I've confirmed its being included in the package that serverless is sending to lambda

divyendu

07/29/2018, 4:01 AM

Can you share your code as a reproduction and create an issue?

zak.singh

07/29/2018, 4:07 AM

I doubt this is an issue with Prisma... To try to clarify my situation a little better: I've copied my generated

prisma.ts

file from my graphql server (which contains my prisma directory as in the examples) into my separate serverless folder. I did this so that I could call the Prisma constructor exposed by prisma.ts. I'm under the impression that

prisma.ts

is only used in the typescript compilation stage and should have no effect on the lambda's execution once it is built and deployed. Nonetheless I'm getting a

cannot find module: graphql

error, while my code never directly imports graphql. Nevertheless I have graphql installed as a dependency, so it shouldnt be an issue in the first place

zak.singh

07/29/2018, 4:10 AM

If I remove the

import { Prisma } from "./prisma"

the error goes away. I tried using the javascript version of the prisma constructor by passing in the generated schema file as a string directly, but it resulted in the same error

zak.singh

07/29/2018, 4:11 AM

Do you have a sample of how you are importing your generated prisma files into your lambda?

zak.singh

07/29/2018, 4:51 AM

I fixed this by rimrafing my node_modules, cleaning my npm cache, and adding

graphql

not only as a dependency but as a resolution

divyendu

07/29/2018, 9:43 AM

Interesting! I would still recommend you to create an issue to help others who run into it and for us to investigate 👍

3 Views

Open in Slack

Previous Next