Manuel

Is this actually fixing a bug or just a refactor to not display a warning message?

What did this PR require? Only upgrading the dependency? I thought it was more because the definitions check [failed](https://github.com/parse-community/parse-server/actions/runs/13992689085/job/39180024608?pr=9625). I assume all the other changes are because you ran lint:fix?

I think we need to be careful running prettier across the whole code base. It could disrupt existing PRs, because the rebase may be difficult. We also have no automation...

Superseded by https://github.com/parse-community/parse-dashboard/pull/2958

@mbfakourii do you understand what is meant here?

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

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

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

To clarify, you can submit a PR at any time, but when it can be merged depends on its implications on our [compatibility policy](https://github.com/parse-community/Parse-SDK-Flutter/blob/master/packages/flutter/README.md#compatibility).

I wonder how this has been implemented. It doesn't seem to be an actual column when looking at the HTML. It's also that the header cell for the row numbers...