We have been using Kotlin for web-development for 2,5 years.
We use Gradle for handling Kotlin build and dependencies. The generated Java-Script is then handled by Webpack, and dependencies in the java-script world is handled by NPM. (We have tasks that chain all this perfectly.)
This works nicely because our NPM and Webpack usage is very complicated, and we don’t want to inhibit it in any way by using a plugin/wrapper of any sort. (Even if in theory there were no downside we would not be migrating any time soon.)
With Kotlin 1.4 it seems JetBrains assume that everybody wants to use NPM and Webpack and that they want to use it through their plugin/wrapper. (I hope I’m wrong.)
When i run the Gradle task ‘mainClasses’ then the unnecessary ‘kotlinNpmInstall’ is part of the chain spewing out NPM-package warnings that confuse people (we have a big build chain that includes ‘mainClasses’ before Webpack is run which gives us our real NPM-package warnings).
Is it possible with the Kotlin Gradle-plugin for Kotlin 1.4 to do a proper build for development and production without any NPM and Webpack being involved?
If not then I feel this is something that should be changed.