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

index-finger

v1.1.0

Published

create indexes for your modules

Downloads

31

Readme

#index-finger

create indexes for your modules

Build Status Dependency Status devDependency Status

##who is this for?

Do you ever find yourself creating modules where the index has almost no content aside from exporting all of the other modules in the folder? If so this tool is for you! index-finger will parse across your module and generate index files for you in each of your folders.

WARNING index-finger will overwrite ANY index files you have in your project. If you are not using version control you could end up a very very sad panda WARNING

##example

Lets say you have a project that looks something like this

.
├── a.js
├── b.js
├── c.js

index-finger will parse through the above provided folder and generate an index.js that looks like this

module.exports = {
  a: require('./a'),
  b: require('./b'),
  c: require('./c')
};

##install

with npm do:

npm install -g index-finger

##usage

index-finger [path to entry] {OPTIONS}

Standard Options:

-o Directory to write to other than source directory -h Show this message

##methods

index-finger can also be used programatically

var indexFinger = require('index-finger');

###indexFinger(src, output (optional), cb)

where src is the src folder to parse, ourput is an optional directory to output to, and cb(err) is a callback function called once the files are done being written.

If ouput is provided index-finger will copy the entire project to the output directory prior to parsing.

##license

MPL V2