New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
npm install of Prisma CLI fails on preinstall with no logs when Node.js version is lower than minimum #20260
Comments
@Dominguezd01 I believe your problem here is that you are trying to install Prisma 5 CLI which requires Node.js v16.13 at minimum. And in your screenshot, it says your deployment is using v14.17 Could you upgrade your Node.js version? (We recommend to upgrade to v18 when possible). |
Why this happened? I think we can keep this issue to see how we can make it better. |
Are we missing the actual error message output there @Jolg42 or is this a Render problem? |
The "box" seems to be truncated here, but a quick local test show the same 🙈
|
@Jolg42 created a PR at #20263 Sorry that this is so hidden in Prisma 5 @Dominguezd01. It will be fixed in 5.1.0. Can you upgrade your Node version on Render to Node 16? |
Okay, changing node version to 16.20.1 and 18.16.1 works fine, my bad, I didnt double check the Node version. |
Aug 27 01:46:17 AM ==> It looks like we don't have access to your repo, but we'll try to clone it anyway. i got this error while deploying on render and my node version is 20 |
@okechukwu26 I think the code is right here as you can see in your logs |
Thanks....I have been able to resolve it render was automatically using node 14.3 to build the app so I have to tell it to using the latest version while building |
kindly help on how you did it |
I created an environment variable on called render node version and input in the value the the node version type 20.5 |
To update Render's Node Version, go into your project and create a new environment variable. NODE_VERSION: *your desired node version. More details on Render's settings can be found here: https://render.com/docs/node-version |
Originally posted by @Dominguezd01 in #20193 (comment)
The text was updated successfully, but these errors were encountered: