firebase-js-sdk VS postgrest

Even though Firebase Auth is supposed to prevent duplicate emails automatically, I was still seeing duplicates. After digging through GitHub issues and Reddit discussions, I realized this problem has been around for a while.

import { initializeApp } from 'firebase/app'; import { initializeAuth } from 'firebase/auth'; // Firebase JS SDK work with expo web // for more information: https://docs.expo.dev/guides/using-firebase/#using-firebase-js-sdk // Initialize Firebase const firebaseConfig = { apiKey: process.env.EXPO_PUBLIC_FIREBASE_API_KEY, authDomain: process.env.EXPO_PUBLIC_FIREBASE_AUTH_DOMAIN, // databaseURL: process.env.EXPO_PUBLIC_FIREBASE_DATABASE_URL, projectId: process.env.EXPO_PUBLIC_FIREBASE_PROJECT_ID, storageBucket: process.env.EXPO_PUBLIC_FIREBASE_STORAGE_BUCKET, messagingSenderId: process.env.EXPO_PUBLIC_FIREBASE_MESSAGING_SENDER_ID, appId: process.env.EXPO_PUBLIC_FIREBASE_APP_ID, measurementId: process.env.EXPO_PUBLIC_FIREBASE_MEASUREMENT_ID, }; let firebaseApp: ReturnType; let auth: ReturnType; try { firebaseApp = initializeApp(firebaseConfig); auth = initializeAuth(firebaseApp); auth.useDeviceLanguage(); } catch (error) { console.error("Error initializing Firestore:", (error as any).message); console.error("Error Stack:", (error as any).stack); console.error("Error Details:", error); } export { auth, firebaseApp }; // To apply the default browser preference instead of explicitly setting it. // For more information on how to access Firebase in your project, // see the Firebase documentation: https://firebase.google.com/docs/web/setup#access-firebase

// public/firebase-messaging-sw.js // Give the service worker access to Firebase Messaging. // Note that you can only use Firebase Messaging here. Other Firebase libraries are not available in the service worker. importScripts('https://www.gstatic.com/firebasejs/8.10.1/firebase-app.js'); importScripts('https://www.gstatic.com/firebasejs/8.10.1/firebase-messaging.js'); // Initialize the Firebase app in the service worker by passing in your app's Firebase config object. // https://firebase.google.com/docs/web/setup#config-object firebase.initializeApp({ apiKey: 'api-key', authDomain: 'project-id.firebaseapp.com', databaseURL: 'https://project-id.firebaseio.com', projectId: 'project-id', storageBucket: 'project-id.appspot.com', messagingSenderId: 'sender-id', appId: 'app-id', measurementId: 'G-measurement-id', }); // Retrieve an instance of Firebase Messaging so that it can handle background messages. const messaging = firebase.messaging();

// Import the functions you need from the SDKs you need import { initializeApp } from "firebase/app"; import { getAuth } from "firebase/auth"; // TODO: Add SDKs for Firebase products that you want to use // https://firebase.google.com/docs/web/setup#available-libraries // Your web app's Firebase configuration const firebaseConfig = { apiKey: "AIzaSyDs5ConzFDM2yGvweN-sZdAPFAlowyCDhE", authDomain: "reactmoviepp.firebaseapp.com", projectId: "reactmoviepp", storageBucket: "reactmoviepp.appspot.com", messagingSenderId: "719848561957", appId: "1:719848561957:web:254facecfb591921474ecc", }; // Initialize Firebase const app = initializeApp(firebaseConfig); export const auth = getAuth(app);

**Add Firebase to Your Project**: If you haven’t done so already, you need to add Firebase to your project. You can follow the steps in this [link](https://firebase.google.com/docs/web/setup) to get started 🎉.

// Import the functions you need from the SDKs you need import { initializeApp, getApp, getApps } from "firebase/app"; import { getAnalytics } from "firebase/analytics"; import { getFirestore, gitFireStore } from "firebase/firestore"; import { getStorage } from "firebase/storage"; // TODO: Add SDKs for Firebase products that you want to use // https://firebase.google.com/docs/web/setup#available-libraries // Your web app's Firebase configuration // For Firebase JS SDK v7.20.0 and later, measurementId is optional const firebaseConfig = { apiKey: process.env.NEXT_PUBLIC_FIREBASE_API_KEY, authDomain: "twitter-v1-6a0d8.firebaseapp.com", projectId: "twitter-v1-6a0d8", storageBucket: "twitter-v1-6a0d8.appspot.com", messagingSenderId: "334598974996", appId: "1:334598974996:web:a16f62518c1c5af1044101", measurementId: "G-Y5F3Q3QG2X", }; // Initialize Firebase const app = !getApps().length ? initializeApp(firebaseConfig) : getApp(); const db = getFirestore(); const storage = getStorage(); const analytics = getAnalytics(app); export { app, db, storage };

Auth persistence Issue Firebase SDK - https://github.com/firebase/firebase-js-sdk/issues/6050

Documentation: https://postgrest.org/

> I was tired of writing backend APIs with the only purpose that they get consumed by the same app's frontend (typically React).

PostgREST is great for this: https://postgrest.org

I run 6 React apps in prod, which used to consume APIs built with Flask, Django and FastAPI. Now they all consume APIs from PostgREST, I no longer write APIs. I define SQL views for the tables I want to expose, and optionally a bunch of SQL grants and SQL policies if I have different roles in the app, and PostgREST automatically transforms the views into endpoints, adds all the CRUD + UPSERT capabilities, handle the permissions, filtering, ordering, returning, pagination, and so on.

I think I know what you're talking about because I ran into this too. In defense of Supabase, you can still use transactions in other ways. Transactions through the client are messy and not easily supported by PostgREST.

The GitHub issue here sums up the conversation about this:

https://github.com/PostgREST/postgrest/issues/286

So... your comment is a bit disingenuous. Regardless of Hacker News's thoughts on MCP servers, there is a cohort of users that are finding them to be immensely useful. Myself included.

This is especially helpful because Supabase uses PostegREST under the hood, which does not support OpenAPI 3.x. Note that some Postgres specific features like enums are not converted to JSON Schema enums as Sequelize doesn't expose that information.

PostgREST stands out as the leading solution for PostgreSQL databases. It turns your database directly into a RESTful API with minimal configuration. The tool automatically creates endpoints for tables and views, supports complex filters, and leverages PostgreSQL's row-level security for fine-grained access control. If you'd like to see this in action, check out our Neon PostgresQL sample.

PostgREST

> I don't really see how the validation schema and ORM model would ever really diverge...

If that were the case, then using a PostgreSQL API[0] that maps tables to APIs would be all that's required.

However, the real world is messy. Requirements change, which could lead the project becoming a reimplementation of full framework such as Django.

Django also comes with generic REST endpoints based on models thus giving you the magic, but still allows for all the different use cases and customizations that might present themselves during the full lifecycle of a project.

[0]https://github.com/PostgREST/postgrest

PostgREST 12.2 is out! It comes with Observability and API improvements. In this post, we'll see what's new.