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

@chbiel/yaln

v1.0.6

Published

Watch for local changes, pack them and install with npm

Readme

yaln (Yet another local npm)

Intention

While developing libraries, using npm link, yarn link and also partially yalc sometimes introduce wierd problems. Especially there can be difference between a built and a linked package.

This package was created to get around those limitations and mimik a real local installation of package in an easy way.

How it works

yaln uses npm pack to create an actual npm package file and store it in ~/.yaln/packages/. Those built packages can be installed in other repositories. It can watch for changes of packages in ~/.yaln/packages/ and installs them locally or install them once.

Install

npm i -g @chbiel/yaln

Or from source

git clone ...
cd ...
npm i -g .

Usage

# In library / source project
# Plain
yaln pack

# With tsc-watch
tsc-watch --onSuccess "yaln pack"

# With rollup
rollup -c --watch --watch.onBundleEnd="yaln pack"
# In the target project
# Plain
yaln install [package list]

# With watch
yaln watch [package list]

Pre commit hook

To ensure, that no local file references are committed to package.json, you can use the following pre-commit hook:

- id: no-relative-packages
  name: no-relative-packages
  entry: bash -c "git diff --cached --name-only | grep -q 'package.json' && cat package.json | grep -E 'file:.+\/\.yaln\/.+' && echo -e 'file references not allowed in package.json' 1>&2 && exit 1 || exit 0"
  language: system
  pass_filenames: false

Known bugs

  • Looks like sometimes, when the first package update gets detected while using watch, the package gets installed twice

Missing features

  • Support yarn
  • Allow configuration of exchangePath