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 🙏

© 2025 – Pkg Stats / Ryan Hefner

emma-test-component

v0.1.5

Published

components

Downloads

9

Readme

VPP Portal Frontend Shared Library

This library contains any components, services or helpers that can be shared amongst the VPP Portal frontend microsites. If you think something should or could be shared please have a discussion with the team and add it to the library. See the Contribution Guide.

Before the VPP team has a dependency resolution platform like Artifactory in place we will use CodeCommit to serve the package.

Usage

Installation

yarn add git+ssh://git-codecommit.ap-southeast-2.amazonaws.com/v1/repos/vpp-portal-frontend-shared-library

If you want a specific version specify the tag like so; yarn add git+ssh://git-codecommit.ap-southeast-2.amazonaws.com/v1/repos/vpp-portal-frontend-shared-library#v0.0.2

Contribution Guide

When contributing to the shared library try to keep your PR commits squashed to 1 commit message. Write the message in imperative tense. Describe what the commit does to the repository i.e. adds NavBar component or fixes a build bug - test coverage threshold was set to 200%.

Release process

When changes are merged into master, the build system will look at the package.json file for the version field. It will then attempt to tag the repository with the version and push the tag to the remote.