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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@tylergasperlin/ticketing-common

v1.0.41

Published

[https://www.npmjs.com/package/@tylergasperlin/ticketing-common] # PACKAGES IN THIS PROJECT ARE SHARED BETWEEN PROJECTS AND PUBLISHED TO NPM 1. npm login 2. See tylergasperlin organization 3. npm publish --access public 4. package.json name and version ar

Downloads

3

Readme

NPM Package

[https://www.npmjs.com/package/@tylergasperlin/ticketing-common]

PACKAGES IN THIS PROJECT ARE SHARED BETWEEN PROJECTS AND PUBLISHED TO NPM

  1. npm login
  2. See tylergasperlin organization
  3. npm publish --access public
  4. package.json name and version are important when publishing to npm

EASIEST WAY TO RE-PUBLISH

npm run pub

We publish the common package in javascript even though we write in typescript

  1. npm build will compile into js
  2. tsconfig => declaration file uncommented so we create a typescript definition file to work between js and ts
  3. outDir build will push js code into a build folder
  4. del-cli will help to remove files from build before rebuilding. In package json we use del to delete the build dir before rebuilding

package json

  1. main specificies the index js file from build folder
  2. types specifies the typescript declarations file
  3. files specifies the files we want in the published build.

npm commands increment version

  1. npm version patch = increment version number on far right