CSP Issue on Chrome 130+ #918

sebastienfontaine · 2024-09-15T10:10:30Z

Build tool

Vite

Where do you see the problem?

In the browser
In the terminal

Describe the bug

When using Chrome version 130 and above, a browser error occurs when loading the content.js script.

content.ts-loader-DE-4zCml.js:

Refused to load the script 'chrome-extension://65fbf486-37dc-4a71-a17e-a567b680778b/assets/content.ts-B_w-r5D-.js' 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:*". Note that 'script-src-elem' was not explicitly set, so 'script-src' is used as a fallback.

TypeError: Failed to fetch dynamically imported module: chrome-extension://65fbf486-37dc-4a71-a17e-a567b680778b/assets/content.ts-B_w-r5D-.js

Reproduction

Clone this repository: https://github.com/furybee/crxjs-extension, or create a new repository with a content.js file as content_scripts.

Run the following command:

npm run build

Import the extension into Chrome 130+ (Canary Builds): https://www.google.com/chrome/canary/

Check the console to see the error.

Logs

No response

System Info

System:
    OS: macOS 14.5
    CPU: (10) arm64 Apple M2 Pro
    Memory: 77.75 MB / 16.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 20.12.2 - ~/.nvm/versions/node/v20.12.2/bin/node
    Yarn: 1.22.22 - ~/.yarn/bin/yarn
    npm: 10.5.0 - ~/.nvm/versions/node/v20.12.2/bin/npm
    Watchman: 2024.05.06.00 - /opt/homebrew/bin/watchman
  Browsers:
    Chrome: 128.0.6613.138
    Chrome Canary: 130.0.6719.0
    Edge: 128.0.2739.79
    Safari: 17.5
  npmPackages:
    @crxjs/vite-plugin: ^2.0.0-beta.25 => 2.0.0-beta.25 
    vite: ^5.4.1 => 5.4.5

manifest.json

{
  "manifest_version": 3,
  "name": "CRXJS Vue Vite Example",
  "version": "1.0.0",
  "action": { "default_popup": "index.html" },
  "content_scripts": [{
    "matches": [ "*://*/*" ],
    "js": [
      "src/content.ts"
    ]
  }]
}

Severity

🚨 blocking all usage of crxjs 🚨

The text was updated successfully, but these errors were encountered:

trungpv1601 · 2024-09-16T01:44:15Z

Same 🚨

My solution for build production

remove chrome.runtime.getURL in content script

(function () {
  'use strict';

  (async () => {
    await import("./chunk-b674a675.js");
  })().catch(console.error);

})();

matteing · 2024-09-16T18:23:05Z

Having the same issue as well.,

pnd280 · 2024-09-20T16:48:28Z

I worked around this by setting use_dynamic_url to false. But even if you don't use use_dynamic_url in manifest.ts, the compiled manifest.json will still have it, and crxjs doesn't have the option to disable it. So one might try to write a Vite plugin to forcefully remove them from the compiled manifest.json.

pnd280 · 2024-09-21T04:08:14Z

It's not only about this CSP issue; it's always been frustrating to work with CRXJS. The docs are the worst I've ever seen. The dev runtime doesn't even work on Firefox. For my project, it has become a debt now. I want to move away from it, but I can't find an alternative that supports HMR for integrated CSUIs (not iframe). I've tried out wxt and plasmo but had no luck. I would much appreciate if someone could recommend alternatives.

trungpv1601 · 2024-09-21T04:14:58Z

It's not only about this CSP issue; it's always been frustrating to work with CRXJS. The docs are the worst I've ever seen. The dev runtime doesn't even work on Firefox. For my project, it has become a debt now. I want to move away from it, but I can't find an alternative that supports HMR for integrated CSUIs (not iframe). I've tried out wxt and plasmo but had no luck. I would much appreciate if someone could recommend alternatives.

Same idea with you but not found the best one 👨‍💻

