Design document for a `kt_library` rule. about rules_kotlin HOT 4 CLOSED

Hi @hsyed ,

Just checking in. I made an attempt to just hack this to work by creating a kt_js_library rule, and just define a parallel execution/provider path for js files.

However, with my limited knowledge of Bazel I got stuck on what to do with the KotlinBuilder class and toolchain, which is currently JVM-specific.

Would love to see this working, but I don't know enough about Bazel yet to proceed any further without significant guidance/direction.

So, putting this on the back burner for now and going back to Gradle to build my kotlin/js 😔

Thanks,
-- Chad

from rules_kotlin.

@hsyed

One main thing that I realized is that in the JS ecosystem, there has to be some core concepts of managing dependencies via npm/yarn, and output bundles.

Other rules libraries implement this in various ways, for example https://github.com/bazelbuild/rules_nodejs or https://github.com/bazelbuild/rules_typescript.

Some of these also implement other features we may or may not want, e.g. building for dev mode, and running local servers (e.g. express).

My main question is: for the core stuff, dependencies and bundles, would we need to reimplement a lot of it, or would it be possible to "compose" or reuse with some of these other sets of rules like the nodejs ones.

If you want make some time to discuss this and give me more context on some of the ideas you outlined and more direction on what to hack on, I'd be happy to. My contact info is on my profile, and I'll include my email here.

Thanks!
-- Chad
[email protected]

from rules_kotlin.

See my last comment in #114 - basically we need a right-shaped JS provider that TypeScript and Kotlin rules both output, then you should have no other work to fit into the JS runtime ecosystem.

from rules_kotlin.

this is obsolete at this point. We generally need to update overview documentation.

from rules_kotlin.