SirAndrii
commented
1 year ago https://github.com/SirAndrii/chromeExtensionIneed/compare/singelton
At this stage this pattern doesn't help to match, because we don't change object after getting data from storage
Currently, the extension has three entry points (options, content, service-worker). Singelton may be a good fit for making content.js more modular and not passing initialized storage as a parameter to split functions or access chrome's storage by API