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 🙏

© 2026 – Pkg Stats / Ryan Hefner

apidoc2dts

v1.1.2

Published

APIDOC to Typescript Definition file convertor

Downloads

45

Readme

apidoc2dts

APIDOC to Typescript Definition file convertor.

Installing

npm install apidoc2dts

Usage

Generate APIDOC and make sure api_data.json, api_project.json exists in PATH_TO_APIDOC folder.

Usage:

./node_modules/.bin/apidoc2dts PATH_TO_APIDOC > TARGET_FOLDER/index.d.ts

How to use generated types:

import { YourApidocGroupNamespace } from 'YOUR_PACKAGE_NAME-types';

Where YOUR_PACKAGE_NAME come from apidoc.json name field, YourApidocGroupNamespace come from @apiGroup tags.

You can optionally use tsfmt to format typescript definition file using your project style guide:

./node_modules/.bin/apidoc2dts PATH_TO_APIDOC/ | ./node_modules/.bin/tsfmt --stdin > TARGET_FOLDER/index.d.ts

Limitations

Typescript interfaces generated only for:

  • Parameter @apiParam group (this is default group)
  • One @apiSuccess group, Success 200 (this is default group) or any other first defined

Example

Example APIDOC:

  /**
   * @api {POST} /token Create authentication token for user
   * @apiName Create
   * @apiGroup AdminUser.Token
   *
   * @apiParam {Object} token
   * @apiParam {Number} .userId
   *
   * @apiSuccess (201) {String} Location HTTP header with url for created resource
   * @apiSuccess (201) {Object} token
   * @apiSuccess (201) {String} token.id
   */

  /**
   * @api {GET} /token/:id Get token
   * @apiName Get
   * @apiGroup AdminUser.Token
   *
   * @apiParam (Route params) {String} id
   *
   * @apiSuccess {Object} token
   * @apiSuccess {String} .id
   * @apiSuccess {Number} .userId
   */

apidoc2dts will generate:

declare module 'apidoc2dts-test-types' {

  namespace AdminUser.Token {

    interface CreateParams {
      token: CreateParams_Token;
    }

    interface CreateParams_Token {
      userId: number;
    }

    interface Get {
      token: Get_Token;
    }

    interface Get_Token {
      id: string;
      userId: number;
    }

  }

}