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-jsduck

v1.0.1

Published

Compile JSDuck documentation.

Downloads

1,033

Readme

grunt-jsduck NPM version

Grunt task to compile JSDuck documentation

Getting Started

Installation

WARNING! Starting from version 1.0.0, the task is incompatible with Grunt 0.3. Use the legacy 0.1.x version you still use Grunt 0.3.

You need to have Ruby and JSDuck installed. Refer to project homepage for installation instructions.

Install this grunt plugin next to your project's grunt.js gruntfile with: npm install grunt-jsduck

Then add this line to your project's grunt.js gruntfile:

grunt.loadNpmTasks('grunt-jsduck');

Configuration

Inside your grunt.js file add a section named jsduck. Read the JSDuck Guide for an overview of its features.

src

Input paths containing JavaScript code to document. You can use wildcards here (see example below).

dest

Output directory for generated documentation.

options

Additional options that will be passed to jsduck. Run jsduck --help for a full list.

Example configuration

jsduck: {
    main: {
        // source paths with your code
        src: [
            'ext-4.1.1/src',
            'project1/js',
            'project2/**/*.js'  // globbing supported!
        ],

        // docs output dir
        dest: 'docs',

        // extra options
        options: {
            'builtin-classes': true,
            'warnings': ['-no_doc', '-dup_member', '-link_ambiguous'],
            'external': ['XMLHttpRequest']
        }
    }
}

Running

Running the jsduck multitask without additional parameters will execute it with all specified targets:

grunt jsduck

Running

grunt jsduck:main

will execute the task with main target.

Sometimes it's useful to override the output directory at compile time. You can pass it as a second argument like this:

grunt jsduck:main:/var/www/my-awesome-project/docs

Contributing

Please follow the existing coding style. Respect the .editorconfig and .jshintrc files.

License

Copyright (c) 2012-2013 Dmitry Pashkevich, contributors. Licensed under the MIT license.