Add webgpu async check

[whatisor]

Related issue: #29916

Description
We want to use WebGPU capability check in nodejs project.

[Mugen87]

With #29933 merged, what parts of the existing WebGPU.js cause issues with node?

[whatisor]

"await" cause issue because it does not allow Global scoped await.

[Mugen87]

So what you are saying is that node.js does not allow the top-level await in the module?

Instead of adding a separate module, I was hoping adding isAvailableAsync() to the existing WebGPU.js would also work.

[donmccurdy]

Node.js supports top-level await (TLA) in all active versions, but some tooling does not. Node.js v22+ has greatly improved ESM support over previous versions, with one notable limitation: CommonJS modules cannot import ESM modules that use TLA, for sync/async reasons.

But I'm not sure if CommonJS is related to the reported issues in Next.js. I'd like to reproduce the issue before we commit to a particular fix for it, see #29916 (comment). Possibly there are other options. I would have hoped a 'use client' directive in the Next.js component would be enough, in this case.

[whatisor]

The ideal is we want to remove all "global" stuff to make it best compatibility with node development.
Right now, I have no idea to support synced version of WebGPU.isAvailable() which is used in many examples folder.

[whatisor]

wait in the module

It will create confliction until we update repo @type/three

[whatisor]

The ideal is we want to remove all "global" stuff to make it best compatibility with node development. Right now, I have no idea to support synced version of WebGPU.isAvailable() which is used in many examples folder.

Also, I propose to update WebGPU and all example to async check (instead of global scope) because of limitation of current browser webgpu context checking.

[Mugen87]

Closing, see #29919 (comment).