Firefox does not support MV3 yet. So for me, only focus on Chrome.

Still using this hot-fix for v130.

#918 (comment)

pietrofxq · 2024-09-24T00:25:59Z

It's not only about this CSP issue; it's always been frustrating to work with CRXJS. The docs are the worst I've ever seen. The dev runtime doesn't even work on Firefox. For my project, it has become a debt now. I want to move away from it, but I can't find an alternative that supports HMR for integrated CSUIs (not iframe). I've tried out wxt and plasmo but had no luck. I would much appreciate if someone could recommend alternatives.

Same idea with you but not found the best one 👨‍💻

Firefox does not support MV3 yet. So for me, only focus on Chrome.

Still using this hot-fix for v130.

#918 (comment)

I think it supports it now. I've ported my MV3 extension to firefox with almost no changes.

trungpv1601 · 2024-09-24T02:16:51Z

It's not only about this CSP issue; it's always been frustrating to work with CRXJS. The docs are the worst I've ever seen. The dev runtime doesn't even work on Firefox. For my project, it has become a debt now. I want to move away from it, but I can't find an alternative that supports HMR for integrated CSUIs (not iframe). I've tried out wxt and plasmo but had no luck. I would much appreciate if someone could recommend alternatives.

Same idea with you but not found the best one 👨‍💻
Firefox does not support MV3 yet. So for me, only focus on Chrome.
Still using this hot-fix for v130.
#918 (comment)

I think it supports it now. I've ported my MV3 extension to firefox with almost no changes.

Nice 😊. Thank you for your information. I will take a look

scisley · 2024-09-25T23:59:31Z

This seems like a big deal. I've just got my first complaint about my extension not working (a user has Chrome Beta). Took me forever to find that this was the problem. Seems like this will impact every extension soon or am I missing something?

I don't think the workaround posted earlier (#918 (comment)) will work for me. I need to call chrome.runtime.getURL in my content script.

trungpv1601 · 2024-09-26T00:01:49Z

This seems like a big deal. I've just got my first complaint about my extension not working (a user has Chrome Beta). Took me forever to find that this was the problem. Seems like this will impact every extension soon or am I missing something?

I don't think the workaround posted earlier (#918 (comment)) will work for me. I need to call chrome.runtime.getURL in my content script.

Can you show example in your code? I will help

pnd280 · 2024-09-26T02:18:50Z

This seems like a big deal. I've just got my first complaint about my extension not working (a user has Chrome Beta). Took me forever to find that this was the problem. Seems like this will impact every extension soon or am I missing something?

I don't think the workaround posted earlier (#918 (comment)) will work for me. I need to call chrome.runtime.getURL in my content script.

here's how I worked around this issue pnd280/complexity#7

trungpv1601 · 2024-09-26T02:29:27Z

This seems like a big deal. I've just got my first complaint about my extension not working (a user has Chrome Beta). Took me forever to find that this was the problem. Seems like this will impact every extension soon or am I missing something?

I don't think the workaround posted earlier (#918 (comment)) will work for me. I need to call chrome.runtime.getURL in my content script.

More attachment on how to hot-fix my extensions

After building, you should edit it like this. I hope it helps.

scisley · 2024-09-26T16:43:56Z

@trungpv1601, @pnd280 - thank you both! The extra details allowed me to piece together a solution.

Toumash · 2024-09-27T14:07:57Z

Are we able prepare a PR for that change or more work is needed?

trungpv1601 · 2024-09-28T00:35:44Z

This seems like a big deal. I've just got my first complaint about my extension not working (a user has Chrome Beta). Took me forever to find that this was the problem. Seems like this will impact every extension soon or am I missing something?
I don't think the workaround posted earlier (#918 (comment)) will work for me. I need to call chrome.runtime.getURL in my content script.

here's how I worked around this issue pnd280/complexity#7

I think this is the best solution for now. It works well for Chrome and Firefox builds.

Thank you @pnd280 🙏

