Actually, the example is based on kotlin 1.2.0.. And also I found kotlin-frontend-plugin that has kotlin-plugin 1.1.61 as a dependency. Seems everything is quite old. Is there some newer approach to simplify the configuration of my js modules? To hide dependency management and node installation? Kotlin-frontend-plugin seems to be the thing, but too outdated.

kotlin-frontend-plugin should be compatible with recent kotlin versions. It should also support handle copying the dependencies without relying on the

copyDependenciesKotlinJs

task. cc @cy

So kotlin-frontend-plugin is recommended to use? Currently I have two modules -- client and server. Client has node plugin and one task that runs npmInstall and webpack. Also it has java plugin for a small cheat: I mark all generated client assets as java sources, so they are automatically go to the classpath of server and final application can just serve it. Now I'd like to introduce slowly some kotlin code to a client side. So I need a transparent dependency management between "pure-js" and "kotlin-to-js" subprojects. Will kotlin-frontend-plugin do it for me? Can I avoid those manual "populateNodeModules"?

AFAIK it should handle copying the dependencies (aka populateNodeModules) and configuring webpack for you.