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

rcli

v0.0.11

Published

Command-line utility for working with React applications

Downloads

10

Readme

React Command Line rcli

rcli is a utility to help quickly scaffold out new, production-grade applications and provide generators for rapid application development.

npm install -g rcli

Overview

Usage: rcli [options] [command]

Commands:

  generate <item>
  new <appName>

Options:

  -h, --help                       output usage information
  -V, --version                    output the version number
  -d, --directory [directory]      The output directory where the item will be placed into.
  -c, --component [componentName]  The name of the component.
  -f, --folder [folder]            Should this component have it's own folder.
  -s, --stateless [stateless]      Specify whether this is a stateless component or not.
  --include-test                   Include a test when creating a component
  -t, --test [testFramework]       Choose a test framework to include in your build.
  -l, --linter [linter]            Choose a linter to include in your build.

Scaffolding new applications

You can quickly scaffold a new application by running:

$ rcli new appName

This will create a folder called applicationName that contains a base project that will allow you to run a development server that includes useful features like Hot-Module Replacement. It also provides a base production-grade implementation that includes support for Server-side Rendering, basic Express Security, and asset fingerprinting.

You can use both features by running the following commands in the application root folder:

# Start the development server with HMR support
$ npm run start:dev

# Build out the application assets, fingerprinting support including
$ npm run build

# Start the production application, includes SSR
$ npm run start:prod

Scaffold options

You can pass in a variety of options while generating a new application. As of right now, rcli supports two flags, --test and --linter and has implementations for the jest testing framework as well as eslint.

To include them when building out your application, just do the following:

$ rcli new appName -t jest -l eslint

And the project will now have jest and eslint support for testing and linting, respectively.

Generators

rcli has support for easy component generation by running the following command:

$ rcli generate component -c ComponentName

By default, this will generate components and put them in your application's src/cmoponents folder. If you want to change that, just use the -d, --directory flag:

$ rcli generate component -c ComponentName -d some/other/directory

You can also specify whether the generated component should be a stateless component with the -s, --stateless flag:

$ rcli generate component -c ComponentName -s

In addition, you can scaffold out a component folder with an included CSS file for working with CSS Modules by using the -f, --folder flag:

$ rcli generate component -c ComponentName -f

Finally, you can choose to include a test for your component in the directory's __tests__ folder by using the --include-test flag:

$ rcli generate component -c ComponentName -t