-
Notifications
You must be signed in to change notification settings - Fork 42
support flutter web wasm builds #112
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
Comments
Thanks for creating the issue. We'd need to:
mainly the While we'd like to support it, it's still a low priority since there are a few limitations to running wasm on the browser so we'd not do this right now but soonish, of course PRs are welcome, happy to guide anyway lending a hand here. |
I tried a little PR, currently I have issues with flutter 3.24 so I couldn't test it again when filing the PR, but this should work using dart:js_interop instead of dart:js. Feel free to use this PR/adjust it etc. |
a few things have to be fixed such as:
|
@marandaneto we are evaluating different product analytics solutions. From a technical perspective PostHog is definitely a standout with how well you support the different ecosystems and frameworks! The only place I can think of where you are now behind is WASM support :P Why is WASM important to us?We as simpleclub, are one of the biggest online education platform in Germany, selling to large German corporations. Being able to run our Flutter web app via WASM drastically reduces the resource consumptions, making our app more accessible to customers with lower end devices. Our customers use Edge in their day-to-day usage, which does support WASM-GC. |
@IchordeDionysos #114 (comment) |
Hey guys, thanks for the efforts! Where are we on this? Currently it's stopping us from building web with --WASM and it's very important for our platform. |
sadly not high prior, but happy to guide/review if you'd like to contribute. |
@marandaneto Thanks for the quick reply. Sry I'm not that familiar with native codes and channels. All I know is that the migration from dart:js to package:web is supposed to be very simple and straight forward. You can access the js object like this:
From there, you just need to convert the object types using this link. |
@EmadHedayati this issue has more context (comments) on what/where things must be changed and what was left in that PR. |
Version
4.5.0
Steps to Reproduce
in a flutter web project, build it with
flutter build web --wasm
Expected Result
it builds
Actual Result
it doesn't build
More Context
flutter web wasm builds are now in
stable
branch and it is now a reasonable expectation for packages to support it https://docs.flutter.dev/platform-integration/web/wasmThe text was updated successfully, but these errors were encountered: