Default to AssetMetaCheck::Never on wasm targets

[UkoeHB]

What problem does this solve or what need does it fill?

Most people building for the web need AssetMetaCheck::Never to load assets properly. Many people have wasted a lot of time debugging their web builds as a result.

What solution would you like?

Default to AssetMetaCheck::Never on wasm targets.

What alternative(s) have you considered?

None

[andriyDev]

For my own learning (since I haven't needed web builds yet): why does web need AssetMetaCheck::Never? What breaks here? Does this only apply when not using asset processing?

[mockersf]

this is only happening with games deployed on itch.io: for files that don't exists, itch.io doesn't reply a 404 but a 403 and that's considered as a file error by Bevy instead of a file missing

[mockersf]

marking as controversial as we try to avoid different defaults per platform

[rparrett]

I think that all 400-level errors should probably be treated as missing files on the web, personally.

this is only happening with games deployed on itch.io

There's a separate issue with dev web servers that default to an SPA mode where missing assets are served with a 200 response (but that response is the content if index.html).

The amount of grief these two issues give users makes it tempting to agree with this request, but I think the situation will be a little different once bevy_asset gets a little more love and meta files become more commonly used. Then people will have the opposite problem of not knowing why their assets aren't being loaded with the correct settings.

Very soon, I think that bevy_cli will help a lot with this. That will be the obvious and easiest way to do local Bevy web dev.