Did someone manage to use the d.ts of its Kotlin/J...

# javascript

[galex]

Did someone manage to use the d.ts of its Kotlin/JS MPP? I do not manage to implement an interface named LifecycleOwner declared like that:

export namespace com.company.core.livedata {
    class Lifecycle {
        constructor();
        readonly tags: kotlin.collections.MutableMap<string, any>;
        isStarted: boolean;
        start(): void;
        stop(): void;
        addStopObserver(block: () => void): void;
        notifyObserversStop(): void;
    }
}
export namespace com.company.core.livedata {
    interface LifecycleOwner {
        readonly lifecycle: com.company.core.livedata.Lifecycle;
    }
}

I just don’t manage to import it in pure React app (with typescript). I import the module like that:

import * as companycore from 'companycore';

I can find Lifecycle class if I log the whole module:

console.log("companycore", companycore)

But not the LifecycleOwner interface.

Any idea?

[Big Chungus]

To get Lyfecycle you need to do this:

import * as com from "companycore"
const Lifecycle = com.company.core.livedata.Lifecycle; // Class

let x: com.company.core.livedata.LifecycleOwner // type declaration

[galex]

I am not sure how to use x to implement a class with it, as I get the following error:

'LifecycleOwner' refers to a value, but is being used as a type here.  TS2749


  > 17 | export class LifecyleComponent extends React.Component implements LifecycleOwner {

}

[Big Chungus]

Looks like your generated *.d.ts are wrong then

[Big Chungus]

There's a known bug where *.d.ts interfaces are getting messed up for non external kotlin interfaces. maybe try adding external to LifecyckeOwner?

[galex]

I can actually use directly the whole reference !!! 😱

[Big Chungus]

What do you mean?

[galex]

This works and now I am required to add a Lifecycle property in the class!

export class LifecyleComponent extends React.Component implements com.company.core.livedata.LifecycleOwner { }

[galex]

Maybe there’s another way to alias an interface?

[Big Chungus]

Ah, yes

[Big Chungus]

type LifecycleOwner = com.company.core.livedata.LifecycleOwner

[galex]

Sweet ! 😮

[turansky]

@galex what about root export?

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

[galex]

@turansky That would be so much better! It’s really a mess right now, I don’t feel like Kotlin/JS is ready yet.

[turansky]

Feature isn’t released. And it means, that root export can be default (like in ScalaJS)

[turansky]

Otherwise export and import will be non-synchronous