Describe the feature

When you run jiti on a file that, directly or indirectly, contains

await import("xyz.wasm")

then you get the following error:

Unknown file extension ".wasm" for xyz.wasm

Would be nice if jiti could transform/setup the loader to correct use wasm modules, perhaps either using unwasm or es-module-lexer.

Additional information

• Would you be willing to help implement this feature?