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 🙏

© 2025 – Pkg Stats / Ryan Hefner

build-doc

v1.0.7

Published

Build tasks for creating documentation.

Readme

build-doc

This package is currently in BETA

Overview

This is a node package that defines gulp tasks that can be used to generate documentation from code. The jsdoc package is used for generating markdown documentation which can be included in a README.md file.

Guide

To install this package execute the following command in the console from within your project.

npm install --save build-doc

Once the package is installed you will need to create a gulpfile.js file within the root folder of your project if there isn't one already. Within this file you will register the gulp tasks that are defined within this package using the registerTasks function. The following is an example of this.

const doc = require('build-doc');

doc.registerTasks({
 glob: '**/*.[jt]s',
 inputDir: './src/local/',
 templateFile: './doc.md',
 outputDir: './',
 outputFile: 'README.md'
});

Once you have registered the doc tasks you can generate documentation using gulp. To generate documentation simply execute the following console command from within your project.

gulp doc

In addition to executing tasks from the console you can also chain the gulp doc tasks together with other gulp tasks to utilize the documentation functionality however it's needed.

Modules

build-doc (module)

Register gulp tasks used to generate documentation using jsdoc.

Functions

registerTasks(opts) ⇒ void

Register documentation generation tasks.

Parameters:

| Param | Type | Attributes | Description | | --- | --- | --- | --- | | opts | Object | | The configuration options. | | opts.glob | String or Array.<String> | | Glob pattern relative to the inputDir that identifies the files to document. | | opts.inputDir | String | optional | The root directory that contains the files to create documentation for. | | opts.templateFile | String | optional | A path to a file that is used as a template. When provided the template will be written out with the first occurance of the text {{jsdoc}} replaced with the markdown that is generated. | | opts.outputDir | String | optional | The output directory. | | opts.outputFile | String | | The file path relative to outputDir that the documentation is written to. | | opts.tasksPrefix | String | optional | An optional prefix to apply to task names. | | opts.tasksDependencies | Array.<String> | optional | Optional array of tasks names that must be completed before these registered tasks run. |

Returns: void