-
-
Notifications
You must be signed in to change notification settings - Fork 256
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[feature]: WebAssembly (Wasm) Support #1105
Comments
Thanks @BrunoMiguens for filing this, it's a very requested feature that we'll be adding in. We're working on some web apps for clients that also want WASM so it'll be in the up next column soon. |
Thanks, that's is great to know as it looks like there's not a lot of work, from a very high level perspective. |
Yup, lots to do there. I'll be dedicating a few days to it soon. |
@FilledStacks |
Awesome! Thanks @Schefferbird we'll do that and push and update to the services now |
Try version 1.5.1 of Stacked services and see if you can compile to WASM @BrunoMiguens |
@FilledStacks I have tried compiling for wasm with version 1.5.1 and still getting errors on the Get dependency. Apparently Get 4.6.6 still uses dart:html, their release candidate no longer has this issue, but this is not stable yet and is not compatible with stacked services atm. |
Is your feature request related to a problem? Please describe.
Currently
web_navigation_history.dart
usesdart:html
which is nt supported by Wasm and should be migrated topackage:web
- ReferenceDescribe the solution you would like
Replace the usage of
dart:html
to use the new web library and support the latest stable Wasm.As far as I could check, it should be a matter of changing the
_history.state
usage, however, I'm not sure if that is all.Additional Context
Flutter 3.22
Support for Wasm is now stable!
WebAssembly support for Flutter web is available on the Flutter stable channel.
Dart's next-gen web interop is now stable!
Migrate your packages to package:web and dart:js_interop to make them compatible with Wasm. Read the Requires JS-interop section to learn more.
The text was updated successfully, but these errors were encountered: