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 🙏

© 2026 – Pkg Stats / Ryan Hefner

gynger

v1.0.0

Published

SaaS Financing

Readme

Gynger

For Local Development

Install all the dependencies

npm install

Generate necessaary types

prisma generate

This will also generate types for type-graphql. These are stored in the node_modules folder under @generated/type-graphql.

Running Locally

You must have docker and docker-compose installed. To run the application simply run npm start and this will spin up a postgres docker and the node docker container.

npm start

If any changes are made to prisma.schema you will need to re-generate the types. Since docker has its own versions of this you will need to rebuild the docker image.

docker-compose build prisma

Deploying Infra

Infra is all setup through terraform. For staging run the following from inside infra/

terraform workspace set staging
terraform apply -var-file="staging.tfvars"

You will need to manually enable firebase auth to get this to work.

Deploy App

gcloud app deploy app.staging.yaml
cloud_sql_proxy -instances=gynger-staging:us-central1:gynger-database-instance=tcp:3307

Resetting the DB

# Delete all users first
# SET the GOOGLE_APPLICATION_CERDENTIALS
export GOOGLE_APPLICATION_CREDENTIALS=/path/to/file
node -r ts-node/register bin/delete-all-users.ts
# REMOVE FIREBASE_AUTH
prisma migrate reset 
prisma seed

In case you accidentally run db reset on staging you need to re-add the api user

GRANT USAGE ON SCHEMA public TO api;
GRANT SELECT, INSERT, UPDATE, DELETE ON ALL TABLES IN SCHEMA public TO api;
GRANT USAGE, SELECT ON ALL SEQUENCES IN SCHEMA public TO api;

Prod DB Connection

# the format should be 
DATABASE_URL=postgresql://username:password@localhost/gynger-db?schema=public&host=/cloudsql/gynger-staging:us-central1:gynger-database-instance

Running Seed In Prod

You need to download a key from firebase then set the keypath in the defualt config under clients.google.keypath