parseIsWeb doesn't work on WASM

[sgehrman]

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');

[parse-github-assistant[bot]]

Thanks for opening this issue!

[mtrezza]

@mbfakourii do you understand what is meant here?

[mbfakourii]

@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.

[mtrezza]

Got it. So we'd need to wait until all the dependencies support the option before the Parse SDK can support it?

[mbfakourii]

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

[mtrezza]

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

https://github.com/parse-community/Parse-SDK-Flutter/blob/a3449f4a1c4060f6afea71f50b204cb5e5a37bd2/packages/dart/lib/src/base/parse_constants.dart#L89

to

const bool parseIsWeb = bool.fromEnvironment('dart.library.js_util');

?

[mbfakourii]

Do we have to wait until all Parse SDK dependencies support the wasm option?

No, all dependencies need to be supported

[mtrezza]

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"?

[2shrestha22]

Do we have a list of packages that does not support WASM and is a dependency?

[mbfakourii]

Do we have a list of packages that does not support WASM and is a dependency?

Based on the reviews, we have a change in the parse_websocket_html.dart class. Also, the following packages need to be updated

package_info_plus: ^5.0.1 => package_info_plus: ^6.0.0

parse_server_sdk: ^6.4.0 in parse_server_sdk_flutter => last version

Dio must use dio_web_adapter: ^2.0.0 in last version

Note that package_info_plus must be updated according to our versioning policy.

[2shrestha22]

I would be happy to help to make it wasm compatible. May be I need know where to start from.

[mbfakourii]

I would be happy to help to make it wasm compatible. May be I need know where to start from.

Most likely in Feb 2025 we will support Wasm.

[2shrestha22]

Why in Feb 2025? Is there anything blocking this done before that?

[mbfakourii]

Why in Feb 2025? Is there anything blocking this done before that?

For our versioning policy.

[mtrezza]

To clarify, you can submit a PR at any time, but when it can be merged depends on its implications on our compatibility policy.