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

@iobxt/objectifiler

v1.1.2

Published

A handy exporter module which aims to alevate dev effort

Readme

@iobxt/objectifiler

A handy exporter module which aims to alevate dev effort.

Installation

npm i @iobxt/objectifiler

Usage

Once the package has been installed you can drop it into an index.js file like so;

const objectifiler = require("@iobxt/objectifiler");

module.exports = objectifiler(__dirname);

When the index.js file is consumed, all the files and directories will be exported as an object.

Description

Disclaimer: This was a quick braindump.

This thing iterates over files in the provided directiory and exports them as an object. You may also provide a configuration object which will be used to configure each module, provided the module has an init function.

You can use this exporter one of two ways.

drop it into your index file and it will try to export the modules in the directory provided.

if your modules need to be initialised it will call the init function of each, passing in the config you have provided. It will try to match up an object in the config with the name of the file. You can also export the module with a name variable if you want the two to be different. if you dont want to initialise each module, you can just drop it in and it will export an object with all your files.

Usage

Given the following directory sructure;

src
  without
    foobar
      foo.js
    bar.js
  foo.js
index.js

and the top level index.js looks like this;

const objectifier = require("objectifier");

module.exports = objectifier(__dirname);

Upon importing src like this;

const foo = require("./src");

You should have an object that looks like this;

{
  without: {
    foobar: {
      foo: () => {}
    },
    bar: () => {}
  },
  foo: () => {}
}