Micael Levi L. Cavalcante

btw you forgot to call `app.use(bodyParser.json())` in the Express version. But yeah, it does triggers the 'close' event. --- I just tested your repro with v8 and v9. None of...

after investigating that a bit, I found this weird(?) behavior: https://github.com/nestjs/nest/blob/8e3af065bb9abbecc91b4e6068c8e205ef79d165/packages/core/router/router-execution-context.ts#L139-L151 adding `const onClose = () => console.log('----------'); req.on('close', onClose)` right before L149, it will make that `onClose` be called....

I just tested something: if we remove the `await` from inside `handler`'s returns by making that `fnApplyPipes` sync, the 'close' event got emitted in controller's method. So I guess that...

that's due to `reflect-metadata` being upgraded to 0.2 while others packages from nestjs are using 0.1 A quick solution is to pin the version of `typeorm` to v0.3.19 

@jmcdo29 🏓

Please provide a minimum reproduction repository. You can start one by running `npm init nest` in your terminal ## [why reproductions are required](https://antfu.me/posts/why-reproductions-are-required)

As a step on the contribution road, what do you think of using github issues forms like we have on nestjs repositories? I can open a PR to add them,...