I am struggling to get my compose web to run in a multiproje

Question

I am struggling to get my compose web to run in a multiproject multiplatform layout root project is defining all plugins but all with apply = false Now project compiles fine but `gradle jsBrowserRun` shows an empty Browser page I guess because build processedResources ends up in the subprojects build folder but build js ends up in the roots build folder how do I get this to work from the js being soley in the subproject

Big Chungus · Answer

do you have index html in your js resources referencing your ` module name js` file

Dirk Hoffmann · Answer

I only copied my working js project into the subproject folder of my multiproject layout its resources index html is unchanged ``` lt body gt lt div id= root gt lt div gt lt script src= minimal compose web js gt lt script gt lt body gt ```

Dirk Hoffmann · Answer

being in the suprojects src jsMain resources folder I just adjusted the src attribute to the name of the js suprojects name+ js

Dirk Hoffmann · Answer

```$ cp web src jsMain resources index html web build compileSync main productionExecutable kotlin $ chrome web build compileSync main productionExecutable kotlin index html``` it works if I copy over the index html to the generated productionExecutable But neither works on ` gradlew jsBrowserRun` nor on ` gradlew web jsBrowserRun`

Big Chungus · Answer

You shouldn t need to copy for jsBrowserRun

Big Chungus · Answer

Hold on your index html does get served right Otherwise you d see 404 page

Dirk Hoffmann · Answer

that s my understanding too But it doesn t find the `minimal compose web js` on jsBrowserrun

Big Chungus · Answer

what s your gradle module name

Dirk Hoffmann · Answer

subproject name is web ```include common android desktop web ```

Big Chungus · Answer

then your js file for jsBrowserRun will be `web js`

Dirk Hoffmann · Answer

aaaaah right that did it thanx

Dirk Hoffmann · Answer

so the local jsBrowserRun index html has to be a bit different than what I d deploy to a production site as there its name should be `minimal compose web js` instead of `web js`

Big Chungus · Answer

Not sure Run gradle build and see what gets packaged in build distribution

Big Chungus · Answer

I think it will still be web js

Dirk Hoffmann · Answer

yep you re right is still web js thanx for your blazing fast support I am sure even a bot would have struggled to beat your MTTR mean time to repair in this case slightly smiling face

Big Chungus · Answer

Hah faced this issue myself plenty of times so I know the pain all too well smile

Dirk Hoffmann · Answer

proves that nowadays a Brain is yet still stronger than AI slightly smiling face

Dirk Hoffmann · Answer

btw is there a doc site saying what Composable stuff does work with kotlin js compse and what of it only works with android desktop native

Big Chungus · Answer

Don t think so but basically only core and runtime compose artefacts are available for js No material stuff or foundation

Dirk Hoffmann · Answer

think for real write once run on any platform including web for compose we ll have to wait for WASM anyways at least my feel of it

Big Chungus · Answer

They re working on canvas based material support right now

Dirk Hoffmann · Answer

very keen on 1 6 20 therefore

Big Chungus · Answer

There s also my <http github com mpetuska kmdc|github com mpetuska kmdc> for accessibility conscious projects very experimental still

Dirk Hoffmann · Answer

they said it ll have webassembly target at least for multiplatform not sure about compose

Big Chungus · Answer

I would not expect WASM being anywhere close to production viable not even ready stable until late 2022

Dirk Hoffmann · Answer

atm just trying to convince my company to give compose a shot being still angular react so for me it would be enough if the current compose WASM support would just make them wow slightly smiling face

Big Chungus · Answer

Well current compose without wasm should still wow them

Big Chungus · Answer

Compare it with vanilla react

Big Chungus · Answer

All it s missing right now is some components lib But it handles plain DOM management exceptionally well

Big Chungus · Answer

And dev experience is amazing other than long reload times after change but that s kotlin issue

Dirk Hoffmann · Answer

well get people away from js ts is some religeous subject I think otherwise js ts would have extinguished long time ago