Fix: Incorrect usage of 'await' in WebGPU.js

[puxiao]

The previous code was very poorly readable.

isAvailable seems to be a Boolean value, but why does it suddenly become a GPUAdapter later?

The most critical error is: await can only run in async function !

If you use vite , when you write this line of code:

const renderer = new WebGPURenderer()

You will receive an error like this:

Top-level await is not available in the configured target environment ("chrome87", "edge88", "es2020", "firefox78", "safari14" + 2 overrides)

----------------

By the way, I don't understand the meaning of getStaticAdapter() at all. It feels completely unnecessary.

[Mugen87]

We do not fix top-level await usage, see #28107. This needs to be solved on bundler side.

BTW: Nothing at top-level await usage is "incorrect". It is a restriction of bundlers.

[puxiao]

I know it can be solved in the following way, but I still don't quite understand why.

vite.confit.js

export default defineConfig({
    ...
    optimizeDeps: {
        esbuildOptions: {
            target: 'esnext'
        }
    }
})

[Mugen87]

Sorry, but the change can't be merged. This breaks all example code.

[wcandillon]

@Mugen87 We are running three.js on Hermes which is very unlikely to support top level await anytime soon. You can see a demo of it here: https://x.com/wcandillon/status/1825862686300672124
To run such a demo, we need to apply to two tiny patches:

• remove top-level await by setting isAvailable to !!navigator.gpu
• And this small PR: ShaderNode: Remove .isArrayInput #29205

Do you think it's something that we could merge upstream eventually?