Richard
Richard
I changed my code to: ```dart import 'dart:math'; import 'package:flutter/foundation.dart'; import 'package:flutter/material.dart'; import 'package:lottie/lottie.dart'; class QRCodeLoginNoScan extends StatelessWidget { const QRCodeLoginNoScan({super.key}); @override Widget build(BuildContext context) { var lottieDelegates = [...
https://github.com/dart-lang/test/issues/2278
Oh OK, I'll try asap.
by the way, the test preformance difference without coverage and with coverage for wasm is `4x`
```yaml platforms: [vm, chrome] compilers: [dart2wasm] on_platform: chrome: {timeout: 10x} ``` This really is a dart2wasm problem.
@osa1 so for now the best would be to get test coverage by dart2js or is it realistic to hope for a fix on the chrome side any soon?
@osa1 thanks for your investigation. Seems like we have to wait for the feature. Thx 😇
To anyone reading this issue: I guess showing to the chrome team, that there is demand for wasm code coverage support, is the best way to let it happen. Go...
This is a blocker at the moment: ~~https://github.com/dart-lang/sdk/issues/55031~~ Which has been fixed. This should work with the next Version of dart. For non wasm compilition it should already work. So...
@Ephenodrom Do you see any issues with this?