-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Usage of deprecated punycode module #21644
Comments
Note: I think this is currently blocked as we depend on an old version of |
I randomly found out this PR in Yarn where they bundle |
@Jolg42 yeah, it's also to remedy this issue, however the warning does come from Prisma itself here. |
@RDIL Sorry for the confusion, I found it interesting that Yarn solved this issue like this and indeed that does not solve the problem with Prisma. |
There are similar issues in projects that are still using node-fetch v2 This issue describes the problem I found serverless/serverless#12237
|
You can now try the dev version This will be part of the next official release planned for May 14th. |
Just tested |
Bug description
Hi Prisma team,
It seems somewhere in the engines package, the
punycode
package is used, which was recently runtime-deprecated by the Node.js team.Just opening this to put it on the radar.
How to reproduce
Here's where it was detected:
Expected behavior
The error should not be raised.
Prisma information
Prisma schema is not relevant to the issue.
Environment & setup
yarn dlx envinfo
:Prisma Version
The text was updated successfully, but these errors were encountered: