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

link-dep

v1.2.4

Published

Module to copy dependency to static folder

Readme

link-dep

Module to link dependencies to static folder. For some reason you might want to use a install dependency in let's say your index.html file which might be served from express

Usage

Pass in a string as the first argument. The second argument is where you would like to place the copied module

const linkDep = require("link-dep");

await linkDep("fs-extra", "./public/some-path");

Pass in an array as the first argument for copying multiple dependencies.

const linkDep = require("link-dep");

await linkDep(["fs-extra", "chalk"], "./public/some-path");

util function with try / catch

const linkDep = require("link-dep");

async function copy() {
  try {
    await linkDep("fs-extra", "./public/some-path");
  } catch (error) {
    throw new Error("Noo", error);
  }
}
…
await copy();

then / catch

const linkDep = require("link-dep");

linkDep("fs-extra", "./public/some-path");
  .then(() => console.log("Yes!"))
  .catch(() => console.error("Something went wrong!"));

Together with express

const path = require("path");
const express = require("express");
const linkDep = require("link-dep");

const app = express();
// `sayHi`-module doesn't exist on npm, it's created at the bottom, btw it's really complex. 🧠
// the module is just for demostration purposes
await linkDep("say-hi", "./public/scripts");

app.use("/static", express.static(path.join(`${__dirname}/public`)));
app.get("/", (req, res) => {
  res.sendFile("./index.html");
});

// index.html
<script src="static/script/say-hi">
// some-depenedency will now be ran

…………………………………………………………………………………………………………………………………………………………

// say-hi module 
module.exports = console.log("I'm saying hi");