Thanks for Krawler — being able to drive a crawl from shared Kotlin code, with the DSL rather than a builder, is why we picked it.
Two things stop it working on web today. We hit both and fixed them on a fork:
BatchCrawlUseCase uses Dispatchers.IO, which doesn't exist on js/wasmJs. An expect val for the IO dispatcher (falling back to Dispatchers.Default on web) resolves it.required() and multiple() in the DSL collide with the same-named properties after JS name mangling. @JsName on the functions fixes it.- The
wasmJs target is missing the ktor-client-js engine dependency.
Separately, there's still no release on Maven Central — I ran into that in #2 — and I see #1 is open for the publishing setup, so consumers currently have to build from source or host their own artifacts.
Happy to open a PR with the three fixes above if it wouldn't collide with #1.
Thanks for Krawler — being able to drive a crawl from shared Kotlin code, with the DSL rather than a builder, is why we picked it.
Two things stop it working on web today. We hit both and fixed them on a fork:
BatchCrawlUseCaseusesDispatchers.IO, which doesn't exist onjs/wasmJs. Anexpect valfor the IO dispatcher (falling back toDispatchers.Defaulton web) resolves it.required()andmultiple()in the DSL collide with the same-named properties after JS name mangling.@JsNameon the functions fixes it.wasmJstarget is missing thektor-client-jsengine dependency.Separately, there's still no release on Maven Central — I ran into that in #2 — and I see #1 is open for the publishing setup, so consumers currently have to build from source or host their own artifacts.
Happy to open a PR with the three fixes above if it wouldn't collide with #1.