FeatureFuel
3

Add Storage Adapter For Chrome.Local.Storage Api

Source: supabase/supabase#21923 · opened by @briowill
Context:
Supabase currently uses localStorage and memoryStorage for persisting auth sessions.

Issue:
When using Supabase in a Chrome Extension development content scripts do not have access to local storage directly.

Current Work Around
1. Chrome messaging can be used to pass the item stored in local storage to the content script which makes development not as smooth.
2. A custom Storage Adapter can be created and passed to the supabase createClient function which would allow persistence to use chrome.storage.local api

Request
Would be nice if :
1. supabase local-storage.ts had a Chrome.Local.Storage Adapter
2. SupabaseAuthClientOptions had a option to specify storage type (chrome api / local storage)

No pledges yet. Be the first to back this.

Make a pledge

Pledge your monetary support if this feature is added.

$

Comments

No comments yet.

Replying to

Add a comment

What do you think about this feature request?


Similar requests