:heavy_exclamation_mark:Hi, folks! Few months ago...

# javascript

[Ilya Kalibrov [JB]]

❗Hi, folks!

Few months ago @Sebastian Aigner wrote an article about migrating from Legacy BE to IR. He described all major cases/issues which can be faced during the migration, but I’m gathering additional information on things that need to be done for successful migration. If you have such cases in your projects - leave a comment in thread with general description/sample/Youtrack ticket or write me direct message 🧵

Your cases will help us to improve the experience of a migration. More cases will be covered - more comfortable this process will be!

In advance, thank’s everyone for the response!

[ankushg]

That article was definitely a great intro to the types of issues that could pop up.

Some things we’re experiencing in our Multiplatform shared library project that targets JS:

Using things like external interface and jsObject are great when you’re in a pure Kotlin/JS project, but don’t necessarily play well in the common portion of Multiplatform projects. There needs to be a way to do all this setup from common. Not sure if there’s a ticket for this.

The common use case right now is one combined JS bundle, but our project is intended to spit out several libraries that are consumed from a real JS app. Hopefully the per-module functionality takes care of this 😄

[altavir]

The primary problem is still debug. It is almost non-existing in IR.

Other problems are mostly with gradle plugin. executable binaries are placed in the same directory as Java application. library mode is mostly undocumented.

[Sebastian Aigner]

@altavir when you say “Debug”, I guess you’re mostly referring to source maps? 🙂

[altavir]

@Sebastian Aigner source maps are just a way to provide debug capabilities. But I actually do not care, how it is done. Maybe there is some better way.