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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@krab7191/react-cli

v1.0.10

Published

A flexible set of command line tools which mimics angular-cli functionality for some common React design patterns.

Readme

react-cli

A flexible set of command line tools which mimics Angular's component generation functionality for some common React design patterns.

NOTE: This package is not finished and should not be installed yet. It does not work.

rc <command> <options> <name>

  • command: ['gc', 'gp', 'help' | '--help' | '-h', 'config', 'version' | '--version' | '-v' ]

    • gc : Generate a component following command line options and falling back to defaults
    • gp : Generate a page component following command line arguments, and falling back to defaults
    • help: Print this help documentation
    • config: Answer a set of questions in order to generate a custom config file for your specific workflow
    • version: Print the installed version of React-cli
  • options:

    • -o : Specifies directory to write to. Default: ./src/components | ./src/pages respectively
    • -s : Specify the suffix to use for files. Default: 'jsx'
    • -t : Specify the componentType (class | functional)
    • -e : Specify the exportType: Default:
      // index.js
      export { default } from './Component';
      Wildcard: (more useful for named exports, TS)
      // index.js
      export * from './Component';
    • -c : Instructs to containerize the component
    • -n : Instructs to nest component in parent folder, and create the parent if it doesn't exist. Requires parent folder name after component name, for example rc gc -n ImgCard ImgContainer will generate an 'ImgCard' subcomponent of existing (or newly created) 'ImgContainer' component.

Config options:

  • componentDirPath: The relative path from your root to the folder where your components reside

  • pageDirPath: The relative path to the directory where your page components reside. May be called 'routes'; whatever you call the folder which holds your frontend routes.

  • suffix: 'js' | 'jsx' | 'ts' | 'tsx' : The file type you want generated

  • componentType: 'functional' | 'class' : Class components will be stateful by default, and functional components stateless

  • exportType: 'default' | 'wildcard' : Define how your component's index.js exports your component's exports. Default results in export { default } from './<ComponentName>'; and wildcard results in export * from './<ComponentName>'

  • casingFix: true | false : If true, component names will be converted to uppercase if lowercase

  • containerize: true | false : If true, a stateful (container) parent component will be created which renders a stateless (presentational) component child

  • classStateful: Default true. Whether or not to generate state in your class component

  • functionHooks: Default false. Whether or not to generate hook code in your functional component

  • nest: Default false. If true the component will be generated as a child of a newly created parent component (must specify both component names)