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

find-npm-assets

v0.3.2

Published

Recursively find assets in node modules

Readme

find-npm-assets

NPM

Recursively find assets in npm packages.

To define assets in a package, add an assets field to the package.json containing an array of file globs to include.

Example

Let's say you have a package named my-site, which contains some assets and npm dependencies that in turn contain additional assets:

{
  "name": "mysite",
  "assets": [
    "src/app/assets/**/*",
    "logo.png"
  ],
  "dependencies": {
  	"mysite-dep": "*"
  }
}
{
  "name": "mysite-dep",
  "assets": "background.jpg"
}

You could retrieve all your project assets with:

var assets = require('find-npm-assets').load();

// Example output:
// ["src/app/assets/**/*", "logo.png", "background.jpg"]

Gulp usage

Integrating find-npm-assets with gulp is extremely easy. The following gulp task copies all your project assets to a destination folder:

var assets = require('find-npm-assets').load();

gulp.task('assets', function() {
    gulp.src(assets)
        .pipe(gulp.dest('build/assets'))
});

For projects with assets coming from multiple packages it is recommended to set the pkgDir property, which allows assets to be organized by project name:

var assets = require('find-npm-assets').load({pkgDir: true});

gulp.task('assets', function() {
    assets.forEach(function(pkg){
        gulp.src(pkg.assets).pipe(gulp.dest('build/assets/' + pkg.name));
    });
})

// Example output:
// [{
//  name: project1,
//  assets: ["src/app/assets/**/*", "logo.png", "background.jpg"]
// }, {
//  name: project2,
//  assets: ["src/app/assets/**/*", "logo.png", "background.jpg"]
// }]

Reference

To output debug information, pass an object with a debug property set to true to the load method:

var assetFind = require('find-npm-assets');
assetFind.load({debug: true});

You can run find-npm-assets from the command line, the -v argument will trigger debug information and -m will trigger the pkgDir option.

License

See LICENSE file.