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.

Hey everyone, I was trying out compose-web and it seems like the behaviour is a bit different as compared to the jvm. E.g, this code did not align the two

Text

composables in a column. Just wanted to know if it's a bug or intended behavior.

Column {
  Text("Hello")
  Text("Compose")
}

Hi, I started using JetPack Compose for Web and I have very good feelings from it. My question is: does it somehow support hot reload (when app executed via

./gradlew jsBrowserRun

) ? I see in web console

client?0774:52 [WDS] Live Reloading enabled.

but I don't think JetPack is supporting it at the moment.

What are the plans for the final API for styling

Text

component? Will it be consistent with https://developer.android.com/jetpack/compose/text or will it require wrapping it with

Span

as is at the moment?

I have a question regarding selector. Is it possible in current version to define styles for HTML elements (eg. for

body

). I found this snippet for classes

object AppStyleSheet : StyleSheet() {
    val myStyle by style {
       ...
    }
}

but I didn't find the way how to define styles for HTML elements globally. Thanks

Any ideas on workarounds or ways to isolate this down further?

Is the flag for

suppressKotlinVersionCompatibilityCheck

supposed to be the same with compose for web? I tried

-P plugin:androidx.compose.compiler.plugins.kotlin:suppressKotlinVersionCompatibilityCheck=true

although it seems to have no effect (I still get the error about the version incompatibility).

Hey everyone! We've published a new version 0.0.0-web-dev-14 - https://github.com/JetBrains/compose-jb/releases/tag/0.0.0-web-dev-14 It's using kotlin 1.5.10 and also adds some API changes (even breaking ones). We are sorry for inconvenience. Let us know how your migration goes if you give it a chance :) Thanks a lot!

Is it possible to store a @Composable function as an attribute and execute it later? I want to implement a table, which holds the composable rows and display/execute the composable row function lazily when needed

data class Cell(val color: Color?, val content: @Composable () -> Unit)

SPOILER: I get this error message:

this._$cell_0._content is not a function. (In 'this._$cell_0._content($composer_0, 0)', 'this._$cell_0._content' is undefined)

Why is

Option { }

only usable from a

UList

, and not from

Select

?

Does 0.0.0-web-dev-14.1 include android binaries, or are they still not included?

Are there existing wrapper for jetbrains ring ui? If not are there are any plans

I'm rewriting my static sites in compose, any possibility to hack out a <strong> tag? Also might be worth mentioning about

--continuous

argument for jsBrowserRun task in Getting Started tutorial, developing with live reload is far more productive

I know it's early, early days for Web, but I'm trying to seed a project that compiles to Android, Desktop and Web targets. It's working out, albeit uncomfortable. Specifically: trying to find the versions of Compose dependencies that all work with the same Kotlin version took some time. The common denominator remains at 1.4.32. (EDIT: Wrong! ⚡ See in-thread for 1.5.x combo ⚡ 🙂 ) Also, code sharing opportunities remain limited due to their separation. What's the ball-park for an all-in-one artifact? Weeks, months, years... or not on any current roadmap?

two questions: 1. how do I set background color of entire page? 2. how do I set font for the app/website?

Hi, I have following code snippet:

import org.jetbrains.compose.web.dom.Input

...

Input(attrs = {
        onInput {
         console.log("New value is", it.nativeEvent.target.asDynamic().value as String))
        }
        attr("type", "email")
        attr("autocomplete", "email")
    }, value = value)

It works fine when I'm typing. But when I use autocomplete, then app crashes with ClassCastException at this line:

Hey! we've released new dev build https://github.com/JetBrains/compose-jb/releases/tag/0.5.0-build220-web Also - please let us know if it's too annoying to announce our weekly releases. It's just that some things are changing every week and till stabilization we'll break back compatibility quite often - though we put lot of effort not to do it when it's not absolutely needed.

Trying to use compose for web, simply adding the dependency and I get lots of errors building along the lines of

e: java.lang.IllegalStateException: Duplicate live literal key found

. Is there a way to turn "live literals" off project wide instead of putting

@NoLiveLiterals

everwhere?

What is "wrong" with the 223 build? Edit: Nothing In a project containing android, desktop and web, this version works for all targets, see https://github.com/hfhbd/ComposeTodo/blob/main/build.gradle.kts But using this build in a single Compose Web target only, Gradle cannot fetch the POM file, https://maven.pkg.jetbrains.space/public/p/compose/dev/org/jetbrains/compose/web/web-core/0.5.0-build223/web-core-0.5.0-build223.pom See https://github.com/hfhbd/routing-compose/pull/11

I’m curious if anyone has attempted to hook up compose-web to canvas kit, and leverage the existing widgets.

Is there a way to control which targets compose compiler runs for without splitting up my code into more modules?

To fully use 'multiplatform widgets' we currently need to use the word web:

implementation(compose.web.widgets)

...in common code. The underlying string is also web-specific, being:

org.jetbrains.compose.web:web-widgets:0.5.0-build224

I hope it's only like this during development phase as it's counter-intuitive. Is there a plan to bring these into a truly common namespace/artifact?

I did not find a typed routing library, so I implemented one by myself. Any feedback is welcome! https://github.com/hfhbd/routing-compose

I’m trying to read Input’s value on input change like this:

Input(type = InputType.Text, attrs = {
    onInput {
        console.log(it.nativeEvent.target.asDynamic().value)
    }
})

Is there a more elegant/safe way of doing it (alternative to

WrappedInputEvent.nativeEvent.target.asDynamic().value

)?

Just another compose thing 😉 🚀 https://twitter.com/theapache64/status/1403995465113169923

A good amount of the work has already been done to optimize compose at the common / compiler level already. I realize performance hasn’t been considered yet from the web / js perspective, but I wonder how good the performance of compose web would be when compared against react when using plain HTML dom components.

not doing a virtual dom should already place it far ahead. a more interesting comparison would be svelte

React noob and compose noob here so sorry if this comes off as stupid, but am I understand what jake said correctly? Compose for web should be "better" perf wise than react because it doesn't use a virtual dom? Isn't the concept of the virtual dom close to composes tree where it "diffs" things?