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

@autom8te/create-starter-templates

v0.0.4

Published

Starter templates for creating NextJS or Express projects.

Downloads

2

Readme

create-starter-templates

Templates

Next.js

  • NextUI
  • yup
  • FontAwesome
  • Supabase
  • Docker

Express.js

  • Supabase
  • Docker

Requirements

Before starting, ensure you have the following installed and configured:

Getting Started

Next.js

  • Create a new Next.js app with npx @autom8te/create-starter-templates@latest -n <project_name> --nextjs. Replace project_name with your camelCase project name
  • Navigate to new project folder
  • Run yarn
  • Run yarn dev
  • Go to http://localhost:3000 in browser

Express.js

  • Create a new Express.js server with npx @autom8te/create-starter-templates@latest -n <project_name> --express. Replace project_name with your camelCase project name
  • Navigate to new project folder
  • Run yarn
  • Run yarn start
  • Go to http://localhost:8100 in browser

You can also set the backend port with --be-port. Setting the backend port allows you to customize the ports used by all backend services, which as of now is the Express server and all local Supabase services. As of now, 10 digits of the ports will be used.

The important ones to know are

  • 1: Supabase's API port
  • 3: Supabase's self hosted UI
  • 8: Express server

All other ports can be seen in Supabase's config.toml file generated in /supabase.

For example, npx @autom8te/create-starter-templates@latest -n <project_name> --express --be-port 7654 will set a backend base port of 765# that will be used for all backend services.

[!TIP] You can create both project types in a single command with npx @autom8te/create-starter-templates@latest -n <project_name> --nextjs --express

Supabase Project Setup

A local Supabase is already initialized for you in the Express project! This template runs supabase init and already has some SQL migrations in there.

  1. Express - Run supabase start in the project root.
  2. Express - Edit the .env.shared file's SUPABASE_KEY with the service_role key from the supabase start's output.
  3. NextJs - Edit the .env.local file's
  • NEXT_PUBLIC_SUPABASE_KEY with the anon key from the supabase start's output.
  • NEXT_PUBLIC_SUPABASE_URL with the API URL from the supabase start's output.

Docker

In any of the projects, run docker compose up -d --build.

[!IMPORTANT] In Express.js' template, make sure to have your env vars in .env.local. In Next.js' template, make sure to update the args in docker-compose.yml.