just noticed that the browserTest task in gradle, ...
# javascript
r
just noticed that the browserTest task in gradle, when using karma, doesn’t cache correctly when using a “custom launcher” (which is easily done by using the noSandbox chrome helper, or others). Seems like the root cause is package org.jetbrains.kotlin.gradle.targets.js.testing.karma.CustomLauncher not being a data class with a stable toString()
could be old news, but figured i’d say something. The caching of the task is based on the toString() of the karma config, hence the problem