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

jsdoc-aerogear

v3.2.0-dev

Published

An API documentation generator for JavaScript. This a forked and modified version specific to the AeroGear Project

Downloads

5

Readme

JSDoc 3

Build Status

An inline API documentation processor for JavaScript. JSDoc 3 is intended to be an upgrade to JsDoc Toolkit (JSDoc 2).

Want to contribute to JSDoc? Please read CONTRIBUTING.md.

Installation

Use git to clone the official JSDoc repository:

git clone https://github.com/jsdoc3/jsdoc.git

Alternatively, you can download a .zip file for the latest development version or a previous release.

You can also install JSDoc within a Node.js project's node_modules directory using npm. To install the latest development version, change directories to your Node.js project, then run the following command:

npm install git://github.com/jsdoc3/jsdoc.git

Or to install JSDoc globally:

npm install -g git://github.com/jsdoc3/jsdoc.git

Note: Although you can install JSDoc with npm, JSDoc does not currently run on Node.js.

Usage

This example assumes that your working directory is the JSDoc application base directory:

./jsdoc yourSourceCodeFile.js

For information about the supported command-line options, use the --help option.

./jsdoc --help

Generated documentation will appear in the folder specified by the --destination option, or in a folder named "out" by default.

Dependencies

JSDoc 3 uses the Mozilla Rhino engine, which requires Java. JSDoc 3 is known to work with version 1.6.0_24 of Java.

JSDoc 3 uses advanced features in Mozilla Rhino that are only available in or after version 1.7R3. In addition, JSDoc 3 requires several customizations to the standard Rhino distribution. The customized version of Rhino is included with JSDoc.

In rare cases, users may have their Java CLASSPATH configured to override the included Rhino and point to an older version of Rhino instead. If this is the case, simply correct the CLASSPATH to remove the older Rhino. (On OS X, you may need to remove the file ~/Library/Java/Extensions/js.jar.)

The version of Rhino distributed with JSDoc 3 can be found here: https://github.com/hegemonic/rhino

Debugging

Rhino is not always very friendly when it comes to reporting errors in JavaScript. Luckily, it comes with a full-on debugger included that can be much more useful than a simple stack trace. To invoke JSDoc with the debugger, run the following command on Windows:

jsdoc --debug

Or on OS X, Linux, and other POSIX-compliant systems:

./jsdoc --debug

If you can't get the short-form commands to work, try invoking Java directly:

java -cp lib/js.jar org.mozilla.javascript.tools.debugger.Main \
-debug -modules node_modules -modules rhino -modules lib -modules . \
jsdoc.js your/script.js

Note: --debug must be the first argument to the short-form command.

This will open a debugging window. Click Debug > Break on Exceptions, then click Run. If there is an error, you should see exactly where it is in the source code.

See Also

Project Documentation: http://usejsdoc.org/ (under development)
Project Documentation Source: https://github.com/jsdoc3/jsdoc3.github.com
JSDoc User's Group: http://groups.google.com/group/jsdoc-users
JSDoc 3 Ant Task: https://github.com/jannon/jsdoc3-ant-task
Project Announcements: http://twitter.com/jsdoc3

License

JSDoc 3 is copyright (c) 2011-2012 Michael Mathews [email protected].

JSDoc 3 is free software, licensed under the Apache License, Version 2.0. See the file LICENSE.md in this distribution for more details.