Michael Spengler

@theweinzierl: It would be great if your enhancement could be added to this module.

@yoshixmk If I'm informed properly the guys from nest.land are working on something that they call the module analyzer - also having some dynamic + static checks on the radar...

cool :) hackathon related updates will follow during the next days. To connect some more dots I want to mention this one also as we can probably combine some cool...

Might be interesting: https://github.com/denosaurs/sauron

I also replaced next() by await next() --> this works fine in my case. after this the controller content can be something like: ``` getChatResponse: async ({ request, response }:...

I can imagine that this makes things much more complicated. From my experience as a "Product Owner" in other contexts I can recommend to wait with the implementation of this...

@nebrelbug thanks for the additional background infos. I can understand that. One more question from my side: Would it also be cool, if you could revoke your current API Key...

:) I understand - ... it's good to have some options on the radar now and I'm pretty sure Tate & friends will choose wisely when the time is right...

This seems to be a crisp and pleasant summary on benefits of vue3 - esp. of the composition API: https://www.youtube.com/watch?v=6HUjDKVn0e0

@buttercubz: I just came across this issue again. I could imagine that the --compat mode could be helpful in this context: https://deno.land/[email protected]/npm_nodejs/compatibility_mode I'm not yet familiar enough with details of...