/cc @neelance

The interface between src/syscall/js/js.go and misc/wasm/wasm_exec.js is internal and not stable. Wasmer can not use wasm_exec.js since it has no JavaScript runtime. So if Wasmer has support for syscall/js, then it seems to be a hack on their end which is using the internal interface. If there is any incompatibility with the new Go version, then it needs to be resolved on Wasmer's end. Please file an issue with the Wasmer project.

The problem is that syscall/js alone is presuming existence fo Nodejs Wasm constants, and it is doing it during declaration of variables. I can guess that it is current limitation, but could we postpone loading of variables from here:

https://github.com/golang/go/blob/master/src/syscall/fs_js.go#L26

I tried to prepare minimal reproducible code in repo: https://github.com/martinkunc/gowasmer

To reproduce, you can run

make build-wasm-1-14 && make build && ./wasmcmd

and then compare it with

make build-wasm-1-13 && make build && ./wasmcmd

I hope I am not using something which is only intended to work this way. I understand that WASMI is not stable, but maybe it might allow at least run at other runtimes, and I hope the change would be small one.

The error "bad type flag" is an internal error. It should not even be thrown if something is null or undefined.

The constants that you say are missing are in your own code: https://github.com/martinkunc/gowasmer/blob/master/wasm/bridge.go#L169
However, this "bridge" is a hack on an internal interface and apparently not compatible with the latest version of said interface.

Thank you for the explanation Richard and for pointing to my code and sorry for a confused report. I think I can close the issue. I will try to fix my hack.

Btw, thank you for all your hard work on the Wasm support :)

@martinkunc excuse me! Has this problem beem solved? How to solve it?

@BruceChoca Unfortunatelly I didn't continued on implementation of fs constants. Instead of what I did was I let my webassembly binary compiled on go 1.13 and built my host binary in latest go.
You can look at what I prepared here: https://github.com/martinkunc/wagather
It is PoC of collecting data from OpenShift Api (list of operators), What I did was I implemented Authenticated Http Proxy on the host, which I called from the webassembly.

@martinkunc thank u !
I found the reason, 1.14+ and 1.13+ typeflag is different. -> https://github.com/golang/go/blob/master/src/syscall/js/js.go#L280
u must modify the typeFlag to make is consistent.
modify function storeValue. -> https://github.com/martinkunc/gowasmer/blob/master/wasm/bridge.go#L352
https://github.com/martinkunc/gowasmer/blob/master/wasm/bridge.go#L420

typeFlag := 0
switch rt.Kind() {
case reflect.String:
	typeFlag = 1
case reflect.Func:
	typeFlag = 3
}

=>

switch rt.Kind() {
case reflect.String:
	typeFlag = 2
case reflect.Func:
	typeFlag = 4
case reflect.Struct:
 	typeFlag = 1
case reflect.Slice:
 	typeFlag = 1
}

u can try, hope it will solve your problem.