Hi everyone, I have been away for a while and have...

# javascript

[gbaldeck]

Hi everyone, I have been away for a while and have a question about ducat and the React wrapper. Has it made the React wrapper obsolete since it can generate the type definitions from the d.ts files?

[Big Chungus]

Dukat is still not perfect (as any other codegen tool) so I personally prefer human rewieved and stable react wrappers over dynamically generated ones

[Vytautas Jakutis]

I think if we manually maintain Kotlin typedefinitions they will never be as good as typescript ones, so for Kotlin.js survival it is necessary that dukat works perfectly for any typescript typedef - I think people will 1) use Kotlin.js with npm/yarn a lot; 2) use dukat to generate Kotlin defs from Typescript defs dynamically in every yarn/npm build script - coding a Kotlin analog to https://github.com/DefinitelyTyped/DefinitelyTyped does not make sense

[Vytautas Jakutis]

@[JB] Shagen, wdyt?

[gbaldeck]

Thanks for the replies, I agree that Dukat will need to be close to perfect for KotlinJs to reach a wider audience

[epabst]

IMO, the most important milestone is that Dukat output doesn't end up with compilation errors. Only a fraction of the generated functions and classes will actually be used from Kotlin, but if Dukat fails or produces code that has compilation errors, it will be a huge blocker.

[epabst]

I would love to see Dukat able to create compilation error-free results of DefinitelyTyped, if if they didn't match the Javascript API exactly.

[Joffrey]

Not only Dukat needs to evolve, but Kotlin also needs to allow typing any sort of JS. This is for instance blocking for me: https://youtrack.jetbrains.com/issue/KT-31799