jlengstorf
11/18/2021, 7:57 PMLisa-Marie Namphy
11/18/2021, 8:02 PMLisa-Marie Namphy
11/18/2021, 8:05 PMM T
11/18/2021, 8:06 PMAydrian Howard
11/18/2021, 8:08 PMAydrian Howard
11/18/2021, 8:10 PMVladi Stevanovic
11/18/2021, 8:10 PMShameem Fairooz
11/18/2021, 8:12 PMAydrian Howard
11/18/2021, 8:12 PMLisa-Marie Namphy
11/18/2021, 8:12 PMLisa-Marie Namphy
11/18/2021, 8:13 PMjlengstorf
11/18/2021, 8:13 PMDaniel Norman
11/18/2021, 8:16 PMSyed Umair Ali
11/18/2021, 8:27 PMAnderson da Silva
11/18/2021, 8:30 PMVladi Stevanovic
11/18/2021, 8:44 PMshane
11/18/2021, 8:52 PMMoneeb
11/19/2021, 12:54 PMPrisma
team! 😛risma-rainbow:Ignacio Ampuero
11/19/2021, 5:47 PMmigrate deploy/generate
prior to starting the app. But it seems to get far more complicated with Planetscale's opinionated idea on database deployments. I've read the docs here, but it seems so unnecessarily(?) complex to implement (creating/deleting branches, connecting to multiple branches, opening/completing deploy requests..). Is this a case of the tooling needing to improve or just how these two technologies need to integrate with each other? Or are my questions actually planetscale questions and how deploys generally would work in a CI/CD environment, regardless of Prisma?Vilke
12/07/2021, 12:34 PMRavi Kumar
04/28/2022, 8:28 AMJohan Rydberg
02/28/2022, 8:03 PMimira
04/01/2022, 2:35 PMHimanshu Sahay
04/22/2022, 1:13 PMENOENT: no such file or directory, open '/var/task/src/functions/<function-name>/schema.prisma'
Details below, please let me know if the right channel for this question or if I should ask in another. Thank you in advance
We've tried a number of solutions suggested in the Issues and Discussion section of the Prisma github project but to do no avail. It appears that a number of others users there are facing the same issue and have not been able to get past it. We believe the issue is that the Prisma Client at runtime depends on schema.prisma
and constructs a url to it, but the schema.prisma is not packaged along with the lambda function zip file so Lambda is not able to. We've tried suggestions in some of the issues including manually creating the expected folders in the packaged zip after compilation in a postBuild
command and copying the schema.prisma
into it.
Some issues we looked at for guidance -
https://github.com/prisma/prisma/issues/10200
https://github.com/prisma/prisma/discussions/10278
https://github.com/prisma/prisma/issues/9435
https://github.com/prisma/prisma/issues/9520Himanshu Sahay
04/27/2022, 4:03 PMsls invoke local --function <name>
the packaging fails with the following error
Error: @prisma/client did not initialize yet. Please run "prisma generate" and try to import it again.
I believe this is because the following part of my serverless.yml
fails to run in this case
custom:
webpack:
includeModules: true
packagerOptions:
scripts:
- prisma generate
Does anyone have pointers on how I can identify the issue here?Marcos Iglesias
07/10/2022, 12:52 PMHill
07/19/2022, 7:07 AMAdônis Uessler
08/07/2022, 9:39 PMMischa
08/17/2022, 4:36 PMVladi Stevanovic
09/15/2022, 7:18 PM