Lonolf · 2024-09-30T13:34:41Z

Same problem, we use our extension with InboxSDK to insert some buttons in the gmail page.
I was able to temporary fix the extension by changing the "use_dynamic_url" flag in the builded manifest to false, but we hope in a more stable solution

quentin-decre · 2024-10-16T10:47:52Z

Can we expect a PR to handle that ? Is someone already on that ?

salmin89 · 2024-10-16T13:43:16Z

is this an issue with chrome that needs to be reported? how come use_dynamic_url became a problem all of a sudden?

pietrofxq · 2024-10-16T14:23:49Z

is this an issue with chrome that needs to be reported? how come use_dynamic_url became a problem all of a sudden?

Looks like support for that property was actually just added in Chrome 130:

https://developer.chrome.com/blog/extension-news-october-2024

Starting in Chrome 130, we will enable support for the use_dynamic_url property on entries under the web_accessible_resources key in the manifest.

I don't know why CRXJS marks it as true in the final manifest.json, looks like a simple PR that removes it would be enough?

pietrofxq · 2024-10-16T14:38:00Z

FIX WITH PATCH-PACKAGE (DEV AND BUILD)

Add patch-package:

yarn add --dev patch-package

Change the use_dynamic_url flag to false in node_modules/@crxjs/vite-plugin/dist/index.mjs in lines 1842 and 1924:

use_dynamic_url: false

Run patch-package:

npx patch-package @crxjs/vite-plugin

Add patch-package to postinstall script in package.json:

"postinstall": "patch-package"

This fixes the issue at the source so it will work correctly in both dev and prod builds

PS: If you are using yarn 3, this can be fixed with yarn patch instead of patch-package

FIX WITH NODEJS SCRIPT (BUILD ONLY)

create a js script, e.g set-dynamic-url.cjs. Update the path of manifest if needed to reflect your folder structure

const fs = require('node:fs')
const path = require('node:path')
const manifest = require('../dist/manifest.json')

const webAccessibleResources = manifest.web_accessible_resources

const updatedWebAccessibleResources = webAccessibleResources.map(resource => {
  if (resource.use_dynamic_url) {
    return {
      ...resource,
      use_dynamic_url: false,
    }
  }
  return resource
})

manifest.web_accessible_resources = updatedWebAccessibleResources

const json = JSON.stringify(manifest, null, 2)
fs.writeFileSync(path.resolve(__dirname, '../dist/manifest.json'), json, 'utf8')

Add it to postbuild under package.json scripts:

"build": "vite build",
"postbuild": "node ./scripts/set-dynamic-url.cjs",

Now the manifest.json in the dist folder will be automatically patched when running yarn build

scarletczen · 2024-10-16T15:58:39Z

For now, the production build works using @pnd280 's solution (thank you), dev mode is still an issue, did anyone get it to work yet?

salmin89 · 2024-10-16T16:08:30Z

I threw together this hack plugin that uses fs.watchFile to update manifest.json in dev mode (works normally for build)
I'm no expert on vite-plugins so feel free to modify or share something more robust.

import path from 'node:path';
import fs from 'fs';
import { PluginOption } from 'vite';
import { ManifestV3Export } from '@crxjs/vite-plugin';

const manifestPath = path.resolve('dist/manifest.json'); // your manifest output location

export function updateManifestPlugin(): PluginOption {
  return {
    name: 'update-manifest-plugin',
    enforce: 'post',
    closeBundle() {
      forceDisableUseDynamicUrl();
    },

    configureServer(server) {
      server.httpServer?.once('listening', () => {
        const updated = forceDisableUseDynamicUrl();
        if (updated) {
          server.ws.send({ type: 'full-reload' });
          console.log('** updated **');
        }

        fs.watchFile(manifestPath, (data) => {
          console.log('** watchFile ** ');
          const manifestContents = JSON.parse(fs.readFileSync(manifestPath, 'utf8'));
          if (manifestContents.web_accessible_resources.some((resource: any) => resource.use_dynamic_url)) {
            const updated = forceDisableUseDynamicUrl();
            if (updated) {
              server.ws.send({ type: 'full-reload' });
              console.log('** updated **');
            }
          }
        });
      });
    },

    writeBundle() {
      console.log('### writeBundle ##');
      forceDisableUseDynamicUrl();
    },
  };
}

