Oleksandr Karpovich

> In case you think this feature (ref) is redundant and must be removed in future - it would be nice to describe how can I understand in future which...

I apologise for a delay. Currently we don't have capacity to approach the `ref` API design and implementation issues. This PR is noted in https://youtrack.jetbrains.com/issue/CMP-5980 and it won't be lost...

Thank you! Could you please cover the new units in the tests https://github.com/JetBrains/compose-jb/blob/master/web/core/src/jsTest/kotlin/CSSUnitApiTests.kt similar to other units?

I asked about the issue with resources in different modules in k/js. It's a known thing, but no official solution available yet. This workaround is a valid thing to do....

That's right. This workaround will be needed if we have many modules with different resources and all of them need to be included in the final distribution. So if we...

Yeah, not urgent. Just some notes for the time we decided to get back to it: demo/jsMain/resources contains the copy of resources, so it would work even without a workaround...

> Hi, I have finished the requested changes. However, I have noticed something else that the `required` attribute extension function as well as some others don't stick to the documented...

I'm wondering in what case you see `e: Compilation failed: Cannot find the Composer class in the classpath`. This erros probably means that you applied the compose plugin but didn't...

> In fact, now that coroutines have androidNative support, Compose Multiplatform could support these too, but that's a separate issue. Nice. We'll consider that. Besides coroutines, we need atomic-fu as...

Thank you @natario1 We'll take some time to discuss how to approach such use cases and provide the flexibility to configure the plugin.