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

re-exp

v1.2.8

Published

Creates an index file (.js, .ts, .jsx, .tsx) in a directory and re-exports variables from modules within that directory.

Downloads

1,054

Readme

re-exp

npm

Overview

re-exp is a command-line tool designed to simplify the project structuring process by automatically creating index files that re-export variables and functions from modules within a directory. This is particularly useful for JavaScript and TypeScript projects where maintaining clean and organized exports is crucial. The tool supports different file extensions including .js, .ts, .jsx, and .tsx, making it versatile enough for a variety of frontend and backend development setups.

Features

  • Automatic Index Creation: Seamlessly generate an index file for your modules.
  • Re-Export All: Automatically re-export all named exports from files in a directory.
  • Flexible Configuration: Specify directory and file extensions through command-line arguments.
  • Extensive Support for File Types: Works with JavaScript and TypeScript files including JS, TS, JSX, and TSX extensions.
  • Silent Mode: Option to run the tool quietly without console output.

Installation

To install re-exp, you'll need Node.js installed on your system. It is recommended to install re-exp globally to have easy access via command line:

npm install -g re-exp

Usage

To use re-exp, simply navigate to the directory for which you want to create an index file and execute the command:

re-exp -d [directory_path] -e [extension]

Options

  • -d, --dir: Required. Specifies the directory to process.
  • -e, --ext: Required. Specifies the file extension to consider (e.g., js, ts, jsx, tsx).
  • -q, --quiet: Runs the command in quiet mode with no console output.

Example

Suppose you have a directory src/components with various .tsx files. To create an index file with re-exports, you would run:

re-exp --dir ./src/components --ext tsx

If you prefer less verbose output, you can add the silent option:

re-exp --dir ./src/components --ext tsx --quiet

Contributing

Feel free to contribute to this project by opening issues or submitting pull requests via GitHub.

License

This project is licensed under the MIT License - see the LICENSE file for details.

Support

For any inquiries or issues, please contact the author Max Shane at [email protected]. Alternatively, you can open issues on the GitHub Issues page.