(Not actually related to your problem, but I did notice a typo -- ""asmScriot" instead of "asmScript".)
I don't really know what might be going on, but i do notice a couple things looking around in the devtools console:
* fetch chunks load scripts in parallel, and it looks like the second script you fetch might need something from the first -- if you put both scripts in one chunk you get an error "
TypeError: r is undefined"
* If you load those scripts sequentially by splitting up the fetches:
```
then you don't get the type error, but then below when you load the plugin chunk you get `
TypeError: can't redefine non-configurable property "signbit"` (and the plugin loader hangs, which is a bug :-( ... )
* if you comment out the second line of the fetch and let the plugin loader retrieve that file, you don't get any errors in devtools, but you get:
```
TypeError: assemblyscript.CompilerTarget is undefined
asmScript.eval()@cell:8:6
```
in the iodide console when trying to run the assemblyscript cell.
Maybe there is a clue in one of those things? @mdboom may be able to say more about how to write a plugin loader helper script that can streamline loading binaryen etc in the correct order, and generally has the most knowledge about wasm etc of anyone on our team. Hopefully he can help.
I think this is really exciting btw! Some of the performance wins potentially available from assemblyscript could make it very interesting for numerical computation and visualization. Please do continue to reach out, we'd love to help! And feel free to ping us on gitter if you want real time chat:
https://gitter.im/iodide-project/iodide
-brendan