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

doc-tree

v0.14.0

Published

Documentation generating tool for JavaScript that matches comments to AST nodes.

Downloads

25

Readme

doc-tree

Build Status npm Version License

doc-tree parses comments in JavaScript code and outputs the structure and context of the comments in any particular format, JSDoc is the default but any documentation parsing function can be supplied. It traverses the Abstract Syntax Tree (AST) to determine the context of a comment. Basically it's glue code between the AST parser Acorn, and the JSDoc parser Doctrine, though any user-supplied parsing function may be used.

Get it from npm:

$ npm install -g doc-tree

Usage

doc-tree operates over stdio. Running doc-tree on its own source code, and outputting the result to docs.json:

$ doc-tree < lib/index.js > docs.json

Or you could use it programmatically, as part of a Node-based build script:

import fs from 'fs'
import docTree from 'doc-tree'

// Parse a string or a buffer.
let doc = docTree.parse(fs.readFileSync('example.js'))

// An array of parsed comments matched with their contexts.
let output = doc.output()

The output method accepts 2 arguments, a function that accepts a comment and returns anything, and an options object to pass to the custom function or the built-in parser, Doctrine.

Example

This code documentation:

/**
 * This is a **Foo** class.
 */
class Foo {
    /**
     * This is the constructor.
     *
     * @param {Object} options
     */
    constructor (options) { ... }
}

Gets outputted as:

[{ comment: { description: '<p>This is a <strong>Foo</strong> class.</p>', tags: [] },
   context: { location: { start: [Object], end: [Object] },
              name: 'Foo', type: 'class' }
 },
 { comment: { description: '<p>This is the constructor.</p>', tags: [Object] },
   context: { location: { start: [Object], end: [Object] },
              type: 'constructor', target: 'Foo' }
}]

Descriptions are rendered into HTML using CommonMark. Use { render: false } in the options for output to turn it off.

The default JSDoc parser will only consider block comments that start with /**.

License

This software is licensed under the GNU General Public License v3.