Does `@JsExport` work in wasm? If yes, could the `...

# webassembly

[mbonnin]

Does @JsExport work in wasm? If yes, could the JsAny bound of unsafeCast be removed (source)? Reason is I have @JsExport classes that I want to unsafe cast in common code and I don't have JsAny available in commonMain . Or is there another way?

[andylamax]

@JsExport doesn't work with wasm last time I checked

https://kotlinlang.slack.com/archives/CDFP59223/p1682147287374119?thread_ts=1682147287.374119&cid=CDFP59223

[mbonnin]

Welp, that settles it, thanks!

[Svyatoslav Kuzmich [JB]]

@JsExports currently does work for package-level functions, but classes are not supported yet.
unsafeCast upper bound will likely remain because we can’t unsafely cast Wasm values, while we can easily do this with JS values (they don’t care about static types).

[andylamax]

Shouldn't we introduce a different annotation WasmExport??

[andylamax]

Coz sometimes, I'd want to export my Js definition but no need to export my Typescript one. And I wan't to do all this from common code.

[Svyatoslav Kuzmich [JB]]

We have @WasmExport/@WasmImport pair, but they are a bit different. They used for exporting and importing raw functions to/from other .wasm modules instead of adapting values for JS.

[Svyatoslav Kuzmich [JB]]

I understand and agree with @andylamax use-case, JsExport shouldn’t apply additional restrictions for K/JS when used in common code. We remember it, but haven’t managed to fix it yet.

[mbonnin]

Thanks a lot for the details!

[andylamax]

Thanks a lot @Svyatoslav Kuzmich [JB]