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

require-hapi-plugin-dir

v1.0.0

Published

A simple method of requiring all files in a directory, but specifically for hapi plugins that don't require an `options` object.

Downloads

19

Readme

require-hapi-plugin-dir

Build Status

A simple method of requiring all files in a directory, but specifically for hapi plugins that don't require options.

Use:

Directory Structure

MyPlugins/
    |- index.js
    |- myplugin1.js
    |- myplugin2.js
    |- myplugin3.js

index.js

module.exports = require('require-hapi-plugin-dir')(module);

This package simply exports each plugin in a flat array. Given the example directory structure above, this array would be equivalent to:

module.exports = [
    require('./myplugin1'),
    require('./myplugin2'),
    require('./myplugin3')
];

See the "load multiple plugins" example under Loading a Plugin for more info.


Alternate directory structure

MyPlugins/
    |- index.js
    |- myplugin1.js
    |- myplugin2.js
    |- myplugin3.js
    |- MyOtherPlugins/
        |- index.js
        |- mypluginA.js
        |- mypluginB.js
        |- mypluginC.js

Which would present as:

module.exports = [
    require('./mypluginA'),
    require('./mypluginB'),
    require('./mypluginC'),
    require('./myplugin1'),
    require('./myplugin2'),
    require('./myplugin3')
];

API

reqHapiPluginDir(module[, options]);

module

Node's module object contains a property named filename, thus it is important to pass this object from the index.js file which is being called.

options

optional options (haha!) object.

  • include - An array of hapi plugins to include manually.
  • flat - If set to true, the above directory structure would only include files from MyPlugins and completely ignore the MyOtherPlugins directory. Default: false.