@peekandpoke I'll run that through the benchmark when I find the time, tnx for the suggestion. Question: do you also target the JVM, or only JS? We only target JVM, and I cannot imagine that you use kotlinx.html for everything without any "long compile time" issues. If you want to remove the inline for your project, it's quite easy to use a hacked version of a library in your project using localMaven (or simply copying a JAR in a project folder and referring to it in your Gradle file).

We use it for JVM and JS. We do not have a lot of JVM templates, so maybe I just do not recognize the impact. I also tried to use "hacked" version once but I had to give up, since we e.g. use Ktor which depends on kotlinx/html and I ended up with lots of conflicting classes ... maybe I just did not do it the right way.

There are some ways to get Gradle to use another version for a transient dependency. There's the

exclude

and

contraints

directives. Also it's not KTor itself that depends on kotx.html, it's

ktor-server-html-builder

(you could also hack that use your hacked dependency, if all else fails).