Hi,
We are working on a Compose Multiplatform proj...
# multiplatformp
pedram
02/22/2025, 11:56 AMHi,
We are working on a Compose Multiplatform project and want to modularize it in a way that avoids generating a single large JS and WASM output files (e.g., composeApp.js). The reason is that as the project grows, the file size is increasing, leading to delays in loading the web application.
Our goal is to have separate JS output files for different modules. For example, we would like Feature-A to have its own JS file, which should appear in the dist package of the main module when built. In our module graph, the Compose App module would act as the main module, with dependencies and other modules structured accordingly.
However, we are unsure of the best way to achieve this in Kotlin Multiplatform. Do you have any suggestions or best practices for structuring the project to generate separate JS outputs for different modules?
Thanks in advance for your help!
5 Views