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

hsdoc

v0.14.2

Published

Build docs for HubSpot projects using Docco

Downloads

5

Readme

HSDoc

Take a Look

Installation

npm install -g hsdoc

Usage

In the root directory of your project:

hsdoc -a

This will give you a gh-pages branch with your documentation in it, and push it to github. Just run it again whenever you make changes.

Files

HsDoc looks for three things: source files, examples, and an intro.

The source files get ran through Docco, and (by default) spat out into docs/build/source. Use the -s parameter (or source in your .hsdoc file) to control what glob pattern is used to find your files.

The examples should be (by default) in docs/examples. The general structure is:

docs/examples/1-My Awesome Example.md
docs/examples/2-Harder Stuff.md

The numbers are used to preserve an order when showing them in the index page, and are optional.

Your intro is either your README.md, or docs/intro.md. It's used to provide a project summary, and on the project's index page. Your intro will also be used in the forthcoming bestjs style guide.

Index Page

HsDoc builds you an index page at index.html with the full (compiled) content of your intro, and a listing of your source files and examples. If you already have an index page of some sort, you might want to use the --index option to have HsDocs index file placed somewhere else.

Options

See hsdoc --help for options. You can also add a .hsdoc yaml file to the root of your project to provide configuration. See hapijs for an example.