function forceDisableUseDynamicUrl() {
  if (!fs.existsSync(manifestPath)) {
    return false;
  }

  const manifestContents = JSON.parse(fs.readFileSync(manifestPath, 'utf8')) as Awaited<ManifestV3Export>;

  if (typeof manifestContents === 'function' || !manifestContents.web_accessible_resources) return false;
  if (manifestContents.web_accessible_resources.every((resource) => !resource.use_dynamic_url)) return false;

  manifestContents.web_accessible_resources.forEach((resource) => {
    if (resource.use_dynamic_url) resource.use_dynamic_url = false;
  });

  fs.writeFileSync(manifestPath, JSON.stringify(manifestContents, null, 2));
  return true;
}

use normally in vite.config.ts

    plugins: [react(), crx({ manifest }), updateManifestPlugin()],

pietrofxq · 2024-10-16T16:32:52Z

my solution above with patch-package fixes it for dev and build modes

salmin89 · 2024-10-16T16:38:28Z

my solution above with patch-package fixes it for dev and build modes

I'm not using yarn tho

pietrofxq · 2024-10-16T16:43:07Z

my solution above with patch-package fixes it for dev and build modes

I'm not using yarn tho

yarn is not required, patch-package is a npm package. Just change it to

npm install --save-dev patch-package

salmin89 · 2024-10-16T16:45:40Z

I will test that approach out. Thanks!

oliverdunk · 2024-10-25T09:44:48Z

Hi all, just checking in to say that we've landed a fix for this which is available in today's Chrome Canary (looks like @allcentury was ahead of me!). We appreciated all of the feedback - the impact here was greater than we hoped and it allowed us to prioritize working on the change. I also apologize for the lacks of heads up about this one - we did some outreach to vite-plugin-web-extension ahead of time but I didn't realize CRX.JS was also impacted.

See crxjs/chrome-extension-tools#918

chauanhtuan185 · 2024-10-28T02:02:23Z

I threw together this hack plugin that uses fs.watchFile to update manifest.json in dev mode (works normally for build) I'm no expert on vite-plugins so feel free to modify or share something more robust.

import path from 'node:path';
import fs from 'fs';
import { PluginOption } from 'vite';
import { ManifestV3Export } from '@crxjs/vite-plugin';

const manifestPath = path.resolve('dist/manifest.json'); // your manifest output location

export function updateManifestPlugin(): PluginOption {
  return {
    name: 'update-manifest-plugin',
    enforce: 'post',
    closeBundle() {
      forceDisableUseDynamicUrl();
    },

    configureServer(server) {
      server.httpServer?.once('listening', () => {
        const updated = forceDisableUseDynamicUrl();
        if (updated) {
          server.ws.send({ type: 'full-reload' });
          console.log('** updated **');
        }

        fs.watchFile(manifestPath, (data) => {
          console.log('** watchFile ** ');
          const manifestContents = JSON.parse(fs.readFileSync(manifestPath, 'utf8'));
          if (manifestContents.web_accessible_resources.some((resource: any) => resource.use_dynamic_url)) {
            const updated = forceDisableUseDynamicUrl();
            if (updated) {
              server.ws.send({ type: 'full-reload' });
              console.log('** updated **');
            }
          }
        });
      });
    },

    writeBundle() {
      console.log('### writeBundle ##');
      forceDisableUseDynamicUrl();
    },
  };
}

