First of all, the only way that type definitions can be/are used in Kotlin is by transforming them into kotlin definitions. This is what Dukat does, and what you can get automatically with the build system in cases. These definitions describe existing types/functions, but don’t define new ones. As such the only compatibility issue would be if you were to use conflicting defintions in the same Kotlin project. The solution to that is to not export the definitions as part of your project. The definitions are certainly not going to create a problem for JavaScript/TypeScript libraries as they would ignore Kotlin definitions.
Of course if you want to provide typescript definitions for your library you need to check how that works, but then it would be a typescript dependency conflict, not a Kotlin one.