Daniele B
06/17/2021, 11:08 PMArkadii Ivanov
06/17/2021, 11:24 PMorg.jetbrains.compose
. And I'm not sure if Android will work with plain JVM module with Compose, but worth to try.Daniele B
06/17/2021, 11:33 PMrnett
06/17/2021, 11:47 PMDaniele B
06/17/2021, 11:50 PMSourceSets
on this gradle file? I didn’t add any, as these composable as not dependent on any libraries. They are pure Compose.rnett
06/17/2021, 11:51 PMDaniele B
06/17/2021, 11:55 PMrnett
06/18/2021, 12:13 AMapi
in composables, since your app projects are depending on it, right? They might need some platform specific dependencies, but the common ones should be as high up in the dependency tree as possibleDaniele B
06/18/2021, 12:17 AMrnett
06/18/2021, 12:36 AMDaniele B
06/18/2021, 12:41 AMrnett
06/18/2021, 1:38 AMdarkmoon_uk
06/18/2021, 4:32 AMimplementation(compose.web.widgets)
from your common
source-set. Yes, the 'web'-named artifact is common
😱 🤦♂️ I called this out last week to [JB] as being misleading.build.gradle.kts
from my client
module, featuring (what I similarly called) a materialCompose
source-set.Arkadii Ivanov
06/18/2021, 7:16 AMapi(compose.runtime)
. Just double check that the version you are using is published with web. 0.5.0-build225
should work!runtime
dependency will be possible in common, others are not published for Web at the moment.Javier
06/18/2021, 7:35 AMcommonMain
(which should be used in all targets), and the specific deps in the specific source sets (maybe navigation in Android, and so on).