function forceDisableUseDynamicUrl() {
  if (!fs.existsSync(manifestPath)) {
    return false;
  }

  const manifestContents = JSON.parse(fs.readFileSync(manifestPath, 'utf8')) as Awaited<ManifestV3Export>;

  if (typeof manifestContents === 'function' || !manifestContents.web_accessible_resources) return false;
  if (manifestContents.web_accessible_resources.every((resource) => !resource.use_dynamic_url)) return false;

  manifestContents.web_accessible_resources.forEach((resource) => {
    if (resource.use_dynamic_url) resource.use_dynamic_url = false;
  });

  fs.writeFileSync(manifestPath, JSON.stringify(manifestContents, null, 2));
  return true;
}

use normally in vite.config.ts

    plugins: [react(), crx({ manifest }), updateManifestPlugin()],

I seem change use_dynamic_url to false will fix the problem right now

Toumash · 2024-10-28T13:10:30Z

Should we close this now, since jack released a fix in @crxjs/[email protected] Pre-release
?

Reactiver · 2024-10-28T20:14:05Z

#918 (comment)

That works, thanks!

Martizs · 2024-10-29T09:08:33Z

@jacksteamdev it works perfect for me on 2.0.0-beta.26. Thanks everyone!

updating to 2.0.0-beta.26 works! Thanks!

SanderMuller · 2024-10-29T10:19:14Z

Will there be a patch for v1? It's nice that v2.0.0-beta.26 fixes the error, but I would rather not ship a major upgrade in beta stage as a hotfix for this issue

Are we going to get a fix on the stable version (v1)? I appreciate the quick fix but now the only solution is to use a beta version.

Tharusha-dev · 2024-11-06T08:06:02Z

Hi,

After upgrading to 2.0.0-beta.26 i get this error


failed to load config from /home/tharusha/Downloads/li_extension_test_1_source/vite.config.js
error when starting dev server:
TypeError: (0 , import_vite_plugin.crx) is not a function
    at Object.<anonymous> (/home/tharusha/Downloads/li_extension_test_1_source/vite.config.js:66:32)
    at Module._compile (node:internal/modules/cjs/loader:1364:14)
    at require.extensions.<computed> [as .js] (/home/tharusha/Downloads/li_extension_test_1_source/node_modules/vite/dist/node/chunks/dep-0a035c79.js:62011:20)
    at Module.load (node:internal/modules/cjs/loader:1203:32)
    at Module._load (node:internal/modules/cjs/loader:1019:12)
    at Module.require (node:internal/modules/cjs/loader:1231:19)
    at require (node:internal/modules/helpers:177:18)
    at loadConfigFromBundledFile (/home/tharusha/Downloads/li_extension_test_1_source/node_modules/vite/dist/node/chunks/dep-0a035c79.js:62019:17)
    at loadConfigFromFile (/home/tharusha/Downloads/li_extension_test_1_source/node_modules/vite/dist/node/chunks/dep-0a035c79.js:61938:32)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5

crxjs/chrome-extension-tools#918

In Chrome 1.30 and 1.31 there's a bug that caused plugins using the chrome.runtime.getURL(...) function loading failures from CSP errors. This should be fixed in v1.32. A fix is also in the crxjsv2 plugin. Refs: https://issues.chromium.org/issues/363027634?pli=1 crxjs/chrome-extension-tools#918 https://www.reddit.com/r/webdev/comments/1gf0v2p/suddenly_getting_content_security_policy_error_in/

* Updates vite and vite crxjs plugin In Chrome 1.30 and 1.31 there's a bug that caused plugins using the chrome.runtime.getURL(...) function loading failures from CSP errors. This should be fixed in v1.32. A fix is also in the crxjsv2 plugin. Refs: https://issues.chromium.org/issues/363027634?pli=1 crxjs/chrome-extension-tools#918 https://www.reddit.com/r/webdev/comments/1gf0v2p/suddenly_getting_content_security_policy_error_in/

Hema-Bala · 2024-11-25T05:35:06Z

Hi,

After upgrading to 2.0.0-beta.26 i get this error


