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

amtech

v1.1.0

Published

## Last reviewed Tony Gayter - 2021-06-15

Readme

Amtech

Last reviewed

Tony Gayter - 2021-06-15

Dependencies

See the following files for more details:

  • Node 10 should be used for installation and builds
  • package.json (dev node dependencies)
  • /.env.example (required global environmental vars and license key placeholders)

Project architecture

  • Inherited project
  • Dockerised Wordpress build.
  • Storefront based theme

Docker

  • Docker files can be found in the docker folder
  • PHP image is based on TheCodingMachine's PHP images
  • Persistent files (uploads / DB files) will be stored in docker/persist

Local development environment setup

  • Pull down repo
  • Populate .env file(s) based on .env.example files
  • Run npm run dd to create required docker containers
  • Follow build process to install dependencies and build site assets
  • Visit the local site and install temp Wordpress database following WP install process
  • Use WP Migrate to pull down database and assets from live / stage

Build process:

  • Run NVM USE to make sure your running the correct Node version
  • Build dependencies are installed with npm install
  • CSS / JS assets are built with grunt in teh src folder

Deployment process:

  • Deployment currently handled by Deploy HQ
  • Pushing to master branch will deploy to staging environment

Project specific notes / issues