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
open handles with body-parser#1.20.0 #772
Comments
I am also seeing this.
express = 4.17.3 |
I'm having the same lucamartini's problem, and I'm using express 4.17.3, supertest 6.2.2 and body-parser version = 1.20.0. It seems to started recently, as I'm upgrading my projects, because I had the tests for quite a while, and just recently this problems appeared. When I put a timeout in afterAll method, depending on how long I wait, the problem do not happen. |
@lucamartini and @ricardomat are you using a fake database? I had the same problem and then by doing my research, I have found a beautiful solution which is using the NPM package mongodb-memory-server This should be installed as development dependency!!! |
Hello! As a plus comment, this also happens when using morgan |
Having the same problem |
It seems |
I ran into this as well, don't feel great running beta in prod though. Other ideas? :D Is this a known issue on the body-parser side? |
Having the same problem |
Having the same problem. Can confirm that |
Have the same problem as well, but upgrading |
@saqib-ahmed fixed the problem in my case.. |
Can confirm that this also worked on my setup.
I had to use
Just want to mention that using
will result to these errors.
|
|
I have the same issue
|
upgrade to jest@29.2.1 and ts-jest@29.0.3 resolved it for me. |
You do not need to use TL;DR we're all barking up the wrong tree here. This is a problem that Express' maintainers (who are not very active) need to solve. |
Hallo,
jest test run does not exit and instead prints this error
We have found this happens only for the routes where we use the express
body-parser
middleware.express version = 4.17.3
body-parser version = 1.20.0
The text was updated successfully, but these errors were encountered: