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

react-docgen-readme

v0.0.1

Published

CLI tool that extracts information from React Components using react-docgen, transforms that information into Markdown and adds it to your README file.

Downloads

9

Readme

react-docgen-readme

CLI tool that extracts information from React Components using react-docgen, transforms that information into Markdown and adds it to your README file.

Install

$ npm install --save-dev react-docgen-readme

Usage

$ rdr <componentsDir> [options]
// `rdr` is a shortcut for `react-docgen-readme`
  1. Add the delimiter in your README file to indicate where you want to insert the docs

    <!-- react-component-docs -->
  2. Then add a new task in your package.json to generate the docs. Note that you must specify the path for the readme and for the components to be documented.

    "scripts": {
        "docs": "rdr src/ --readmeFile docs/README.md"
    }

Configuration

--readmeFile

Default: './README.md'

The path to the readme file where generated documentation is appended.

--template

Default: 'react-docgen/readme/src/template.md'

The path to the template used for generating the markdown documentation.

--delimiter

Default: 'react-components-docs'

Use a custom delimiter. Used to let the tool know where to place the docs in your readme.

This generates <!-- react-components-docs --> and <!-- react-components-docs:end --> delimiters.

--ext

Default: ['.js', '.jsx']

File extensions to consider. Used by react-docgen.

--ignoreDir

Default: ['node_modules', 'bower_components']

Folders to ignore. Used by react-docgen.

Running the project locally

Clone the project and from the root of the repo run the following commands:

$ npm install
$ npm link
$ cd example/
$ npm link react-docgen-readme

Then, from example/ you can run npm run docs and see the magic happen.

Debugging

With iron-node

$ iron-node bin/cli.js components/ --readmeFile ./README.md

With node-inspector

$ node-debug bin/cli.js components/ --readmeFile ./README.md

License

Distributed under the MIT license.

TO-DO