Support manifest v3

[jcblw]

Support manifest v3

[jcblw]

closed in

#172

Just to explain what we did to support v3.

We migrated off webextension-toolbox. There is only a small configuration to get Webpack to work. Even used the library as an example of what needed to be done.

We now have full control of the extension webpack compilation. I actually removed the paths to ./scripts this made service workers work in the current Chrome versions.

I had to bump minimum_chrome_version to 88.

Lastly with the polyfill. The actual error was coming from webextension-toolbox so with full control I used this instead of window on the replacement loader. This worked in the background file, as well as the client.

Looking forward to start working with a v3 extension.

[here-nerd]

@jcblw thank you for sharing how you overcome the current limitation of webextension-toolbox. Is there any chance that your solution would be integrated back webextension-toolbox so that everyone does not have to repeat the same fix by themselves?

[jcblw]

@jcblw thank you for sharing how you overcome the current limitation of webextension-toolbox. Is there any chance that your solution would be integrated back webextension-toolbox so that everyone does not have to repeat the same fix by themselves?

A majority of the changes are pretty small. I think the only large one would be the change to how hot reloading works in terms of injecting the script into the bundle instead of appending to the background script.

Ill make a few PRs this weekend to start the process. 😁