Ben Lee

We currently do not have any plans to build out support for KMP in `rules_kotlin` but are open to community contributions. `rules_jvm_external` also lacks support for KMP dependencies but that...

`include_stdlibs` doesn't control what gets passed into the `--direct_dependencies` flag. That option just translates to a Kotlinc flag that the compiler internally handles. https://github.com/bazelbuild/rules_kotlin/blob/dc98c15a7e26c4c02197b4a4ed2eb78122b5b712/src/main/starlark/core/options/opts.kotlinc.bzl#L55

We do what rockwotj does and just provide our own version of the std libraries that we pull from `rules_jvm_external` as well as passing the `-no-stdlib` option. Having the `com_github_jetbrains_kotlin`...

No immediate updates here at the moment, but I expect this to be resolved once we switch to the Starlark implementation of `rules_android`.

@pswaminathan are you able to confirm if this works?

Going to close this PR since we rolled back to the previous behavior https://github.com/bazelbuild/rules_kotlin/commit/0f4c0af37ea4451fa01e001cf704a8fc6c897d22

Are you referring to the new experimental transitive dependency pruning that was introduced in this PR? https://github.com/bazelbuild/rules_kotlin/pull/842

@telescopic Bzlmod works now but you will need to be using the latest Bazel rolling release until the actual fix get backported into the 6.x release track.

@telescopic not much documentation right now. Bzlmod doesn't actually seem to be fully working if you are using `rules_android` at HEAD. If you are still using the native rules it's...

@ahumesky I did some digging yesterday afternoon to try to figure out what's going on here. We found a few things: 1. Inside rules_jvm_external the `_get_aar_import_statement_or_empty_str` macro seems to be...