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

@ahi40/common

v1.0.88

Published

* The code in here is shared among the scout services

Readme

Common Library

  • The code in here is shared among the scout services

Basics

  • the folder common is published on npm registry in a public organisation (everybody can see code)
  • the common lib is also part of a seperate git repo (required by npm to have seperate git repo)
  • to login to npm before pushing lib, run `npm login'
  • to push lib, run npm publish --access public
  • the libs in the common lib are written in typescript but published in JS to guarantee compatibility
  • Publish process
    1. Commit changes to git
    2. increase package version tag by running npm version patch or setting it manually in package.json
    3. run npm run build
    • depending on the operating system, you may need to change the del-cli cmd in package.json clean script
    1. run npm publish
    2. install or update the common lib in services: npm [install|update] @pauls_ticket_sales/common
  • to import module, add import {BadReuestError|component name} from '@pauls_ticker_sales/common

Contains Logic that ...

  • Does the listening and revceiving of events via nats event bus
    • To ensure that typescript can check the contents of new events when used in service
      • Define new event name/subject in subject.ts
      • Define specialised event properties in a new interface file detailing event properties such as TicketCreatedEvent
    • Defines a base class for publishing and listening of events (base-listerner.ts and base-receiver.ts)
  • ensuring checking of event names and properties as done here is not cross platform independent as it is bound to java script. Cross platform independant solutions are JSON schema, Protobuf (lecture 301)