'jvmRuntimeElements-published' capability io.ktor:...
# webassembly
v
'jvmRuntimeElements-published' capability io.ktorktor client logging2.3.10 declares a library for use during runtime: - Incompatible because this component declares a component, as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'jvm' and the consumer needed a component, as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'wasm' - Other compatible attributes: - Doesn't say anything about its target Java environment (preferred optimized for non-jvm) - Doesn't say anything about org.jetbrains.kotlin.wasm.target (required 'js') 2.3.10 not working
a
Try ktor
3.0.0-beta-2
l
Use the latest eap
K 1
v
Could not find io.ktorktor client logging3.0.0-beta2.
getting this error
v
Could not find io.ktorktor client logging3.0.0-beta-2-eap-926.
a
Have you added it?
Copy code
repositories {
  maven {
    url = uri("<https://maven.pkg.jetbrains.space/public/p/ktor/eap>")
  }
}
v
yes after that project :composeApp
Could not find org.jetbrains.kotlinkotlin stdlib1.9.23.
Searched in the following locations:
a
You need to have the next
repositories
section inside your Gradle settings:
Copy code
repositories {
        google()
        mavenCentral()
        maven("<https://maven.pkg.jetbrains.space/public/p/compose/dev>")
        maven("<https://maven.pkg.jetbrains.space/public/p/ktor/eap>")
    }
In this case everything should work fine
v
- Variant 'metadataApiElements' capability io.github.theapache64rebugger1.0.0-rc02 declares a library: - Incompatible because this component declares a component for use during 'kotlin-metadata', as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'common' and the consumer needed a component for use during 'kotlin-api', as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'wasm' - Other compatible attributes: - Doesn't say anything about its target Java environment (preferred optimized for non-jvm) - Doesn't say anything about org.jetbrains.kotlin.wasm.target (required 'js')
a
Seems like
rebugger
doesn't have the
wasm
target
v
yes many libraries still don't have wasm
a
We are working on it 🙂
👍 1