cxreiff
cxreiff
Explore posts from servers
CDCloudflare DevelopersDTDrizzle Team
PostsComments
DTDrizzle Team
Created by cxreiff on 11/22/2023 in #help
Edge Runtime + Supabase + Drizzle: Possible?
Hello all- I am attempting to move my DB from planetscale to supabase, but after swapping to postgres clients, I started getting errors from Vercel during build: "The Edge Function "404" is referencing unsupported modules". The modules in question have been postgres when using postgres.js and then pg-connection-string, pg, pgpass, and split2 for node-postgres. I assumed this meant that these clients are not compatible with the edge runtime, so I looked at how others were connecting in environments like CF Workers, and it seemed like the recommendation was to use the "@supabase/supabase-js" supabase SDK instead. However I'm not sure if its possible to wrap drizzle around this client, rather than one of the plain postgres ones. Anybody figure out how to get drizzle working with supabase from an edge serverless function? I know Neon has a serverless client but I'm trying to make use of supabase's auth tools. Here is my repo: https://github.com/cxreiff/figrid/tree/5aaee1a69dc3a7eaa357c1e73ddc5e63a07589be
3 replies
DTDrizzle Team
Created by cxreiff on 11/17/2023 in #help
Drizzle Studio with Safari:
I started up Drizzle Studio and followed the instructions in the right-hand column: 
brew install mkcert
brew install nss
mkcert -install
brew install mkcert
brew install nss
mkcert -install
...and restarted my browser. However I am getting the same localhost access issues as before, and I am stuck in the splash screen: 
[blocked] The page at https://local.drizzle.studio/ was not allowed to display insecure content from http://localhost:4983/.
Not allowed to request resource.
XMLHttpRequest cannot load http://localhost:4983/ due to access control checks.
[blocked] The page at https://local.drizzle.studio/ was not allowed to display insecure content from http://localhost:4983/.
Not allowed to request resource.
XMLHttpRequest cannot load http://localhost:4983/ due to access control checks.
Is there another step I can take here to get the cert recognized? Thank you for your help.
2 replies