Open dyaskur opened 3 years ago
If you then browse to http://127.0.0.1:8844/ do you get a page load? If not, what do you get?
Following the same steps as @dyaskur, i get similar output in the shell. The wep page at 127.0.0.1:8844 does not display anything but the loading gif for me.
Picture shows the network tab in chrome dev tools
Can you also provide the browser console output? It appears to be loading all the right things into the page, possibly the error is happening in-browser.
Image shows console output when following said steps. Following the link that leads to where the error occurs displays this output.
Same here:
wasm_exec.js is returning an empty file which is causing this error.
Copying this file in place with cp /usr/local/go/misc/wasm/wasm_exec.js dist/
(or the Windows equivalent) solves it.
@mertnacakgedigi I don't see any code in here to deal with wasm_exec.js. When you were testing this before did you just copy this file in place manually? The build process should be updated to include finding and copying that file in place, or as a quick fix we should at least document what the user needs to do to fix it manually.
💯 after cp wasm_exec.js to dist
and restarting the binary the demo now works.
I tried to do these steps:
and returned: