You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I made sure that the issue I am raising doesn't already exist
Use case / Problem
We are hoping to use this package to create an exciting demo game (that uses Flutter and Flame) for an upcoming event. The game will support WASM, which is a critical product message Flutter team wants to land. Therefore, we would also appreciate it if this package could support WASM.
# Description
This PR migrates usage of `dart:html` and `package:js` to their new
replacements. It also updates version constraints and CI configuration
to account for the versions required. These changes enable compilation
to Wasm and improves compatibility with Dart's evolving web interop
story. There are potentially bundle size improvements as well.
Dart and Flutter will prefer `dart:js_interop`, extension types, and
`package:web` as used here going forward. Check out
https://dart.dev/interop/js-interop/package-web to learn more.
Fixes#1765
Checklist
Use case / Problem
We are hoping to use this package to create an exciting demo game (that uses Flutter and Flame) for an upcoming event. The game will support WASM, which is a critical product message Flutter team wants to land. Therefore, we would also appreciate it if this package could support WASM.
Proposal / Solution
Having a quick look, it looks like all the web code is here:
https://github.com/bluefireteam/audioplayers/tree/main/packages/audioplayers_web/lib
There's one file importing package:js and one file importing dart:html.
Hopefully these are the only two files that need to be touched in order to make the package compatible with WASM.
Example Code
Example Code
Affected platforms
web
Platform details
WASM specific support
Audio Files/URLs/Sources
No response
Mockups
No response
Related issues / more information
No response
Working on PR
no way
The text was updated successfully, but these errors were encountered: