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

@try-mingo/common

v1.0.19

Published

try-mingo-api-common is an npm package containing functionality that is used from multiple services of _try-mingo-api_

Readme

try-mingo-api-common

try-mingo-api-common is an npm package containing functionality that is used from multiple services of try-mingo-api

Development workflow

  1. install dependencies yarn --frozen-lockfile
  2. install yalc yarn global add yalc
  3. make changes inside this repo that you want to see reflected in try-mingo-api service
  4. run yarn build and yalc publish. The result will be eg: @try-mingo/[email protected] published in store.
  5. copy the first part, i.e. @try-mingo/[email protected]
  6. cd to the service inside try-mingo-api in which you want to use the update code, at the level where that service's package.json lives
  7. run yalc add @try-mingo/[email protected]
  8. docker desktop will redeploy that service's dependencies with the changes that we made in try-mingo-api-common

Contributing

  1. Branch of the feature branch that includes the linear ticket name
  2. Make any changes, commit, bump the version, push and open a PR against develop
  3. Once the PR has been approved, merge it and it will be published to npm