Hi all. this question might not be 100% kotlin, b...

# javascript

[xxfast]

Hi all. this question might not be 100% kotlin, but a question of interop between kotlin and typescript

in my kotlin-js module, i have a package say com.organisation.product.core which has this kotlin class

@JSExport
class Service()

once exported with npm-publish - when importing this from a typescript project it looks like

import {com} from "@organisation/core";
const Service = com.organisation.product.core.Service;

This kinda woks, but when you have another module (for example, com.organisation.product.feature) they both end up sharing the com

import {com} from "@organisation/core";
import {com} from "@organisation/feature"; // not allowed

I know you can get around this with alias like

import {au as core} from "@organisation/core";
import {au as feature} from "@organisation/feature";

const Service = core.organisation.product.core.Service;
const FeatureService = login.organisation.product.feature.Service;

Is there a way to make these imports much nicer without losing my package structure from kotlin side?

[ephemient]

in principle I think

import {com: {organization: {product: {core}}}} from "@organization/core"
import {com: {organization: {product: {feature}}}} from "@organization/feature"
const com = {organization: {product: {core, feature}}}

would work but that may be too cumbersome

[rnett]

There's also several youtrack issues for top level exports and more control over JS exports. I'm not sure what the timeline is and don't have links, but at least you can watch and upvote them.

[turansky]

https://youtrack.jetbrains.com/issue/KT-37710

[turansky]

Also you can remove redundant package via webpack

[turansky]

library.export option

[turansky]

Example - https://github.com/turansky/kfc-plugins#task-patchwebpackconfig