colorcal VS supabase

Using thin-backend has been one of the most delightful experiences I've had making an SPA with a simple backend. The developer experience with the generated TypeScript types is particularly great, the DB migrations remind me of Prisma, and knowing I have a standard Postgres db under the hood is comforting. It isn't a large or complex app, but Marc has been super responsive to bugs and feature suggestions so it has been fun to iterate on. You can find the code at https://github.com/ianobermiller/colorcal.

So, we will use Supabase as a Postgres database to store the tokens and Prisma as our ORM of choice to communicate with our database.

Supabase (postgREST, Auth)

[5] https://supabase.com/

Implemented read only UI for indexes. PR

Before we start, make sure you have a GitHub account. You also need Node.js and npm installed on your local machine (note: you also have the option to host it on a cloud environment using Gitpod for example; that would be another post). If you need accounts on Vercel, Supabase, and Resend, create them by visiting the Vercel, Supabase, and Resend websites.

GitHub: https://github.com/supabase/supabase/tree/master/studio

Supabase a project tagged "The open-source Firebase killer" is an open-source alternative to Firebase. A SAS platform from Google. Supabase Like Firebase is a SAS platform. Supabase provides you with a Backend as a service to enable rapid application development by keeping your concerns related to only the front end of your application enabling you to focus fully on delivering a good user experience.

Supabase

So why another article? Well, as much as I was being a bit tongue-in-cheek about libraries changing all the time, it certainly seems to be the case with Supabase. Their Next.js Auth Helpers has recently undergone several significant updates, and they are worth talking about.

Supabase: https://github.com/supabase/supabase/pulls?q=is%3Apr+author%...