Summary
com.huanshankeji.generate-kotlin-js-browser-webroot-for-vertx-web currently hardcodes jsBrowserDistribution and looks it up with tasks.getting inside afterEvaluate of the consuming project.
That is insufficient when:
- Wasm — consumers need
wasmJsBrowserDistribution (and typically *.wasm / related assets), not only JS.
- Evaluation order — if the frontend KMP project has not registered the distribution
Sync yet, configuration fails with “Task with name '…BrowserDistribution' not found”. Workarounds need evaluationDependsOn(frontend) or a lazy tasks.named(…).
Ask
Extend the plugin (or add a sibling) so consumers can choose JS vs Wasm (or both), include Wasm artifacts, and resolve the frontend distribution task without fragile evaluation-order failures.
Summary
com.huanshankeji.generate-kotlin-js-browser-webroot-for-vertx-webcurrently hardcodesjsBrowserDistributionand looks it up withtasks.gettinginsideafterEvaluateof the consuming project.That is insufficient when:
wasmJsBrowserDistribution(and typically*.wasm/ related assets), not only JS.Syncyet, configuration fails with “Task with name '…BrowserDistribution' not found”. Workarounds needevaluationDependsOn(frontend)or a lazytasks.named(…).Ask
Extend the plugin (or add a sibling) so consumers can choose JS vs Wasm (or both), include Wasm artifacts, and resolve the frontend distribution task without fragile evaluation-order failures.