-
-
Notifications
You must be signed in to change notification settings - Fork 194
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
parseIsWeb doesn't work on WASM #1018
Comments
Thanks for opening this issue! |
@mbfakourii do you understand what is meant here? |
What they mean is the new wasm option, which is used to increase the output of Flutter Web. This feature is currently at the beginning of the work and many packages still do not support this feature, including the dependencies that are in the Parse Flutter project. |
Got it. So we'd need to wait until all the dependencies support the option before the Parse SDK can support it? |
Yes, we should wait |
Do we have to wait until all Parse SDK dependencies support the wasm option? Or is the issue only related to that one single code line that has been mentioned above, and is the solution to change
to
? |
No, all dependencies need to be supported |
I don't understand your response. Do you mean "Yes we need to wait for all dependency maintainers to support WASM, before we can support WASM?", or "No, we can make changes in our SDK to support WASM without waiting for the dependencies"? |
const bool parseIsWeb = identical(0, 0.0);
fails on wasm.
Why not do the normal thing?
I see this code is dart and not flutter. Flutter does it this way which I assume works.
const bool parseIsWeb = bool.fromEnvironment('dart.library.js_util');
The text was updated successfully, but these errors were encountered: