Engaged on an internet extension is an attention-grabbing expertise — you get to style internet whereas working with particular extension APIs. One such API is storage
— the net extension taste of persistence. Let’s discover how you should use session
and native
storage inside your Manifest V3 internet extensions!
Enabling Extension Storage
The extension storage
API is not out there by default. To allow the storage
API, it is advisable to cite it within the manifest.json
file of your extension:
{ // extra.... "manifest_version": 3, "identify": "__MSG_appName__", "permissions": [ "storage", // more.... ], // extra.... }
Including storage
to the permissions
array, which is a prime degree 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 chrome.storage.session.set({ identify: "David", shade: "inexperienced" }); // get const { identify, shade } = await chrome.storage.session.get(["name", "color"]); // take away await chrome.storage.session.take away(["name", "color"]);
Just a few issues to notice:
get
requires an array argument, not a single worth likelocalStorage
andsessionStorage
set
must be an object formattake away
can be an array, very similar toget
- You need to use
chrome.storage.native
orchrome.storage.session
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 simply need to clear all knowledge for native or session storage, there is a clear
technique:
await chrome.storage.session.clear();
Utilizing clear
is efficient however you will need to make sure that you do actually need to clear all the things — clear
might develop into a upkeep problem.
Storage is an important a part of most internet extensions. Whereas the API is easy, the async format and technique names are totally different.