Content Security Policy error on BEX dev mode using app-vite #17801
Labels
bug/1-repro-available
A reproduction is available and needs to be confirmed.
flavour/quasar-cli-vite
kind/bug 🐞
mode/bex
Qv2 🔝
Quasar v2 issues
What happened?
Good afternoon!
After updating to vite-app 2.x I'm no longer able to run BEX in development mode. The browser loads the extension, starts opening and closing multiple windows and the console outputs the following:
Refused to execute inline script because it violates the following Content Security Policy directive: "script-src 'self' 'wasm-unsafe-eval' 'inline-speculation-rules' http://localhost:* http://127.0.0.1:*". Either the 'unsafe-inline' keyword, a hash ('sha256-eV5p0xsw4UC/bJ48fZ5luze2UmXZbYuQMHs4vAKQynQ='), or a nonce ('nonce-...') is required to enable inline execution.
.This does not happen if I
quasar build -m bex -T chrome
the extension and load it afterwards.I'm using the latest quasar version and the latest vite-app version, and it happens even with an unmodified project created with
npm init quasar@latest
.Couldn't test it on firefox, unfortunately.
What did you expect to happen?
The browser extension to load and run without any problems.
Reproduction URL
https://stackblitz.com/edit/quasarframework-stackblitz-templates-7yyrnlxz?file=src%2Fpages%2FIndexPage.vue
How to reproduce?
npm init quasar@latest
)quasar mode add bex
)quasar dev -m bex -T chrome
Flavour
Quasar CLI with Vite (@quasar/cli | @quasar/app-vite)
Areas
BEX Mode
Platforms/Browsers
Chrome
Quasar info output
Relevant log output
Additional context
No response
The text was updated successfully, but these errors were encountered: