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

jsd-jekyll

v0.3.0

Published

JSDoc Plugin and Template for making a Github Pages compatable Jekyll Site

Downloads

3

Readme

JSDoc Jekyll

A JSDOC Plugin and Template to generate a GitHub Pages compatible Jekyll Documentation Site from jsdoc comments.

Install

npm install --save-dev jsd-jekyll

Configuration

Add "./node_modules/jsd-jekyll" as a plugin and template in your jsdoc config file.

Example:

{
   "opts": {
      "template": "./node_modules/jsd-jekyll",
      "destination": "./out/",
      "recurse": true
   },
   "plugins": ["./node_modules/jsd-jekyll"]
}

Extra opts

repos { array }

Optionally a link to your source code on GitHub can be added to the documentation. Under opts in the jsdoc config file add:

"opts": {
  "repos" : [{
    "folder": "folderName",
    "name": "user/repo"
  }]
}

Multiple repos can be added to the array to support sub repositories based on the file path of the source code.

includeAll { boolean } default false

This will tag all files processed with @module filename if no @module tag is present.

functionFix { boolean } default false
  • Removes bracket from a function names. @function myFunction() becomes @function myFunction.
  • Tags untagged descriptions added below the @function tag
    /**
     * @function myFunction
     * This is a description in the wrong place.
     */
    Changes to
     /**
      * @function myFunction
      * @description This is a description in the wrong place.
      */
folderCategory { boolean } default false
  • Assigns modules to categories based on the file location /api/main/index.js will be tagged @category api-main

JSDoc

Basic @jsdoc tags should work as documented. Not all currently work with this template, more will be added over time.

Custom Tags

The following custom tags can be added.

@category

A category can be added to a @module comment block to organize modules. Each category will create an index page with the relevant modules linked to the main api index. Modules without a @category tag will display on the api index.

@route

Use @route to document api routes in the following format

/**
/* @route {GET} /api/path description...
*/

Add parameters using the appropriate param tag (@routeparam, @headerparam, @bodyparam, or @queryparam). All follow the @param fromat ({type} name description)

Linking Types

When using a module as a return or parameter type preface the module name with module: Example:

/**
/* @param {module:myMod1} paramName description of the parameter
/* @returns {module:myMod2} description of the return
*/

Jekyll

To run Jekyll locally (requires ruby):

bundle install
bundle exec jekyll serve

Only /_data/jsdoc.json will be overwritten when running jsdoc a second time. Other files can be customized as needed. To reset them, delete and run jsdoc.

Set up GitHub Pages

Credits