For now quite some time, I am no longer able to bu...

# javascript

[Luc Girardin]

For now quite some time, I am no longer able to build my JavaScript targets using dependency substitutions applied to composite builds (either include or includeBuild). The main benefit was that one could skip the publishToMavenLocal step and therefore boost productivity. This works nicely for other targets, but not for JS. I have tried to get attention by filling an issue and creating a sample project (https://youtrack.jetbrains.com/issue/KT-50064), but alas without much success as Kotlin 1.6.20 still exhibits the same problem. I am therefore wondering if any of you has found a good setup where one doesn’t need to resort to creating artifacts during the development cycles but still eventually be able to publish these artifacts once stable.

[andylamax]

We are not using composite composite builds at all, but we are using gradle subprojects. This works well for us at the moment

[Luc Girardin]

@andylamax Thanks for input. By gradle subprojects, you probably mean using the “include” directive. Did you manage to substitute names of published artifacts with local modules? In other words, how to you manage your local dependencies?

[andylamax]

No, at the moment, since we are actively building, we do not substitute names. we just include out projects as a project dependency.

When done, we intend to clean all project imports and point to the respective coordinates for each subproject which I admit, might be tedious and highly repetitive

[Luc Girardin]

@andylamax This I am also able to do 😉 What I am looking after is to be able to automatically substitute some dependencies (typically using the dependencySubstitution mechanism of Gradle).