Extension types | Dart
JS interop | Dart
we would like to be allowed to rewrite the dart minsdk so that we can use the extension type that has been available since dart 3.3. Right now, the vscide extension refuses to allow rewriting.
environment:
sdk: ">=3.0.0 <4.0.0"
If this is not done, a compilation error occurs because minsdk is specified as 3.0.0 on the dart side.
If the minsdk is not set to 3.3.0 or higher, the compilation will not pass.
But now the extension type cannot be used because the rewrite is rejected.
What is troubling about this is that it forces me to write in dart:js, dart:js_util, package:js and dart:html, which are deprecated.
The current recommendations are
package:web,dart:
dart:js_interop,
dart:js_interop_unsafe
to be written with only three libraries.
When implementing a web implementation in PWA, it is necessary to use this package, but at that time, XXX.callmethod, etc. cannot be used in js_interop, so it is required to implement with the extension type recommended by js_interop. However, this is currently not possible. As a result, we have to rely on very old code and writing style.
What we asking FF for is permission to rewrite minsdk to 3.3.0, etc.
I understand that it may be consistent with other libraries, but we have tried it locally and FlutterFlow is running on build web with no problems at all as minsdk 3.3.0.
Please grant us permission to rewrite the minsdk part of this pubspec.yaml ASAP.
we think they are working on wasm support, but first of all, minsdk3.3.0 is required for full support of js_interop, which is necessary for that.