Short article about migrating a KMP project to using Amper <https://johnoreilly.dev/posts/amper-kmp-...

# amper

[John O'Reilly]

Short article about migrating a KMP project to using Amper https://johnoreilly.dev/posts/amper-kmp-climatetrace/

[amakeev]

Thanks for looking at Amper and writing a post, John! Apart from the problems you’ve run into, do you have general impressions/feedback that you are ready to share to help us improve Amper?

[John O'Reilly]

Hi @Anton Makeev, I've reported any issues I found in this channel and sounds like they're being worked on. Big one right now is probably support for Wasm based Compose for Web clients (cc @bashor). I have use of Amper in a branch of ClimateTraceKMP right now but will probably merge in to main branch once that's supported.

[amakeev]

Thanks, we are working on it, will let you know if we have a fix for you

[Alexander Tsarev]

@John O'Reilly Hi! You can try to use 0.3.0-dev-438 version, it should not fail just because of wasm platform presence (currently only browser one is used). But if it will fail for some other reason - then I'm here :)

[John O'Reilly]

@Alexander Tsarev what is that a version for?

[Alexander Tsarev]

This is a version for the Amper plugin:

id("org.jetbrains.amper.settings.plugin").version("0.3.0-dev-438")

[John O'Reilly]

ah, gotcha.....forgot that was there!

[John O'Reilly]

do I need to add particular maven repo to be able to pick that up?

[Alexander Tsarev]

AFAIK, no

[John O'Reilly]

hmm, it's not finding that version

[Alexander Tsarev]

Let me recheck

[zsmb]

I think the dev versions come from

maven("<https://packages.jetbrains.team/maven/p/amper/amper>")

As opposed to the public releases from

maven("<https://maven.pkg.jetbrains.space/public/p/amper/amper>")

[Alexander Tsarev]

Ah, true, my bad

[John O'Reilly]

k, it's finding it now

[John O'Reilly]

I ended up adding some dependencies before to dependencies: that don't have support for wasm......can I "factor these out" like with gradle where you can say group wasm and non-wasm dependencies?

[Alexander Tsarev]

Well, as I can see, you can use aliases to create some "nonWasm" alias that contains all other platforms. And then use dependencies@nonWasm

[John O'Reilly]

ah, remember seeing those now....I'll try that

[John O'Reilly]

what should "app" folder be called.....wasm-app ?

[John O'Reilly]

ah, that's probably not supported right now?

[John O'Reilly]

I moved stuff around e.g. use of src@noWasm etc and other targets seem to be working fine

[John O'Reilly]

Just downloaded latest 1.31 Fleet preview and also using 0.3.1-dev-420 (was getting errors with one I had been using)....doesn't look like that includes wasm platform as one above did?