failed to load config from /home/tharusha/Downloads/li_extension_test_1_source/vite.config.js
error when starting dev server:
TypeError: (0 , import_vite_plugin.crx) is not a function
    at Object.<anonymous> (/home/tharusha/Downloads/li_extension_test_1_source/vite.config.js:66:32)
    at Module._compile (node:internal/modules/cjs/loader:1364:14)
    at require.extensions.<computed> [as .js] (/home/tharusha/Downloads/li_extension_test_1_source/node_modules/vite/dist/node/chunks/dep-0a035c79.js:62011:20)
    at Module.load (node:internal/modules/cjs/loader:1203:32)
    at Module._load (node:internal/modules/cjs/loader:1019:12)
    at Module.require (node:internal/modules/cjs/loader:1231:19)
    at require (node:internal/modules/helpers:177:18)
    at loadConfigFromBundledFile (/home/tharusha/Downloads/li_extension_test_1_source/node_modules/vite/dist/node/chunks/dep-0a035c79.js:62019:17)
    at loadConfigFromFile (/home/tharusha/Downloads/li_extension_test_1_source/node_modules/vite/dist/node/chunks/dep-0a035c79.js:61938:32)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5

getting the same issue

package.json has the following dependencies:
"@crxjs/vite-plugin": "^2.0.0-beta.28",
"vite": "4.3.1",

tabomagic · 2024-11-25T22:50:51Z

I am seeing this error with @crxjs/vite-plugin 2.0.0-beta.28 on Chrome 131.0.

Starting from the default project template, I updated the manifest.json to:

{
  "manifest_version": 3,
  "name": "CRXJS React Vite Example",
  "version": "1.0.0",
  "action": { "default_popup": "index.html" },
  "permissions": ["activeTab"],
  "content_scripts": [
     {
        "matches": ["<all_urls>", "file://*/*"],
         "js": ["src/content.js"]
     }
  ]
}

And created this very simple content.js file:

console.log("this is my content script")

Loading any site with this extension enabled gives the following error:

content-script-loader.content.cf5e09e9.js:7 Refused to load the script 'chrome-extension://32964004-721d-4b1f-9a38-db85a4190627/content.js' 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:*". Note that 'script-src-elem' was not explicitly set, so 'script-src' is used as a fallback.

TypeError: Failed to fetch dynamically imported module: chrome-extension://32964004-721d-4b1f-9a38-db85a4190627/content.js

If I manually edit the manifest.json generated by 'npm run build' (in dist/) and replace the pointer to the content-loader script directly with my content script, the content script runs as expected.

The generated manifest.json is:

jonathanbetz@Jonathans-Air test-crxjs % cat dist/manifest.json  
{
  "manifest_version": 3,
  "name": "CRXJS React Vite Example",
  "version": "1.0.0",
  "action": {
    "default_popup": "index.html"
  },
  "permissions": [
    "activeTab"
  ],
  "content_scripts": [
    {
      "js": [
        "assets/content.js-loader-DNTlUQNq.js"
      ],
      "matches": [
        "<all_urls>",
        "file://*/*"
      ]
    }
  ],
  "web_accessible_resources": [
    {
      "matches": [
        "<all_urls>",
        "file://*/*"
      ],
      "resources": [
        "assets/content.js-DTKNx72A.js"
      ],
      "use_dynamic_url": false
    }
  ]
}

And the generated content loader script is:

(function () {
  'use strict';

  const injectTime = performance.now();
  (async () => {
    const { onExecute } = await import(
      /* @vite-ignore */
      chrome.runtime.getURL("assets/content.js-DTKNx72A.js")
    );
    onExecute?.({ perf: { injectTime, loadTime: performance.now() - injectTime } });
  })().catch(console.error);

})();

trungpv1601 mentioned this issue Sep 16, 2024

Content Security Policy Issue guocaoyi/create-chrome-ext#93

Open

Zortrox mentioned this issue Sep 27, 2024

