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

di-modules

v0.2.2

Published

Simple helper to create module specification objects for di

Downloads

13

Readme

node-di-modules

Simple helper to create module specification objects for node-di. It gives you two methods to add modules to the container. The first one, .add(), is nothing more than just setting modules[moduleName] = [type, module] manually. The reason why I built this is the second method, .addDir(), which dynamically requires all *.js files in the given folder and adds them to the module container, using the file name as the module name and assuming type = 'factory'.

Installation

npm install di-modules

Usage

var di = require('di');
var modules = new (require('di-modules'))();

modules.add('fs', 'value', require('fs'));
// directory paths must be relative to __dirname of the calling file
modules.addDir('./src'); // contains myModule.js and yourModule.js, which must be "factory" modules
modules.addDir('./src2', true); // recursively goes deeper into subdirectories
// add all node_modules entries (in the same directory as the calling file)
modules.addNodeModules();
// add specific modules by name
modules.addNodeModules(['events', 'express', 'async']);

// use di as if you filled the modules container manually
new di.Injector([modules]).invoke(async, fs, events, express, myModule, yourModule) {
  ...
});

Ideas

  • .addDir() could support other module types than 'factory', either by specifying when calling it or by indicating it in the file name

Changelog

  • 0.2.0
    • .addNodeModules()