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

sn-tgt

v1.0.31

Published

File changing tool useful for switching quickly between similar brand relevant files in a single reusable project.

Readme

TGT - Target

The target tool is used to facilitate branding apps across multiple platforms. The concept is to have the apps use local brand data which shouldn't change for the brand once it is created, but lets the app get dynamic app config data from Firebase and dynamic images from an S3 bucket. The local data should only be the minimum necessary to set up services and know what brand info to use. The Firebase data should be any config data that is dynamic in the app, like colors, fonts, ui element sizes, image names, etc. The config's image names should point to files stored on the bucket.

The tool is meant to accomplish a few main goals :

  1. Download and keep app repo branches up to date locally in the folder
  2. Move brand files in the app repos
  3. Build one or all brands for needed platforms
  4. Set the Firebase data for brands
  5. Set Firebase data for the map layers
  6. Manage production vs staging data on Firebase and S3
  7. Upload brand files to S3 bucket

To do so, a tgtconfig.json file is read to know what branding actions are needed. The file's object has four parts.

  1. repos: An array where each item represents a repo to clone for the app, and each item is an array with three strings. The first string is the repo name and the second the branch to checkout, and the third the repo url to clone.