Switch JS/TS API wrappers to ES modules

[Whathecode]

Previously, the JS/TS wrappers were compiled as UMD modules. This PR switches them to use the ES module system. The underlying generated libraries by Kotlin are still compiled as UMD.

This may make it easier to incorporate these libraries in modern web projects which use ES module systems by default. As such, this PR replaces PR #455.

[Whathecode]

There is still one piece missing to make this work. A package.json needs to be added to the generated libraries, otherwise they aren't recognized. Probably a more stringent requirement in the newer module system.

Adding a minimal pacakge.json, e.g., like this one, works:

{
  "name": "@cachet/carp-common-generated",
  "main": "index.js"
}

[Whathecode]

@jakdan99

I updated build.gradle to copy over package.json files and slightly modify them in line with other changes made to the JS sources in the build pipeline. Tests pass now.

You should be able to run verifyTsDeclarations (just like the build server does to test the JS/TS sources) and find/copy over the relevant packages from carp.core-kotlin\typescript-declarations\node_modules\@cachet.

Could you review please, and see whether the new generated sources work for you?

[jakdan99]

Supressing these errors with @ts-nocheck for testing purposes, both the httpclient's tests and the dashboard runs successfully.

[jakdan99]

I could fix all of the above errors by copying Kotlin-DateTime-library-kotlinx-datetime-js-ir.d.ts, kotlinx-serialization-kotlinx-serialization-core.d.ts and kotlinx-serialization-kotlinx-serialization-json.d.ts files from carp-kotlinx-* folders to their respective folders and renaming them to index.d.ts. So if it can be done while generating the ts library every comment of mine can be resolved

[Whathecode]

So if it can be done while generating the ts library every comment of mine can be resolved

Thank you for finding the root cause! 🦾 The error messages indeed indicated missing declaration files, so presumed it was something going wrong in the lookup.

This should give me enough input to change the build pipeline, and hopefully it subsequently still passes with the build setup of this project. :)

Either way, looks super promising, and that this PR is the way to go then, instead of #455.

[jakdan99]

Now it builds perfectly. Great work!