Thanks for better-parse — the combinator API is what made it viable to parse our own DSL in shared code instead of shipping a grammar per platform.
0.4.4 publishes jsIr, jsLegacy, jvm and a native matrix, but no wasmJs; the only wasm-shaped variant is wasm32, the Kotlin/Native target that has since been removed.
js and wasmJs are a single web source set in Kotlin's default hierarchy template — group("web") { withJs(); withWasmJs() } — and Compose Multiplatform builds web as Wasm-first, with Kotlin/JS only as the fallback for older browsers. So a js-only dependency blocks the half that modern browsers actually run.
Worth being upfront that this isn't a one-line change: on a fork, the current build didn't configure under recent Kotlin/Gradle without dropping the buildSrc codegen and the benchmarks module first.
Happy to open a PR if the project is taking changes — I see #71 is still open, so no expectations either way.
Thanks for better-parse — the combinator API is what made it viable to parse our own DSL in shared code instead of shipping a grammar per platform.
0.4.4 publishes
jsIr,jsLegacy,jvmand a native matrix, but nowasmJs; the only wasm-shaped variant iswasm32, the Kotlin/Native target that has since been removed.jsandwasmJsare a singlewebsource set in Kotlin's default hierarchy template —group("web") { withJs(); withWasmJs() }— and Compose Multiplatform builds web as Wasm-first, with Kotlin/JS only as the fallback for older browsers. So a js-only dependency blocks the half that modern browsers actually run.Worth being upfront that this isn't a one-line change: on a fork, the current build didn't configure under recent Kotlin/Gradle without dropping the
buildSrccodegen and thebenchmarksmodule first.Happy to open a PR if the project is taking changes — I see #71 is still open, so no expectations either way.