-
Notifications
You must be signed in to change notification settings - Fork 65
Prisma and node 12.19.0 #907
Comments
This comment has been minimized.
This comment has been minimized.
Looks like node We will need to report this to node.js I think.
|
Undici issue for this: nodejs/undici#448 |
This comment has been minimized.
This comment has been minimized.
Current workaround until a fix is found and released in next Prisma release is to pin your Node.js version to a previous version of Node (<12.9.0). |
Undici 2.0.7 was released with the fix from this PR nodejs/undici#449 I updated the dependency with prisma/prisma#3884 It's now in Next step: confirm the fix @divyenduz |
Here is an example on how to pin a Node.js dependency for Netlify and Vercel, thanks to @thedavidprice redwoodjs/redwood#1313 (comment)
|
The fix was confirmed with prisma/ecosystem-tests#834 It will be part of the 2.9.0 release tomorrow 🚀 |
Bug description
Prisma (latest dev, 2.8.0, 2.8.1, 2.7.0 versions) with node 12.19.0 results in the following error:
How to reproduce
git clone https://github.com/divyenduz/prisma-client-js-907 p2-node-12
cd p2-node-12
12.19.0
in the environmentDB_URL
toprisma/.env
(ping Divy, if needed)node index.js
http://localhost:3000
), it should failThe error mentioned above should be visible in the logs.
Expected behavior
Prisma and node
12.19.0
should work.The text was updated successfully, but these errors were encountered: