This is an experiment to use webext-redux in event driven web extensions.
With Manifest v3, we no longer have a persistent background script that keeps running as long as the browser is open. We now have service workers that go idle after a short time when the extension is not used. This means that any state stored in that service worker won't be kept, as well as any connection that was initialized for message passing between the extensions and the background scripts or the popup.
As a consequence, and at the time of writing webext-redux (v2.1.9) can't be used right way in Manifest v3 extensions.
It's still possible to use it by adapting the code architecture a bit, and this is what this repo attemps to demonstrate.
- To solve the non-persistence issue of the Redux store, we can use the chrome.storage API.
- Even if a storage is already used, when the service worker is idle, any interaction with the extension that involves the redux store will trigger
the following error:
Port error: Could not establish connection. Receiving end does not exist. To solve this issue, we can make sure that the connection is established before attempting to send messages.
Run yarn build, this will create a dist folder that can be loaded as an unpacked extension.
You can play around with the counter and wait for the service worker to become idle.
When the popup is opened again, you can notice that the state is preserved and we don't get any error 🚀