Skip to content
Vite Plugin CI

fix: workaround for the issue with chrome.runtime.getURL introduced in Chrome 130 causing CSP rejecting script due to different origin (GUID instead of chrome extension id) #1733

Sign in to view logs

fix: workaround for the issue with chrome.runtime.getURL introduced in Chrome 130 causing CSP rejecting script due to different origin (GUID instead of chrome extension id)

fix: workaround for the issue with chrome.runtime.getURL introduced in Chrome 130 causing CSP rejecting script due to different origin (GUID instead of chrome extension id) #1733

Re-run triggered October 20, 2024 10:59
@jacksteamdevjacksteamdev
#928
onv:fix/chrome-runtime-get-url
Status Failure
Total duration 2m 14s
Artifacts –

vite-plugin.yml

on: pull_request
Lint
28s
Lint
E2E Tests
2m 4s
E2E Tests
Unit and Output Tests
43s
Unit and Output Tests
Fit to window
Zoom out
Zoom in

Annotations

1 error and 3 warnings
Unit and Output Tests
Process completed with exit code 1.
Lint
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Unit and Output Tests
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
E2E Tests
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3, actions/cache@v3, coactions/setup-xvfb@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/