Is the conversion to .gradle.kts required to enable the wasmJs target? If not, it would be best to leave that conversion for a different PR since this one has a lot of files that are just moved and it's more difficult to review the actual changes here.

Sure, I will revert this change

@dellisd Hi!
I've rebased on the latest master.
Here are changes since your comment:

1. Reverted the migration to .gradle.kts.
2. Made web-worker-driver tests for js and wasmJs common.
3. Made createWebWorkerDriver helper function which allows creating the default WebWorkerDriver in the jsCommon sourceSet.
4. Upgraded Kotlin to 2.0.0-Beta3 and KSP to 2.0.0-Beta3-1.0.17

@dellisd Hi!
I've rebased on latest master.
Here're changes since my previous comment:

1. Upgraded Kotlin to 2.0.0-Beta4 and KSP to 2.0.0-Beta4-1.0.17
2. Upgraded kotlinx.coroutines to 1.8.0 with wasmJs support
3. Temporarily added Sonatype repository containing Turbine 1.1.0-SNAPSHOT

I'm not sure why, but instrumentation tests are failing on CI.
They're passing locally on my M1 Max.
https://github.com/IlyaGulya/sqldelight/actions/runs/7957378205/job/21719986393

Turbine 1.1.0 with wasmJs support is out

Replaced Turbine snapshot with 1.1.0

Currently trying to fix tests 🙂

Still any update on the same

Hi
Until this MR is merged ,
I've created a no operation wasm target version 2.1.0-wasm-no-op.4

Need to make some changes while adding the lib

update settings.gradle.kts

pluginManagement {
    repositories {
        mavenLocal()
        google()
        gradlePluginPortal()
        mavenCentral()
+        maven { url = uri("https://s01.oss.sonatype.org/content/groups/staging") } // <---- add this
    }
}

dependencyResolutionManagement {
    repositories {
        mavenLocal()
        google()
        mavenCentral()
+        maven { url = uri("https://s01.oss.sonatype.org/content/groups/staging") } // <---- add this
    }
}

then update only plugin and library group, app.cash.sqldelight -> io.telereso.kmp.sqldelight

-id("app.cash.sqldelight") version "2.0.2"
+id("io.telereso.kmp.sqldelight") version "2.1.0-wasm-no-op.4"

-implementation("app.cash.sqldelight:sqlite-driver:2.0.2")
+implementation("io.telereso.kmp.sqldelight:sqlite-driver:2.1.0-wasm-no-op.4")

No need to update src classes imports

My use case that I had 9 project with db I needed to expose to web ,
I've tested 1 so far it worked
I had to change the logic to not store/fetch from db in browser target, but rather use network directly

I'll try to publish this MR too to see if it works or not , but need some time

@dellisd any update?

Upgraded to latest master, fixed all errors.

I appreciate the huge amount of enthusiasm around this PR, and I want to say that I'm also very excited about the prospect of using SQLDelight in Wasm projects.

I also really appreciate the contributions being made here, but this PR is very difficult to review as-is because of its size and because of all of the changes that aren't directly related to enabling Wasm that are being pulled into here.

My recommendation would be to break this PR up into a few smaller PRs that are more focused and will be easier/quicker to review:

1. A PR that enables the wasmJs() target in the runtime and extensions
2. A PR that adds Wasm support for the web worker driver
3. Additional PRs to make other gradle config/code cleanliness changes after the fact

Thank you!

@dellisd Agree, there are lots of changes to just accept ,

but until it's broken down, can we get snapshot from this PR,
we already have some none production use cases that are only blocked by sqldelight right now
we can help test the changes too 😄

I appreciate the huge amount of enthusiasm around this PR, and I want to say that I'm also very excited about the prospect of using SQLDelight in Wasm projects.

I also really appreciate the contributions being made here, but this PR is very difficult to review as-is because of its size and because of all of the changes that aren't directly related to enabling Wasm that are being pulled into here.

My recommendation would be to break this PR up into a few smaller PRs that are more focused and will be easier/quicker to review:

1. A PR that enables the wasmJs() target in the runtime and extensions
2. A PR that adds Wasm support for the web worker driver
3. Additional PRs to make other gradle config/code cleanliness changes after the fact

Thank you!

Sure, I will make those changes it in the next couple of weeks

@ahna92 you can always publish this branch to your mavenLocal and take a look 🙂
Making a snapshot is not that easy so I'll just focus on preparing this PR to be merged.

@dellisd first PR is here #5531 🙂

I'll be closing this PR in favour of the new ones!