Any idea what could have introduced this (present ...

# kotest-contributors

[Oliver.O]

Any idea what could have introduced this (present on current master)?

> Task :kotest-assertions:kotest-assertions-json:compileKotlinJs FAILED
e: file:///home/oliver/Repositories/open-source/Kotlin/kotest/kotest-assertions/kotest-assertions-json/src/commonMain/kotlin/io/kotest/assertions/json/schema/parse.kt:54:44 Unresolved reference: serializer
e: file:///home/oliver/Repositories/open-source/Kotlin/kotest/kotest-assertions/kotest-assertions-json/src/commonMain/kotlin/io/kotest/assertions/json/schema/parse.kt:58:46 Unresolved reference: serializer
e: file:///home/oliver/Repositories/open-source/Kotlin/kotest/kotest-assertions/kotest-assertions-json/src/commonMain/kotlin/io/kotest/assertions/json/schema/parse.kt:59:36 Unresolved reference: serializer
e: file:///home/oliver/Repositories/open-source/Kotlin/kotest/kotest-assertions/kotest-assertions-json/src/commonMain/kotlin/io/kotest/assertions/json/specs.kt:34:41 Unresolved reference: serializer

[Emil Kantis]

will have a look

[Emil Kantis]

serializer() is an extension function added by kotlinx serialization compiler plugin. Is that not being applied properly to JS now for some reason?

[Oliver.O]

Looks like that but why?

[Emil Kantis]

can you try upgrading kotlinx-serialization = "1.3.3" to 1.6.2 or 1.5.0?

[Oliver.O]

I’ll try tomorrow. Just wondering as this was present on the commit tagged for the 5.8.0 release.

[Emil Kantis]

no clue tbh.. would be good to see when it started being an issue, but seems jsTests have been passing recently? perhaps tests havent been run due to caching?

[Emil Kantis]

compileKotlinJs is passing for me on master 😕

[Oliver.O]

I’ve run clean, followed by allTests.

[Emil Kantis]

i did clean as well.. the actual target shouldnt really matter but I'll try allTests just in case.

[Oliver.O]

One more idea: I have been switching between lots of Kotlin versions recently. Maybe there is some extra configuration left over and still tied to 1.9.x. I’ll check later.

[Emil Kantis]

plausible explanation, yeah 🙂

[Oliver.O]

That was it! I had used the wrong version of a private plugin which provides extra yarn.lock version checks (not really necessary anymore). This pulled in the Kotlin Multiplatform plugin version 1.9.10. Thanks Emil for helping to isolate the problem!