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

load-modules

v0.1.1

Published

Load the resolved filepaths to npm modules, either directly in your config or from Underscore/Lo-Dash templates.

Readme

load-modules NPM version

Use matchdep to filter and resolve filepaths to npm module dependencies

Use returned filepaths in your node projects (var load = require('load-modules').load('*')), or load into your project's Grunt config data with templates (<%= _.load("foo*" %>).

Getting started

Install the module with: npm install load-modules --save

var load = require('load-modules').load(pattern, config);
console.log(load);

Examples

// Resolve filepaths to all dependencies from package.json
require('load-modules').load('foo*');

// Resolve filepaths to all devDependencies
require('load-modules').loadDev('bar-*');

// Resolve filepaths to both dependencies and devDependencies
require('load-modules').loadAll('*-baz'));

// Resolve the path to a specific module
require('load-modules').filepath('module-to-resolve');

More examples →

Lo-dash templates

First, mixin this module's methods so they can be used in Lo-Dash templates:

module.exports = function (grunt) {
  // start by adding this line of JavaScript to your Gruntfile
  grunt.util._.mixin(require('load-modules'));

  grunt.initConfig({...});
  grunt.registerTask(...);
};

with the mixins defined, you can use them in templates like this:

grunt.initConfig({
  less: {
    src: ['<%= _.load("normalize.css") %>', '<%= foo.bar %>', 'theme.less'],
    dest: 'dist/'
  }
});

Any specified template strings (<%= %>) will be processed when config data is retrieved.

More examples →

Usage

// Resolve filepaths for dependencies
load(pattern, config)
// Resolve filepaths for devDependencies
loadDev(pattern, config)
// Resolve filepaths for all dependencies
loadAll(pattern, config)
// Resolve filepath for a specific module
filepath(pattern, config)

Contributing

In lieu of a formal styleguide, take care to maintain the existing coding style. Add unit tests for any new or changed functionality.

Related projects

Author

Jon Schlinkert

Release History

  • 2013-09-07 v0.1.0 First commit.

License

Copyright (c) 2013 Jon Schlinkert, contributors. Licensed under the MIT license.