Allow using chrome.storage.local

[Stvad]

I use it in https://github.com/transclude-me/extension

Motivation: I started using this via template, but apparently the values for settings are too large to store remotely 😿 . I still like the interface/form sync aspects of this and so, substituting the storage area to be local storage seems like a good solution.

Prior interest: #19

---

Question/confusion I have here - this lib is using the the chrome* api*s and yet works with FF, and supplying browser.storage.local works for passing the stoarge area here, but presumably this has different apis (callback vs promise). How does interop work here?

[Stvad]

So it seems my confusion is not unwarranted, passing in browser.storage.* works in FF but not in Chrome (??). Theoretically one can pass chrome.storage* but that seems counterinuitive in crossbrowser extension. So thinking of:

• pass string storage area type instead
• migrate the library to use webext-polyfill and promise api's, which would allow to preserve object passing interface and probably a good thing to do anyhow. It's a bit of a larger change though 🤔

Lmk if you have preferences between those 2!

[Stvad]

Ok, went with option 2 as it seemed simple enough

[fregante]

Thank you for the PR! I'd rather not include the polyfill, also because this change won't work if users pass a raw chrome.storage.local object (which isn't promised on Manifest v2 in Chrome).

You can pass a string instead

[Stvad]

I'd rather not include the polyfill,

huh, I'm curious why? I was really surprised this using chrome* as it is aiming to be cross-browser (and a bit surprised it works in FF tbh :p )

[fregante]

huh, I'm curious why?

Because it's as large as this package + it's not necessary (webext-options-sync has worked fine without it since its inception) + the polyfill won't be deduplicated across dependencies because they release a "server breaking" version every time.

If I really need promise API, I made a 300-byte wrapper, but that's still not required for this change.

I was really surprised this using chrome* as it is aiming to be cross-browser

chrome.* APIs are the cross browser APIs because Chrome only supports those. Every other browser has just been playing catch up and have to support that, even if they push a more generic browser.* API.

[Stvad]

Pushed an update to use the string type

[fregante]

managed is read-only, it's not supported by webext-options-sync

Suggested change

	export type StorageType = 'sync' | 'local' | 'managed';
	export type StorageType = 'sync' | 'local';

[aspiers]

Suggested change

	Type: `'loacal' | 'sync' | 'managed'`
	Type: `'local' | 'sync' | 'managed'`

[Stvad]

checking in! 🙂

[fregante]

The changes and the readme update look great!

[aspiers]

Awesome, thanks so much both - looking forward to trying this!