Is there a reason that the webpack tasks are by de...

# javascript

[steamstreet]

Is there a reason that the webpack tasks are by default always enabled? When I’m writing a multiplatform library that includes Javascript (or even just a JS lib), there doesn’t seem to be a really good reason to run webpack. Am I missing something? Could this at least be linked to the explicitApi() setting? It’s become somewhat tiresome to always be putting tasks["jsBrowserWebpack"].enabled = false in my build files for JS libraries.

[steamstreet]

This is probably also true of the DCE task, which I don’t think should be run? Perhaps there are good reasons, but I’m not aware of them.

[turansky]

Since 1.4 it will be called only if you call
binaries.executable()

[steamstreet]

That does not appear to be the case with the multiplatform plugin.

[steamstreet]

even without binaries.executable(), jsBrowserProductionWebpack is invoked when I execute the assemble task.

[steamstreet]

and the browser block does not allow one to disable webpack, just configure it.

[andylamax]

I think you should open a ticket on YT

[turansky]

@steamstreet If you use Kotlin 1.4 and legacy mode, than add following

kotlin.js.generate.executable.default=false

in gradle.properties

[turansky]

With this option webpack will be called only with binaries.executable()

[altavir]

In ir mode webpack eists only for binaties

[steamstreet]

great! thank you!