firebase-admin-node VS Next.js

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. 🤦‍♂️

Remember to start the Next.js server with pnpm dev.

We want to share with you the best testing setup we've experienced - and this includes using Playwright and NextJS. It's a setup we've come up with for Infinite React DataGrid, which is a complex component, with lots of things to test, but this configuration has helped us ship with more confidence and speed.

If you're acquainted with NextJs, the directives will come as no surprise.

Deploying a full-stack Next.js web app can seem complex, but with the right tools, it's straightforward. This tutorial will cover the essentials to get your app up and running quickly:

This is a Next.js project bootstrapped with create-next-app.

This article contrasts two whales: Next.js vs Node.js. Both projects are open-source but have different use cases. Next is React-based, which supports static and server-rendered pages, helping build dynamic and hybrid applications thanks to its automatic static optimization feature. Node is a runtime environment for implementing JavaScript code outside the browser, particularly on the server.

In this tutorial, we will learn how to use Strapi, ChatGPT, and Next.js to build an app that displays recipes using AI.