You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using vite + vue3 + this vad package Version 0.0.19.
In vite dev server everything works well, but when actually building and loading the extension I get the following error during the MicVAD initialization:
wasm streaming compile failed: 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'"
and further:
`
falling back to ArrayBuffer instantiation
(anonymous) @ ort-wasm-simd-threaded.mjs:22
ort-wasm-simd-threaded.mjs:21 failed to asynchronously prepare wasm: CompileError: WebAssembly.instantiate(): 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'"
(anonymous) @ ort-wasm-simd-threaded.mjs:21
ort-wasm-simd-threaded.mjs:20 Aborted(CompileError: WebAssembly.instantiate(): 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'")
`
There are many users who have successfully used this package in chrome extension like https://github.com/Pedal-Intelligence/saypi-userscript so I would be super grateful for any hint how to initialize the Model correctly for Manifest v3 Chrome extensions or where this problem could possibly stem from.
The text was updated successfully, but these errors were encountered:
I am using vite + vue3 + this vad package Version 0.0.19.
In vite dev server everything works well, but when actually building and loading the extension I get the following error during the MicVAD initialization:
wasm streaming compile failed: 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'"
and further:
`
falling back to ArrayBuffer instantiation
(anonymous) @ ort-wasm-simd-threaded.mjs:22
ort-wasm-simd-threaded.mjs:21 failed to asynchronously prepare wasm: CompileError: WebAssembly.instantiate(): 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'"
(anonymous) @ ort-wasm-simd-threaded.mjs:21
ort-wasm-simd-threaded.mjs:20 Aborted(CompileError: WebAssembly.instantiate(): 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'")
`
There are many users who have successfully used this package in chrome extension like https://github.com/Pedal-Intelligence/saypi-userscript so I would be super grateful for any hint how to initialize the Model correctly for Manifest v3 Chrome extensions or where this problem could possibly stem from.
The text was updated successfully, but these errors were encountered: