chrome.runtime.getURL introduced in Chrome 130 causing CSP ( content script loader )

[JoeyDoey]

Build tool

Vite

Where do you see the problem?

• In the browser
• In the terminal

Describe the bug

• CRxJS v.2.0.0-beta-28
• Vite ^5.4.8

Curious if there should also have been an update to the actual content script loader code along with PR #928 https://github.com/crxjs/chrome-extension-tools/pull/928/files#diff-38edcc526cad433b0a47988742b914aadd43cc56903ae94148fafe33f821edfaL20

The content script loader still generates chrome.runtime.getURL....

Reproduction

• create new project w/ CRxJS v.2.0.0-beta-28
• see generated /dist content script loader js

Logs

No response

System Info

System:
    OS: macOS
  Binaries:
    Node: 20.13.0
    bun: 1.0.33
  Browsers:
    Chrome: 131.0.6778.109
  npmPackages:
    vite: ^5.4.8 => 5.4.11

Severity

annoyance

[JoeyDoey]

Disregard the above! This issue has actually been fixed in latest crx beta v.2.0.0-beta-28

Just for more info:

I'm using CRX under the hood for Bedframe which i have installed globally on local. Bun aggressively caches installs such that running bun add <package>@latest still uses older local installation of package instead of actually installing latest from npm.