Hey Guys, my wasm target is now failing. I used to...

# doodle

[Norris]

Hey Guys, my wasm target is now failing. I used to be able to run it before.

[Nick]

hmm. looks like gradle isn’t able to resolve dependencies. have you cleaned etc.?

[Norris]

Yes, just cleaned again

[Norris]

pasting build.gradle file

build.gradle.kts

[Norris]

Getting dependency error:

[Norris]

That is unrelated though.

[Nick]

do your JS or JVM builds work?

[Norris]

My JVM build works, but the JS build does not work

[Norris]

neither does the Wasm build

[Nick]

had they worked before? was there a change to the kotlin or doodle version that broke things? also, what does your gradle output look like? finally, were you prompted to do a yarn lock upgrade (not at comp now, so don’t remember the exact gradle task kotlin has for this)?

[Norris]

The wasm and JVM target worked after upgrading the yarn lock before. I am trying to figure out what has changed. I think this is definitely a dependency issue.

I am running the
• wasJSBrowserRun
• jsBrowserRun
• jsRun
Scripts.

They are all failing.

[Norris]

Due to this dependency issue

[Norris]

For wasmJSMain

[Norris]

for JSMain.

[Norris]

I do remember the IDE reporting that the framework was missing but when running the gradle script it ran fine.

[Norris]

I checked for updates but I am not seeing any. Not sure how to get pass this.

[Nick]

hmm. can try to repro when i have some time to see if i find a root cause.

[Nick]

wasn't able to reproduce your issue. here's a gist with essentially the new project i setup: https://gist.github.com/pusolito/7ca26c40b567f14966e4516d881a1e99. it excludes the jvm stuff for simplicity and has a very basic app that is inline (not sure if yours is in commonMain for example.

are you able to make the gist work? how about the code that is complaining about application not being found? is it in jsMain or wasmJsMain? this is where it needs to be.