Jan Tennert

Closing due to inactivity.

Yea, I think that should be fine. Originally there were some problems with Compose in the same class path, but that has been fixed a while ago.

Handling this currently, unsure if this as easy as it sounds. Each sample has their own modules & settings, which makes it hard to include them all without a lot...

@MohamedRejeb any idea on this?

If we mean the same thing, we already have some methods to make the configuration easier: https://github.com/supabase-community/supabase-kt/blob/master/Storage/build.gradle.kts But yea, we can probably continue improving on these, if we include all...

> root project already takes 40 min. Probably a bit less if the Gradle files are cached, but its still ~25-30min.

We can close this issue now, all non-deprecated samples have been migrated.

Update: Both Kermit and multiplatform settings have now WASM support, which means I can start adding the WASM target in supabase-kt. We may still have to wait until Kotlin 1.9.20...

You can now use the newest version in your wasm project: [2.2.2-wasm0](https://github.com/supabase-community/supabase-kt/releases/tag/2.2.2-wasm0)

It may take even longer than expected as WASM support in Ktor will only come in the new 3.0.0 version which apparently releases sometime this year. Not sure if it's...