Prisma•17mo ago•

1 reply

Using Prisma Client (and libquery engine) on AWS SAM without Layers

Hi,
I am trying to get the Prisma client libquery engine to work directly inside the Lambda. I have one root

package.json

package.json

where I install prisma deps, and I am trying to import the engine with

import x from '../../node_modules/.prisma/.../.so.node

import x from '../../node_modules/.prisma/.../.so.node

, but that was giving me issues unable to resolve the module or find type declarations. Then I tried to use

tsconfig.json

tsconfig.json

to set up some paths for it to find the engine file, but no success. That is, whenever I would run

sam build

sam build

I would get the

schema.prisma

schema.prisma

in the build folder but not the

libquery...so.node

libquery...so.node

. I eventually stumbled across the idea to change the output folder (

/generated/client

/generated/client

) to the same local folder (i.e.

src/common/prisma

src/common/prisma

) where I have my

schema.prisma

schema.prisma

and now I get the libquery engine as part of the sam build. The issue now is Im getting errors with Dynamic require of "fs" not supported as I have set up my project to use SAM's built-in transpiler using ESM format.

I'm not sure where to go to get this setup working. Is it even possible to use Prisma directly with Lambdas and with Layers, or should I be very strongly considering using a Layer to get this working?

Prisma•17mo ago•

1 reply

threadsnips

Using Prisma Client (and libquery engine) on AWS SAM without Layers

Hi,
I am trying to get the Prisma client libquery engine to work directly inside the Lambda. I have one root

package.json

package.json

where I install prisma deps, and I am trying to import the engine with

import x from '../../node_modules/.prisma/.../.so.node

import x from '../../node_modules/.prisma/.../.so.node

, but that was giving me issues unable to resolve the module or find type declarations. Then I tried to use

tsconfig.json

tsconfig.json

to set up some paths for it to find the engine file, but no success. That is, whenever I would run

sam build

sam build

I would get the

schema.prisma

schema.prisma

in the build folder but not the

libquery...so.node

libquery...so.node

. I eventually stumbled across the idea to change the output folder (

/generated/client

/generated/client

) to the same local folder (i.e.

src/common/prisma

src/common/prisma

) where I have my

schema.prisma

schema.prisma

Using Prisma Client (and libquery engine) on AWS SAM without Layers

Similar Threads

Using Prisma Client (and libquery engine) on AWS SAM without Layers

Similar Threads

Similar Threads

Similar Threads