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

wilster-doc

v1.0.4

Published

Creates simple documentation for ReactJS components

Readme

wilster-doc

Are you also troubled with generating documentation? Wilster-doc is a tiny library that reads your ReactJS annotations using react-docgen and react-docgen-markdown-renderer and generates a simple documentation in markdown. It's not a 100 % solution for documentation, but it does remove the need to read the code.

All you need to do, is provide a (1) path to a folder and (2) documentation output path.

Installation

npm install -g wilster-doc

Usage

wilster-doc run -f PATH_TO_FOLDER_WITH_COMPONENTS -o OUTPUT_FILE

CLI params

-f   (--folder) Path to component folder

-o   (--output) Path for the output file (the documentation)

-t   (--template) In you want to use a custom template file.

Examples

See examples folder documentation.md

Output

Annotation | Description ---- | -------- @componentName | Used to label the component. Documentation is sorted by this name. If none is provided, the component's own name is used. @description | The description of the component. @yourVariable | You can use your own variables; but does require a custom template.

NOTE: If you want to extract custom annotations e.g. @tag, @category, @version they are already accessable. Simply use a custom template in the command -t MY_TEMPLATE and access them in the template using description.tag description.category, description.version.

/**
 * @componentName MyLib.Button
 * @description This is a button. Super nice component.
 */
export class FancyButton extends React.Component {
  render() {
    return <div />
  }
}

FancyButton.defaultProps = {
  type: 'default'
}

FancyButton.propTypes = {
  /**
   * One of basic types of buttons you can display.
   */
  type: PropTypes.oneOf(['default', 'primary']).isRequired()
}

Result

See examples folder documentation.md

Create a custom template

You can overwrite the default template by providing a template file -t PATH_TO_TEMPLATE to the command e.g. wilster-doc run -f ./src -o ./documentation.md -t ./myTemplate.tmp.

Default template You can find the default template here