Few tips

[konsoletyper]

Hi! Great project. Though after digging a bit into code I found few places where it can be improved:

1. You don't need any customized runtime. I guess you patch it in order to workaround Safari bug? If the only method that does not work on Safari is WebAssembly.Module.imports, then you can simply switch off auto importing by passing noAutoImports: true to load options. You don't import any ES modules, so you don't need this. Anyway, this can be workarounded better, for example, by adding custom section with ES descriptors. I could do it a bit later.
2. You pass sources which are async. I would not do so for performance reasons. Better fetch entire class file, await for it and then feed to the decompiler. It's also worth removing any async code from the decompiler itself. If you want, I could look a bit deeper into it and give few tips. Any async code influences performance not only locally, but globally across entire code base.

[zlataovce]

hello and thank you for the kind words

I'm going to try noAutoImports, as I'd love to get rid of the custom runtime, thank you for the recommendation

async is frankly a necessary evil for now, as I don't actually know the class files the decompiler will need, it often needs a part of the JDK or other dependent classes to complete its internal class hierarchy - I can't simply load everything into memory either, as the project is built for viewing huge JARs and everything is read+decompressed only on demand to not strain the memory budget
I could try to build a deeper integration with the decompiler and ask it about the necessary classes before decompiling, but it's not a priority for me, since the performance is comparable with running it on a real JVM

[konsoletyper]

Another question. Don't you mind if I add a link to your project to TeaVM gallery?

[zlataovce]

not at all, sharing the project is always welcome, thank you ❤️