Methods to Use Storage in Net Extensions

Methods to Use Storage in Net Extensions

Engaged on an internet extension is an attention-grabbing expertise — you get to style net whereas working with particular extension APIs. One such API is storage — the net extension taste of persistence. Let’s discover how you need to use session and native storage inside your Manifest V3 net extensions!

Enabling Extension Storage

The extension storage API is not out there by default. To allow the storage API, it’s good to cite it within the manifest.json file of your extension:

  // extra....
  "manifest_version": 3,
  "identify": "__MSG_appName__",
  "permissions": [
    // more....
  // extra....

Including storage to the permissions array, which is a prime stage manifest.json key, gives session and native storage capabilities to your extension.

Get, Set, and Take away Storage Values

Very like conventional localStorage and sessionStorage APIs, extension storage gives get, set, and take away operations:

// set
await{ identify: "David", shade: "inexperienced" });

// get 
const { identify, shade } = await["name", "color"]);

// take away
await away(["name", "color"]);

Just a few issues to notice:

  • get requires an array argument, not a single worth like localStorage and sessionStorage
  • set must be an object format
  • take away can be an array, very similar to get
  • You should utilize or relying on how
  • All the extension storage API strategies are promise-based, with await or callback codecs

Clear All Storage

Within the occasion that you just wish to clear all knowledge for native or session storage, there is a clear methodology:


Utilizing clear is efficient however you will wish to make sure that you do actually wish to clear every thing — clear may grow to be a upkeep concern.

Storage is a necessary a part of most net extensions. Whereas the API is straightforward, the async format and methodology names are totally different.