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 🙏

© 2025 – Pkg Stats / Ryan Hefner

postlink

v0.3.6

Published

auto `npm link` your npm packages after `npm install`

Readme

postlink

auto npm link your npm packages after npm install

Why do you need npm link ?

A bar package depends on a foo package and you want node_modules/foo to stay in sync with ${HOME}/foo

How would you npm link foo ?

It can be done using npm link ${HOME}/foo.
The right way to do is to run npm link postinstall by adding it to your package.json scripts.

What postlink does ?

It prevents you from having to maintain npm link calls in your package.json.
It read dependencies from package.json and npm link all packages found in a folder you can define.

How to use

In your package.json add postlink as dependency and run it postinstall

{
    "dependencies": {
        "postlink": "*"
    },
    "scripts": {
        "postinstall": "postlink"
    }
}

Define the folder containing your npm packages : npm config set postlink_path "${HOME}".
postlink now runs after npm install ensuring node_modules/* packages are in sync with ${HOME}/*

Defining the folder containing npm packages

This config value is set using : npm config set postlink_path {value}.
You can define many folders : npm config set postlink_path "${HOME}/GitHub;${HOME}/npm_packages"