Hey team! We're adding wasmJs to our KMP app using...

# room

[Sagar Khurana]

Hey team! We're adding wasmJs to our KMP app using Room 3.0.0-alpha01.

room3-runtime resolves for wasmJs perfectly, but room3-paging does not — it's missing a wasmJs variant.

The problem: Room 3.0 requires @DaoReturnTypeConverters(PagingSourceDaoReturnTypeConverter::class) on @Dao/@Database for PagingSource return types. But our DAOs are in commonMain, and we can't put room3-paging in commonMain because it has no wasmJs artifact. Moving it to a mobile-only source set means the annotation can't reference the converter class.

Are there plans to add wasmJS to room3-paging? Or is there a way to register converters via KSP args instead of annotations?
Filed - https://issuetracker.google.com/issues/492780663

[danysantiago]

In the meantime while waiting for release, a possible workaround you can try is t In the meantime, while waiting on release, a possible workaround is to have a small actual/expect DAO that has the Paging return types with the converter for mobile only while for web it is an empty DAO.