I would also like to remind you that another experimental feature was added in 1.4.20 - <Ignoring co...

# javascript

[Dmitry Romanov [JB]]

I would also like to remind you that another experimental feature was added in 1.4.20 - Ignoring compilation errors with IR compiler.
How many of you guys have tried it and ready to share some feedback?

[Robert Jaros]

With the SYNTAX tolerance policy the wrong code is just removed or copied to the destination JS file?

[hallvard]

My tests fail in an MPP when using IR or BOTH for the JS compilation. Did I miss something?

[Roman Artemev [JB]]

@Robert Jaros It depends on what syntax error is. In case of expression with such error it gets translated into throwing exception with problem code snippet in its message

[Oliver.O]

I'd love to switch to the JS IR backend, but I'm not ready to give up debugging.

Unfortunately, the JS IR backend still does not support source maps. There is no ETA given, it is not even on the roadmap. Feedback has been requested at https://youtrack.jetbrains.com/issue/KT-39447.

What are your experiences with the JS IR backend? How do you tackle debugging?

[Robert Jaros]

Debug with legacy (source maps), release with IR (smaller bundle) 🙂

[Oliver.O]

@Robert Jaros Yes, that's an option to consider.

Sooner or later we'll probably run into problems seeing the legacy backend sunsetting (bug present in legacy, not in IR). [KT\-42291](https://youtrack.jetbrains.com/issue/KT-42291):

As our main focus is on the new JS backend, we’re limiting our involvement in the Classicold backend.

And even now, we'll get stuck if we'd like to use some compiler plugin which depends on the IR backend, like https://github.com/bnorm/kotlin-power-assert