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

discoverable

v1.1.1

Published

discover packages and modules to compose your applications

Downloads

8

Readme

Discoverable

Discover packages and modules to compose your applications.

Packages declare what types they provide and what modules implement those types in their package.json files.

Applications declare what packages to scan for discoverable modules in their package.json files.

It's a layer of indirection between your code and your dependencies. Use discover('foo') in your code and configure what specific modules implement "foo" in your package.json.

Install

npm i -S discoverable

Usage

var discover = require('discoverable');

discover('things').then(function(things) {
  // use things here
});

// or

discover('things', function(err, things) {
  // use things here
});

Configuration

Packages

A package is discoverable if it has something like this in its package.json:

  "discoverable": {
    "modules": {
      "things": "lib/things/*.js",
      "otherThings": "lib/other/*-thing.js"
    }
  }

To be more selective, do this:

  "discoverable": {
    "modules": {
      "things": [
        "lib/thing1.js",
        "lib/thing2.js"
      ],
      "otherThings": "lib/other/other-thing.js"
    }
  }

There are no requirements on what modules must export, but they should be polymorphic for any given type.

Applications

If the packages you need are public and discoverable, install them with npm and put this in your package.json:

  "discoverable": {
    "packages": "node_modules/*"
  }

If you want to be more selective, do this:

  "discoverable": {
    "packages": [
      "node_modules/foo",
      "node_modules/bar"
    ]
  }

If the packages you want to discover aren't discoverable (or not even proper packages), do this:

  "discoverable": {
    "packages": {
      "lib/*": {
        "modules": {
          "things": "lib/things/*.js"
        }
      }
    }
  }

You can be as selective as you want.

API

The default export is a function:

var discover = require('discoverable');

discover

Discovers and requires modules of the given type.

Arguments:

  • type - String
  • callback - function(err, modules) (optional)

Returns:

  • Promise for Array of the modules' exports

discover.modules

Discovers modules of a given type without require'ing them.

Arguments:

  • type - String
  • callback - function(err, modules) (optional)

Returns:

  • Promise for Array of modules objects that look like this:
{
    type: 'type',
    package: 'name', // from "name" in package.json or directory name
    filename: '/path/to/module.js',
    name: 'module', // from filename
    exports: null, // might be defined if previously required
    require: function() {
      // requires the module, later returns cached exports
    }
}