wasm docs should mention CSP requirement

[paulmillr]

wasm is disabled in browser extensions by default because of CSP. Other, security-concious consumers, may enable CSP per-domain, outside of web extensions, on simple web pages.

One needs specific wasm-unsafe-eval header to make it work.

see https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/Content_Security_Policy

https://developer.chrome.com/docs/extensions/reference/manifest/content-security-policy

Where did you find it?

https://oxlib.sh/guides/engine

[jxom]

Thanks! I also just noticed AWASM, so I might switch to that.