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 🙏

© 2024 – Pkg Stats / Ryan Hefner

moddy

v0.3.1

Published

a elegant way for searching modules(not just node module)

Downloads

23

Readme

moddy

a elegant way for searching modules(not just node module)

Conceptly, module and package are the same thing.

Install

$ npm install moddy

Quick start

  var Moddy = requrie('moddy');
  var options = {
    searchPaths: ['.']
  };
  Moddy(options, function(err, mods) {
    if (err) throw err;
    console.log(mods);
    /*
    [{
      name: 'modA',
      version: '1.0.0',
      path: '/application/modules/modA',
      deps: [{
        name: 'modB',
        version: '2.0.0',
        path: '/application/modules/modA/node_modules/modB'
        deps: [],
        ...
      }],
      ...
    }, ...]
    */
  });

API

Moddy([options,] callback)

options

optional

  • options.searchPaths

{Array} specify search path to find node modules, default to process.cwd()

  • options.rules

{Object} Each key-value pair stands for a certain rule for field validation of module's package.json. e.g. { name: 'koa' } matches module with a name koa which as we all know and { name: /^koa-.*/ } matches all the modules that have a name prefixed with koa- and { name: function(val) { return val !== 'koa'} } matches any module whose name is not koa(in this case, param val is the value of that field in package.json). So value can be RegExp, function or any primative value.

  • options.packageDir

{String} Directory that modules locate. Default to node_modules. If you want to search bower components, set it to bower_components.

  • options.packageFile

{String} Package file. Defaults to package.json.

  • options.scopeDir

{String} Scope of module. A module's name may be prefixed with a scope name. e.g. a module named with xxx/yy has scope xxx and it locates at node_modules/xxx/yy when installed. Defaults to ''.

callback

node-style callback that takes in two params: err, mods.

mods is a collection of modules. Each module includes all the fields of its package.json and with extra path, deps fields.path is the absolute path of the module and deps is a collection of modules that it depends on.

LISENCE

MIT