I just sent you a response on the helpdesk chain as well, and I’m pasting it here for reference.
Also, my site is dev.florianworks.com
My response to the helpdesk chain ( with some additions ):
We’re deploying a RedwoodJS project on netlify, to deploy that, you can follow steps in their tutorial in Chapter 1 to set up a project and then Chapter 4 for deployment to Netlify.
The deployments we were testing were PR deployments (deploy previews) that get built when a Pull Request in Github is created or updated.
What we were seeing yesterday was that even with deploy configuration pinned to Node 18, the runtime node version was 20, and that was causing issues with Prisma. To detect this, go to the function logs and see the node version that gets printed in there for the
Below is a copy from the logs as of today morning, where node v20.13 is getting used.
Dec 2, 07:40:32 AM: INIT_START Runtime Version: nodejs:20.v13 Runtime Version ARN: arn:aws:lambda:us-west-2::runtime:0593533e3a90a967b5685780855b7a89f7ba80b7d910603abf59369c6c4c7331
And this leads to the error posted above by me and others, which is not fixed when u add to the binary targets as the error message suggests below.
Prisma Client could not locate the Query Engine for runtime \"rhel-openssl-3.0.x\".\n\nThis happened because Prisma Client was generated for \"debian-openssl-1.1.x\", but the actual deployment required \"rhel-openssl-3.0.x\".\nAdd \"rhel-openssl-3.0.x\" to `binaryTargets` in the \"schema.prisma\" file and run `prisma generate` after saving it
I reached out to the redwood team and they were able to reproduce the issue, following which they asked me to test by changing the .nvmrc file from
While this worked for deployments in us-east-1, it wasn’t working in us-west-2.
So tl;dr: It looks like Netlify is using Node 20 for the function lambdas when configuration is pinned to v18, and that the fix to change the .nvmrc file is working in some regions and not working in other regions.
Additionally: the .nvmrc file has been unchanged (for my project at least) since inception almost a year ago, and that something has changed on Netlify’s end starting sometime on 12/1 to take v20 instead of v18 with this setup and configuration, because my PRs were deploying fine until late 11/30 PST.
However, as of today morning, v18 seems sticky in both these regions, though I will need to confirm after deploying some more PRs and I haven’t tested more regions.
I hope this is enough information for you to debug / reproduce.