Constantin

To work around this issue I wrote myself this thing: ``` class ThreadSavingHandler( private val nonThreadSaveHandler: () -> ChannelDuplexHandler, ) : ChannelDuplexHandler() { private var handler: ChannelDuplexHandler = nonThreadSaveHandler() private...

My search in finding anything that can be just 'plugged in' for Webmachine the Rack adapter was not successful, so I guess there is nothing but writing out every json...

ah ok. I was also checking if we could use rust + wasm to not have a binary at all. But I think that's a big topic. is the compilation...

Wasm could export the matcher and plugin part. This would have the benefit that (in theory) all languages could use it and just the http part would need to be...

but that still means, that we have to have a post install hook

I can't figure out how to get node-gyp to cross-compile the binaries 😖. If it's not possible I could create a github action and run it for every major architecture...

is there a difference between alpine and 'standard' linux? esbuild seems to also not make a difference

Just dropping this here: https://github.com/OAI/OpenAPI-Specification/issues/1368 Might be a feature 'support openapi 3.1'

there is for example an [ubuntu](https://gallery.ecr.aws/ubuntu/ubuntu) on aws, which is really nice. Would be nice to see alpine as well :)

is there any downside of always adding this permission?