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
Prisma Client (Binary): upgrade to undici@4 #7539
Comments
Also related #6925 |
We should try to upgrade to the latest version, |
Obsolete as it is out now: #7705 |
Note from undici v4 package.json the Node.js supported version is Prisma supported version is Node.js v12 releases https://nodejs.org/en/download/releases/ So it looks like we would need to bump Prisma to the same version? |
Our tests should catch that 👍 |
I couldn't find why 2.18 was required maybe it's a choice and not an hard requirement. Found this interesting bit for info
|
To investigate #7705 (comment) |
Is there any update on this issue? Running into similar deployment issues in AWS Amplify (similar to this #8503) |
PR up: #7931 |
Currently running into memory issues due to WASM being instatiated many times. Waiting for #8831. |
If #8831 turns out to be fine, we still need to investigate the impact of the new files in the package and decide if we can/want/need to bundle them somehow instead. We also found a few weird bits where |
New PR is at #8842, tests are passing now. |
We have a long standing bug for the combination of Undici and Webpack: #6899 + #6564 Unfortunately there is no full workaround.
Undici@4 will most probably fix this, and we should upgrade to that as soon as possible.
To make sure this is possible, we should also try to upgrade to one of the recent release candidates as well and help them get that over the line, and make sure we have the necessary adaptations ready when the stable version is released.The text was updated successfully, but these errors were encountered: