Hmm, that’s disappointing that Kotlin/JS libraries aren’t forward-compatible. I haven’t upgraded any of my projects to 1.8 yet, and didn’t notice this issue yet.
I am currently working on a major release, and was planning the update to Kotlin 1.8.0 to also go in Ballast 3.0.0. I was also considering doing these 3.0 breaking changes still on Kotlin 1.7 to maximize backward compatibility and ease transition, then follow it up quickly with a bump to Kotlin 1.8. I don’t have an estimate yet for when 3.0.0 will be ready, though.
Regardless, I’ll cut a special release soon to compile the current 2.3.0 version against Kotlin 1.8.0, and figure out a permanent strategy for Ballast 3.0.0 and Kotlin 1.8 later.