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

ts-quick-docs

v0.5.3

Published

quick TypeScript documentation extractor

Downloads

10

Readme

ts-quick-docs NPM Circle CI

quick TypeScript documentation extractor

This little tool parses a TypeScript 2.1 project and spits out a big list of documentation objects for each interface and const discovered. That data file can be used to generate human-friendly documentation in any desired format.

Usage

CLI

  1. ts-quick-docs [path/to/file.ts]... > interfaces.json
  2. open interfaces.json

Note: options are not supported from the CLI.

Node API

From TypeScript program:
const ts = require("typescript");
const program = ts.createProgram(files, compilerOptions);

const tsdoc = require("ts-quick-docs");
const documentation = tsdoc(program, { /* options */ });
// documentation is an array of IDocEntry items
fs.writeFileSync("interfaces.json", JSON.stringify(documentation, null, 4));
From set of files:
const tsdoc = require("ts-quick-docs");
const documentation = tsdoc.fromFiles(files, compilerOptions, { /* options */ });
// documentation is an array of IDocEntry items
fs.writeFileSync("interfaces.json", JSON.stringify(documentation, null, 4));

Note that files must be an array but it can contain just the entry file if it imports others. A dummy TS program is created internally so we'll walk that tree for you.

Options

excludeNames: (string | RegExp)[]

Array of patterns that will be matched against each entity's name. Matching entities will be excluded from the output.

excludePaths: (string | RegExp)[]

Array of patterns that will be matched against each file's path. Matching files will be parsed but entities in those files will not appear in the output.

includeDefinitionFiles: boolean = false

Whether to include symbols from .d.ts files in the generated documentation blob. These files are excluded from the output by default because they tend to produce a lot of noise: do you really need every symbol from @types/node.d.ts??

includeBasicTypeProperties: boolean = false

Whether built-in properties for basic types should appear in the output (such as String.prototype.toString). Basic types include boolean, number, string, arrays of those three, string literals, and numeric literlas. Defaults to false because these properties tend to pollute output for no benefit.