A modern programming language that makes developers happier.

kotlinlang

<@U0RM4EPC7> <https://github.com/arrow-kt/Arrow-JS-Template> looks like not working now. Except that it refer to SNAPSHOT-versions it could not find, I get this kind of errors:
```* What went wrong:
Could not determine the dependencies of task ':packageJson'.
&gt; Could not resolve all dependencies for configuration ':npm'.
   &gt; Could not resolve io.arrow-kt:arrow-core:1.0.0.
     Required by:
         project :
      &gt; No matching variant of io.arrow-kt:arrow-core:1.0.0 was found. The consumer was configured to find a usage of 'kotlin-runtime' of a component, as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'js', attribute 'org.jetbrains.kotlin.js.compiler' with value 'legacy' but:
          - Variant 'commonMainMetadataElements' capability io.arrow-kt:arrow-core:1.0.0:
              - Incompatible because this component declares a usage of 'kotlin-api' of a component, as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'common' and the consumer needed a usage of 'kotlin-runtime' of a component, as well as attribute 'org.jetbrains.kotlin.platform.type' with value 'js'
              - Other compatible attribute:
                  - Doesn't say anything about org.jetbrains.kotlin.js.compiler (required 'legacy')```

Not published at all to Maven Central? I only see JVM version here: <https://mvnrepository.com/artifact/io.arrow-kt/arrow-core/1.0.0>

For the snapshot versions, there might be an incompatibility between ir and legacy compilers?

<@U4UGS5FC7> I don't see the claim "In Arrow 1.0, Arrow now gets tested and distributed on the different multiplatform targets supported by Kotlin, including JVM, Native, and JS." in the blog post to be valid yet then?

<@U01BB20TXCL>, we attempted to release all artifacts mpp on 1.0.0 but there seems to be a problem with some metadata in certain targets. <@UE206C71V> <@U0RM4EPC7> and I are looking into releasing 1.0.1 with the fixed metadata. We had to rework a lot of the gradle setup to get this right. This problem did not happen in our snapshots and it just seemed to be an issue with the way we were invoking the gradle tasks in the publication. We expect to release 1.0.1 with the fixes for the remaining targets in the next weeks.

Your link is still not the right place to look, the remaining artifacts for multiplatform get published here <https://repo1.maven.org/maven2/io/arrow-kt/>

There you can see many of the published platforms which get automatically selected whenyou use arrow-core as coordinates in an mpp setup and you define the tarjets you want to compile too

In 1.0.0 the problematic targets seem to be so far the native macos ones. I’m not sure we setup publishing for npm but we maybe able to just fix it and publish it in the next minor patch release.

Ah ok. But I find it a bit strange for it to complain about some missing native artifacts when I try to build on JS platform?

Japp, it's there <https://mvnrepository.com/artifact/io.arrow-kt/arrow-core-js|https://mvnrepository.com/artifact/io.arrow-kt/arrow-core-js>

If Gradle detect that it requires a dependency for a native platform it will first force to load that resource before it will even attempt to compile your code. `./gradlew jsTest` can fail on `native` dependency not being available :confused: