Compiler Error when working with Jetpack Compose for Web

Describe the bug When working with Serialization within the new Compose for Web library, I get a Compiler Error on trying to define Serializable data classes to interact with the public Pokemon API

To Reproduce Attach a code snippet or test data if possible.

models.kt

@Serializable
data class PokemonAPIResponse<T>(
    val count: Int,
    val next: String?,
    val previous: String?,
    val results: T
)

@Serializable
data class Pokemon(
    val id: Int,
    val name: String
)

build.gradle.kts

plugins {
    kotlin("plugin.serialization") version "1.4.32"
    kotlin("multiplatform") version "1.4.32"
    id("org.jetbrains.compose") version "0.0.0-web-dev-11"
}

group = "org.marks0mmers"
version = "1.0-SNAPSHOT"

repositories {
    mavenCentral()
    maven("https://maven.pkg.jetbrains.space/public/p/compose/dev")
}

kotlin {
    js(IR) {
        browser()
        binaries.executable()
    }
    sourceSets {
        val jsMain by getting {
            dependencies {
                implementation(compose.web.web)
                implementation(compose.runtime)
                implementation("org.jetbrains.kotlinx:kotlinx-serialization-json:1.2.0")
            }
        }
    }
}

Expected behavior Program to compile and be able to properly serialize these two classes

Environment

• Kotlin version: [e.g. 1.3.30] 1.4.32
• Library version: [e.g. 0.11.0] 1.2.0
• Kotlin platforms: [e.g. JVM, JS, Native or their combinations] JS
• Gradle version: [e.g. 4.10] 6.8
• IDE version (if bug is related to the IDE) [e.g. IntellijIDEA 2019.1, Android Studio 3.4] IntelliJIDEA 2021.1.1
• Other relevant context [e.g. OS version, JRE version, … ] Windows 10, JRE 11

[MrPowerGamerBR]

A workaround for now is creating a module without Compose that has your serializable classes, and then the Compose module without the Kotlinx Serialization plugin can depend on that module.

I haven’t tested everything yet, but it works for simple serialization/deserialization.

[brianguertin]

Looks like this is a longstanding issue, also filed over at the compose repo: https://github.com/JetBrains/compose-jb/issues/738