Request for workaround or removal of `WebAssembly.Module()` from `@web3auth/openlogin-adapter` due to Chrome manifest V3 restrictions

Help - Plug n Play
1
  • The @web3auth/openlogin-adapter package runs WebAssembly.Module() in the global scope.
  • Manifest V3 does not allow WebAssembly. (Overview of the Chrome Extension Manifest V3 - Chrome Developers)
  • Chrome Web Store now allows only MV3 extensions to be uploaded.
  • In other words, wallet extensions using the @web3auth/openlogin-adapter package are no longer eligible for registration in the Chrome Web Store.

I’ve built a minimal demo to prove what I’m saying. (GitHub - simcheolhwan/demo-openlogin-adapter-mv3: demo-openlogin-adapter-mv3)
If you install this and upload the dist folder as a Chrome extension, you will see the following error.
The dist folder is the result of a vite build.

WebAssembly.Module(): 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'"

Just in case, as soon as you add wasm-eval to manifest, it returns an error as soon as you add the dist folder to Chrome.
Is it possible to remove WebAssembly.Module() from your sdk? Or is there any workaround?

2

5.2.0 solved this.

Thank you :slight_smile:

1 Like
3

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.