A modern programming language that makes developers happier.

kotlinlang

Maybe I'm alone on this, but it feels weird to mark the new JS IR as stable (or even beta) without supporting some version of exported enum classes at all: <https://youtrack.jetbrains.com/issue/KT-37916>

I suppose the rationale is it’s not a regression.

Right, it is considered as a separate new feature with its own lifecycle.

We can consider splitting it into two parts export enums and generate TS declarations for them. Does it make sense?

<@U0BMF6PDJ> makes sense! submitted <https://youtrack.jetbrains.com/issue/KT-44494>

As a consumer, my qualm is that we could expose enums to JS clients in the old backend with DCE's `keep`. If we can't export them in the new IR (even without typescript definitions), that feels like a regression in functionality

TS declarations can definitely be a separate thing to prioritize/tackle