Attila Orosz

Yes, but unfortunately the time we can allocate is limited. I’m planning some refactoring and support for latest socket.io in the near future.

@driescroons I have made a config in webstorm to build everything and do an npm link automatically.

I think the clear workaround for this is to return the response object itself. ```typescript @Controller("/test") export default class TestController { @Head() head(@Res() resp:any){ console.log("head"); resp.send(); return resp; } @Get()...

No, the project is not dead. It just needs a little love. I know it was a bit miscommunicated but here's a thread from NoNameProvided: https://github.com/typestack/class-validator/issues/1775 or https://github.com/typestack/typedi/issues/391 @spicemc Would...

@NoNameProvided I believe this has been solved. Package is working as expected. I agree that controllers should maybe register themselves in the DI without the explicit @Service decorator but that's...

@RirUchida the stack property should only be added if your node env is not prod. Could you please check if setting it helps?

@shinelp100 Could you add more context to your question?

Seems like there are no real breaking changes in terms of class-transformer usage (I might be wrong here) so you can just update the package since it is only a...

@lerit this seems like an interesting idea but I’m not sure if this should be the responsibility of this package. Since you are the one creating the response I think...

@TKul6 If you disable the default error handler and implement your own you could destroy your container instance there.