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

make-index

v0.0.4

Published

Make an index that exports modules from subfolders

Downloads

3

Readme

make-index

Create an index file containing exports for modules in sub folders.

Why?

This is useful in React when you have a lot of components split in to types and you want to make them all available from a single import.

## Example

Given a folder structure:

 src
   - components
     - AComponent
       - index.js
     - AnotherComponent
       - index.js

Running make-index --d src/components, will create a file at src/components/index.js with the contents:

// DO NOT EDIT - this file was generated by [make-index](https://github.com/penx/make-index)
export AComponent from './AComponent';
export AnotherComponent from './AnotherComponent';

Assumptions

Usage assumes leaf folders are uniquely named throughout the tree (e.g. AComponent and AnotherComponent component in the example above).

CLI

Usage: make-index [options]

  -d, --directory <directory>  The source directory to index, relative to the current working directory.
  -s, --source <source>        Glob for finding modules in the given directory.
                               (default: **/index.js)
  -t, --target <target>        The file to write to, relative to <source>.
                               (default: index.js)
  -h, --header <header>        String to prepend to top of generated file.
                               (default: // DO NOT EDIT - this file was generated by [make-index](https://github.com/penx/make-index))
  -l --line <line>             String template for each line, following sprintf format
                               (default: export %1$s from './%2$s';)
  -h, --help                   output usage information