https://kotlinlang.org logo
#kotest-contributors
Title
# kotest-contributors
o

Oliver.O

12/02/2023, 11:08 PM
Any idea what could have introduced this (present on current master)?
Copy code
> 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
e

Emil Kantis

12/02/2023, 11:14 PM
will have a look
serializer()
is an extension function added by kotlinx serialization compiler plugin. Is that not being applied properly to JS now for some reason?
o

Oliver.O

12/02/2023, 11:18 PM
Looks like that but why?
e

Emil Kantis

12/02/2023, 11:18 PM
can you try upgrading kotlinx-serialization = "1.3.3" to 1.6.2 or 1.5.0?
o

Oliver.O

12/02/2023, 11:20 PM
I’ll try tomorrow. Just wondering as this was present on the commit tagged for the 5.8.0 release.
e

Emil Kantis

12/02/2023, 11:21 PM
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?
compileKotlinJs is passing for me on master 😕
o

Oliver.O

12/02/2023, 11:33 PM
I’ve run clean, followed by allTests.
e

Emil Kantis

12/02/2023, 11:36 PM
i did clean as well.. the actual target shouldnt really matter but I'll try allTests just in case.
o

Oliver.O

12/03/2023, 12:23 AM
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.
e

Emil Kantis

12/03/2023, 8:46 AM
plausible explanation, yeah 🙂
o

Oliver.O

12/03/2023, 2:54 PM
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!
👍 1