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

restjsdoc

v0.0.7

Published

Parser for RESTJSDoc

Downloads

9

Readme

Build Status

A parser to read jsdoc-like inline documentation

See the test/sample.js for examples of what the inline docs look like.

Releasing

First setup your github username and a generated access token in environment variables:

GITHUB_USERNAME
GITHUB_PASSWORD

Please don't use your web access password, generate a token.

Then, to release:

* Increment and release patch version upgrade (e.g., `0.0.3` -> `0.0.4`): `grunt release:patch`
* Increment and release minor version upgrade (e.g., `0.1.3` -> `0.2.0`): `grunt release:minor`
* Increment and release major version upgrade (e.g., `2.1.3` -> `3.0.0`): `grunt release:major`

You should never have to touch the versions inside package.json manually, the task increments it for you. Also, make sure your working copy is clean and that: git fetch origin; git diff origin/master while on the master branch has no differences.