Closed duhrer closed 8 months ago
I have been discussing this with @jobara, as the UIO+ extension will also need to be updated. The biggest concern is replacing all previous background scripts (including dependencies like Infusion) with a single service worker.
ES imports are not universally supported by browsers, which means we need some way of ensuring our dependencies are available in the context of the service worker code.
Justin pointed out that we might be able to import the code we need using importScripts
.
It seems like others are also using bundling tools to smack together their dependencies and unique code into a single file. Browserify seems like a passable option, Justin also pointed out that within the wider Infusion community, Laravel and Terser are being used for the kind of bundling we require.
Hey @duhrer @the-t-in-rtf, I've been away for a very long time and trying to catch up through this issue. Can you please tell if anything was finalised on the bundling part and the major blockers (if any) that are preventing us from settling on a bundler?
Hi, @dmahajan980. I still need to look at this. I will also create a ticket to add a privacy policy so that we can get the plugin added to the Chrome Web Store again.
It seems like the new version is now required, so I suspect we'll have to address this before we can restore the web store listing.
After reviewing the approach UIO+ used in migrating and reading this helpful guide, I have made a first pass at updating. Thus far I have confirmed that the following work:
I am in the process of testing all methods. Thus far I have confirmed the following working (in the order they appear in the configuration menu):
The following don't seem to work, I will have to look into that further tomorrow:
I have continued testing and will comment further on the pull.
The work has been reviewed and the pull has been merged.
Loading the plugin now throws an error:
We need to update our manifest version by the end of the year.