Any setup improvements for the jsTest task in a multiplatform build? I cobbled together my own proce...

# javascript

[Rob Murdock]

Any setup improvements for the jsTest task in a multiplatform build? I cobbled together my own process near the beginning of 2019 and am hoping things have improved (especially unpacking the js dependency tree to a location that a js test process can access it)

[snrostov]

jsTest works out of the box since 1.3.40. Just write browser {} or nodejs inside js target and it should work.

kotlin {
   targets {
     js {
        browser {
        }
     }
   }
}

https://kotlinlang.org/docs/reference/js-project-setup.html

[Rob Murdock]

excellent, it was not clear to me that this was for both the multiplatform plugin and the kotlin(*js”) plugin

[Rob Murdock]

trying it now 🙂

[Rob Murdock]

the functions browser & nodejs are both available, but they appear to fail for me when using the multiplatform plugin. I’ll keep poking.

The error is:

Cannot add task ‘clean’ as a task with that name already exists.

[Rob Murdock]

(I triple checked that I’m not adding any clean functionality myself 😅)

[Rob Murdock]

Looks like it must be a plugin interaction, as the behavior doesn’t exhibit in a simple project. Should be easy enough to fix. 🙂

[Rob Murdock]

On further investigation, it looks like it was fighting with tasks I’d declared in the “root” of my multiproject build, which I didn’t expect a Gradle plugin to do. I think I can figure out a workaround.

[Rob Murdock]

Running into a different, and maybe more fun, problem now - I need my tests to be able to access files from src/commonTest/resources, while running in the slick nodejs runner (very nice!). My google-jitsu has failed me for a long time to find a “standard” multiplatform resource loading style in Kotlin, so any tips would be appreciated.

[turansky]

Do you really need nodejs target?

[turansky]

Could you use browser instead?

[turansky]

Webpack config example for browser target - https://github.com/turansky/yfiles-kotlin/blob/master/gradle-plugin-test/webpack.config.d/resources.js

[Rob Murdock]

worth considering. Does it solve that problem?

[Rob Murdock]

Ah I see what you’re doing. Its not far off from my interim solution, which is require with an ugly directory jumping hardcoded path. I keep hoping for a cleaner solution 😅

[turansky]

I'm waiting for standard resources support too!