form.parse's Promise never resolves in tests about formidable

[Angryman18]

If you have body-parser package just remove or comment it. Hope it will resolve

[maxlath]

I migrated an Express app using body-parser and formidable v1.2.6 to formidable v3.5.1, and bumped into that issue. I was able to keep body-parser on, by calling await form.parse(req) from a middleware running before body-parser. See commit inventaire/inventaire@3b3c556. Hope that that can help others

[allthesignals]

This is happening to me too, not even in test environment. 3.5.1. The promise just never resolves

[GrosSacASac]

(reminder for me: try req.on('data') earlier)

are you testing formidable, or a project using formidable ?

[george-i]

If you have body-parser package just remove or comment it. Hope it will resolve

I tried commenting out busboy and busboy-body-parser and the parsing completed successfully.

[egargale]

If you have body-parser package just remove or comment it. Hope it will resolve

I had been banging my head against the wall for two days.... Thank you

[tunnckoCore]

@george-i @egargale yeah, that's a known thing that things don't work well if someone else is interacting with the body too.

Formidable can be simplified A LOT, but the problem to move directly the newest stuff is that people are relying on old versions, there's still people on v1.. I had the code ready for over a year, a dream of mine for v4-5, but yeah ;d

[Ray0907]

I encounter the same issue. Is there any solution available to resolve the problem?