[wasm-mt] Improved experience when SharedArrayBuffer is not available

[lambdageek]

Runtime JS should check that SharedArrayBuffer is available and if it isn't diagnose whether CORS headers are being served, and provide a nice error message.

For Blazor and Uno we should provide some kind of callback that can be triggered if the runtime's requirements are not met

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

Tagging subscribers to 'arch-wasm': @lewing
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Runtime JS should check that SharedArrayBuffer is available and if it isn't diagnose whether CORS headers are being served, and provide a nice error message.

For Blazor and Uno we should provide some kind of callback that can be triggered if the runtime's requirements are not met

Author:	lambdageek
Assignees:	-
Labels:	arch-wasm, untriaged, area-Threading-mono
Milestone:	-

[maraf]

@pavelsavara Is this resolved with the mentioned PR? Or should we do more?

[pavelsavara]

We don't read cors headers, but I'm not sure we really want to.
If we should, which files we should check ? And how to check it on ES6 import keyword ?

I'm closing this as done.