-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CSP issue #146
Comments
I am having the same issue. I have 700 users who are now unable to use their extension... don't we just love Chrome randomly updating things like this. |
+1 |
For anyone encountering this issue, here's a super simple fix that works for me and T0RNATO: In vite config webExtension({
manifest: getManifest(version),
+ useDynamicUrlWebAccessibleResources: false,
}), |
This helped, big thanks @SleepyStew ! |
Awesome, thanks a lot! |
I'm wondering why we have to explicitly set it to vite-plugin-web-extension/README.md Lines 165 to 168 in fd56ebb
|
@DerStimmler yeah it is strange isn't it. Searching through this repo I found quite a few (although old) files where it was documented to set |
Yes, the type definition claims that the default is vite-plugin-web-extension/types/index.d.ts Lines 33 to 37 in fd56ebb
I'm not 100% sure, but I think the default is set here in line 17: vite-plugin-web-extension/src/utils/getAdditionalInputAsWebAccessibleResource.ts Lines 3 to 19 in fd56ebb
|
Hi, I wanted to create a simple manifest v3 extension but get the following two errors when I open the default popup:
This happens in my extension but also when I create a new project with
npm init @samrum/vite-plugin-web-extension@latest
and leave everything as it is.It hasn't worked on Chrome v129 and now after I updated to v130.0.6723.59 still the same problem.
The text was updated successfully, but these errors were encountered: