next-netlify-starter VS next-firebase-auth

This part is really simple. Here's a great Next.js Netlify starter that was kindly prepared by the wonderful Cassidy Williams. To get up and running in a minute, click the Deploy To Netlify button on the repo and that's it, you're set. The advantage of using this starter is that:

Hey I was just wondering what the main differences are between next-firebase-auth and next-firebase-auth-edge They seem incredibly similar and I decided to go with auth-edge, but I was wondering if anyone has experience with the other library and what the main differences are. I am unfamiliar with security and dealing with auth tokens inside the browser's cookies, so I would like to have a better understanding of these tools and the pros and cons. Thanks in advance!

you can see how next-firebase-auth does it here https://github.com/gladly-team/next-firebase-auth/blob/v1.x/src/firebaseAdmin.js

There is a next firebase auth package that implements SSR: https://github.com/gladly-team/next-firebase-auth

In the SSR case, if all you want is firestore, then the admin SDK is perfect for this and easy enough to use from the server-side. If you want authentication also, that adds some moving pieces and I would probably at next-firebase-auth (which works with firebase authentication) or next-auth (which can use firestore for it's database, but handles authentication itself) to take care of the heavy lifting of SSR authentication.

But if you want to use the benefits of Next.js server side rendering and obtain a user inside getServerSideProps you'd have to use next-firebase-auth. They have a section in the docs that could help you make this decision.

Both Firebase and Next-Auth have what you're looking for. The security is baked in. https://github.com/gladly-team/next-firebase-auth https://next-auth.js.org/