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

@peris1000tickets/common

v1.0.16

Published

This is a project that will be a shared lib for the rest of the services

Readme

This is a project that will be a shared lib for the rest of the services

$ mkdir common
$ cd common
$ npm init -y

At package.json name change it to '@peris1000tickets/common'

$ git init
$ git add .
$ git commit -m "initial commit"
$ npm publish --access public

If you got an error of type ENEEDAUTH, unauthorised etc. then use

$ npm login

and follow the process getting logged in.

The common project will be written in typescript but we will be publishing that as JS to avoid any typescript version conflicts etc.

$ cd common
$ tsc --init
$ npm install --save-dev typescript del-cli
$ npm run build
$ npm version patch
$ npm publish

Moving errors and middlewares folders from auth project to common project

$ cd ticketing
$ mv auth/src/errors common/src/
$ mv auth/src/middlewares common/src/
$ npm install express express-validator cookie-session jsonwebtoken @types/cookie-session @types/express @types/jsonwebtoken
$ npm run pub

Now to fix import errors to the auth project

$ cd auth
$ npm install @peris1000tickets/common

and fix manually the import errors.

From now on whenever a change is taking place to common project and we need this change to take place to the other projects

cd ../common
$ npm run pub
cd ../auth
$ npm update @peris1000tickets