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

module-indexgen

v0.41.0

Published

Generates barrel (index.js) files that rollup exports for each module in a directory and re-exports them as a single module.

Downloads

48

Readme

Module Indexgen

Generates barrel (index.js) files that rollup exports for each module in a directory and re-exports them as a single module.

Table of Contents

Install

https://www.npmjs.com/package/module-indexgen
npm install module-indexgen

Not to be confused with indexgen which is similar but deprecated.

Usage

npx indexgen <targetDir> [<targetDir>...] [options]

Options:

--watch: Regenerate on file changes.

--watchDelay: Number of milliseconds to delay before reacting to file changes. Default is 1000.

--type: cjs or esm. Default is cjs.

--fullySpecified: Maintain fully specified import paths as required by esm. Default is true for esm, otherwise false.

--only: Glob pattern to limit included files. Default is *.{cjs,mjs,js,json,jsx}.

--ignore: Paths to ignore. Default is node_modules.

--case: Case to apply to generated keys. Options are camel, pascal, auto, none. Default is auto.

--sortSeparator: Ignores the left side for the purpose of ordering, e.g. 1--b.js and 2--a.js becomes b and a in that order. Default is --.

--reverseDelimiter: Reverses generated keys by comma, e.g. bar,foo becomes fooBar. Default is ,.

Example

Given the following directory structure:

proj/
    src/
        components/
            foo.js
            bar.js

Running indexgen from the proj directory produces:

proj/
    src/
        index.js
        components/
            bar.js
            foo.js
            foo-bar.js
            index.js

Contents of proj/src/components/index.js:

module.exports = {
    bar: require('./bar'),
    foo: require('./foo'),    
    fooBar: require('./foo-bar')
}

Notice the key for foo-bar is camel cased to fooBar.

Contents of proj/src/index.js:

module.exports = {
    components: require('./components')
}

require('./src') produces:

{
    components: {
        foo: (exported value for foo.js),
        bar: (exported value for bar.js),
        fooBar: (exported value for foo-bar.js)
    }
}

Architecture

Can't see the diagram? View it on GitHub
graph TD;
    strategies-->util;
    lib-->strategies;
    lib-->util;
    fsx-->io;
    commands-->fsx;
    commands-->lib;
    commands-->io;