I just checked the Kotlin roadmap for the next six...

# amper

[suresh]

I just checked the Kotlin roadmap for the next six months, but I found no mention of Amper (https://kotlinlang.org/docs/roadmap.html). Is there a separate roadmap for Amper, and what can we expect in the near future?

[joffrey]

Yeah, sorry about this, we are not really part of the Kotlin roadmap, and don't have our own public roadmap.

The main big thing we're working on is the prototype of extensibility (Amper plugins / custom tasks). We want to get early feedback on this, as it's a critical piece of our build system.

We're also investigating how to improve the quality of life for the server-side development story (like making modules with a single JVM platform less "weird").

On the KMP side of things, we are improving the rough hot reload prototype to make it fast enough to be useful, and adding some basic support for JS and WASM (by basic I mean without involving any extra webpack/nodejs toolchain - just plain JS/WASM generation).

Apart from this, we generally improve the UX with little things (e.g. customizing the Kotlin version, adding better diagnostics, etc.)

We didn't forget about publication, this is also coming up in the near future.

[suresh]

Thanks for the details. Really looking forward to the plugin support.

server-side development

• Can we expect to set any custom JDK version for compilation anytime soon (say I want to test JDK 25 or 26-EA builds)? Today, even though we can set jvm.release to 25 on IDE, at runtime, we are getting '-Xjdk-release=25' option is not supported by used JDK: ../Library/Caches/JetBrains/Amper/extract.cache/7de4a97883-amazon-corretto-21.0.1.12.1-macosx-aarch64.tar.gz.058c52.d/Contents/Home
• What’s the plan for version catalog support to unify dependency versions? Having a gradle directory makes this a little weird.😄
Are any of these part of the upcoming release?

[joffrey]

The custom JDK version is indeed recognized as a low-cost high-reward feature. So we should add support for this soon-ish. If it doesn't make it to 0.8.0, probably in 0.9.0.

[joffrey]

> What’s the plan for version catalog support to unify dependency versions? Having a gradle directory makes this a little weird
Yeah I very recently made it possible to place the libs.versions.toml file at the root level (not under gradle/ ) to avoid the awkwardness (beware that the IDE support is not there, so it will yield some red code in the editor).
We'll introduce an Amper-style library catalog in the future, but in the meantime, this should help

[suresh]

Thanks! For version catalogs, are there any plans to reference the version information from the catalog for use in the module YAML files, like Kotlin/Kotlinx serialization versions? This is possible in Gradle version catalogs.

$libs.versions.kotlin