Closed jochem-brouwer closed 4 years ago
I'd kindly ask you to get wasm work with Karma standalone first, which is out of scope for this project. And I honestly have no clue / hint for you where you should start looking.
If that works it makes sense to investigate the missing bits that keep karma-browserify from handling it.
Does that make sense?
Yup, it does, thanks!
We are having a very hard time to get karma-browserify (or possibly karma itself) to work with wasm: https://github.com/ethereumjs/ethereumjs-vm/pull/785. We have tried setting
handleBinaryFiles
totrue
, including themime
wasm type, but karma either reports thathandleBinaryFiles
is set tofalse
or thatwasm
is an unknown file which will then default tojs
(which obviously fails).There do not seem to be any issues about this. Is wasm supported? How do we get it to run with wasm? We'd rather just fetch it as a static file and import the binary directly, but this is not possible (seems we get a
400
code from Karma).