Differential D16261
[Cashtab] Modify extension manifest to support wasm Authored by bytesofman on May 31 2024, 22:35.
Details
Chrome extensions do not automatically allow wasm execution. This must be specified in a CSP directive in the manifest. Ref https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy The wasm-unsafe-eval directive, while scary looking, "Allows the loading and execution of WebAssembly modules without the need to also allow unsafe JavaScript execution" The web assembly is a bit of a black box -- however we are building it from a trusted source. npm run extension, load manually, it works
Diff Detail
Event Timeline
Comment Actions The local extension build fails as it can't find ecash-lib, even after I've npm ci'ed already. I assume this is likely to be a relative path issue?  Comment Actions
most likely ecash-lib is not built locally. I don't have the same issue, and Cashtab builds ok in the docker container now. cd modules/ecash-lib-wasm ./dockerbuild.sh cd ../ecash-lib npm run build cd ../../cashtab npm run extension does npm run build work in Cashtab but npm run extension fails? Comment Actions cd modules/ecash-lib-wasm ./dockerbuild.sh cd ../ecash-lib npm run build cd ../../cashtab npm run extension Yup it was this order of build that fixed the issue. Loaded extension manually and works fine. Comment Actions The above build order should probably be in one of the 3 module's README, given how the dependencies are relative now. | ||||||||||||||