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

grunt-readme-plus

v1.0.4

Published

README.md generator that doesn't suck and requires little effort to use.

Downloads

16

Readme

readme-plus Build Status Code Climate Test Coverage

Join the chat at https://gitter.im/thinkingmedia/grunt-readme-plus

Readme+ uses the contents of the current work folder to generate a README.md file for the project. Most of your time is spent in the source code and this is where you can add notes to be included in the output README.md.

Readme+ searches for @readme markers in the source code comments.

Naming The Sections

Each heading in a readme file is defined by a section of source code comments that use the @readme indicator. The first word after the @readme indicator is the name and default title of the section.

/**
* \@readme Install
*
*  Use `npm` to install the `foobar` module.
*
*  ```shell
*  $ npm install foobar
*  ```
*\/

In the above example a heading labelled Installations will be added under the root section with the markdown text found in the comment.

Changing The Section Title

You can customize the heading used for each section by providing title text after declaring the section.

/**
* \@readme Install Installation Instructions
*
*  Use `npm` to install the `foobar` module.
*
*  ```shell
*  $ npm install foobar
*  ```
*\/

In the above example the default heading Install is replaced with Installation Instructions.

Usage

Run readme on the command line in the working folder where you want to generate a README.md file.

$ cd /home/user/work
$ readme

The default options assume your working folder contains a sub-folder named src that contains the source code for your project.

Usage: readme [options] <path>

Example: readme --source=./www/js /home/mathew/thinkingmedia/readme

Options:
-h, --help       shows this usage message
-v, --version    print version number
-s, --silent     hides copyright message
-d, --debug      show debug message
-t, --trace      write source code references in README.md
--verbose        send README.md output to console
--source         path to source folder (default: ./src)
--trace          write source code references in README.md
--file           name of output file (default: README.md)