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

linknpm

v1.3.0

Published

install npm packages globally and link them in your projects also adding the entries in your package.json file

Downloads

7

Readme

Download an npm package once and reuse it in any future projects without installing again.

Also handles the package.json conflict from foreign project

Installation

You need to install the package globally to use over directories.

$ npm install -g linknpm

Use (Foreign Project)

Navigate to a foreign project directory where package.json is present and node_modules is to be installed

$ cd foreign_app
$ link    # links every dependencies present in package.json file

Use (New Project)

Navigate to a new project directory to link the globally installed packages

only one package allowed at once for now

$ cd newapp
$ link express    # downloads latest "express" module globally, links and updates package.json file

On Conflict between installed version and package.json requirement, it'll prompt for input

  • "u" to update the global package and npm link => npm i -g && npm link
  • "l" to force link the older version that's already installed, gives warning