Angular expects modules that contain a TypeScript declaration file. expects those modules to be, unpacked, in the node_modules directory (typically by npm, yarn, etc)Ģ. expects module dependencies to be part of a package.json file b. Angular expects a project to be built in the Node.js environment, which a. There are a number of different problems when it comes to integrating Kotlin modules into an Angular build:ġ. However, I have also done the same with a React-TypeScript based application, and the solution works in both cases. In this article I discuss the issues with respect to an Angular based browser application. The tricky part is integrating this into the Node.js based build for the browser application. The build tool will compile the Kotlin code and provide (by default) a jar that contains a UMD JavaScript module. The JavaScript side is a little more tricky. This can be used just like any other JVM jar. Gradle and the Kotlin Multiplatform plugin), the Kotlin code is built into an easy to use jar module. On the JVM side Kotlin integration is easy, with an appropriate build tool (i.e. The context of the integration is a Web Application that uses a JVM on the server side (backend) and the Browser Application (frontend) is developed using a TypeScript based framework such as Angular or React (with the TypeScript option). I have simplified the integration by providing a Gradle-plugin that wraps up the complexity, but a full explanation is provided below for those of you that really want to understand the problems encountered and possible solutions. Some of the solution requires some fairly complex Gradle build script code.
This article describes the problems I encountered whilst integrating Kotlin generated modules with a TypeScript browser application, including, of course, how I overcame them. This is particularly useful for passing complex data structures between a frontend browser and a backend server.
In the context of web applications this Multiplatform feature of Kotlin enables us to write code once, in Kotlin, and then use that code on both a JVM backend and a JavaScript frontend. However, one thing I have found that makes Kotlin especially useful is that it targets multiple platforms, not just the JVM. Kotlin is one of many new languages that target the JVM.
0 kommentar(er)
