So, if I'm
seeing it right, in MV3 the wasm won't work without changing CSP first to:
```
"content_security_policy": {
"extension_pages": "script-src 'self' 'wasm-unsafe-eval'; object-src 'self';"
},
```
Without that, it will fail with:
```
Uncaught (in promise) CompileError: WebAssembly.instantiateStreaming(): Refused to compile or instantiate WebAssembly module because neither 'wasm-eval' nor 'unsafe-eval' is an allowed source of script in the following Content Security Policy directive: "script-src 'self'"
```
I've never had to change CSP before so I'm not really comfortable to do so (I know malware extensions often relaxes CSP).
I guess I should focus on the real features and not fun optimizations :)