Make getStaticAdapter async

[wcandillon]

Related issues:
#28107
#26626
#28124

Description

We run three.js in an environnement where top-level await is not available. Making getStaticAdapter async fixes the issue. I couldn't find places where this method is used. Not sure if this approach is sensible, I'd love to hear your thoughts on this.

cc @RenaudRohlinger

[RenaudRohlinger]

Isn't there some kind of top-level await polyfill in react-native?

I recall discussing this and concluded that it’s more effective to address it within the development tooling. /cc @Mugen87

[wcandillon]

@RenaudRohlinger As far as I am aware top-level async is a very different kind of JS features that cannot be polyfilled because it makes the whole module system async. I'm the maintainer of React Native Skia and it's something we've looked at a lot because the Web Skia implementation is using WebAssembly and therefore the Web module loading is async.
@tmikov had a good summary on the topic here: facebook/hermes#1481 (comment)

[sunag]

I think we can remove WebGPU.isAvailable() from WebGPURenderer class if we have a callback for initialization error without breaking the examples for this

[wcandillon]

I'm very sympathetic to the argument of making this the bundler/env problem instead.
As an open-source maintainer myself, I think this is very sensible.

But of course since the change appears so minimal we would love if there is a fix for this as we would be able to run Three.js on React Native WebGPU without patching the build.
Below is a demo of a Three.js build that only contains two tiny changes: (one already landed) and this PR.

demo.mp4

@sunag I'm very excited that is an opportunity to maybe not use top-level await for now. Let me know if I can do anything to help. ❤️