firebase-js-sdk VS firebase-admin-node

// 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);

Before You Begin 🎯 Before you start, there are a few prerequisites you need to take care of: **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 🎉. **Upgrade to the Blaze Plan**: The JustPass Firebase extension requires the Blaze (pay as you go) plan. If you haven’t upgraded your project yet, you should do so now. **Install or Update the Firebase CLI**: The Firebase CLI allows you to install and manage Firebase extensions from the command line. Make sure you have the latest version installed. **Enable Cloud Storage**: The JustPass Firebase extension requires Cloud Storage to be enabled for your project. You can check if it’s enabled from this [link](https://console.cloud.google.com/apis/api/firestore.googleapis.com/overview). **Find Your Firebase Project ID or Alias**: You will need either your Firebase project ID or a previously configured project alias to install the extension. You can run the appropriate command from your local app directory to find these. **Get Your JustPass Keys**: Go to the JustPass.me Dashboard and copy the following keys. You will need them to configure the extension: — JUSTPASSME_ORGANIZATION_NAME — JUSTPASSME_ID — JUSTPASSME_API_SECRET Step 1: Installing the Extension Once you have taken care of the prerequisites, you can proceed to install the JustPass Firebase extension. Here’s how you do it: **Set up an Empty Extensions Manifest**: Run the following command to set up an empty Extensions manifest: firebase ext:dev:init 2. **Install the Extension**: Run the following command to install the JustPass Firebase extension: firebase ext:install justpassme/firebase-extension --project=Replace \\ with your actual Firebase project ID.` Step 2: Deploying the Extension ✅ After you have installed the JustPass Firebase extension, you can deploy it to your Firebase project by running the following command: firebase deploy — only extensions` You have now successfully added passkeys authentication to your Firebase project using the JustPass Firebase plugin 🎉 ✅. Make sure to keep it safe, as you’ll need it for granting access to users. If you have any questions or run into any issues, feel free to reach out to [email protected] for assistance. Happy coding! 💪

**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

Connecting to firebase is as simple as copying and pasting the credentials (that Firebase gives you) into your frontend app. Here is a link to the documentation. If you need help, simply make a more detailed post about the issues you are running into.

Google has an Edge Network, but they push serverless functions like Cloud Run, which is also what version 2 of Firebase Cloud Functions use. Firebase Functions need a Version 3, which is built on the Edge. However, first Firebase, specifically firebase-admin would need to work on the edge. Google, who makes Angular, might then be able to compete better for deployment options. Cold Starts are terrible and should die IMHO, unless you have have specific use cases for them.

There's a lot of different ways to skin this cat, the easiest would be to use a client library like firebase storage to upload the photo directly and you can get an image url from that to use. If you are trying to send it your own API, then you probably want to set up a multipart http request to attach the image and then with your admin storage library of choice to upload the image. I have done the second one before with ktor and firebase admin sdk .

Hi, I've recently gave supabase a shot to as an alternative to firebase because I needed SQL. One thing that I've struggled with from the start is that supabase seems to ignore backends completely.

I don't want to use supabase edge functions, since I want to keep it simple with a single express backend and don't want to be vendor-locked.

In firebase, the Admin SDK https://firebase.google.com/docs/admin/setup solves this, but seems to be missing in supabase. For example, for a simple JWT verification, I had to go to old github issues, rather than finding the answer in the docs. https://github.com/supabase/supabase/issues/491#issuecomment...

IMO, the best supporting runtime for firebase would either be nodejs or flutter. Along with firebase admin, you could technically fullstack JS/TS and have better-than-average support for the firebase ecosystem (e.g. NextJS for frontend/apis, react native for mobile). However, it doesn't mean you can't use .NET with firebase.

Without looking too far into errors other people had, it seemed like it had to do with syncing clocks (what a strange error) - the problem could go away if you reissue a different service account key from the console or sync your local clock(???)

The one thing I was missing for my latest experiment was a reliable way to authenticate users and allow them access to their profile. There are other services that can be easily integrated but they can get quite expensive. Firebase on the other hand has a good free quota; perfect for this use case so I started by installing the Firebase Admin SDK. But alas the admin sdk has some dependencies on nodejs which are not included in the workers/functions runtime. 🤦‍♂️