By default gradle kotlin-dce-js plugins runs on bo...

# javascript

[gaetan]

By default gradle kotlin-dce-js plugins runs on both main and test code. Is there a reason to include tests code?

[konsoletyper]

No, there's no reason

[konsoletyper]

You can work-around this by disabling corresponding task

[gaetan]

By default we could have just dce on main code. The build would be faster.

[konsoletyper]

Why do you need faster builds?

[gaetan]

Well, I’m always trying to have fast builds and to do just I need to 😉. If the dev can save few seconds during it’s workflow… why not.

[konsoletyper]

Why do you need DCE at dev's environment? You can run it only for building production

[gaetan]

Yes but sometimes you need to run you prod build . As prod don’t need to have dce on it, I prefer not to have it.

[konsoletyper]

DCE takes only few seconds. I don't think it's much for buidling prod. Production builds often take many minutes to build, and may be several hours to pass all tests.

[konsoletyper]

Anyway, simply don't run DCE. What's the problem?

[gaetan]

It’s okay, I just add runDceTestKotlinJs.enabled = false

[konsoletyper]

BTW, here I provided example of setup for dev environment: https://youtrack.jetbrains.com/issue/KT-20210

[gaetan]

It’s more on tuning than changing features

[ilya.gorbunov]

@konsoletyper The problem is that DCE is applied both to the main and test sourcesets and for test it doesn't make sense.