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

web-whitelabel

v1.15.0

Published

White label version of the TK web app

Downloads

49

Readme

web-whitelabel

White label version of the TurnKey web app.

Getting Started

This application is built using Next.js. If you are not familiar with Next or want a refresher, check out the docs. It is also written in TypeScript docs and uses nodemon to automatically re-compile changes on both the client and server.

  • Make sure you are in the root of the project
  • Grab the local.json file (located in s3 at tkvr-cred-store/local-configs/web-whitelabel) and place it in the config/ folder.
  • Create a .env file at the root of the project.
    • Add REACT_SPINKIT_NO_STYLES=true to the .env file
  • Run npm install
  • If you don't already have nodemon and ts-node installed globally, do so by running npm install nodemon -g and npm install ts-node -g
  • Build the project by running npm run build
  • Start the project in development mode by running npm run start:dev

Local configuration

The local.json file has a key for nextjs and default values as follows:

{
    ...

    "nextjs": {
        "useAssetPrefix": false,
        "buildType": "development"
    }

    ...
}

The useAssetPrefix key allows us to set an assetPrefix for test/production servers while we have the application load balanced (so we can slowly migrate pieces of the site).

The buildType key determines how Next builds/serves the application.

  • If it is set to production it will build the entire application before starting up the server, allowing for what is essentially a static bundle for the application (which gives us a large increase in performance).
  • If it is set to development it will build the application on the fly and reload the application on any code changes. This allows for rapid iteration and should only be used for local development.