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

write-index

v1.1.1

Published

A utility to help build index files in directories that imports and exports sibling files in ES6 format

Downloads

7

Readme

write-index

npm Downloads

write-index creates and writes index.js files in specified directories that imports and exports sibling files in ES6 format.

Examples


Directory with sibling files

utils-/
    - bar.js
    - foo.js

Run command idx-compose (with no arguments)

Finds or creates index.js, then outputs the file exports as such

utils-/
    - bar.js
    - foo.js
    - index.js (newly created)

/* utils/index.js contents */
export { default as bar } from './bar.js';
export { default as foo } from './foo.js';

When you need to import from another directory

In this example we want to import all files from our utils into the root index.js

-/ (project root)
    - index.js
    - utils-/
        - bar.js
        - foo.js

Run command idx-compose fromDir toDir

In this case idx-compose ./utils/ ./

Updates this index.js file with

/* ./index.js contents */
export { default as baz } from './utils/baz.js';
export { default as barf } from './utils/barf.js';

Usage


Installation

npm install write-index

Cli options

Usage: idx-compose [options] [importFrom] [pathToIndex]

Example: idx-compose -e whatever.js ./utils ./

Creates index.js from sibling files or directory specified

Options:
  -v, --version           output the current version

  -c, --config            use config file arguments
                          - ignores cli arguments in favor of an .idxrc file

  -e, --entryFile <name>  specify entry file name
                          - default: "index.js"

  -h, --help              output usage information

Changing the entryFile


By default we create or update index.js, but you can override this behavior with the -e or --entryFile options
using the command idx-compose -e <name>.js

Config file


This allows you to specifiy multiple directories to update using
idx-compose -c or idx-compose --config

Create an .idxrc file in the root of your project

Note: This ignores any other arguments coming from the cli

Arguments

  • dirs: An array of specified directories to update on command
    • pathToIndex - where to create and/or update the index.js files
    • importFrom - the directory location we want to import files from
  • entryFile: name to call the entryFile if you want to override index.js

Example .idxrc file

{
    "dirs": [
        {
            "pathToIndex": "./",
            "importFrom": "./utils"
        },
        {
            "pathToIndex": "./utils",
            "importFrom": "./utils"
        }
    ],
    "entryFile": "index.js"
}

Dependencies