Use tabs.executeScript() instead of import()

[WofWca]

Maybe.
Using dynamic imports makes us have to add web_accessible_resources:

jumpcutter/src/manifest.json

Lines 26 to 30 in 81b4e50

	"web_accessible_resources": [
	"content/SilenceDetectorProcessor.js",
	"content/VolumeFilterProcessor.js",
	"chunks/*.js"
	],

, which is not ideal, as I heard: https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/manifest.json/web_accessible_resources#security
It's also a little dangerous to not have the import URL set in stone, maybe it could be somehow manipulated by a malicious page to import something else on behalf of the extension (Mozilla's web-ext warns about this).

jumpcutter/src/native-dynamic-import-webpack-plugin/LoadScriptRuntimeModule.js

Line 39 in 81b4e50

`const urlAbsolute = (typeof browser === 'undefined' ? chrome : browser).runtime.getURL(url)`,

Edit: Actually this doesn't look super dangerous, since we're passing the string through runtime.getURL(,

But then, it sounds a little stupid that there's virtually no native support for dynamic importing in extensions. Or am I missing something?

Another big thing is with .audioWorklet.addModule:

jumpcutter/src/entry-points/content/StretchingController/StretchingController.ts

Line 164 in 81b4e50

const addWorkletProcessor = (url: string) => audioContext.audioWorklet.addModule(browser.runtime.getURL(url));

For it we can't do executeScript(). Maybe the spec needs to be changed. I don't know what's the best practice.

This may also help with #26