Room 3.0 + wasmJs: `room3-paging` missing wasmJs t...

# compose-web

[Sagar Khurana]

Room 3.0 + wasmJs: room3-paging missing wasmJs target - how to use @DaoReturnTypeConverters in commonMain?

I'm adding wasmJs support to an existing KMP project (Android + iOS) using Room 3.0.0-alpha01. The room3-runtime resolves for wasmJs perfectly, but room3-paging does not - it lacks a wasmJs variant.

The issue: Room 3.0 requires @DaoReturnTypeConverters(PagingSourceDaoReturnTypeConverter::class) on @Dao/@Database classes for DAO methods returning PagingSource. However, my DAOs and Database are in commonMain, and PagingSourceDaoReturnTypeConverter comes from room3-paging, which cannot be in commonMain (no wasmJs target).

Moving room3-paging to a mobileMain source set resolves dependency resolution, but then the @DaoReturnTypeConverters annotation cannot reference the converter class from commonMain.

Questions:
1. Are there plans to add wasmJs support to room3-paging?
2. Is there a way to register DaoReturnTypeConverters via KSP arguments instead of annotations (to avoid the commonMain class resolution issue)?
3. Are there any recommended workarounds for KMP projects targeting both mobile and wasmJs?

Using: Room 3.0.0-alpha01, Kotlin 2.3.10, sqlite 2.7.0-alpha01, Compose Multiplatform 1.10.1

[Sagar Khurana]

@Chrimaeon, where should I post it?

[Chrimaeon]

Well, both libraries are maintained by Google so I‘d open a ticket on the their bug tracker.

[Oliver.O]

Since this is used in the context of Compose Web, I'd consider it absolutely legitimate to post here.

[soufianehamama9]

@Sagar Khurana did you find any solution for this

[Sagar Khurana]

@soufianehamama9 its coming on March 25th - https://issuetracker.google.com/issues/492780663