PD
🧩 Plasmo Developersrpdn8n
Supabase url and anon key exposed
I am a newbie exploring Plasmo for supabase authentication. The public url and anon keys are added in the .env file. On building the file, I find the supabase url and anon keys are exposed in popup.js, which can be traced in Devtool sources. The bad actors may use the url and anonkey to exploit the auth.
What are the best ways to deal with supabase auth without exposing the url and key? Am I missing something?
What are the best ways to deal with supabase auth without exposing the url and key? Am I missing something?
2.1KMembers
View on DiscordWant results from more Discord servers?
More PostsSupabase url and anon key exposedI am a newbie exploring Plasmo for supabase authentication. The public url and anon keys are added iFirefox dev server manifest warningsThe
```json
{
"content_security_policy": {
"extension_pages": "script-src 'self' http://localhimport url no longer workingHey folks 👋🏻 just upgraded our extension at Attio to the latest version of Plasmo (0.85). It seemsCan't figure out how to navigate from my extention to my auth pageI'm trying to test a popup extension I made that has a button that is supposed to navigate to `http: