Shaw Donaire
Reputation: 1
Alasql - Manifest V3 migration error - doesn't allow content scripts to use eval() and friends
I'm having trouble executing eval() and friends for alasql, it is not supported to manifest v3 migration for chrome extension. Based from their Manifest V3 migration checklist:
You can no longer execute external logic using chrome.scripting.executeScript({code: '...'}), eval(), and new Function().
And got this error:
Uncaught (in promise) EvalError: Refused to evaluate a string as JavaScript because 'unsafe-eval' is not an allowed source of script in the following Content Security Policy directive: "script-src 'self'".
Alasql is using the 'new Function()' class/method thingy, and it causes error in manifest v3.
Does anyone have encountered the same issue?
Upvotes: 0
Views: 426
Answers (0)
Related Questions
- Manifest v3, Failed to load extension: Invalid value for 'web_accessible_resources[0]'. Invalid match pattern. Could not load manifest
- Errors when migrating extension to Manifest v3
- Error with migrating my Chrome Extension to Manifest v3
- Chrome extension - migrate from manifest v2 to v3
- executeScript is undefined or not a function in a ManifestV3 extension
- Migrating Extension to Manifest v3
- Chrome Extension Manifest Returns Error
- Adding 'unsafe-eval' to existing chrome extension
- Manifest.json Error Invalid value for 'content_scripts[0].matches[0]':Invalid scheme.
- migrating chrome extension to manifest 2 - script injection