I don't think there's much reason to migrate here for now, given how early-stage the new compiler is, but capturing notes from some initial testing:
On Kotlin 1.4.31, switching to IR and adding @JsExport to all files in the web package causes compilation errors. Oddly, it seems to work fine if I only add it to a few files - there seems to be some threshold above which it stops working. I can't test with 1.5.0 yet until #7 is resolved.
It doesn't seem supported to compile both legacy and IR versions while also supporting binaries.executable; I'm not sure if this implies that the library components would need to be better separated from the web UI. The documentation has since been updated to suggest binaries.library(), which might work instead?
I don't think there's much reason to migrate here for now, given how early-stage the new compiler is, but capturing notes from some initial testing:
On Kotlin 1.4.31, switching to IR and adding @JsExport to all files in the web package causes compilation errors. Oddly, it seems to work fine if I only add it to a few files - there seems to be some threshold above which it stops working. I can't test with 1.5.0 yet until #7 is resolved.
It doesn't seem supported to compile both legacy and IR versions while also supporting binaries.executable; I'm not sure if this implies that the library components would need to be better separated from the web UI. The documentation has since been updated to suggest binaries.library(), which might work instead?