Artifacts for group io.matthewnelson have been migrated from oss.sonatype.org to s01.oss.sonatype.org. As such, need to update publishing plugin from SonatypeHost.DEFAULT to SonatypeHost.S01.

https://issues.sonatype.org/browse/OSSRH-88262

Add to doc macosCommonMain in hierarchical structure diagram

https://kotlinlang.org/docs/multiplatform-dsl-reference.html#targets

androidNativeArm32
androidNativeArm64
androidNativeX86
androidNativeX64

Add support for npm-publish plugin for publishing js projects to the respective npm registry. Should also include ability to publish to a local npm instances for testing/development purposes.

See https://github.com/mpetuska/npm-publish/tree/2.1.2

publish.sh --host darwin only builds ios + macos + tvos + watchos KMP_TARGETS. It should also build JVM and JS targets so that tests are run to ensure any platform specific code for those are working properly.

Move dependencies to to the /kotlin directory in their own individual files. This will help with CI caching, and make it a bit more pleasant to work with as there will be no more need utilize imports.

the jvmJsCommon source set is not being enabled when property KMP_TARGETS does not contain both JVM and JS.

add support for the following new targets:

• linuxArm64

There is a need to add an additional argument to setupModule via the kmpConfiguration plugin extension. It is to apply plugins after source sets are configured, such as the kotlinx-atomicfu plugin.

Refactor the Android Kmp target by adding default configurations

Instead of having to declare each individual target:

kmpConfiguration {
    setupMultiplatform(targets=
        setOf(
            KmpTarget.Jvm.Jvm.DEFAULT,
            KmpTarget.NonJvm.JS.DEFAULT,
            // ...
        )
    )
}

Add the ability to use the + operator to add all targets for a given platform

kmpConfiguration {
    setupMultiplatform(targets=
        setOf(
            KmpTarget.Jvm.Jvm.DEFAULT,
            KmpTarget.NonJvm.JS.DEFAULT,
        ) +
        KmpTarget.NonJvm.Native.Unix.Darwin.Ios.ALL_DEFAULT     +
        KmpTarget.NonJvm.Native.Unix.Darwin.Macos.ALL_DEFAULT   +
        KmpTarget.NonJvm.Native.Unix.Darwin.Tvos.ALL_DEFAULT    +
        KmpTarget.NonJvm.Native.Unix.Darwin.Watchos.ALL_DEFAULT +
        KmpTarget.NonJvm.Native.Unix.Linux.ALL_DEFAULT          +
        KmpTarget.NonJvm.Native.Mingw.ALL_DEFAULT,

        commonMainSourceSet = {
            dependencies {
                // ...
            }
        }
    )
}

Kotlin 1.8.0 introduced a new source set layout version for android to mitigate naming conflicts. This change should be applied automatically for kotlin-component consumers.

Shouldn't be a big issue as androidMain stays the same, and is the only thing considered in the publications.

Currently, if applying dependencies via

setupModule(
    // ...
    commonMainSourceSet = {
        dependencies {
            // my common dependencies
        }
    }
)

the dependencies are not propagated to the intermediary source sets, because the commonMainSourceSet argument is invoked before anything is setup. The invocation should come after setting up intermediary source sets.

https://kotlinlang.org/docs/multiplatform-dsl-reference.html#targets

wasm32

Currently, all androidNative targets depend on intermediate source set native. They should actually depend on the intermediate source set unix.

kmp plugin needs some work.

• Source set re-naming
• Fix support for all targets (jetbrains hoodwinked everyone and removed iosArm32 from the ios shortcut target)
• Fix iosSimulator issue

New target just dropped in Kotlin 1.8.0... watchosDeviceArm64

Currently, JavaVersion is specifically declared in all module's KmpTarget.

Removing such declaration will rely on the default JavaVersion (11) used by KmpTargets.