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

@grantstrachan/npm-packaging-test

v0.0.9

Published

Package for testing Nexus3 proxy issue

Readme

Node Express demo project

Developers testing Nexus3 repository manager start here:

Use .env.template to create a local .env file to store the relevent variables or replace variables placeholder in the below commands before running commands

source .env

NPM

This operation confirms that all package dependencies are being pulled via Nexus as your main NPM proxy

npm conf set always-auth true

npm conf set registry $NPM_REPO_URL

npm conf set email $NPM_EMAIL

npm conf set _auth $NPM_RO_BASE64_STRING

cat package.json.template |sed "s/NPM_PACKAGE_VERSION/${NPM_PACKAGE_VERSION}/" > package.json

npm install

DOCKER

  • Build docker image to pull package from Nexus3 hosted NPM repository

docker build --tag $IMAGE_NAME:$IMAGE_TAG --build-arg NPM_EMAIL=$NPM_EMAIL --build-arg NPM_REPO_URL=$NPM_REPO_URL --build-arg NPM_RO_BASE64_STRING=$NPM_RO_BASE64_STRING .
  • Login and pull the demo container from Nexus3 hosted docker repository
docker login -u $DOCKER_RO_USER -p $DOCKER_RO_PW $DOCKER_URL

# use --rm to perform automatic container cleanup when container is stopped
docker run -d --rm -p $PORT:$PORT --name demo_express $DOCKER_URL/$IMAGE_NAME:$IMAGE_TAG

# Application can be access from the browser on http://localhost:$PORT

docker stop demo_express

Only available to Devops admins to populate new empty Nexus instance

####
source .env

npm conf set registry $NPM_REPO_URL && \
npm conf set email $NPM_EMAIL && \
npm conf set _auth $NPM_RW_BASE64_STRING

cat package.json.template |sed "s/NPM_PACKAGE_VERSION/${NPM_PACKAGE_VERSION}/" > package.json

npm publish

# Uses devops admin's person user token as NPM_RO_BASE64_STRING to test pulling packages
docker build --tag $IMAGE_NAME:$IMAGE_TAG --build-arg NPM_EMAIL=$NPM_EMAIL --build-arg NPM_REPO_URL=$NPM_REPO_URL --build-arg NPM_RO_BASE64_STRING=$NPM_RO_BASE64_STRING .

docker tag $IMAGE_NAME:$IMAGE_TAG $DOCKER_URL/$IMAGE_NAME:$IMAGE_TAG

docker login -u $DOCKER_RW_USER -p $DOCKER_RW_PW $DOCKER_URL

docker push $DOCKER_URL/$IMAGE_NAME:$IMAGE_TAG

#
# End Devops admin section
####

Quick all in one command for devops admins

. e2e_test.sh