<@U01512EH19C> <https://github.com/mipt-npm/plotly...
# javascript
a
@Dmitry Romanov [JB] https://github.com/mipt-npm/plotly.kt/releases/tag/v0.3.0-dev-rc. Full IR migration. I will start releasing all other projects in IR shortly. If everything is fine, I will promote it to bintray.
🙏 1
🎉 4
d
Cool! Can you tell us what has changed since switching to the JS IR BE?
a
I did not encounter any critical problems, so Plotly and upsteam DataForge library are in JCenter. Kmath needs some logic updated but will be released soon. VisionForge has a bug with external typescript library and also requires some logic change. As for the changes. • Size of the bundle diminished slightly (most of the bundle is external libraries, so one can't diminish it more). • Source maps do not work 🤷‍♂️ . Not that I need them so much. • React requires even more ceremony with external interfaces on PRops. I wont to drop it anyway. Looking forward to Compose-web. Maybe KVision in a short perspective. • JsExport is a nice feature. I like it. It allows to better understand what is exposed to JS. • There is a bug with a typescript es6 compatibility in VisionForge.
must call new in super constructor
or something like this. I am not sure, why it happens, but I am pretty sure that it worked before migration to IR. • Some
🙏 1