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

jsdocp

v1.3.0

Published

Simplified JSDoc publishing using git

Downloads

13

Readme

jsdocp

npm version Build Status Dependency Status Dev Dependency Status

The links to the Tutorials and API docs below are examples of what can be generated by jsdocp:

Generated jsdoc/jsdocp pages

JSDoc publishing

jsdocp is a jsdoc/git publishing agent that generates versioned documentation, CHANGELOGs, auto-deployment to a documentation hosting service (e.g. gh-pages, etc.) and much more!

With jsdocp any number of jsdoc templates can be used for a personalized experience without the added complexities of setting up your own template extension.

Features:

Page customizations:  

  • Use virtually any JSDoc supported template- adds a responsive navigation bar to the doc pages that contains icons/links to the npm module (optional), CHANGELOG (optional), source code (optional) and doc version selection
  • Branded documentation using your own logo
  • Add your own CSS, JavaScript and meta to the documentation pages without altering the chosen template

Versioned documentation:  

  • Each time docs are tagged/deployed to GitHub or any other git supported documentation hosting service, the old docs are archived in a versioned directory
  • versions.json generation for real-time version selections in previously deployed docs (no more wiping out old docs, and old docs auto-reference an updated set of versions!)
  • Tag filtering option to restrict doc generation for tagged versions that are released for major or minor versions rather than every version that is tagged

CHANGELOG generation:  

  • Each time docs are tagged/deployed a CHANGELOG.md as well as a markdown parsed CHANGELOG.html are generated (optional)
  • Customizable CHANGELOG header and lines using markdown, git formatting (e.g. %h, etc.) and package/publishing parameter substitutions using Template Literal syntax
  • Customizable grep regular expressions for determining which commit messages will appear in the logs (including support for sub-sectioning into Breaking Changes, Features, Fixes and Merges/Pull Requests)

Documentation deployment:  

  • Page deployment execution via Node.js cli from the command line or via the provided API
  • Easy integration in continuous integration services like travis-ci, etc.

Markdown extensions:  

  • Include preprocessed source files into any of your tutorial pages. For example, if we have path/to/my/project/file.js that we want to include in a tutorial page that contains:
function sum(a, b, c) {
  return a + b + c;
}

And the following markdown is added to the page:

The published docs will contain:

>> Check out the Tutorials to get started (also generated by jsdocp)