ESM isn't suited for importing objects containing non-JavaScript identifiers

[ghost]

Example:
A JavaScript module imports a Wasm module, the Wasm module is as follows:

(func (export "+") (param f64 f64) (result f64)
    local.get 0
    local.get 1
    f64.add
)

How does JavaScript import that?

Yes, ESM allows renaming imports, but it doesn' not allow surrounding them with quotes or something that would allow any name to be imported and renamed.

Currently, this would result in a syntax error:

import { "+" as add } from "./module.wasm";

How would this be handed?

[devsnek]

We are adding this exact functionality to JS: tc39/ecma262#2154

[ghost]

We are adding this exact functionality to JS: tc39/ecma262#2154

Oh perfect, beat me to it.
It seems to have already passed the proposal stage and is already being worked on implementation?
If so, I'll close this issue as it is no longer true.

[ExE-Boss]

You can already do the following, which is what I’d presume transpilers might do:

import * as _module_wasm from "./module.wasm";

And then instead of add, you’d use _module_wasm["+"].