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

depdown

v0.0.3

Published

Node.js dependency installer

Readme

Why ?

The original code of this is from the barelyhuman/wrap package and is being extracted into a sub package in case someone else would like to manage dependencies dynamically.

The sole purpose for the existence of this is to avoid having to install deps that the user might already have installed. This reduces duplication of dependencies. There is no version check right now which can be counterproductive but that's in the pipeline.

Demo

You can setup an empty node package and start by adding wrap to it and running npx wrap build to see the installer in action.

or if this short video works for you, then that.

$ npm init -y
$ npm i -D @barelyhuman/wrap
# edit package.json to have a "source" and "main" field
$ npx wrap # will install rollup and other deps in devDeps
# or
$ npx wrap -f # will install standard in devDeps

Install

$ npm i depdown
# or if you use yarn
$ yarn add depdown

Usage

import { depdown } from "depdown";

async function main() {
  await depdown(["standard"], { mode: "dev" });
}

API

depdown: (deps: string[],options: Options) => Promise<void>;

  • deps - String of package names to be installed
  • options
    • mode - enum dev | direct | peer (default: dev) - where to install the packages in the package.json dependency tree

License

MIT © Reaper