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

grunt-vdoc

v0.3.5

Published

A grunt plugin that compiles inline documentation into html files

Downloads

3

Readme

grunt-vdoc

Getting Started

This plugin requires Grunt ~0.4.5

If you haven't used Grunt before, be sure to check out the Getting Started guide, as it explains how to create a Gruntfile as well as install and use Grunt plugins. Once you're familiar with that process, you may install this plugin with this command:

npm install grunt-vdoc --save-dev

Once the plugin has been installed, it may be enabled inside your Gruntfile with this line of JavaScript:

grunt.loadNpmTasks('grunt-vdoc');

The "vdoc" task

Overview

In your project's Gruntfile, add a section named vdoc to the data object passed into grunt.initConfig().

grunt.initConfig({
  vdoc: {
    compile: {
      options: {
        meta: {
          name: "myProject",
          version: "0.0.0",
          github: "https://github.com/user/myProject"
        },
        dest: "./docs/build/",
        source: "./src/build/lib.js",
        content: "./docs/content/data.json",
        templates: "./docs/theme/",
        partials: "./docs/theme/partials/",
        assets: "./docs/theme/assets/"
      }
    }
  },
});

Options

Specify directories
  • templates where are the handlebar templates located?
  • partials where are the partials located? (The sub-templates handlebars use)
  • dest where is the destination of the built documentation? (html files)
  • assets where are the assets located? (css, svg, js, other assets for documentation)
Specify files
  • content where is the documentation content located?
  • source where is the source code to get the documentation content from?
Meta data
  • Add any meta data you want, the meta object is transfered to the documentation content in the json file. Which can then be used with the handlebars.