Newsletter
Join the Community
Subscribe to our newsletter for the latest news and updates
A Next.js boilerplate that adds Firebase authentication and displays GitHub repositories.
Next Login Firebase is a Next.js boilerplate template that lets developers add Firebase authentication to a web app and display the signed-in user's GitHub repositories. This starter project pairs the Next.js React framework with Firebase Auth and Tailwind CSS, giving you a working login flow plus a simple repo viewer out of the box.
Next Login Firebase is a basic Next.js template that authenticates users with Firebase and then shows GitHub repositories for a configured username. It takes Firebase project credentials and a GitHub API URL as input and produces a running web app with a sign-in flow and a repo list. The template is maintained on GitHub by realtouseef and is intended as a boilerplate for future projects.
npm start and yarn dev commands for running a local development server.http://localhost:3000 as an authorized JavaScript origin.https://github.com/realtouseef/next-login-firebase.git and can be cloned and reused freely.The setup requires a Firebase project: after creating one, you obtain web client credentials from the Google APIs console and authorize your local or deployed frontend URL. You then copy your Firebase config values and the GitHub API URL into a .env file using the variable names listed in the README, install dependencies with npm install or yarn, and launch the dev server with npm start or yarn dev.
Yes, the template is open-source. You can clone the GitHub repository and use it without paying a license fee; you only need your own Firebase project.
The NEXT_PUBLIC_GITHUB_REPO_URL environment variable sets which GitHub API endpoint the app uses to fetch repositories, such as api.github.com/users/username.
Yes. The template has no backend of its own; it relies on Firebase for authentication, so you must create a project at firebase.google.com and configure the environment variables before the login flow works.
The README labels it as a basic boilerplate and does not mention deployment steps, so it is best treated as a starting point rather than a production-ready app.
