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

dirreq

v0.1.4

Published

Node.js require directory module

Downloads

11

Readme

Node.js require directory module

Installation

npm install dirreq

Usage

var dirreq = require('dirreq');
var requiredObject = dirreq(relativePath, options);

Options

{
  debug: Boolean, default false
  defer: Boolean, default true
  extensions: Array, default Object.keys(require.extensions)
  onlyFiles: Boolean, default true
  recursive: Boolean, default false
  requireFunction: Function, default require
  stripExtension: Boolean, default true
}
  • debug: if set to true, will output debug information to stdout about skipped files and directories
  • defer: if set to true, will call the require function only when accessed via requiredDirectory.field
  • extensions: accepted file extensions. By default, .js, .json and .node are accepted
  • onlyFiles: if set to true and recursive option is not set, will skip directories (i.e. not call the require function on anything that doesn't comply to fs.statSync(path).isFile())
  • recursive: if set to true, will also require directories inside the given base directory
  • requireFunction: if set, will call this function instead of the default require()
  • stripExtension: if set to true, will remove extension in the field name in the returned object

Example

test
|
+-+ test
  |
  +- nested.js
+- test1.js
+- test2.js
+- test3.txt

Default

var dirreq = require('dirreq');
var dirs = dirreq('./test');

console.log(dirs);
/*
{ test: { nested: { nested: [Function] } },
  test1: [Function],
  test2: {} }
*/

Defer and no recursion

var dirreq = require('dirreq');
var dirs = dirreq('./test', {
    defer: true,
    recursive: false,
});

console.log(dirs);
/*
{ test1: [Getter], test2: [Getter] }
*/

Concerns

When loading files recursively (options.recurse set to true), the original directory structure will be kept.