Running into another situation today where my kotl...

# javascript

[Rob Murdock]

Running into another situation today where my kotlin js build is failing due to a change in an indirect javascript dependency (I think… old green builds now don’t work 😞 ).

Has anybody got any lock-file-style solutions for this sort of thing? or any ideas?

[rnett]

https://docs.gradle.org/current/userguide/dependency_locking.html Not sure how it works with npm dependencies though. If it doesn't it would be worth raising an issue to JB.

[Rob Murdock]

worth a shot! I forgot that even existed. Thanks

[Rob Murdock]

initial testing… not promising 😬

[Rob Murdock]

it really seems to struggle with the multiplatform variants specifically. get a lot of

- Variant 'watchosX64ApiElements-published' capability org.jetbrains.kotlinx:kotlinx-coroutines-core:1.5.1:
              - Incompatible because this component declares attribute 'org.jetbrains.kotlin.platform.type' with value 'native' and the consumer needed attribute 'org.jetbrains.kotlin.platform.type' with value 'js'
              - Other compatible attributes:
                  - Doesn't say anything about org.jetbrains.kotlin.js.compiler (required 'ir')
                  - Doesn't say anything about org.jetbrains.kotlin.localToProject (required 'public')

kinda things

[Rob Murdock]

things that the regular build knows how to handle just fine, but this particular resolution logic doesn’t

[Rob Murdock]

and that’s long before it gets to any of the npm dependencies