hello all, I am getting this error when deploying ...
# orm-helpd
David Turton
04/30/2020, 3:26 PMhello all, I am getting this error when deploying to AWS Lambda. Locally I can invoke the function deployed in AWS it will fail.
r
Ryan
04/30/2020, 3:32 PMHey David đź‘‹ can you send your Cloudwatch logs so that we can get more insight in this issue?
d
David Turton
04/30/2020, 3:33 PMsure thing.. Let me grab them
David Turton
04/30/2020, 3:34 PM{"errorType": "Error","errorMessage": "@prisma/client did not initialize yet. Please run \"prisma generate\" and try to import it again.\nIn case this error is unexpected for you, please report it in <https://github.com/prisma/prisma-client-js/issues/390>.","stack": ["Error: @prisma/client did not initialize yet. Please run \"prisma generate\" and try to import it again.","In case this error is unexpected for you, please report it in <https://github.com/prisma/prisma-client-js/issues/390>."," at new PrismaClient (/var/task/node_modules/.prisma/client/index.js:3:11)"," at Module.call (/var/task/_lumigo/webpack:/src/tasks/shouldOrderProcess.ts:3:16)"," at t (/var/task/_lumigo/webpack:/webpack/bootstrap:19:22)"," at Object.call (/var/task/_lumigo/webpack:/_lumigo/shouldOrderProcess.js:5:17)"," at __webpack_require__ (/var/task/_lumigo/webpack:/webpack/bootstrap:19:22)"," at /var/task/_lumigo/webpack:/webpack/bootstrap:83:10"," at Object.<anonymous> (/var/task/_lumigo/shouldOrderProcess.js:1:966)"," at Module._compile (internal/modules/cjs/loader.js:1158:30)"," at Object.Module._extensions..js (internal/modules/cjs/loader.js:1178:10)"," at Module.load (internal/modules/cjs/loader.js:1002:32)"]}David Turton
04/30/2020, 3:34 PMI only see this error
David Turton
04/30/2020, 3:36 PMnot sure what else you may need
David Turton
04/30/2020, 4:13 PM@Ryan Any ideas?
r
Ryan
05/01/2020, 6:49 AMCould you check if it's connecting properly to your remote DB locally
Also check the following points as well
•
prisma generateserverless deployschema.prisma Copy code
generator client {
provider = "prisma-client-js"
binaryTargets = ["native", "rhel-openssl-1.0.x"]
}d
David Turton
05/01/2020, 12:40 PMHi Ryan, it looks like the problem is using serverless-webpack
David Turton
05/01/2020, 12:40 PMthe .prisma folder in node_modules is missing files
r
Ryan
05/01/2020, 12:48 PMCould you try this setting in serverless-webpack?
Excluding bundling of that should make it work
d
David Turton
05/01/2020, 12:50 PMYou mean adding “includeModules: true”
r
Ryan
05/01/2020, 12:52 PMand configuring the
webpack.config.jsd
David Turton
05/01/2020, 12:55 PMI actually have that config in the webpack and serverless.yml
David Turton
05/01/2020, 12:55 PMI have been trying to hours to figure this out
David Turton
05/01/2020, 12:58 PMcan we do a quick screen share?
r
Ryan
05/01/2020, 2:07 PMsure
d
David Turton
05/01/2020, 2:08 PMcan you join here https://us02web.zoom.us/j/7862133978
David Turton
05/01/2020, 2:11 PMlet me know when you are ready
David Turton
05/01/2020, 2:18 PM@Ryan did you mean to meet now?
r
Ryan
05/01/2020, 2:18 PMI have joined
d
David Turton
05/01/2020, 3:11 PMHello Ryan.. here is the repo https://github.com/dturton/serverless-webpack-prisma
l
Luke
05/10/2020, 10:49 PMI'm having this same issue deploying to vercel (zeit now). @David Turton did you solve this ?
d
David Turton
05/10/2020, 10:57 PMhi @Luke this solved it for me: https://github.com/prisma/prisma/issues/2303 but I decided not to use prisma for now..
David Turton
05/10/2020, 10:57 PMbasically it needs to have a postinstall script in packages.json to run prisma generate
r
Ryan
05/11/2020, 7:57 AMHey @David Turton đź‘‹
this repo would be helpful for you in the future.
11 Views