A modern programming language that makes developers happier.

kotlinlang

Should it be possible to have likes of following in `settings.gradle.kts` for an amper based project.....trying to pull in some Wasm specific dependencies

```dependencyResolutionManagement {
    repositories {
        google()
        mavenCentral()
        maven("<https://maven.pkg.jetbrains.space/public/p/compose/dev>")
        maven("<https://maven.pkg.jetbrains.space/kotlin/p/wasm/experimental>")
    }
}```

ah, looks I can do following

```repositories:
  - <https://maven.pkg.jetbrains.space/kotlin/p/wasm/experimental>```

doesn't seem to be using that

```   &gt; Could not find io.ktor:ktor-client-core:3.0.0-wasm2.
     Searched in the following locations:
       - <https://dl.google.com/dl/android/maven2/io/ktor/ktor-client-core/3.0.0-wasm2/ktor-client-core-3.0.0-wasm2.pom>
       - <https://jcenter.bintray.com/io/ktor/ktor-client-core/3.0.0-wasm2/ktor-client-core-3.0.0-wasm2.pom>
       - <https://maven.pkg.jetbrains.space/kotlin/p/kotlin/dev/io/ktor/ktor-client-core/3.0.0-wasm2/ktor-client-core-3.0.0-wasm2.pom>
       - <https://plugins.gradle.org/m2/io/ktor/ktor-client-core/3.0.0-wasm2/ktor-client-core-3.0.0-wasm2.pom>
       - <https://maven.pkg.jetbrains.space/public/p/compose/dev/io/ktor/ktor-client-core/3.0.0-wasm2/ktor-client-core-3.0.0-wasm2.pom>```

You can still use the `dependencyResolutionManagement` declaration from your initial post in your `settings.gradle.kts`, even when using Amper. Or are you asking about an Amper-native way to declare the same thing?

If it's about using dependencies in your modules (not in gradle plugins/build script), then `repositories` should be the way to go, indeed (and you could use a template to share them between modules). If that doesn't work, it might be a bug

I've tried both and still not resolving that dependency

Mmmh ok thanks for reporting then. We'll take a look

I reproduced the issue with `dependencyResolutionManagement` and with `repositories` in a single Amper module file. I'm still investigating the exact cause, though. I will keep you posted.

FYI, specifying the `repositories` in the `module.yaml` files of _all_ involved modules solved the problem for me. It also works when doing this via a template, and applying the template to the relevant `module.yaml` files.