❗ Hello, everyone! My name is Ilya and I’m product manager at Kotlin/JS :kotlinnew:. I’m looking for Compose for Web users that are willing to have a 30-45 mins chat with me regarding their experience with Compose for Web (especially if you are using it in production). If you are willing to talk, please, write me in the DM or leave a reaction on this message and I will write you. Thank’s to all the responders in advance 😉

@Ilya Kalibrov [JB], I tried really hard to be able to use Compose/Web on a (hobby) project but I always ran into problems. There were issues with the Compose plugin, the Gradle tooling, Idea integration, etc. Most of them were fixed in Kotlin 1.6.10 and Compose JB 1.0.1. The current blocker issue is that I cannot use `jsBrowserDevelopmentRun`: https://youtrack.jetbrains.com/issue/KT-50871. I don't want to complain but until now my experience was far from excellent, so I cannot imagine that I would use Kotlin/JS + Compose/Web for a serious project in its current state. Of course I will try again after the issue mentioned above is fixed, and the progress is really-really promising 😉

Hi @Norbi! Could you please take a look at https://github.com/JetBrains/compose-jb/issues/1751 It might be similar to what you described in kt-50871. And if your project (with compiler error) is available on github, could you please leave a link in the issue comment? There is no fix for the issue yet, but collecting more cases could help. Just a fyi: the fact that jsBrowserProductionRun doesn't fail could mean that the problem is related to some unused code branches (since production run uses dce)

@Oleksandr Karpovich [JB], thanks for your reply. My project is not on GitHub and is not public. But I'm sure that none of the `@Composable fun`s is

inline

.

related to some unused code branches (since production run uses dce)

Hm, that sound logical but unfortunatelly the error doesn't contain any context. This is not the first internal compiler error or similar "_compiler_" error I ran into. Maybe all of these asserts should include some context about the currently compiled file/expression/anything to help investigations...

@Norbi, one more thing that might be the case: it's not necessary that your code contains

inline fun @Composable

. Perhaps, it has usages of composable Style function (which is inline). by the way, did the problem popped up after updating on a certain version of compose?

@Oleksandr Karpovich [JB], you must be right, I use styling in the Compose/Web project... Unfortunatelly I cannot validate it because I decided to not use Compose/Web until it gets a little bit more stable (until then I experiment with Compose/Desktop - unfortunatelly I don't have much time for this hobby project, so I don't want to "fight" much with the framework 😞 ).