Extension fails to start due to CSP error Zortrox/steamchecker#14

Closed

Spurlos mentioned this issue Oct 5, 2024

Extension fails to start due to CSP error Haaxor1689/humble-steam-sync#22

Closed

Herobread mentioned this issue Oct 16, 2024

Extension is not working on chrome 130 Herobread/better-studres-v2#101

Closed

xc2 mentioned this issue Oct 16, 2024

chore: disable use_dynamic_url as Chrome 130 is obviously not ready for it xc2/follow-it-later#22

Merged

Cyclodex added a commit to SoulcodeAgency/bexio-chrome-extension that referenced this issue Oct 25, 2024

fix(package) Updating @crxjs/vite-plugin

6f978a4

See crxjs/chrome-extension-tools#918

brsanthu mentioned this issue Oct 25, 2024

BroBench icon is gone in chrome version 130. datasert/brobench-community#9

Closed

nandenjin mentioned this issue Oct 26, 2024

Refused to load the script because it violates the following Content Security Policy directive nandenjin/tsukimi#39

Closed

pnd280 mentioned this issue Oct 28, 2024

[Bug]: Potential CSP Issue in Chrome 130 pnd280/complexity#7

Closed

2 tasks

jacksteamdev closed this as completed Oct 28, 2024

jacksteamdev pinned this issue Oct 28, 2024

BrettBedarf mentioned this issue Oct 29, 2024

Chrome 130 + crxjs CSP bug thetarnav/solid-devtools#310

Closed

noahajohn mentioned this issue Oct 29, 2024

How to disable content-script loader #946

Open

2 tasks

BlackStar1453 mentioned this issue Oct 29, 2024

fix csp_error openai-translator/openai-translator#1709

Closed

JSerwatka mentioned this issue Oct 30, 2024

Extension is not loading in latest Chrome + CSP error JSerwatka/notion-syntax-highlighter#9

Closed

mtalcott mentioned this issue Nov 2, 2024

Actually fix chrome extension loading mtalcott/google-photos-deduper#69

Merged

wittjosiah mentioned this issue Nov 6, 2024

chore: upgrade crxjs dxos/dxos#8137

Merged

ducminh-phan pushed a commit to ducminh-phan/coda-extension that referenced this issue Nov 6, 2024

feat: Update crxjs to fix CSP issue on Chrome 130+

4a4647e

crxjs/chrome-extension-tools#918

edwardoranj added a commit to oranj-base/strike that referenced this issue Nov 8, 2024

chore: updated @crxjs/vite-plugin crxjs/chrome-extension-tools#918

0d90305

t0d4 mentioned this issue Nov 9, 2024

Chrome 130におけるCSPの更新に伴うvite-pluginのアップデート NSL-Admin/ra-timecard-autofiller#4

Merged

jonfriesen mentioned this issue Nov 22, 2024

Updates vite and vite crxjs plugin jonfriesen/quickcite#19

Merged

MJBlack9000 mentioned this issue Dec 11, 2024

CSP issues on Chrome 130+ yosevu/react-content-script#23

Open

futabooo mentioned this issue Dec 13, 2024

fix csp issue futabooo/notion-bar-colorize#19

Merged

sunya9 mentioned this issue Dec 14, 2024

Fix CSP error in Chrome 130+ r7kamura/amazon_url_shortener#32

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

CSP Issue on Chrome 130+ #918

CSP Issue on Chrome 130+ #918

sebastienfontaine commented Sep 15, 2024 •

edited

Loading

trungpv1601 commented Sep 16, 2024 •

edited

Loading

matteing commented Sep 16, 2024

pnd280 commented Sep 20, 2024

pnd280 commented Sep 21, 2024

trungpv1601 commented Sep 21, 2024

pietrofxq commented Sep 24, 2024

trungpv1601 commented Sep 24, 2024

scisley commented Sep 25, 2024

trungpv1601 commented Sep 26, 2024

