If I use `0.0.0-web-dev-13` then I get following ...

# compose-web

[John O'Reilly]

If I use 0.0.0-web-dev-13 then I get following

This version (1.0.0-beta08) of the Compose Compiler requires Kotlin version 1.5.0 but you appear to be using Kotlin version 1.5.10 which is not known to be compatible.

but if go from Kotlin 1.5.10 back to 1.5.0 then I get following when I build Compose for Desktop module (which is using v 0.4.0-rc1)

This version (1.0.0-beta08) of the Compose Compiler requires Kotlin version 1.5.10 but you appear to be using Kotlin version 1.5.0 which is not known to be compatible.

[Oleksandr Karpovich [JB]]

Do I understand correctly, that you have two modules (one for js and second for desktop) and both of them have different versions of compose plugin?

0.0.0-web-dev-13 is using 1.5.0. the build with 1.5.10 should be released next week.
but I'm curious about your use case with two modules and I guess different compose versions. Did it work before 0.4.0-rc1?

[John O'Reilly]

what's in main branch (for https://github.com/joreilly/PeopleInSpace) works right now

[John O'Reilly]

but only seeing this when starting to update for Kotlin 1.5 (and related compose web/desktop versions)

[John O'Reilly]

when you say "two modules and I guess different compose versions.", is suggestion that compose for desktop and compose for web modules can/should be using same compose version?

[Oleksandr Karpovich [JB]]

yes, kind of. We assumed that the same version would be used at least for convenience purpose + for some code behaviour consistency (since versions are usually not in full sync at least for now. we expect to have it improved soon). I just didn't think about using different versions, so thanks for bringing this thought 🙂 ideally the same version should work equally good for all targets.

it's nice to hear it worked. I see you don't have any Compose code in common source. I think that gives some explanation to me. And I'll have a more mindful look at your repository a bit later.


And ideally, we'll come to the point when web is included into the same published artefact with the same version. So there won't be a need to set different versions

[John O'Reilly]

Yeah, hope to look soon at having common Compose code

[John O'Reilly]

I can see all right the need to align versions if that's being done. Am curious though how that will be managed....it seems like Desktop/Web can be put under single version as you said but how is it hoped to align with Android releases then?

[Oleksandr Karpovich [JB]]

there is no answer at the moment. that needs to be figured out. perhaps in small steps.
also compose desktop publications already include android binaries, so if we add web there, it should get much more convenient.