Hi, could someone look at <https://youtrack.jetbra...

# javascript

[CLOVIS]

Hi, could someone look at https://youtrack.jetbrains.com/issue/KT-58685 please? It's now been almost three months that we cannot release any of our apps and libraries which use Kotlin/JS because of this.

[Edoardo Luppi]

Upvoted. Hopefully you're going to get unblocked. Three months is quite a long time.

[turansky]

@CLOVIS WA - also will work for you?

[CLOVIS]

@turansky Sorry, I do not understand your comment.

[CLOVIS]

@Edoardo Luppi Yeah, I understand they have many things they need to do, but this is quite a big blocker 😕

[Edoardo Luppi]

@CLOVIS my eng manager would have started asking me to rewrite it in some other technology 😂

[CLOVIS]

…we're lucky that this is happening during a complete rewrite of our main project, so we still have a few months before it actually becomes a big problem, but I'm growing more worried by the day.

[CLOVIS]

But well, with the Kotlin release cycle and the time it's realistically going to take them to fix it…

[Edoardo Luppi]

@CLOVIS yeah that's a lucky point on your side!
I'm currently evaluating KMP by building a POC while my colleagues keep going the native TypeScript route. No major issues as of now, but many small quirks that impact productivity.

[CLOVIS]

Globally, same experience for me. I've been running Kotlin/JVM+JS in production for almost two years now. I've hit many small setbacks (mostly configuration related), but it's my first actual blocker. Thankfully, I've yet to have an issue that wasn't caught by CI, so the quality of the app was never impacted even when productivity was.

[Edoardo Luppi]

Let's see what the Kotlin roadmap will look like after this month update.
I'll make up my mind after reading what's their plan

[turansky]

WA - workaround
Do you need workaround for this problem as temp solution?

[CLOVIS]

Yes, that would unblock me until a real fix arrives. The problem is relatively localized in my codebase (happens in around 5 places) so it's possible to write those slightly differently for now if needed. I haven't managed to find one yet though 😕

[CLOVIS]

I just can't downgrade Kotlin because of Compose

[CLOVIS]

Hi @turansky, sorry for the reminder. You mentioned the possibility of a workaround, do you have any specific idea in mind?

[turansky]

In most cases workaround exists.
Do you know what is source of problem?
Is it compiler problem? Or problem located inside promise extension?

[CLOVIS]

I'm not using the promise extension. I originally reported it to KotlinX.Coroutines, then they reported it to the Kotlin compiler, so I assume it's on their side. It's something to do with the compiler calling the `finally`block twice in that specific case? I don't know how to reduce that or find another way to make it work.

[turansky]

Code with finally call - is it JS specific code?

[turansky]

Could you use Promise.finally in that place?

[turansky]

TS example

[CLOVIS]

I don't use promises.