npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

hello-next-app

v1.0.8

Published

Next.js Starter Project to get you up and running in production quickly with Firebase Authentication, Cloud Firestore Database, Serverless Edge Functions, Playwright Testing and more.

Downloads

10

Readme

Hello Next App


From Zero to Production

Hello Next App is a Next.js Starter Project to get you up and running in production quickly with Firebase Authentication, Cloud Firestore Database, Serverless Edge Functions, Playwright Testing, Vercel and more.

Setting Up the Project

To bootstrap the app, run the following command and answer the prompts:

npx create-hello-next-app

This will create project in a new directory and install the dependencies.

You will need to create a new Firebase project.

Go to the Firebase console and add your project by following the prompts. Once you’re project is created, set up Firebase Authentication and enable Email/Password initially as an authentication provider to get started.

If you’d like to use Google as an Authentication Provider, you will need to provide a Google Support Email Address. You will need a google email address. If you would like to have a dedicated email address for support, you can set one up on groups.google.com. You will also need to add your production domain to Authorized Domains under Authentication Settings.

To use Firebase, you will need to copy the config into your codebase. Go to your Firebase project dashboard, click on the gear icon, and choose "Project settings"

Under "Your apps," click on the "</>" icon to create a new web app, and follow the prompts. After creating the app, copy the Firebase config object. Use those values to replace the ones in /src/lib/firebase/config.ts.

Next, you will need to create the .env variables for the Firebase Admin SDK. In your Firebase project console, go to Project Settings then the Service Accounts tab. Click the ‘Generate new private key’ button then download the JSON file.

Rename the .env.example file to .env then replace the values with the corresponding properties in the Firebase Admin SDK json file.

Local Environment

To run locally, do:

npm run dev

To run tests, do npm run test or npm run test-watch.

Deploy to Vercel

Sign up for Vercel and link your project on Github. When you push your code, it should deploy to Vercel.

You will need to set environment variables on your project with the values from your local .env file. You will also need to add your production domain to the list of Authorized Domains under your Firebase Project’s Authentication settings.

You will also need to add the same environment variables to the "Settings" tab in your GitHub repository for them to be available to the CI test runner.