pnd280 commented Sep 26, 2024

trungpv1601 commented Sep 26, 2024 •

edited

Loading

scisley commented Sep 26, 2024

Toumash commented Sep 27, 2024

trungpv1601 commented Sep 28, 2024

Lonolf commented Sep 30, 2024

quentin-decre commented Oct 16, 2024 •

edited

Loading

salmin89 commented Oct 16, 2024

pietrofxq commented Oct 16, 2024 •

edited

Loading

pietrofxq commented Oct 16, 2024 •

edited

Loading

scarletczen commented Oct 16, 2024 •

edited

Loading

salmin89 commented Oct 16, 2024 •

edited

Loading

pietrofxq commented Oct 16, 2024

salmin89 commented Oct 16, 2024

pietrofxq commented Oct 16, 2024

salmin89 commented Oct 16, 2024

oliverdunk commented Oct 25, 2024

chauanhtuan185 commented Oct 28, 2024

Toumash commented Oct 28, 2024 •

edited

Loading

Reactiver commented Oct 28, 2024

Martizs commented Oct 29, 2024

SanderMuller commented Oct 29, 2024

Tharusha-dev commented Nov 6, 2024

Hema-Bala commented Nov 25, 2024

tabomagic commented Nov 25, 2024

CSP Issue on Chrome 130+ #918

CSP Issue on Chrome 130+ #918

Comments

sebastienfontaine commented Sep 15, 2024 • edited Loading

Build tool

Where do you see the problem?

Describe the bug

Reproduction

Logs

System Info

Severity

trungpv1601 commented Sep 16, 2024 • edited Loading

matteing commented Sep 16, 2024

pnd280 commented Sep 20, 2024

pnd280 commented Sep 21, 2024

trungpv1601 commented Sep 21, 2024

pietrofxq commented Sep 24, 2024

trungpv1601 commented Sep 24, 2024

scisley commented Sep 25, 2024

trungpv1601 commented Sep 26, 2024

pnd280 commented Sep 26, 2024

trungpv1601 commented Sep 26, 2024 • edited Loading

scisley commented Sep 26, 2024

Toumash commented Sep 27, 2024

trungpv1601 commented Sep 28, 2024

Lonolf commented Sep 30, 2024

quentin-decre commented Oct 16, 2024 • edited Loading

salmin89 commented Oct 16, 2024

pietrofxq commented Oct 16, 2024 • edited Loading

pietrofxq commented Oct 16, 2024 • edited Loading

FIX WITH PATCH-PACKAGE (DEV AND BUILD)

FIX WITH NODEJS SCRIPT (BUILD ONLY)

scarletczen commented Oct 16, 2024 • edited Loading

salmin89 commented Oct 16, 2024 • edited Loading

pietrofxq commented Oct 16, 2024

salmin89 commented Oct 16, 2024

pietrofxq commented Oct 16, 2024

salmin89 commented Oct 16, 2024

oliverdunk commented Oct 25, 2024

chauanhtuan185 commented Oct 28, 2024

Toumash commented Oct 28, 2024 • edited Loading

Reactiver commented Oct 28, 2024

Martizs commented Oct 29, 2024

SanderMuller commented Oct 29, 2024

Tharusha-dev commented Nov 6, 2024

Hema-Bala commented Nov 25, 2024

tabomagic commented Nov 25, 2024

sebastienfontaine commented Sep 15, 2024 •

edited

Loading

trungpv1601 commented Sep 16, 2024 •

edited

Loading

trungpv1601 commented Sep 26, 2024 •

edited

Loading

quentin-decre commented Oct 16, 2024 •

edited

Loading

pietrofxq commented Oct 16, 2024 •

edited

Loading

pietrofxq commented Oct 16, 2024 •

edited

Loading

scarletczen commented Oct 16, 2024 •

edited

Loading

salmin89 commented Oct 16, 2024 •

edited

Loading

Toumash commented Oct 28, 2024 •

edited

Loading