Hey, yes we do have a plan to do that. We haven't published the Kotlin/JS plugin to the Gradle plugin portal because we actually want to change the plugin's API (use our own model of compilations and source sets, unified with MPP, instead of the model created by the Java plugin) and publish the plugin to the plugin portal as a single step, so that no backward-incompatible change is made to the published plugin. That plugin with the new API is going to eventually replace the
kotlin2js
plugin, but the latter will stay for a while for smooth migration. Expect this change in one of the upcoming tooling updates.