Requesting a BEX extension built on Quasar CLI with Vite implementing manifest version v3 as an example project
#12935
-
|
I read that Quasar BEX is supporting now manifest version v3 and CLI with Vite. I followed the related documentation but the generated project is running into many issues, so I suppose that I might be doing something wrong. For example, the default Content Script (my-content-script.js) generated by default includes the keyword 'export' but Chome is complaining about that: Uncaught SyntaxError: Unexpected token 'export' |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
You're not installing it in the browser from the correct location. Install it from dist/bex. This is an important difference from the usage in q/app-webpack. It's even highlithed in the terminal on quasar dev command. |
Beta Was this translation helpful? Give feedback.
-
|
Oh, I guess I didn't read that important part. From dist/bex the extension loaded successfully. Thanks a lot. |
Beta Was this translation helpful? Give feedback.
You're not installing it in the browser from the correct location. Install it from dist/bex. This is an important difference from the usage in q/app-webpack. It's even highlithed in the terminal on quasar dev command.