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

npmy

v1.3.0

Published

`npm/npx` on steroids.

Readme

NPMy

  • npm
    • Init: npmy --init
    • Install: npmy + typescript or dev npmy ++ typescript
    • Uninstall: npmy - typescript
    • Outdated + Update: npmy up
    • Publish: npmy :publish --draft, npmy :publish --rc, npmy :publish --minor
  • npm.scripts
    • npmy :build
  • npx
    • npmy @mail-core/cli init

Setup

# Install
npm install -g npmy

# Help
npmy --help

npm

# Install
npmy + @mail-core/cli

# Install as dev
npmy ++ @mail-core/cli

# Uninstall
npmy - @mail-core/cli

npm scripts

# `npm start`
npmy :start

# `npm run build`
npmy :build

npm publish

# Release
#  version: x.UP.x
#  npm.tag: latest
npmy :publish --minor

# RC
#  version: x.x.x-{branch}.UP
#  npm.tag: rc
npmy :publish --rc

# Draft (prerelease)
#  version: x.x.x-{branch}.UP
#  npm.tag: draft
npmy :publish --draft

npx

With support custom registry!!1

# Default regsitry
npmy @mail-core/cli init

# Customize
npmy @mail-core/cli init --registry=https://my.npm.registry.dev

npm outdated

# Soft update deps
npmy up

# Update to latest
npmy up --latest

# Update by filter (starts with):
npmy up @mail-core # ← up deps for "@mail-core/*"

npm link

  1. npm install -g npmy
  2. cd path/to/project
  3. Add .npmyrc to .gitignore
  4. touch .npmyrc
  5. Edit .npmyrc as JSON-file and write {"%TARGET_DEPENDENCY%": "%LOCAL_PATH_TO_PACKAGE_FOLDER%"}
  6. npmy --link .
  7. ...
  8. Profit!

API

npmy --link [path] [--include=pattern]

  • path — by default current folder
  • add — add packages into .npmyrc (relative or absolute pattern)
  • include — see glob
  • version — print current version
  • verbose — process detailing of installation and linking

Description of work / Read article Ru

npmy --link — special tool for local packages development, subjecting to other packages being in development.

Usually I solve this task via npm link, or just symlink. These methods don't work, when dependent package has difficult publish cycle (modifies it's source, e.g. using Babel/Rollup/etc) or there are more then one.

Trust me, npmy --link covers all above mentioned tasks.


Inline usage

# Before: `cd` to your project folder
npmy --link --pkg=tx-i18n --to=~/artifact-project/tx-i18n

Development