We're actually using runSkikoComposeUiTest() for roborazzi-compose-desktop, which should work seamlessly on WASM via Skiko. Perhaps we should consider renaming 'roborazzi-compose-desktop' to 'roborazzi-compose-skiko'. The issue is that Skiko isn't very well-known, so I'm curious about its adoption rate.
We're actually using runSkikoComposeUiTest() for roborazzi-compose-desktop, which should work seamlessly on WASM via Skiko. Perhaps we should consider renaming 'roborazzi-compose-desktop' to 'roborazzi-compose-skiko'. The issue is that Skiko isn't very well-known, so I'm curious about its adoption rate.