Skip to content
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

[DEP0131] DeprecationWarning: The legacy HTTP parser is deprecated in Node 12.22.0 #702

Closed
timsuchanek opened this issue Apr 8, 2021 · 5 comments
Labels
bug Something isn't working

Comments

@timsuchanek
Copy link
Contributor

Bug Description

When running undici@3.3.3 with Node 12.22.0, we get this warning:

(node:3380211) [DEP0131] DeprecationWarning: The legacy HTTP parser is deprecated.
    at internalBinding (internal/bootstrap/loaders.js:136:34)
    at process.binding (internal/bootstrap/loaders.js:113:14)
    at Object.<anonymous> (/root/code/prisma/src/node_modules/.pnpm/undici@3.3.3/node_modules/undici/lib/node/http-parser.js:4:32)
    at Module._compile (internal/modules/cjs/loader.js:999:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1027:10)
    at Module.load (internal/modules/cjs/loader.js:863:32)
    at Function.Module._load (internal/modules/cjs/loader.js:708:14)
    at Module.require (internal/modules/cjs/loader.js:887:19)
    at require (internal/modules/cjs/helpers.js:74:18)
    at Object.<anonymous> (/root/code/prisma/src/node_modules/.pnpm/undici@3.3.3/node_modules/undici/lib/core/client.js:5:20)

Is there anything we can do to disable it?
Thanks!

@timsuchanek timsuchanek added the bug Something isn't working label Apr 8, 2021
@ronag
Copy link
Member

ronag commented Apr 8, 2021

This will be fixed in undici 4. I think we’re a week away from release.

@timsuchanek
Copy link
Contributor Author

👍 That was a fast response! Thanks, that's great to hear!
We now have this issue in all Prisma Client installations with the latest Node 12.
Is there anything we could do in the meantime?

@ronag
Copy link
Member

ronag commented Apr 8, 2021

I might be able to do another v3 release

@ronag
Copy link
Member

ronag commented Apr 8, 2021

Please try 3.3.4

@timsuchanek
Copy link
Contributor Author

That fixes it!
Thanks a lot for taking care of this so quickly.
We'll do our next stable release next week Tuesday, so then we can directly roll out this fix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants