Had an issue with the multiplatform project with c...

# compose-web

[Arslan Armanuly]

Had an issue with the multiplatform project with compose-web fronted and ktor backend. apparently adding compose compiler plugin forces having compose runtime in the jvm. in this case i guess it is not that lethal although adding unnecessary dependency is weird

[Big Chungus]

Why not isolate compose frontend in a separate gradle module and only apply the plugin there?

[JCollardBovy]

But why would it make sense to isolate frontend (or any other platform) as a separate module?
I fail to understand why this would be a good solution. One of the most important features of Multiplatform plugin is that it allows to configure multiple targets and write code for different platforms in a coherent way

[Big Chungus]

It does for web, because it's a standalone application

[hfhbd]

You can still use different modules even with the multiplatform plugin, as it still has some bugs.
And you have to split it anyway if you are using kotlinx.serialization.

[Arslan Armanuly]

I was just using multiplatform fullstack template

[Arslan Armanuly]

I know that it can be easily solved by making modules for each sources, but still, i think its weird that its mandatory having compose runtime

[Big Chungus]

I personally only use multiplatform plugin for library modules and native stuff. All the app modules just consume those as standalone modules.

[PHondogo]

https://github.com/JetBrains/compose-jb/issues/537

[PHondogo]

Just for now you can make compose dependencies for jvm as compileOnly.