We've finally managed to publish the open previews...

# javascript

[Edoardo Luppi]

We've finally managed to publish the open previews of our VS Code extensions using Kotlin/JS (and JVM) as their "backend".
The extensions use TypeScript for everything related to UI interactions, but rely on `@JsExport`ed Kotlin code for the actual logic (TCP protocols, ANTLR parsing, XML parsing, handling of in-memory data, validation, etc.).
https://marketplace.visualstudio.com/items?itemName=IBM.zfaultanalyzer
https://marketplace.visualstudio.com/items?itemName=IBM.zfilemanager

Just for the sake of completeness, our tech stack currently is:
• Kotlin
• TypeScript
• Angular
• Nx & Gradle
Plus, we've managed to fit everything into a monorepo to maximize DX.

Overall we had a nice experience with K/JS, although with new requests from external teams to consume our code, what we are looking for in the future is:
• Better TS types generation, with support for outputting KDoc as JSDoc. This is crucial for JS consumers.
• Improved DX for per-file and ESM compilation, especially in relation to TS types. As VS Code moves forward with ESM, we'd like to move with the flow.
• Easier handling of plain JS objects (with the plain objects plugin + KT-17683)
• Improvements to the test framework to handle before & after-class hooks
And personally I'd like more people to participate in discussions for KT-70986 and KT-70477 as it seems they are kinda "hidden" topics for most K/JS users.